On Sun, May 11, 2008 at 12:46:58AM +0200, Loïc Minier wrote: > Perhaps you could simply disable the default dbus-launch invocation by > removing use-session-dbus and then add a custom invocation?
You propose that a user may add a redefinition of OPTIONFILE inside his .xsessionrc (that is sourced in 40x11-common_xsessionrc) along with a custom dbus-launch, so when 75dbus_dbus-launch runs it looks inside a custom OPTIONFILE, does not find the line use-session-dbus and does not start dbus. This could work, but it assumes that the xsessionrc file is sourced before the dbus invocation (I'm not an expert, is this a safe assumption?). Moreover it forces the user to change the OPTIONFILE variable (ok, he may create a on-the-fly copy of the system file stripping the dbus line just before changing the OPTIONFILE). It works, though it's not very elegant. I believe that the correct solution would be an upstream change in dbus: IMHO --session should really check for a user session.conf before using the system one. Ludovico -- <[EMAIL PROTECTED]> #acheronte (irc.freenode.net) ICQ: 64483080 GPG ID: 07F89BB8 Jabber: [EMAIL PROTECTED] Yahoo: gardenghelle -- This is signature nr. 3949 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
