Fluxbox & Thunar mounting fix

chess · 08-05-2012, 07:20 PM

Also, to get Thunar to automount in Fluxbox and other wm's after latest Changelog updates, add this polkit file:

/etc/polkit-1/localauthority/50-local.d/20-plugdev-group-mount-override.pkla

[plugdev group mount override]
Identity=unix-group:plugdev
Action=org.freedesktop.udisks2.filesystem-*;org.freedesktop.udisks2.eject-*
ResultAny=yes
ResultInactive=yes
Result=Active=yes

If user is in the 'plugdev' group then they can mount/unmount in Thunar whether they use startx to start fluxbox or start it from XDM.

andrew.46 · 08-06-2012, 03:32 AM

Works nicely here, thanks

. I am still a bit puzzled by the pop-box that comes with unmount:

Volume is busy
One or more applications are keeping the volume busy
tumblerd
/usr/lib64/tumbler-1/tumblerd

Any magic for that?

GazL · 08-06-2012, 06:35 AM

@chess, I suspect you may only be treating the symptom there. For polkit authentication/authorisations to work correctly, dbus-launch must be run within the console-kit session environment. The current xinitrc files run dbus-launch prior to starting the console-kit session and this is actually what is breaking thunar. By changing the polkit rules you're avoiding this one problem, but the underlying issue still exists and may manifest with other programs that rely on dbus/polkit (maybe the nm-applet issue for example?)

Unfortunately trying to launch the window manager via an argument to dbus-launch breaks XDM authentication as we found out with the last approach, but
using blackbox as an example, I got thunar working with the following approach

xinitrc.blackbox:

Code:

#!/bin/sh
# 

startscript=/usr/bin/startblackbox

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/etc/X11/xinit/.Xresources
sysmodmap=/etc/X11/xinit/.Xmodmap

# merge in defaults and keymaps

[ -f $sysresources ]  &&  xrdb -merge $sysresources

[ -f $sysmodmap ]  &&  xmodmap $sysmodmap

[ -f $userresources ]  &&  xrdb -merge $userresources

[ -f $usermodmap ]  &&  xmodmap $usermodmap


# Start the window manager:

if [ -z "$DESKTOP_SESSION" -a -x /usr/bin/ck-launch-session ]; then
  exec ck-launch-session $startscript
else
  exec $startscript
fi

/usr/bin/statblackbox

Code:

#!/bin/sh
#  startblackbox v1.0

# Start DBUS session bus

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
   eval `/usr/bin/dbus-launch --sh-syntax --exit-with-session`
fi


# Start Window Manager

exec /usr/bin/blackbox

I've already emailed Pat a couple of times on this, and was waiting to see how he responds, but as you've posted on the same subject, I thought it prudent to post what I'd discovered.

chess · 08-06-2012, 07:04 AM

@GazL: - yes, I've been hacking around at the dbus issue as well and also emailed Pat about it, along with these 2 posts I made here re: thunar and nm-applet fixes with polkit files.

But with these polkit files I have fluxbox and thunar and nm-applet working with Pat's .xinitrc/.xsession files whether I launch fluxbox from startx or XDM.

Still, I agree that these .xinitrc files still might need some massaging.

GazL · 08-06-2012, 07:16 AM

Ahh, ok chess. thanks. Sounds like the issue is well undertood now, so it's just a case of seeing what our BDFL decides to do.

BTW, while were on the subject of .xinitrc/.xsession, can I suggest an enhancement to xwmconfig so that it also creates a 755 ~/.xsession file in addition to the ~/.xinitrc so that XDM starts the chosen session as well as startx.

chess · 08-06-2012, 07:55 AM

Quote:

Originally Posted by GazL

BTW, while were on the subject of .xinitrc/.xsession, can I suggest an enhancement to xwmconfig so that it also creates a 755 ~/.xsession file in addition to the ~/.xinitrc so that XDM starts the chosen session as well as startx.

Agreed - that would be nice. IIRC, I think the XDM config would also need to be modified to uncomment those lines re: a user's .xsession.

GazL · 08-06-2012, 08:12 AM

No need chess, It will work just fine.

In addition to the commented out exec to ~/.xsession on line 109, there's also one further down on line 167, and that's the one that appears to do the actual starting - assuming that one doesn't manually choose a session from the XDM screen (which is unlikely since the only translation in the default Xresources file is for the failsafe session.

)

The main gotcha with using a ~/.xsession is that /etc/X11/xdm/Xsession does a test -x ~/.xsession, so unlike ~/.xinitrc it needs +x permissions.

To be honest, /etc/X11/xdm/Xsession could stand a little work itself. I guess because KDM is the primary display manager in Slackware it hasn't been given much attention.

chess · 08-06-2012, 08:15 AM

Ah, ok, thanks for that. It's been forever since I poked around in there. I don't ever use XDM myself -- just plain ol' startx. ;-)

allend · 08-07-2012, 11:30 AM

I like the solution that GazL has provided as it seems to work around the issues discussed here. http://lists.freedesktop.org/archive...ch/000080.html

Quote:

If "ck-launch-session" is successful it then sets the XDG_SESSION_COOKIE
environment variable which is inherited by all children processes.
...
As you point out, however, apps lacking PAM integration such as
"xinit" or "startx" need to manually start a ConsoleKit session. In
this respect "ck-launch-session" is definitely required and certainly
not deprecated. Unfortunately this tool starts a new user-shell
(bash,zsh, whatever) instead of exporting the XDG_SESSION_COOKIE to
the current shell.

chess · 08-09-2012, 10:20 PM

@GazL: looks like our BDFL adopted some of our suggestions. :-) Thanks for sending your .xinitrc/.xsession changes. Those are good.

GazL · 08-10-2012, 03:34 AM

You're welcome chess. Thanks for the polkit stuff too. I'm sure the nm-applet users will appreciate those, and I wouldn't have figured that out without having to do a lot of reading - assuming freedesktop.org have actually done any documentation (it was pretty sparse last time I went looking).

It's just a shame that the freedesktop.org stuff is so ugly that we need to jump through these hoops in the first place.

Still, all's well that ends! :-)