the startup script does exactly what it was supposed to do; because
there was no default session manager (broken symlink) it falls back to
using the default window manager. The script can only test for the
default session manager, and not every single one available. In your
case the bug was when
** Changed in: xorg (Ubuntu)
Status: Confirmed = Triaged
--
gnome-session not started if /etc/alternatives/x-session-manager is a dangling
symlink
https://bugs.launchpad.net/bugs/289451
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The bug still exists in Jaunty. The described test was about nonexistent
/usr/bin/x-session-manager, but my bug report was about
/etc/alternatives/x-session-manager being a dangling symlink.
Reproduction:
r...@macks-laptop:~# mv /etc/alternatives/x-session-manager
Looks like it's working properly for me on Jaunty.
r...@salisbury:/etc/X11/Xsession.d# STARTUP=
r...@salisbury:/etc/X11/Xsession.d# source 50x11-common_determine-startup
r...@salisbury:/etc/X11/Xsession.d# echo $STARTUP
x-session-manager
r...@salisbury:/etc/X11/Xsession.d# mv
** Changed in: xorg (Ubuntu)
Importance: Undecided = Medium
Status: Incomplete = Triaged
--
gnome-session not started if /etc/alternatives/x-session-manager is a dangling
symlink
https://bugs.launchpad.net/bugs/289451
You received this bug notification because you are a member of
** Summary changed:
- [intrepid] gnome-session not started if /etc/alternatives/x-session-manager
is a dangling symlink
+ gnome-session not started if /etc/alternatives/x-session-manager is a
dangling symlink
--
gnome-session not started if /etc/alternatives/x-session-manager is a dangling
