Bug 1241228

Summary: Can't unlock a locked screen in Mate
Product: [Fedora] Fedora Reporter: Giulio 'juliuxpigface' <juliux.pigface>
Component: mate-screensaverAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED ERRATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 23CC: juliux.pigface, leigh123linux, raveit65.sun, stefano
Target Milestone: ---Keywords: Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-07-22 20:19:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
abrt_backtrace
none
abrt_core_backtrace
none
.xsession-errors
none
mate-screensaver --debug
none
output of killall mate-screensaver none

Description Giulio 'juliuxpigface' 2015-07-08 19:11:50 UTC
Description of problem:
I can't unlock a locked session on mate.

Version-Release number of selected component (if applicable):
mate-screensaver-1.10.1-2.fc23.i686

How reproducible:
Happens everytime I try to reproduce it


Steps to Reproduce:
1. Install 20150704 Nightly Rawhide (Mate i686 spin) inside a qemu-kvm guest
2. Log in as user in a graphical session
3. Press the button 'Lock Screen', from the menu 'System'
4. Type the correct password inside the dialog
5. Press the appropriate button to unlock

Actual results:
The screen remains locked

Expected results:
The screen should be unlocked, since the password is correct.

Additional info:
Is it an issue related to virtualization?

Comment 1 Wolfgang Ulbrich 2015-07-08 19:28:35 UTC
I don't know.
Please use stable releases and not rawhide a month after f22 release.
Sorry, i'm the only mate maintainer in fedora and i don't start to work on rawhide reports before f23 beta :)
I'm not a redhat employee and all i do for mate in fedora is in my free time.

Comment 2 Wolfgang Ulbrich 2015-07-08 20:27:30 UTC
closed because of fake email address

Comment 3 Giulio 'juliuxpigface' 2015-07-08 20:33:56 UTC
Sorry, I didn't understand.

Which email address are you talking about?

Comment 4 leigh scott 2015-07-09 06:49:03 UTC
(In reply to Giulio 'juliuxpigface' from comment #0)

> Additional info:
> Is it an issue related to virtualization?

Run

killall mate-screensaver
mate-screensaver --debug

reproduce the issue and post the terminal error here, you may need to kill the screensaver from another VT to get back in.
Also post .xsession-errors

Comment 5 Giulio 'juliuxpigface' 2015-07-09 18:26:49 UTC
@All: I've just found that abrt catches the issue ("mate-screensaver-dialog killed by SIGSEGV") and so it might provide interesting information. I'm sorry I haven't noticed it before. Here's the link of the retrace: https://retrace.fedoraproject.org/faf/reports/bthash/77b7d2e726e67e7a33746771875f67144b49e454

I'm posting some attachments, but feel free to ask me further.

@Leigh: thank you for your comment, I'll provide the requested bits in a while.

@Wolfgang: I'm just doing release validation testing for Fedora QA. Nobody forces you to fix this bug promptly, because Mate is not a release blocking desktop. But I'd suggest not to close this report, otherwise we'll probably forget about the issue before F23 beta reaches the light.

Comment 6 Giulio 'juliuxpigface' 2015-07-09 18:29:51 UTC
Created attachment 1050392 [details]
abrt_backtrace

Comment 7 Giulio 'juliuxpigface' 2015-07-09 18:31:08 UTC
Created attachment 1050393 [details]
abrt_core_backtrace

Comment 8 Giulio 'juliuxpigface' 2015-07-09 18:32:13 UTC
Created attachment 1050394 [details]
.xsession-errors

Comment 9 Giulio 'juliuxpigface' 2015-07-09 18:33:11 UTC
Created attachment 1050395 [details]
mate-screensaver --debug

Comment 10 Giulio 'juliuxpigface' 2015-07-09 18:33:52 UTC
Created attachment 1050397 [details]
output of killall mate-screensaver

Comment 11 Wolfgang Ulbrich 2015-07-10 13:10:19 UTC
another report for the record, which will never happends if all lowlevel stuff will run fine in f23.

Comment 12 Wolfgang Ulbrich 2015-07-17 13:26:55 UTC
works here out of box with inatallation from nightly build f23 from 2015-07-16 in virtualmanager qemu-kvm :)

Comment 13 Giulio 'juliuxpigface' 2015-07-22 20:19:01 UTC
(In reply to Wolfgang Ulbrich from comment #12)
> works here out of box with inatallation from nightly build f23 from
> 2015-07-16 in virtualmanager qemu-kvm :)

Tested with Fedora 23 20150717 (i686, qemu-kvm).
I confirm that the issue isn't present on that build.