Make gdm depend on gnome-session

[PeterPall]

Binary package hint: gdm

Hello, here!

This bug might be Bug #396321 that has come back for lucid:

If gnome-session is not installed gdm on current lucid will lock completely before asking for the password. The only way to recover is killing gdm-simple-slave with signal 9, since after this crash it won't react to sigterm any more.

If apparmor is installed gdm will segfault after asking for the password, instead, and return to the login prompt.

The easy fix is making gdm depend on gnome-session. But this might re-open Bug #400901, so this has decided by somebody who knows more of these things.

Thanks in advance,

    Gunter.

ProblemType: Bug
Architecture: i386
Date: Wed Jan 6 16:41:46 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
Package: gdm 2.29.1-0ubuntu9
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-9.13-generic
SourcePackage: gdm
Tags: lucid
Uname: Linux 2.6.32-9-generic i686

[Sebastien Bacher (seb128)]

Thank you for your bug report, it's not the same issue than the other bug you list though, gdm does depends on gnome-session-bin which has the gnome-session command...what issue do you get exactly?

[PeterPall (peterpall)]

If the package gnome-session is not installed gdm-simple-slave will segfault after clicking on my user name midways into drawing the passwor prompt.
Before that it will complain that it cannot find users because it cannot get a seat-id, --- and that it cannot find my saved gnome session.

Alternatively it can segfault after asking for my user name - which will return me to the login screen.

Will try to deinstall gnome-session again tomorrow evening so I can reproduce the problem and give you the excact logs.

[PeterPall (peterpall)]

Tried it again: Instructed synaptic to completely remove gnome-session, - and restarted the computer.

The result was again, that gdm hung itselves up as soon as i clicked on my username, so the problem is reproducible at least on my computer.

ps -x |grep gdm reported while gdm was hanging:
{{{
 1514 tty1 S+ 0:00 /usr/sbin/gdm-binary
 1583 tty1 S+ 0:00 /usr/lib/gdm/gdm-simple-slave --display-id /org/gnome/DisplayManager/Display1
 1585 tty7 Ss+ 0:00 /usr/bin/X :0 -br -verbose -auth /var/run/gdm/auth-for-gdm-18EJcG/database -nolisten tcp vt7
 1624 tty1 S+ 0:00 /usr/lib/gdm/gdm-session-worker
 1865 tty4 S+ 0:00 grep gdm
}}}

restarted gdm, but this time didn't klick on my username but only kill gdm and saved all logfiles this produced. Will attach them to this comment as soon as I find out how.

[PeterPall (peterpall)]

:0-slave.log.1 is empty; to the console gdm only outputs:

gdm-binary[1875]: WARNING: Unable to find users: no seat-id found

Did install gnome-session afterwards again to get network access using the nm-applet. With gnome-session installed logging in into gdm just worked fine.

[PeterPall (peterpall)]

:0-slave.log.1 is empty; to the console gdm only outputs:

gdm-binary[1875]: WARNING: Unable to find users: no seat-id found

Did install gnome-session afterwards again to get network access using the nm-applet. With gnome-session installed logging in into gdm just worked fine.

[PeterPall (peterpall)]

:0-slave.log.1 is empty; to the console gdm only outputs:

gdm-binary[1875]: WARNING: Unable to find users: no seat-id found

Did install gnome-session afterwards again to get network access using the nm-applet. With gnome-session installed logging in into gdm just worked fine.

[Chris Coulson (chrisccoulson)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/apport/apport-qt --crash-file=/var/crash/_my_crash_report.crash in a terminal - where _my_crash_report.crash is the crash you would like to report.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

[PeterPall (peterpall)]

I understand, - and suddenly started working after reading your mail - only that gdm-simple-slave definitively stops to respond to anything except of a signal 9 after klicking on it.
But after the last update of my system it no longer segfaults, and thus doesn't give apport no chance to automatically generate a crash report.

The contents of my /etc/default/apport is:
{{{
 set this to 0 to disable apport, or to 1 to enable it
# you can temporarily override this with
# sudo service apport start force_start=1
enabled=1

# set maximum core dump file size (default: 209715200 bytes == 200 MB)
maxsize=209715200
}}}

Is there anything I can do in this case?

Thanks in advance.

     Gunter.