Bug 478636
| Summary: | Cannot unlock screen | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adrien Bustany <adrien-xx-redhatbz> | ||||||
| Component: | gnome-screensaver | Assignee: | jmccann | ||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | low | ||||||||
| Version: | rawhide | CC: | cschalle, davidz, jmccann, mclasen, rstrode, walters | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2009-02-21 20:39:32 UTC | Type: | --- | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
Error from log: stener-dbus.c:296 (17:28:10): Updating ConsoleKit idle status: 1 [gs_listener_update_console_kit_idle] gs-listener-dbus.c:321 (17:28:10): org.freedesktop.DBus.Error.AccessDenied raised: A security policy in place prevents this sender from sending this message to this recipient, see message bus configuration file (rejected message had interface "org.freedesktop.ConsoleKit.Session" member "SetIdleHint" error name "(unset)" destination "org.freedesktop.ConsoleKit") Probably this fallout from the dbus security errata: http://bugs.freedesktop.org/show_bug.cgi?id=19020 What version of dbus do you have installed? Hi, I have dbus-1.2.4-2.fc10.x86_64 (and dbus-glib-0.76-3.fc10.x86_64) have you rebooted since installing that version of dbus? *** Bug 479370 has been marked as a duplicate of this bug. *** seems like the permissive dbus builds are still blocking things. Created attachment 328521 [details]
gnome-screensaver log
I am not sure about permissive builds of dbus. But when rawhide downgraded to dbus-1.2.4-1.fc11.i386.rpm, I got attached log.
Are there any dbus messages in /var/log/syslog ? Oh, this is still with 1.2.4? We need to know about comment #3 - you need to have rebooted for it to take effect. in my case I am rebooting daily and updating rawhide daily but still i see this bug. It turns out the SetIdleHint denial was not related to this problem. Moving back to gnome-screensaver. Looking at the attached log: (/usr/libexec/gnome-screensaver-gl-helper:6339): Gdk-CRITICAL **: gdk_x11_visual_get_xvisual: assertion `visual != NULL' failed rather stands out. Hi, I still observe this behaviour after a reboot, using dbus-1.2.4-2.fc10.x86_64 . I have a friend running F10 x86_64 too which is not affected by this bug, but he's running a fresh install while I updated from F9, and maybe from F8 to F9 too, I can't remember. I hope it helps :) Do you guys see this problem if you choose a non-GL screensaver? (Say blank screen)? I use the default (blank screensaver). Upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=561855 * Sat Feb 21 2009 Matthias Clasen <mclasen> - 2.25.2-4 - Make all hacks work again |
Created attachment 328078 [details] Debug log of the gnome-screensaver daemon Description of problem: When the screen is locked (either explicit request via gnome menu or when resuming from s2ram), I can't unlock the screen : I press a key, I briefly see the screen (solar fedora background), and it blanks again (I don't even see the password dialog). I need to switch to another VT and kill gnome-screensaver to get back to my session. I suspected gnome-power-manager, but I still get the same behavior when it's not running. Version-Release number of selected component (if applicable): Both gnome-screensaver-2.24.1-2.fc10 and gnome-screensaver-2.25.2-1.fc11 rebuilt for F10 (so the bug might be lying in an underlying lib ?) How reproducible: Lock the screen, try to unlock it. Attached is a debug log, logging the daemon start, then a lock and several attempts to unlock