Bug 828952 - with both internal and external monitor enabled, screensaver password dialog isn't displayed
Summary: with both internal and external monitor enabled, screensaver password dialog ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 17
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-06-05 15:40 UTC by Dirk Hohndel
Modified: 2013-08-01 10:11 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-08-01 10:11:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Dirk Hohndel 2012-06-05 15:40:50 UTC
Description of problem:

Sometimes (but not always) when locking the screen and touching the mouse / keyboard in order to type in the password, the dialog flashes up briefly but then the whole screen turns blue. Typing in the password still works and everything seems fine afterwards - but just seeing a plain blue screen and no dialog box is disconcerting.

Version-Release number of selected component (if applicable):

gnome-screensaver-3.4.1-1.fc17.x86_64

How reproducible:

Not reliably. It happens some times when locking the screen with both internal and external monitor enabled on my MacBook Air.

Steps to Reproduce:
1. attach external monitor to laptop, not mirroring 
2. Ctrl-Alt-L to lock screen
3. hit a key to display the login dialog
  
Actual results:

login dialog flashes up briefly and is immediately replaced by a solid blue screen

Expected results:

visible login dialog

Additional info:

I found these two lines in /var/log/messages at about the time this last happened; no idea if they are related...

Jun  5 08:26:35 air dbus-daemon[3372]: dbus[3372]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.3" (uid=0 pid=3312 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.42" (uid=1000 pid=3786 comm="gnome-session ")
Jun  5 08:26:35 air dbus[3372]: [system] Rejected send message, 2 matched rules; type="method_return", sender=":1.3" (uid=0 pid=3312 comm="/usr/lib/systemd/systemd-logind ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.42" (uid=1000 pid=3786 comm="gnome-session ")

Comment 1 karlp 2012-11-08 10:54:34 UTC
Possible duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=749244

Comment 2 Fedora End Of Life 2013-07-04 03:06:44 UTC
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2013-08-01 10:11:36 UTC
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.