should not run xsplash and whatnot for "xterm" session

[Tormod Volden]

Binary package hint: gdm

If I choose "xterm" from the greeter (I believe this is the old "failsafe terminal session" option) and log in, xsplash is running for a while, and afterwards several gnome-processes are running other than my xterm and bash.

Whenever I need to use "xterm" session, it is for debugging reasons and I want to have as little as possible running, not a half-baked gnome session.

After logging in (which takes abnormally long time, probably because of the useless xsplash) these processes are around:

UID PID PPID C STIME TTY TIME CMD
tormod 3582 1796 0 09:28 tty3 00:00:00 -bash
tormod 3645 1 0 09:28 ? 00:00:00 /usr/bin/gnome-keyring-daemon --daemonize --login
tormod 3660 3510 0 09:28 ? 00:00:00 xterm
tormod 3701 3660 0 09:28 ? 00:00:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session xterm
tormod 3704 1 0 09:28 ? 00:00:00 //bin/dbus-daemon --fork --print-pid 7 --print-address 9 --session
tormod 3705 1 0 09:28 ? 00:00:00 /usr/bin/dbus-launch --exit-with-session xterm
tormod 3706 3660 0 09:28 pts/0 00:00:00 bash
tormod 3744 3706 0 09:31 pts/0 00:00:00 ps -fu tormod

ProblemType: Bug
Architecture: i386
Date: Sat Sep 19 09:53:27 2009
DistroRelease: Ubuntu 9.10
Package: gdm 2.27.90-0ubuntu7
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
SourcePackage: gdm
Uname: Linux 2.6.31-10-generic i686

[bcrowell (launchpadcrowell07)]

Yes, please fix this. Gnome cruft should not be creeping into non-Gnome areas.

[bcrowell (launchpadcrowell07)]

This may or may not be related to this bug: https://bugs.launchpad.net/ubuntu/+source/xsplash/+bug/504403

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. A new version of GDM is available in both Lucid and Maverick and we are wondering if this is still reproducible in any of those versions, May you please test and give us of feedback about it? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.