You are not logged in.
Is there any way to make LXQt's automounting feature respect udisks2's default directory for mounting. Under udisks2, it's /run/media/$USER. Under LXQt's automounting scheme, disks are mounted under /media/ directly.
I guess I can add my removable drive in my fstab array with the nofail option.
Last edited by ssri (2015-02-22 00:55:47)
Offline
Don't do that - fstab is not intended for removable devices.
Are you sure lxqt is using udisks2? Mounting under /media/ is the way udisks does it, not udisks2. Have you both installed? Does the lxqt automounter (about which I know nothing, just to be clear) have the option to choose one or the other?
Offline
Don't do that - fstab is not intended for removable devices.
Then the wiki should be amended with that caveat.
Are you sure lxqt is using udisks2? Mounting under /media/ is the way udisks does it, not udisks2. Have you both installed? Does the lxqt automounter (about which I know nothing, just to be clear) have the option to choose one or the other?
Ahh, that might be the issue as d-bus is starting udisks' daemon (udisks) instead of udisks2's (udisksd). The wiki warns against explicitly loading either daemon as d-bus handles it automatically. As for lxqt's automounter, there is practically no configuration menu, or any .conf files to be found under ~/.config/lxqt/, that can change or specify any parameters of the automounter.
UNIT LOAD ACTIVE SUB DESCRIPTION
avahi-daemon.service loaded active running Avahi mDNS/DNS-SD Stack
bumblebeed.service loaded active running Bumblebee C Daemon
chrony.service loaded active running Chrony Network Time Daemon
cpupower.service loaded active exited Apply cpupower configuration
dbus.service loaded active running D-Bus System Message Bus
getty@tty1.service loaded active running Getty on tty1
haveged.service loaded active running Entropy Harvesting Daemon
kmod-static-nodes.service loaded active exited Create list of required static device nodes for the current
lm_sensors.service loaded active exited Initialize hardware monitoring sensors
netctl@blahblah.service loaded active exited Automatically generated profile by wifi-menu
polkit.service loaded active running Authorization Manager
systemd-backlight@backlight:intel_backlight.service loaded active exited Load/Save Screen Backlight Brightness of backlight:intel_bac
systemd-fsck@dev-disk-by\x2duuid-3152e3d1\x2db216\x2d4dd1\x2d9f38\x2d218b85227318.service loaded active exited File System Check on /dev/disk/
systemd-fsck@dev-disk-by\x2duuid-5aa046f4\x2df4a3\x2d4a2f\x2db0c1\x2debf9e1a45fe9.service loaded active exited File System Check on /dev/disk/
systemd-journal-flush.service loaded active exited Flush Journal to Persistent Storage
systemd-journald.service loaded active running Journal Service
systemd-logind.service loaded active running Login Service
systemd-modules-load.service loaded active exited Load Kernel Modules
systemd-random-seed.service loaded active exited Load/Save Random Seed
systemd-remount-fs.service loaded active exited Remount Root and Kernel File Systems
systemd-rfkill@rfkill0.service loaded active exited Load/Save RF Kill Switch Status of rfkill0
systemd-rfkill@rfkill1.service loaded active exited Load/Save RF Kill Switch Status of rfkill1
systemd-rfkill@rfkill2.service loaded active exited Load/Save RF Kill Switch Status of rfkill2
systemd-sysctl.service loaded active exited Apply Kernel Variables
systemd-tmpfiles-setup-dev.service loaded active exited Create Static Device Nodes in /dev
systemd-tmpfiles-setup.service loaded active exited Create Volatile Files and Directories
systemd-udev-trigger.service loaded active exited udev Coldplug all Devices
systemd-udevd.service loaded active running udev Kernel Device Manager
systemd-update-utmp.service loaded active exited Update UTMP about System Boot/Shutdown
systemd-user-sessions.service loaded active exited Permit User Sessions
systemd-vconsole-setup.service loaded active exited Setup Virtual Console
udisks.service loaded active running UDisks
upower.service loaded active running Daemon for power management
user@1000.service loaded active running User Manager for UID 1000
wpa_supplicant.service loaded active running WPA supplicantLast edited by ssri (2015-02-20 20:31:35)
Offline
Maybe just remove udisks, see if it changes over to udisks2.
Feel free to change the wiki if you want.
Offline
I removed udisks and rebooted. According to systemctl, D-BUS does not start up udisks2 upon logging into the shell. Furthermore, starting up lxqt via 'startx' results in no devices automounted. I guess lxqt's automounter uses udisks, which is strange because hasn't development for udisks ceased several months ago? So, I tried the udisk2 wrapper, devmon (uses udevil), by enabling and starting it.
# systemctl enable devmon@<username>.serviceSo, devmon is up and running and it automounts my removable drive upon logging in! But, the friggin' drive is mounted in udisks' mounting scheme (/media/LABEL) and not udisks2 (/run/media/<username>/LABEL). Seeing that the udevil was last built two years ago, I guess it uses udisks' mounting scheme. Grrrr..
I guess I can throw in the towel and reorganize my symlinks accordingly. But, the problem is that KDE's automounter appears to use udisks2's mounting directory scheme and I've been jumping back and forth between the two DE's lately. Furthermore, going to lxqt and using pcmanfm-qt, it also uses udisks, so without udisks, mounted volumes do not appear under "Places". Then again, since devmon starts upon logging before launching any DE, udisks' directory scheme will be used. Might as well edit my symlinks.
Just a quick question. The fstab entry allows me to set the drive's mount directory according to udisks2's directory scheme. Outside fstab's design, is there a reason why it is not a recommend solution here?
Last edited by ssri (2015-02-21 01:22:55)
Offline
Do you have doc or a link to a doc about the lxqt's automounter?
How do you use it?
Could you tell me if lxqt features a system tray please?
Offline
Do you have doc or a link to a doc about the lxqt's automounter?
There appears to be no documentation but here's the source.
How do you use it?
It is a panel widget. It functions like KDE's device notifier, left click brings a small list of devices that can be mounted. To add it to LXQt's panel, right click the panel > Add Panel Widgets > Removable media. Configuration options are really limited: 
Could you tell me if lxqt features a system tray please?
Yes, there's a system tray widget.
Unfortunately liblxqt-mount seems to prefer udisks even though there's code to use udisks2 (see source link).
Last edited by ssri (2015-02-22 16:39:20)
Offline
So, I tried the udisk2 wrapper, devmon (uses udevil), by enabling and starting it.
# systemctl enable devmon@<username>.serviceSo, devmon is up and running and it automounts my removable drive upon logging in! But, the friggin' drive is mounted in udisks' mounting scheme (/media/LABEL) and not udisks2 (/run/media/<username>/LABEL). Seeing that the udevil was last built two years ago, I guess it uses udisks' mounting scheme. Grrrr..
Please follow the instructions in https://wiki.archlinux.org/index.php/Udisks#Devmon which disable udevil's mount functionality, using udisks2 instead.
Mods are just community members who have the occasionally necessary option to move threads around and edit posts. -- Trilby
Offline
Unfortunately liblxqt-mount seems to prefer udisks even though there's code to use udisks2
In fact the lxqt mounter tries first to use udisks2, and only if this is not available, it then tries to use udisks legacy; as shown in 'mount.cpp':
MountManager::MountManager(QObject *parent):
QObject(parent),
mProvider(0)
{
mProvider = new UDisks2Provider(this);
if (!mProvider->isValid())
{
delete mProvider;
mProvider = 0;
mProvider = new UDiskProvider(this);
if (!mProvider->isValid())
{
delete mProvider;
mProvider = 0;
}
}
...After a reboot and login to graphical desktop, do you have something like that:
$ systemctl status udisks2
● udisks2.service - Disk Manager
Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static; vendor preset: disabled)
Active: active (running) since dim. 2015-02-22 10:16:55 CET; 5h 29min ago
Docs: man:udisks(8)
Main PID: 598 (udisksd)
CGroup: /system.slice/udisks2.service
└─598 /usr/lib/udisks2/udisksd --no-debug
févr. 22 10:16:55 arch64 udisksd[598]: udisks daemon version 2.1.4 starting
févr. 22 10:16:55 arch64 systemd[1]: Started Disk Manager.
févr. 22 10:16:55 arch64 udisksd[598]: Acquired the name org.freedesktop.UDisks2 on the system message busie is the name 'org.freedesktop.UDisks2' available?
If not, lxqt mounter will use udisks legacy if available.
As an aside, udisks legacy is deprecated and should be avoided as much as possible.
Thanks for the infos you provided to me in your post.
Last edited by berbae (2015-02-22 15:29:58)
Offline
In fact the lxqt mounter tries first to use udisks2, and only if this is not available, it then tries to use udisks legacy; as shown in 'mount.cpp'
Ideally yes, but it does not appear to be in reality. Here's what happened after I disabled devmon, removed any udev rules I placed for udisks2. So, here goes after rebooting:
Pre-DE login:
$ systemctl status udisks ; systemctl status udisks2
● udisks.service - UDisks
Loaded: loaded (/usr/lib/systemd/system/udisks.service; disabled; vendor preset: disabled)
Active: inactive (dead)
● udisks2.service - Disk Manager
Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:udisks(8)Post-LXQt login:
$ systemctl status udisks ; systemctl status udisks2
● udisks.service - UDisks
Loaded: loaded (/usr/lib/systemd/system/udisks.service; disabled; vendor preset: disabled)
Active: active (running) since Sun 2015-02-22 12:19:15 PST; 30s ago
Main PID: 650 (udisks-daemon)
CGroup: /system.slice/udisks.service
├─650 /usr/lib/udisks/udisks-daemon
├─658 udisks-daemon: not polling any devices
└─723 /sbin/mount.ntfs /dev/sdc1 /media/Music -o rw,nodev,nosuid,uid=1000,gid=100,dmask=0077,fmask=0177,uhelper=udisks
● udisks2.service - Disk Manager
Loaded: loaded (/usr/lib/systemd/system/udisks2.service; static; vendor preset: disabled)
Active: inactive (dead)
Docs: man:udisks(8)févr. 22 10:16:55 arch64 udisksd[598]: udisks daemon version 2.1.4 starting févr. 22 10:16:55 arch64 systemd[1]: Started Disk Manager. févr. 22 10:16:55 arch64 udisksd[598]: Acquired the name org.freedesktop.UDisks2 on the system message busie is the name 'org.freedesktop.UDisks2' available?
If not, lxqt mounter will use udisks legacy if available.
That appears to be the case, as nowhere in my journal log does it state udisksd being started. Checking loginctl, my session contains 'Remote=no' and 'Active=yes', duh. It appears that d-bus is not starting udisksd by demand. The wiki also suggests to configure policykit manually if my session is not active or present, which isn't the case. Furthermore, that wiki tip mentions and offers a policykit configuration to be placed under its respective ./rules.d. However, it deals with the storage group. Hasn't storage been deprecated with the advent of systemd and logind or rather subsumed?
As an aside, udisks legacy is deprecated and should be avoided as much as possible.
Hence the purpose of this thread (see post #5)
Thanks for the infos you provided to me in your post.
Sure anytime. Rather than deal with this udisks/udisks2 mess wrt LXQt, I'm thinking about renabling devmon and modifying udevil.conf to set mountpoints at /run/media/$User.
Last edited by ssri (2015-02-22 22:03:25)
Offline
Not sure if you still have this issue, but PCManFM requires gvfs and gvfs-afc (they're optional dependencies) for mounting removable devides, and gvfs itself uses udisks2.
PCManFM properly uses udisks2 on my install. And so does the removable media widget.
Last edited by polomi (2015-03-01 20:14:18)
Offline