GNOME Bugzilla – Bug 677476
Races with GDM3.0 and accountsservice
Last modified: 2012-06-29 13:54:59 UTC
With GDM 3.0.4-4 from Debian Sid/unstable sometimes the ordering of the account names is changed and sometimes no accounts are shown at all [1]. I could capture the following logs when no account names were shown at all. # less /var/log/gdm3/\:0-greeter.log gnome-session[951]: WARNING: Failed to start app: Unable to start application: Kindprozess »gnome-power-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) Gtk-Message: Failed to load module "atk-bridge" gdm-simple-greeter[1138]: Gtk-WARNING: Overriding tab label for notebook gdm-simple-greeter[1138]: Gtk-WARNING: Overriding tab label for notebook gdm-simple-greeter[1138]: Gtk-WARNING: Overriding tab label for notebook gdm-simple-greeter[1138]: Gtk-WARNING: Overriding tab label for notebook gdm-simple-greeter[1138]: Gtk-WARNING: Overriding tab label for notebook gdm-simple-greeter[1138]: Gtk-WARNING: /tmp/buildd/gtk+3.0-3.4.2/./gtk/gtkwidget.c:7117: widget not within a GtkWindow gdm-simple-greeter[1138]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed gdm-simple-greeter[1138]: Gtk-CRITICAL: gtk_widget_get_preferred_height_for_width: assertion `width >= 0' failed gdm-simple-greeter[1138]: Gtk-WARNING: gtk_widget_size_allocate(): attempt to allocate widget with width -47 and height -47 Warnung der Fensterverwaltung:Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x1000007 (Anmeldefen) Warnung der Fensterverwaltung:meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. [1] http://lists.freedesktop.org/archives/systemd-devel/2012-May/005211.html
Thanks for taking the time to report this bug. However, you are using version 3.0.x which is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes by GNOME developers for the version that you use. Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME, or feel free to file a bug report in the bug tracking system of Debian if Debian still supports this version.
(In reply to comment #1) > Thanks for taking the time to report this bug. > However, you are using version 3.0.x which is too old and not supported > anymore. GNOME developers are no longer working on that version, so > unfortunately there will not be any bug fixes by GNOME developers for the > version that you use. I know. But maybe some developers remembers such a problem and can point out a culprit or a commit fixing this. > Please feel free to reopen this bug if the problem still occurs with a newer > version of GNOME, or feel free to file a bug report in the bug tracking system > of Debian if Debian still supports this version. Well, this *is* the version currently in Debian Sid/unstable.
As a follow up, Debian Sid/unstable now ships GDM 3.4.1 for some time and I have not seen this problem with 3.4.1. So it was fixed between 3.0.4 and 3.4.1.
(In reply to comment #2) > I know. But maybe some developers remembers such a problem and can point out a > culprit or a commit fixing this. I don't think that using Bugzilla to get such information from developers is a good use of resources. Check for closed bug reports and git logs instead? > Well, this *is* the version currently in Debian Sid/unstable. It's Debian's decision what to ship. In GNOME it is obsolete and unsupported.