[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

unable to log into gdm3 after reboot



Hi.  I logged out of my gnome session this morning for the first time in over a week.  When I tried to log in again, I was unable to do so.
I rebooted with no luck.  It appears something got broken badly in the latest upload of gdm3 to Sid.
I believe the problem is in the greeter, but don't know for sure.  It will be over a week until I can get anyone sighted to look at my screen.
I checked and don't see any bug filed about this yet.  Could someone please update to the latest gdm3 and see if they also have a problem?
I'll attach the log file from the greeter to this mail in case my problem is user error.

Thanks in advance for any help.
          Kenny

** (<unknown>:1756): DEBUG: Client registered with session manager: /org/gnome/SessionManager/Client1
Window manager warning: Failed to read saved session file /var/lib/gdm3/.config/metacity/sessions/10bbfff0a0f1a31a1f128558819254681500000017520005.ms: Failed to open file '/var/lib/gdm3/.config/metacity/sessions/10bbfff0a0f1a31a1f128558819254681500000017520005.ms': No such file or directory

(polkit-gnome-authentication-agent-1:1768): GLib-GObject-WARNING **: cannot register existing type `_PolkitError'

(polkit-gnome-authentication-agent-1:1768): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
** (process:1770): DEBUG: Greeter session pid=1770 display=:0.0 xauthority=/var/run/gdm3/auth-for-Debian-gdm-e4SJoi/database

** (gnome-power-manager:1769): WARNING **: Either HAL or DBUS are not working!

** (gnome-power-manager:1769): WARNING **: proxy failed

** (gnome-power-manager:1769): WARNING **: failed to get Computer root object

** (gnome-power-manager:1769): WARNING **: proxy NULL!!
gdm-simple-greeter[1770]: Gtk-WARNING: /build/buildd-gtk+2.0_2.20.1-1+b1-i386-jmql5R/gtk+2.0-2.20.1/gtk/gtkwidget.c:5628: widget not within a GtkWindow
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x180002b (Login Wind)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.

Reply to: