LinuxQuestions.org - [SOLVED] Slack curr is having some major issue, 4 me anyway, automount no longer working in old school wm's

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Slack curr is having some major issue, 4 me anyway, automount no longer working in old school wm's (https://www.linuxquestions.org/questions/slackware-14/slack-curr-is-having-some-major-issue-4-me-anyway-automount-no-longer-working-in-old-school-wms-4175647073/)

Slack curr is having some major issue, 4 me anyway, automount no longer working in old school wm's

This has been like this for awhile, I don't know if anyone else is experiencing this, if not it's probably because no one is still using old school window managers but me. :)

I noticed this in e16 after I got this other 'new' used laptop, then installed slack current dvd, updated it, then installed e16, using pcmanfm, and this even takes place with Thunar.

Where KDE and Cinnamon automount just find when ever a drive is plugged into the USB, but Windowmanger and e16 and ones such as that no longer do.

Code:

        # Start DBUS session bus:

        if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then

        {

                    eval `dbus-launch --sh-syntax --exit-with-session`

                echo "setting: $DBUS_SESSION_BUS_ADDRESS"

                    export DBUS_SESSION_BUS_ADDRESS

        }

        else

                echo "alldone $DBUS_SESSION_BUS_ADDRESS"

        fi

is in e16 auto start file, this works in other distros and e16, ie Debian, Mint, void linux. but no longer in slack ( current ). so what needs to be fixed so even the window managers that come package with slackware will work again using automount?

Quote:

but no longer in slack ( current )

What were the most recent changes/updates to -current? Your post presumes that it was working before and recently stopped.

Quote:

Originally Posted by ChuangTzu (Post 5954162)

What were the most recent changes/updates to -current? Your post presumes that it was working before and recently stopped.

I am not presuming anything, it was when I was using my other laptop a few mounths ago,and long before that running slack current, when ever I used windowmaker, or fluxbox, or the other installed with system wm automount always worked in them, then i got this laptop, hp 840 g2 - I already seen the slight issues I am having with it using a non discrete video - ie Intells chip instead of the ati chip I had on my other laptop.

The changes that took place between then and now, if I knew that then I'd probably not be asking.

in other words,

I have no idea.

Quote:

Originally Posted by rkelsen (Post 5954170)

Does this help?

https://www.linuxquestions.org/quest...nt-4175574561/

I do not get the rebiuld the file manager thing, but that last part/post is already in play, dbus thing as poted, and the desktop file changing :: exec=wmaker to exec=startwindowmaker

Code:

$ startwmaker

bash: startwmaker: command not found

how is that suppose to work when there is no command named that. create a link to it.

Code:



ls -s  /usr/bin/wmaker /usr/bin/startwmaker

that's a bit redundant. so I do not know where allend got that idea.

so the answer would be no that does not help, thanks.

this is working in cinnamon and not working in wmaker images

lsblk shows it is mounted on the system. If you look at what the images comparing them, the image showing it not working even all of the mounts that it is showing are different, proc, floppy, shm, pts why is it showing that??

sdc being the usb port plugged in but not showing up in the file manager.

ps I am in fluxbox, just checked it, and auto mount is working in here.

Recently I had to edit my /usr/share/apps/kdm/sessions/wmaker.desktop file, as per post #5 of the thread rkelsen linked, to get automounting working in Thunar running in Windowmaker after the file was overwritten by upgrading the kde-workspace package.
You need to create the /usr/bin/startwmaker file.

Quote:

Originally Posted by allend (Post 5954221)

and what does this file, "/usr/bin/startwmaker" consist of? wmaker is the executable to WindowMaker.

The "/usr/bin/startwmaker" file is a little wrapper script to set the DBUS_SESSION_BUS_ADDRESS variable before launching /usr/bin/wmaker as detailed in post #5 of the linked thread.

Quote:

Originally Posted by allend (Post 5954231)

The "/usr/bin/startwmaker" file is a little wrapper script to set the DBUS_SESSION_BUS_ADDRESS variable before launching /usr/bin/wmaker as detailed in post #5 of the linked thread.

well color me blind, I see what you're doing. I'll give that a try.thanks

that's insane, what once worked, no longer works so I have to do a work around in order to get it to work again.

It's nothing new. Been like this a while now. Basically, launching a window-manager directly through dbus-launch is unreliable and best avoided.

Unfortunately slackware's shipped xinitrc.wmaker uses dbus-launch in this unreliable way.

IMO it would be better to redo them as follows:

/etc/X11/xinitrc/xinitrc.wmaker:

Code:

#!/bin/sh

# $XConsortium: xinitrc.cpp,v 1.4 91/08/22 11:41:34 rws Exp $



userresources=$HOME/.Xresources

usermodmap=$HOME/.Xmodmap

sysresources=/etc/X11/xinit/.Xresources

sysmodmap=/etc/X11/xinit/.Xmodmap



# merge in defaults and keymaps



if [ -f "$sysresources" ]; then

    xrdb -merge "$sysresources"

fi



if [ -f "$sysmodmap" ]; then

    xmodmap "$sysmodmap"

fi



if [ -f "$userresources" ]; then

    xrdb -merge "$userresources"

fi



if [ -f "$usermodmap" ]; then

    xmodmap "$usermodmap"

fi





# Start the window manager:

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

  exec ck-launch-session /usr/bin/startwmaker

else

  exec /usr/bin/startwmaker

fi

/usr/bin/startwmaker (new file):

Code:

#!/bin/sh



# Start d-bus:

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ] && [ -x /usr/bin/dbus-launch ]; then

  eval $( dbus-launch --sh-syntax --exit-with-session )

fi



# If the user lacks $HOME/GNUstep, install it:

if [ ! -f $HOME/GNUstep/Defaults/WindowMaker ]; then

    wmaker.inst

fi



# Test for cpp, which wmaker uses to process config files:

if [ ! -x /usr/bin/cpp ]; then

  NOCPP="--no-cpp"

fi



# Start the window manager:

exec /usr/bin/wmaker $NOCPP

I've also moved the wmaker.inst call from the xinitrc into startwmaker as that seems a more appropriate place for it than in the xinitrc.

Quote:

I've also moved the wmaker.inst call from the xinitrc into startwmaker as that seems a more appropriate place for it than in the xinitrc.

I think that should also remain in xinitrc. On a fresh install of Slackware, the default is to boot to run level 3. I would typically use xwmconfig to select Windowmaker, then use startx, which will trigger the wmaker.inst call on the first pass. When I am happy, then I would change to booting to run level 4.