Lock screen dialog not visible after leaving message

Bug #518787 reported by Nate on 2010-02-08
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-screensaver

Using "ATI/AMD proprietary FGLRX graphics driver" in Karmic on HP TouchSmart tx2. gnome-screensaver 2.28.0-0ubuntu3.3 installed. After clicking "Leave Message" on lock screen and leaving message, all subsequent activations of the lock screen show only the screensaver but still allow login by moving mouse and typing password followed by enter.

ProblemType: Bug
Architecture: amd64
Date: Mon Feb 8 05:51:24 2010
DistroRelease: Ubuntu 9.10
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: fglrx wl
Package: gnome-screensaver 2.28.0-0ubuntu3.3 [modified: usr/share/gnome-screensaver/lock-dialog-default.ui]
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-19.56-generic
SourcePackage: gnome-screensaver
Uname: Linux 2.6.31-19-generic x86_64
XsessionErrors:
 (gnome-settings-daemon:2272): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:2272): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (nautilus:2403): Eel-CRITICAL **: eel_preferences_get_boolean: assertion `preferences_is_initialized ()' failed
 (polkit-gnome-authentication-agent-1:2429): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (firefox:3054): GLib-WARNING **: g_set_prgname() called multiple times

Nate (cool-vespa) wrote :
Chris Coulson (chrisccoulson) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem.

Changed in gnome-screensaver (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
importance: Undecided → Low
status: New → Incomplete
Nate (cool-vespa) wrote :

I haven't been able to recreate this behavior even though it has happened at least twice before with separate installations on the same hardware.

Marc Deslauriers (mdeslaur) wrote :

Can you still reproduce this issue with Ubuntu 10.10 (Maverick)?

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers