[Xfce-bugs] [Bug 1060] New: startxfce4 fails on Sparc/Solaris when dbus is installed

[bugzilla-daemon at xfce.org]

Do NOT reply to this email.  To make further comments on this bug, use
the URL below:
http://bugzilla.xfce.org/show_bug.cgi?id=1060

           Summary: startxfce4 fails on Sparc/Solaris when dbus is installed
           Product: Xfce
           Version: 4.2.1
          Platform: Sun
        OS/Version: Solaris
            Status: NEW
          Severity: major
          Priority: High
         Component: xfce-utils
        AssignedTo: xfce-bugs at xfce.org
        ReportedBy: jh at junetz.de


Effect:
XFce does not start when dbus (e.g. version 0.23.4; doesn't matter here) is
installed.

Error message:
DBUS_SESSION_BUS_PID=12345: is not an identifier

Cause:
In the startxfce4 script on line 35, $prog is assigned the value /bin/sh. $prog
is then used to exec XFce's xinitrc. In that file on line 67, the result of
dbus-launch is handed over to eval.

Explanation:
On Sparc/Solaris, the eval fails because /bin/sh is not bash and not capable of
handling something like "export foo bar=val" which it would have to in order to
process the output correctly: A typical

dbus --sh-syntax --exit-with-session

gives something like this:

DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/dbus-somesalt'
export DBUS_SESSION_BUS_ADDRESS
DBUS_SESSION_BUS_PID=12345

but when executed by /bin/sh through eval:

DBUS_SESSION_BUS_PID=12345: is not an identifier

because eval automatically replaces newlines in the output of dbus-launch by
spaces and /bin/sh cannot cope with that, unlike bash. If dbus-launch wrote a
semicolon after each output line, there would be no problem either.

Possible solution:
Replacing prog=/bin/sh by prog=/bin/bash in startxfce4 on systems that have bash
installed does the trick. However, I don't know if one can assume that there is
a bash on a standard Solaris system. :-/

The problem probably still exists in XFce 4.2.2.

-- 
Configure bugmail: http://bugzilla.xfce.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.