- Edited
Thought it would be better to post a new topic instead of resurrecting an old one: https://forum.obarun.org/viewtopic.php?id=1348&p=2
I've followed the advice from @ eric at post # 23, but permission errors still pop up from Thunar about not having authorization when click-to-mount is desired. My system is up-to-date as of now.
As per the advice, I've switched my ~/.xsession to:
For now, I've reverted to the "wrong" way where /usr/share/sddm/scripts/Xsession is modified instead, as suggested by @ negative at post # 12:
This isn't really an urgent matter for me so no need to be too alarmed, but just letting you guys know just in case.
I've followed the advice from @ eric at post # 23, but permission errors still pop up from Thunar about not having authorization when click-to-mount is desired. My system is up-to-date as of now.
As per the advice, I've switched my ~/.xsession to:
# !/usr/bin/bash
_user=hyperspace
list=( $(ls -A1 /home/${_user}/.66/conf/svscan@ ${_user}) )
for i in ${list[@ ]};do
var=( $(</home/${_user}/.66/conf/svscan@ ${_user}/${i}) )
for j in ${var[@ ]}; do
export ${j}
done
done
66-all up
But the permission errors still persist in Thunar. For now, I've reverted to the "wrong" way where /usr/share/sddm/scripts/Xsession is modified instead, as suggested by @ negative at post # 12:
if [ -z "$*" ]; then
exec xmessage -center -buttons OK:0 -default OK "Sorry, $DESKTOP_SESSION is>
else
if [ -x /usr/bin/ck-launch-session ]; then
exec ck-launch-session dbus-run-session $@
else
exec $@
fi
fi
Where "dbus-run-session" is the change suggested. This works without permission errors for click-to-mount.This isn't really an urgent matter for me so no need to be too alarmed, but just letting you guys know just in case.