I would like to turn off the automounting feature in Artix as I have some external hard drives that I plug in to work with at times. Currently every time a usb device is plugged in it automounts in /run/media/****, I wish to manually mount these drives to my own choice of mount point if possible.
Thank you!
https://forum.artixlinux.org/index.php/topic,1923.0.html
Thanks for the reply, I have already searched the forum and the Arch wiki without success. Is there any other information that you require?
Artix openrc is the system.
Read the article I linked. You supplied virtually no information. For example, I have installed Artix from base ISO, don't use a DE, and I don't have my media automounted.
There is nothing actually 'wrong' with my system, which is why I don't think any logs would help in this case. I would like to know which piece of software handles automounting, I am quite happy to research how to turn it off if I know where to look. :D
The Arch wiki is not helpful as it uses systemd to mount devices.
There is no default "automount" mechanism in Artix. You apparently installed something that automounts drives for you. It could be a million different things. There's no way for any of us to know.
Thank you for that, I thought that it happened immediately after install of the openrc- lxqt iso, but I could be wrong about that, I will check with another fresh install.
I have just downloaded the latest lxqt-openrc iso, booted in live mode, then inserted a usb stick and it was immediately mounted automatically....
I am sorry to have to ask again, but does anyone here know what causes this behaviour please?
Thanks in advance for any pointers.
It most likely is some software that comes with lxqt. DEs all tend to do that kind of thing.
I agree, I love Artix but so far have been unable to do without a DE by building from the base iso. I have partially succeeded in installing Fluxbox but have trouble in getting the system to shutdown rather than just log out. I only use LXQT because it is the least bloated of the full isos. I will keep trying though ;D
I have found the culprit on the automount problem and it was pcmanfm-qt, I tried to alter the config to stop automounting but was unable to. Removing pcmanfm-qt cured the 'problem' for me, and I can either install another file manager or just stick with the excellent midnight commander.
Thanks for the information that you use LXQt and PCManFM-Qt.
Automount can be configured in the applications menu of PCManFM:
Go to -> Preferences -> Volume and disable or enable items to your need.
Thanks for the reply, I was aware of that and had previously tried it without apparent success, however, I have tried again on another installation and you are right! I must have missed some config or other on the previous attempt, apologies for troubling everyone.
That is not the answer
pcmanfm isn't automounting anything. It is using a freedesktop service to do that and that service needs to be turned off somehow.
No doubt but it there are only so many of them and it is nearly impossible to do an install without them being installed. The GIMP has a gvfs dependency. There is no reason to make it a mandatory dependency, but the package doesn't seem to care about that. Meanwhile, automounting is out of control.
flatbush:[ruben]:~$ sudo rc-status
Runlevel: default
syslog-ng [ started 00:18:39 (0) ]
acpid [ started 00:18:39 (0) ]
cronie [ started 00:18:39 (0) ]
dbus [ started 00:18:45 (0) ]
dhcpcd [ started 00:18:39 (0) ]
net.eth0 [ started ]
netmount [ started ]
sshd [ started 00:18:39 (0) ]
cupsd [ started 00:18:33 (0) ]
lxdm [ started ]
alsasound [ started ]
local [ started ]
agetty.tty1 [ started 00:18:13 (0) ]
agetty.tty2 [ started 00:18:13 (0) ]
agetty.tty3 [ started 00:18:13 (0) ]
agetty.tty4 [ started 00:18:13 (0) ]
agetty.tty5 [ started 00:18:13 (0) ]
agetty.tty6 [ started 00:18:13 (0) ]
Dynamic Runlevel: hotplugged
Dynamic Runlevel: needed/wanted
xdm-setup [ started ]
avahi-daemon [ started 00:18:33 (0) ]
Dynamic Runlevel: manual
openrc-settingsd [ started ]
flatbush:[ruben]:~$
where is the automounter?
@mrbrklyn , please don't:
- Necropost in a thread last active in July 2021 (9 months ago). Open a new thread instead.
- Post multiple times in succession. You can use the More... -> Modify menu item in the bottom right part of the post or the Quick Edit button to edit your post instead.
udisks (https://wiki.archlinux.org/title/Udisks), or more precisely, the daemon
udisksd, is responsible for automounting. It is part of the package
world/udisks2 and required by
gvfs, so any other package depending on
gvfs automatically pulls
udisks2 for installation. The linked article gives more details about udisks.
Also see:
man udisks udisksctl
P.S: If you want as little as possible to have with poetterware such as dbus, udisks, polkit and so on, I recommend what I'm using myself: no-DM (https://wiki.archlinux.org/title/Xinit#Autostart_X_at_login), no-DE, WM-only GUI. I use dwm (https://dwm.suckless.org/). I also prefer to mount disks manually, from the command line (I also use st (https://st.suckless.org/)).
Thank you. FWIW - it is the GIMP that is requiring gvfs and I can't seem to remove the package with pacman without removing the gimp and I need the gimp. FWIW, I am using wmaker . My environment doesn't require this. It is actually the program that theoretically has existed for decades before potterware by 20 years or was created before Leonard was an adult.
I only want things to mount when I use the mount command, especially on my servers and workstations.
Unknown command `stop'
Usage:
udisksctl COMMAND
Commands:
help Shows this information
info Shows information about an object
dump Shows information about all objects
status Shows high-level status
monitor Monitor changes to objects
mount Mount a filesystem
unmount Unmount a filesystem
unlock Unlock an encrypted device
lock Lock an encrypted device
loop-setup Set-up a loop device
loop-delete Delete a loop device
power-off Safely power off a drive
smart-simulate Set SMART data for a drive
turning it off seems to no not an option
If you read the linked article, and the output of
udisksctl itself (command summary), more closely, you will see that you can't "stop" it. You can
pkill udisksd as root, but it will come back when requested by the applications which require it as it is
activated through dbus.Read what I posted more carefully.
I did read it and I also read that this thread is marked solved when it is not solved. I appreciate the help. I don't appreciate the sarcasm and ridicule.
Reading docs is NOT enough for learning. It requires collaboration and discussion and analysis. And frankly, docs are sometimes, if not often, wrong.
What you are saying, if I understand you correctly, is that it can't be controlled it can only be removed because core applications are setting it off and they would all have to be recompiled without the dependencies. That is what the man pages seem to say as well.
So all these would have to go
Packages (23) akonadi-contacts-21.12.3-1 digikam-7.6.0-1
ffmpegthumbs-21.12.3-1 gimp-2.10.30-2 grantleetheme-21.12.3-1
gvfs-1.50.0-1 kaccounts-integration-21.12.3-1 kamera-21.12.3-1
kcmutils-5.92.0-1 kdeclarative-5.92.0-1 kio-5.92.0-1
knewstuff-5.92.0-2 knotifyconfig-5.92.0-1 kparts-5.92.0-1
kpimtextedit-21.12.3-1 libakonadi-21.12.3-2 libkleo-21.12.3-2.1
lxqt-panel-1.0.0-1 lxqt-powermanagement-1.0.0-1
okular-21.12.3-1 purpose-5.92.0-1 solid-5.92.0-1
udisks2-2.9.4-1
Meanwhile, up until now I have been running both the gimp and okular without this problem. What if I just remove it with rm?
So one solution to make this better is to remove gvfs
that required swapping out the gimp
yay -S gimp-stripped
sudo pacman -R gvfs
That doesn't get rid of disks2 but it is much cleaner and better.
The documentation for most free software is extensive and correct. Such is the case for udisks as well. Read it, understand what is udisks and its general mode of operation, then either accept it for what it is or uninstall it along with all the programs which require it, such as gimp. The command
pactree -r udisks2
can be used to get a dependency tree of that package.
Since the original question seems to be solved, I will lock this. Feel free to create another thread if you have another issue.
Update 20220403: gvfs has been moved to optional dependencies (https://forum.artixlinux.org/index.php/topic,3865.msg25014.html#msg25014).