Hardcoded /usr/bin in Xsession.d files makes jhbuild sessions to fail
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
seahorse (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Tried to launch the GNOME 2.19 session installed using jhbuild under /opt/gnome2, many "autostart" services and deamons (dbus-daemon, seahorse-agent, gnome-settings-
This is not good for my development/testing purpose, 'cause the session runs mixing settings and code from both GNOME installations, while it should use only settings and code from the one under /opt/gnome2
The only reason I can see for this wrong behavior is the hardcoded /usr/bin path in some files under /etc/X11/Xsession.d directory. For example, in /etc/X11/
# This file is sourced by Xsession(5), not executed.
SEAHORSE=
if [ -x $SEAHORSE ]; then
fi
Same occurs for 55gnome-
I'll try to remove this hardcode path.
Further info:
* jhbuild sandbox was installed following info on http://
* it always worked fine on dapper and edgy, I'm experiencing this issue now in feisty
I removed /usr/bin from 75dbus_dbus-launch and 60seahorse and now the jhbuild session goes fine.
I don't know if this is the real issue, but it's really annoying for GNOME developers using Ubuntu as base distro :-(
Please fix it.