On 02 Jun 16:27, Chris G wrote:
On Wed, Jun 02, 2010 at 03:47:13PM +0100, Brett Parker wrote:
On 02 Jun 15:12, Chris G wrote:
Well I just tried it on my xubuntu 9.04 system and .xsessionrc *isn't* run.
Remember that Ubuntu and its derivatives have also broken much of what ssh-agent does by replacing it with their own seahorse stuff. (Talk about re-inventing the wheel!).
Weird, I don't know why they'd break that, it doesn't seem logical. Just to follow up a bit, it appears from a poke around that it's sourced by /etc/X11/Xsession.d/40x11-common_xsessionrc...
And gdm defers to the usual Xsession foo for setup of parts, afaict. So maybe, just maybe, umbongo have removed that part.
Well, maybe, but on my system there's a custom /etc/gdm/Xsession so it doesn't run the standard /etc/X11/Xsession. *Ah* and *that's* why it doesn't run ~/.xsessionrc.
In /etc/X11/Xsession (which is not run on my system because it uses /etc/gdm/Xsession instead) we have:- USERXSESSIONRC=$HOME/.xsessionrc
... and in /etc/X11/Xsession.d/40x11-common_xsessionrc we have:- if [ -r "$USERXSESSIONRC" ]; then . "$USERXSESSIONRC" fi
but since USERXSESSIONRC isn't set by /etc/gdm/Xsession it doesn't get run in my case.
Ah, but I too have a seperate /etc/gdm/Xsession, but that does run through the common /etc/X11/Xsession.d scripts... Wonder if I added that, or if it's a debian default...
(Also, it's not actually run, it's sourced...)
Surely, if we are to be *so* pedantic, 'run' is a sort of common/generic non-techie word for either execute or source indicating that the instructions in the file being 'run' are acted upon. Yes, I know it's important that it's sourced so that it affects the caller's environment but still.... :-)
Well, quite. Meh.