GNOME Bugzilla – Bug 669250
gdm-simple-slave[31794]: WARNING: Failed to set slave bus name on parent: Message did not receive a reply (timeout by message bus)
Last modified: 2018-05-24 10:40:07 UTC
Using GDM 3.0.4-4 from Debian/unstable sometimes the GDM screen does not show up when switching users. I think I have not yet experienced this when just logging out. But I am not sure. I am also not sure if that only happens in conjunction with suspend and resume, i. e. only after the system was resumed and then persists until the system is halted. Sometimes wanting to switch users, GDM does not start up for the (second) user and the screen stays black with a curser _ blinking in the top left corner. The only way to get a working system again is to log in using for example `ssh` and to issues `sudo service gdm3 restart`. This unfortunately destroys the session of the already logged in user and kills the programs. I am not sure how to debug this problem. It is not reproducible but happened two or three times already. You will find some excerpts from log files ahead. I could not spot anything relevant in the Linux kernel ring buffer (`dmesg`). Looking at `/var/log/syslog` there are a lot of warnings. Feb 1 19:32:33 joe gdm-simple-slave[23533]: WARNING: Failed to get value: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Please find the compressed log file attached. At 18:57 the system was resumed and at the popped up screen saver »Switch user« was selected. Then the screen stayed black with a cursor blinking in the top left corner at around 19:31 the GDM window appeared and the could log in indicated by the PulseAudio messages. At around 20:09 this user was logged out (*not* switch user) and the screen stayed black with the cursor blinking in the top left corner. I guess that the `gdm-simple-slave` was somehow killed by the Linux kernel although I could not find any messages supporting this. Please find the output of `ps aux | grep -i gdm` also attached. Debugging help is greatly appreciated. This report is more or less copied from the report I submitted to the Debian BTS [1]. [1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=658290
Created attachment 206640 [details] output from `ps aux | grep gdm` This is the output of `ps aux | grep gdm` listing all processes having gdm in their name. This shows quite a lot of processes.
Created attachment 206641 [details] `/var/log/syslog` with warnings and other hopefully useful messages (I needed to compress the file since it was too big.) `/var/log/syslog` contains a lot of the following. It was even there after restarting GDM and it worked again. Feb 1 19:31:37 joe pulseaudio[27077]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn. Feb 1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »/usr/lib/gnome-volume-manager/gnome-volume-manager« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) Feb 1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagle-search« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) Feb 1 19:31:43 joe pulseaudio[27209]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn. Feb 1 19:31:43 joe gnome-session[26373]: WARNING: Failed to start app: Unable to start application: Kindprozess »beagled« konnte nicht ausgeführt werden (Datei oder Verzeichnis nicht gefunden) Feb 1 19:31:46 joe pulseaudio[27270]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn. Feb 1 19:32:33 joe pulseaudio[27276]: [pulseaudio] main.c: User-configured server at localhost:30002, refusing to start/autospawn. Feb 1 19:32:33 joe gdm-simple-slave[26411]: WARNING: Failed to set slave bus name on parent: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Feb 1 19:32:33 joe gdm-simple-slave[24967]: WARNING: Failed to get value: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. Feb 1 19:32:33 joe gdm-simple-slave[24409]: WARNING: Failed to get value: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
I don't think that 3.0 is still being worked on in upstream - testing 3.2 would be more appreciated by upstream developers.
3.2 is coming soon to Debian, but there are still changes I need to push (like the new handling of dconf defaults) before it happens. Sorry for the delay in packaging it.
I suspect this is obsolete. Can you still reproduce, and if so, what is the new error message?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/88.