LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 03-10-2016, 07:04 PM   #1
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,735

Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
Thunar does not automount USB stick in Windowmaker on Slackware64-current


Can anybody else replicate this corner case of Thunar launched in Windowmaker on Slackware64-current (as at 9 March 2016) not automounting USB sticks when plugged?
This is a little weird to me, as:
Thunar launched in XFCE on the same system behaves as expected.
Dolphin launched in Windowmaker on the same system behaves as expected.

Thunar launched in Windowmaker on 32bit Slackware-current behaves as expected.
 
Old 03-11-2016, 05:24 AM   #2
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,735

Original Poster
Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
I have taken the lack of answers as a No.

I just rebuilt my proprietary nVidia graphics driver and the problem has gone away. Go figure!
 
Old 04-16-2016, 01:15 AM   #3
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,735

Original Poster
Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
Just an update on this since upgrading to Slackware64 14.2-RC2.

Following the upgrade to the 4.4.7 kernel, I patched the kernel source and rebuilt the generic kernel to suit the nVidia 304.131 driver that I use. http://www.linuxquestions.org/questi...it-4175576863/

For kicks, I rebuilt the thunar-volman package from source and reinstalled, and the problem went away.
I then reinstalled the thunar-volman package from my local Slackware mirror, and the problem returned.
Reinstalling the locally built thunar-volman package made the problem go away again.

As this does not appear to be affecting anybody else, then it is obviously not a big issue, but perhaps thunar-volman could do with a recompile before Slackware 14.2 is released.

Further update:
Compiling locally shows some additional links in /usr/bin/thunar-volmam and /usr/bin/thunar-volman-settings to the nVidia driver.
Code:
ldd
...
        libnvidia-tls.so.304.131 => /usr/lib64/../lib64/tls/libnvidia-tls.so.304.131 (0x00007f0a57cae000)
        libnvidia-glcore.so.304.131 => /usr/lib64/../lib64/libnvidia-glcore.so.304.131 (0x00007f0a558c4000)

Last edited by allend; 04-16-2016 at 01:34 AM.
 
Old 04-17-2016, 10:37 AM   #4
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,735

Original Poster
Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
My apologies that this is a blog post, but this is getting on my goat. The previous fix did not stick.

The fundamental problem seems to be the setting of the DBUS_SESSION_BUS_ADDRESS environment variable. This affects both WindowMaker and FVM2 when booting to run level 4.

When I boot to run level 3, the DBUS_SESSION_BUS_ADDRESS environment variable is set for KDE, XFCE, FluxBox, WindowMaker and FVWM2, so all is OK and Thunar recognises the plugging of a USB stick.

When I boot to run level 4 using kdm as the login manager, then both WindowMaker and FVWM2 do not see the DBUS_SESSION_BUS_ADDRESS environment variable set (unlike KDE, XFCE and FluxBox), so Thunar does not recognise the plugging of a USB stick.

This can be worked around by adding 'dbus-launch ' in front of a call to Thunar, but this is a kludge that was not required until recently for reasons that I cannot elucidate.
 
1 members found this post helpful.
Old 04-18-2016, 08:29 AM   #5
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,735

Original Poster
Rep: Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271Reputation: 2271
I have looked at this some more and have discovered that the following changes allow WindowMaker, FVWM and Blackbox to see the DBUS_SESSION_BUS_ADDRESS environment variable when started from run level 4 using kdm.

For WindowMaker:
1. Create a file /usr/bin/startwmaker (I copied the existing /usr/bin/startblackbox and edited) containing
Code:
#!/bin/sh
#  startwmaker v1.0

########################################################################
##  Start DBUS session bus                                            ##
########################################################################


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


########################################################################
##  Start wmaker Window Manager                                       ##
########################################################################


exec /usr/bin/wmaker


########################################################################
2. Edit /usr/share/apps/kdm/sessions/wmaker.desktop to read
Code:
[Desktop Entry]
Type=XSession
Exec=startwmaker
TryExec=startwmaker
...
Comment - A similar fix probably applies to TWM and MWM.

For FVWM:
1. Edit /usr/share/apps/kdm/sessions/fvwm.desktop to read
Code:
[Desktop Entry]
Type=XSession
Exec=startfvwm2
TryExec=startfvwm2
...
For Blackbox:
1. Edit /usr/share/apps/kdm/sessions/blackbox.desktop to read
Code:
[Desktop Entry]
Type=XSession
Exec=startblackbox
TryExec=startblackbox
...

Last edited by allend; 04-18-2016 at 08:44 AM.
 
2 members found this post helpful.
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
32bit -current+XFCE+usb stick=no automount the_penguinator Slackware 18 12-20-2015 11:53 PM
[SOLVED] slackware64-current thunar 1.6.2 problems OscarMike Slackware 9 04-10-2013 11:36 AM
[SOLVED] Thunar 1.4.0 and Fluxbox on -current: no trash or automount usb devices andrew.46 Slackware 29 09-05-2012 02:59 AM
Slackware64 -current update July 19 2012: Thunar is throwing icon errors TL_CLD Slackware 3 07-19-2012 08:41 AM
Slackware64-current installation via usb stick hangs before setup mr_mandrill Slackware - Installation 9 09-11-2009 09:21 AM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 05:41 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration