[SOLVED] Slackware(64) 14.2 - Pendrives not automount & i can't shutdown from Menu
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Slackware(64) 14.2 - Pendrives not automount & i can't shutdown from Menu
Hi there, i am under Slackware(64) 14.2 still XD. before upgrade to 15.0 i am using some days testing things.
After all i had update & upgrade the packages to the latest version the system detect with slackpkg & slpkg.
Well i notice packages like udisks udisks2 and udiskie had upgraded, but now when i connect a usb pendrive, in thunar does not appear the partitions automatically, i should mount manually the 3 partitions of my pendrive.
I prefer Dolphin over Thunar but I depend heavily on File Managers. I've never liked hard disk automounts simply because I sometimes need to have a consistent mount point so for at least the ones I most commonly work with, I hard spec them in /etc/fstab, then I know exactly where to look. If there is any downside, it has never bothered me.
There is a specific permissions setting in some WM/DEs that grants permission for common Users to initiate shutdown or reboot. In most cases simply logging out, especially to runlevel 3 in Slackware, will sidestep that requirement.
You have tagged this thread with xfce, so I assume you are using XFCE.
Do you have DBUS running? (Check whether /etc/rc.d/rc.messagebus is executable. You can also use 'pkgtool'. Select 'Setup' -> 'services' -> 'rc.messagebus').
I prefer Dolphin over Thunar but I depend heavily on File Managers. I've never liked hard disk automounts simply because I sometimes need to have a consistent mount point so for at least the ones I most commonly work with, I hard spec them in /etc/fstab, then I know exactly where to look. If there is any downside, it has never bothered me.
There is a specific permissions setting in some WM/DEs that grants permission for common Users to initiate shutdown or reboot. In most cases simply logging out, especially to runlevel 3 in Slackware, will sidestep that requirement.
i prefer not specify too much things under fstab, just the hard disk partitions i know i ever use, but searching on internet yesterday i found a blog article says «fstab is not just for boot» well i don't see too much sense put UUID of Pendrive inside fstab.
you know how i can determinate why xfce is not allow me to use «power» or «reboot» from the menu ?
You have tagged this thread with xfce, so I assume you are using XFCE.
Do you have DBUS running? (Check whether /etc/rc.d/rc.messagebus is executable. You can also use 'pkgtool'. Select 'Setup' -> 'services' -> 'rc.messagebus').
Yes i am using Xfce 4.12 under Slackware64 14.2 :
Code:
ls -la /etc/rc.d/rc.messagebus
-rwxrwxrwx 1 inukaze users 1864 mar 3 2022 /etc/rc.d/rc.messagebus
ps -A | grep dbus
1132 ? 00:00:00 dbus-daemon
2138 ? 00:00:00 dbus-launch
2139 ? 00:00:00 dbus-daemon
2159 ? 00:00:00 dbus-daemon
2189 ? 00:00:00 dbus-launch
2190 ? 00:00:00 dbus-daemon
/etc/rc.d/rc.messagebus status
System dbus-daemon is running.
content of /etc/rc.d/rc.messagebus
Code:
#!/bin/sh
#
# messagebus: The D-BUS systemwide message bus
#
# description: This is a daemon which broadcasts notifications of system events \
# and other messages. See http://www.freedesktop.org/software/dbus/
#
# processname: dbus-daemon
# This is a modified version of the rc.messagebus script distributed with the
# dbus sources. Thanks to Don Tanner of the GWare <http://gware.org> Project
# for most of the work involved --Robby Workman <rworkman@slackware.com>
PIDFILE=/var/run/dbus/dbus.pid
start() {
mkdir -p $(dirname $PIDFILE)
if ! ps -u messagebus -c | grep -wq dbus-daemon; then
rm -f $(dirname $PIDFILE)/*
if [ -x /usr/bin/dbus-uuidgen -a -x /usr/bin/dbus-daemon ] ; then
echo "Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system"
/usr/bin/dbus-uuidgen --ensure
/usr/bin/dbus-daemon --system 1> /dev/null
fi
fi
}
stop() {
if [ -e "$PIDFILE" ]; then
echo "Stopping system message bus..."
pid=$(cat $PIDFILE)
kill $pid 1> /dev/null 2> /dev/null
# Just in case:
killall dbus-daemon 1> /dev/null 2> /dev/null
rm -f $PIDFILE
fi
}
reload() {
echo "Reloading system message bus configuration..."
if [ -e "$PIDFILE" ]; then
pid=$(cat $PIDFILE)
kill -HUP $pid
else
killall -HUP dbus-daemon
fi
}
status() {
if ps -u messagebus -c | grep -wq dbus-daemon; then
echo "System dbus-daemon is running."
else
echo "System dbus-daemon is stopped."
fi
}
# See how we were called.
case "$1" in
start)
start
;;
stop)
stop
;;
restart)
stop
start
echo "You may need to restart your Window Manager to reconnect to the system dbus."
;;
reload)
reload
;;
status)
status
;;
*)
echo $"Usage: $0 {start|stop|restart|reload|status}"
;;
esac
Well i don't know why some files on my system are corrupted.
i had installed udiskie, i try to launch and i get the follow output :
Code:
Deprecation warning: Running on python 2.7. The next major version of udiskie will require at least python 3.5!
Failed to connect UDisks2 dbus service..
Falling back to UDisks1.
Traceback (most recent call last):
File "/usr/lib64/python2.7/site-packages/udiskie/cli.py", line 306, in _start_async_tasks
self.udisks = yield get_backend(self.options['udisks_version'])
Error: g-dbus-error-quark: Error calling StartServiceByName for org.freedesktop.UDisks: GDBus.Error:org.freedesktop.DBus.Error.Spawn.PermissionsInvalid: The permission of the setuid helper is not correct (32)
i need a sanaty-check tool to found which file are corrupted like /usr/libexec/dbus-daemon-launch-helper or "$HOME/.config/QtProject.conf" like i had explain before in the post -> https://www.linuxquestions.org/quest...gs-4175705598/
the qt5 apps have a several slow down on open/save dialogs take too much time for show that dialogs if that file are corrupted, when i remove i open vlc and open any videofile just take some seconds instead minutes (5 minutes when i select the file, and 23 minutes waiting the vlc start the playback of the video i had choose to play)
Well i going to delete this file and search which package content it.
Code:
rm -rf /usr/libexec/dbus-daemon-launch-helper
slackpkg reinstall dbus ; slackpkg install dolphin pulseaudio ; ldconfig
#i had install PulseAudio because Firefox does have any audio output when just exist ALSA, or well i don't know if cause by another corrupted file or files like the two before examples from above this same message.
Warning /usr/lib64/libpulse.so.0 is not symbolic link
Warning /usr/lib64/libpulse-mainloop-glib.so.0 is not symbolic link
Warning /usr/lib64/libpulse-simple.so.0 is not symbolic link
cd /usr/lib64
rm -rf /usr/lib64/libpulse.so.0 /usr/lib64/libpulse-mainloop-glib.so.0 /usr/lib64/libpulse-simple.so.0
ln -sf libpulse.so.0.20.0 libpulse.so.0
ln -sf libpulse-simple.so.0.1.0 libpulse-simple.so.0
ln -sf libpulse-mainloop-glib.so.0.0.5 libpulse-mainloop-glib.so.0
well i decide to test dolphin like «enorbet» comment mention that file manager, and look, Thunar does not show the USB Partitions, but dolphin yes (with udiskie running).
Screenshot -> https://i.postimg.cc/tRkN6bp9/dolphin-vs-thunar.png
Code:
dolphin
dolphin(3142) KSambaSharePrivate::testparmParamValue: We got some errors while running testparm "testparm: /usr/lib/libp11-kit.so.0: no version information available (required by /usr/lib/libgnutls.so.30)
Load smb config files from /etc/samba/smb.conf
Loaded services file OK.
WARNING: lock directory /var/cache/samba should have permissions 0755 for browsing to work
WARNING: state directory /var/lib/samba should have permissions 0755 for browsing to work
WARNING: cache directory /var/cache/samba should have permissions 0755 for browsing to work
chmod 0755 /var/cache/samba
chmod 0755 /var/lib/samba
i had forgot when i run more two times a KDE Plasma 4 application, for unknow reasons for me still, the window manager just disappear from that kind of windows like kpat or dolphin.
The content of my custom file /usr/bin/dolphin for this workaround (i use a custom size of window because i ever the change on the conky in the right side of the screen) :
Code:
#!/usr/bin/env bash
echo '
Autor ----------------> Inukaze ( Venezuela )
Sitio ----------------> https://goo.gl/ij6WqW
Correo-E -------------> bloginukaze@gmail.com
Licencia -------------> GPL 2
******* Inicio : Acerca de este Guion ********
Este Mini-Guion es para poder iniciar Dolphin
mientras se usa Compiz & Conky ya que suele
Iniciar correctamente la primera vez, pero
Apartir de la segunda vez inicia en el modo
Pantalla Completa y sin bordes de ventana
Por lo cual hay que modificar una linea del
Archivo de configuracion de Dolphin relativa a
vez en modo ventana y con los bordes de la
ventana visible.
******** Fin : Acerca de este Guion **********'
unset EncontrarEjecutable
unset Corregir
unset Ejecutar
function EncontrarEjecutable()
{
rutadolphin=$(whereis -B "/usr/sbin" "/usr/local/sbin" "/sbin" "/usr/bin" "/usr/local/bin" "/bin" -b dolphin.real | grep -i "dolphin.real" | cut -d " " -f02 | sed 's/[/]dolphin.real//')
if [ -x "$rutadolphin/dolphin.real" ]; then
dolphin="$rutadolphin/dolphin.real"
else
echo -e "dolphin no esta instalado\nPor favor, Instala dolphin antes de usar este guion"
exit 1
fi
}
function Corregir()
{
Archivo="dolphinrc"
Directorio="$HOME/.kde"
if test -d "$Directorio"
then
Directorio="$HOME/.kde/share"
else
echo "el directorio $Directorio no existe"
exit 1
fi
if test -d "$Directorio"
then
Directorio="$HOME/.kde/share/config"
else
echo "el directorio $Directorio no existe"
exit 1
fi
if test -d "$Directorio"
then
if test -f "$Directorio/$Archivo"
then
echo "Archivo de configuracion encontrado"
#Notas necesito encontrar :
#
# 1 : Como eliminar la linea «Height 1024=» justo debajo de «[MainWindow] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Height 1024=885/}' "$Directorio/$Archivo"»
#
# 2 : Como eliminar la linea «Width 1280=» justo debajo de «[MainWindow] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Width 1280=1058/}' "$Directorio/$Archivo"»
#
# 3 : Como eliminar la linea «Height 1024=» justo debajo de «[SettingsDialog] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Height 1024=391/}' "$Directorio/$Archivo"»
#
# 4 : # 3 : Como eliminar la linea «Width 1280=» justo debajo de «[SettingsDialog] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Width 1280=690/}' "$Directorio/$Archivo"»
#Mientras no encuentre como borrar las lineas de «Height 1024» y «Width» justo despues de «[MainWindow» y «SettingsDialog», utilizar la via menos inteligente "tee" :
echo '[CompactMode]
FontWeight=50
PreviewSize=32
[DetailsMode]
FontWeight=50
IconSize=48
PreviewSize=96
[General]
BrowseThroughArchives=true
EditableUrl=true
FilterBar=true
ShowFullPath=true
[IconsMode]
FontWeight=50
IconSize=64
PreviewSize=128
[MainWindow]
Height 1024=885
MenuBar=true
ToolBarsMovable=Disabled
Width 1280=1058
[PreviewSettings]
Plugins=directorythumbnail,imagethumbnail,jpegthumbnail
[SettingsDialog]
Height 1024=391
Width 1280=690
' | tee "$Directorio/$Archivo"
sed -i 's/.*MenuBar=.*/MenuBar=true/' "$Directorio/$Archivo"
else
echo "No existe el archivo de configuracion $Archivo en el directorio $Directorio"
#Notas necesito encontrar :
#
# 1 : Como eliminar la linea «Height 1024=» justo debajo de «[MainWindow] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Height 1024=885/}' "$Directorio/$Archivo"»
#
# 2 : Como eliminar la linea «Width 1280=» justo debajo de «[MainWindow] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Width 1280=1058/}' "$Directorio/$Archivo"»
#
# 3 : Como eliminar la linea «Height 1024=» justo debajo de «[SettingsDialog] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Height 1024=391/}' "$Directorio/$Archivo"»
#
# 4 : # 3 : Como eliminar la linea «Width 1280=» justo debajo de «[SettingsDialog] para poder utilizar «sed '/[MainWindow]/{n;s/.*/Width 1280=690/}' "$Directorio/$Archivo"»
#Mientras no encuentre como borrar las lineas de «Height 1024» y «Width» justo despues de «[MainWindow» y «SettingsDialog», utilizar la via menos inteligente "tee" :
echo '[CompactMode]
FontWeight=50
PreviewSize=32
[DetailsMode]
FontWeight=50
IconSize=48
PreviewSize=96
[General]
BrowseThroughArchives=true
EditableUrl=true
FilterBar=true
ShowFullPath=true
[IconsMode]
FontWeight=50
IconSize=64
PreviewSize=128
[MainWindow]
Height 1024=885
MenuBar=true
ToolBarsMovable=Disabled
Width 1280=1058
[PreviewSettings]
Plugins=directorythumbnail,imagethumbnail,jpegthumbnail
[SettingsDialog]
Height 1024=391
Width 1280=690
' | tee "$Directorio/$Archivo"
sed -i 's/.*MenuBar=.*/MenuBar=true/' "$Directorio/$Archivo"
fi
fi
}
function Ejecutar()
{
echo ''
"$dolphin" "$@" &
#
#IDEA : Esperar que la ventana de Dolphin exista para que xdotool presione «Control+M»
# Ya que Dolphin cada vez que inicia cambia la linea «MenuBar=true» por «MenuBar=Disabled»
# Justo antes de mostrar la ventana. Por ende resulta imposible en esta version tener activa
# La barra de menues por defecto, ya que el propio Dolphin la deshabilita antes de mostrarse.
#
#NO FUNCIONA# until pids=$(pidof "$dolphin")
#NO FUNCIONA# do
#NO FUNCIONA# wait "$pids"
#NO FUNCIONA# echo "Esperando que inicie Dolphin"
sleep 5
#NO FUNCIONA# done
#NO FUNCIONA#
#NO FUNCIONA# for pid in $pids
#NO FUNCIONA# do
#NO FUNCIONA#
#NO FUNCIONA# DOLPHIN=$(wmctrl -l | grep -w "Dolphin" | head -n 1)
#NO FUNCIONA# if [ -z "$DOLPHIN" ]
#NO FUNCIONA# then
#NO FUNCIONA# echo "Dolphin aun no ha sido iniciado"
#NO FUNCIONA# else
#NO FUNCIONA# echo "Dolphin esta en ejecucion"
idv=$(xdotool search --onlyvisible --pid $(pidof dolphin.real)) ; \
xdotool windowactivate "$idv" ; \
xdotool key ctrl+m
#NO FUNCIONA# fi
#NO FUNCIONA# done
echo -ne "\n" | exit 0
}
# Usar las funciones
EncontrarEjecutable
Corregir
Ejecutar
This still looks like a problem with your DBUS setup to me.
KDE Plasma uses an internal DBUS system, which would explain why dolphin is working for you,
I see
Code:
bash-5.1$ ls -l /usr/libexec/dbus-daemon-launch-helper
-rwsr-x--- 1 root messagebus 60864 Feb 13 2021 /usr/libexec/dbus-daemon-launch-helper*
Perhaps try reinstalling the dbus package after checking that you have an entry
Code:
messagebus:x:81:
in your /etc/group. (IIRC there have been additions to that file between 14.2 and 15.0)
well i change "/mnt/exports/$LABEL" by "/media/$LABEL" well i need a solution for allow the common users umount the pendrives, well because i don't have idea in which file of configuration i must set the "eject" option should be usable by common users and that make the automount script can use umount without says need a root privilegies. the most ease solution i think should be this
restart the system, and now is solved, well i not know why i should make this manually when months before the system without my intervention make things like automount usb and allow eject like a normal user.
nobody know a tool to check & repair the most common default slackware configurations for things like that works fine or the qt open/save dialog does not take too much time ?
Code:
su
usermod -a -G audio,cdrom,floppy,plugdev,video,power,adm,cdrom,plugdev,sambashare,dialout inukaze
and for unknow reasons, the xfce4 shutdown helper, now is working. after i do the things i had explain here.
Curious i almost try things like editing the /etc/sudoers file but adding :
Code:
user localhost=NOPASSWD:/usr/lib/xfce4/xfsm-shutdown-helper
or search the xinitrc of xfce4 to force
Code:
exec ck-launch-session startxfce4
or put inside "~/.profile" or "~/.bashrc"
Code:
# Monturas :
alias mount="sudo mount"
export mount
alias umount="sudo umount"
export umount
but i dont need make that last thing i mention i almost try.
This still looks like a problem with your DBUS setup to me.
KDE Plasma uses an internal DBUS system, which would explain why dolphin is working for you,
I see
Code:
bash-5.1$ ls -l /usr/libexec/dbus-daemon-launch-helper
-rwsr-x--- 1 root messagebus 60864 Feb 13 2021 /usr/libexec/dbus-daemon-launch-helper*
Perhaps try reinstalling the dbus package after checking that you have an entry
Code:
messagebus:x:81:
in your /etc/group. (IIRC there have been additions to that file between 14.2 and 15.0)
Well after the thing i explain after this answer i am quoting, right now after reboot, when i connect the usb, i had double partitions with same names. i am doing the follow :
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
Slackware(64) 14.2 - Pendrives not automount & i can't shutdown from Menu
