Talk:Udisks
Udiskie - Window Manager Menu Scripts
[Restoring here the scripts deleted with https://wiki.archlinux.org/index.php?title=Udiskie&diff=next&oldid=248036 without an appropriate discussion. -- Kynikos (talk) 07:00, 14 April 2013 (UTC)]
[Moved from Talk:Udiskie because Udiskie now redirects to Udisks and the following scripts might still be relevant. -- Lahwaacz (talk) 11:38, 27 August 2014 (UTC)]
- Assuming this should be kept, doesn't it belong in the respective window manager articles? -- Alad (talk) 00:45, 17 January 2016 (UTC)
- It's always the same dilemma with cross-software content, I think arguments can be brought to support both sides, and I'd be completely neutral; maybe if restored in the respective WM articles, their sections could be linked from here, or vice versa.
- Regarding the keep or delete problem, I don't like deleting original work, but since I haven't tested the scripts I won't restore them either. I don't mind if they stay here until somebody tests them and moves them back to an article if working, or deletes them if broken.
- — Kynikos (talk) 03:33, 18 January 2016 (UTC)
For convenience, you can add a script to the menu in some window managers to allow for easy access and control of removable media.
Openbox
Here's an openbox menu script that offers a slight variation on the WindowMaker example below:
#!/bin/bash # An openbox menu for removable media (requires udiskie). # # This script will generate sub-menus for any device mounted # under /media. You can browse the device in a file manager or # unmount it. # # It will ignore the "cd", "dvd", and "fl" directories and the U3 # containers found on some windows formatted drives # # By default, this script uses the rox file manager to browse the # media. DIR=$(cd $(dirname "$0") && pwd) SCRIPT=$(basename "$0") NOTIFY="notify-send" FM_CMD="rox" pipemenu() { cd /media echo '<openbox_pipe_menu>' for i in * do if [ "$i" != "*" ] && [[ ! "$i" =~ ^U3|cd|dvd|fl ]]; then echo "<item label=\"Browse $i\">" echo "<action name=\"Execute\">" echo "<execute>$FM_CMD /media/$i</execute>" echo "</action></item>" echo "<item label=\"Unmount $i\">" echo "<action name=\"Execute\">" echo "<execute>$DIR/$SCRIPT unmount /media/$i</execute>" echo "</action></item>" echo "<separator/>" fi done echo "<item label=\"Eject CD/DVD\">" echo "<action name=\"Execute\">" echo "<execute>eject -T</execute>" echo "</action></item>" echo "<item label=\"Remount all\">" echo "<action name=\"Execute\">" echo "<execute>$DIR/$SCRIPT remount</execute>" echo "</action></item>" echo "</openbox_pipe_menu>" } case $1 in unmount) udiskie-umount $2 if mountpoint -q $2; then $NOTIFY "Failed to unmount $2" else $NOTIFY "Unmounted $2" fi ;; remount) killall udiskie udiskie & $NOTIFY "Mounting removable media..." ;; *) pipemenu ;; esac
Window Maker
Create a "Generated Submenu" entry in the root menu.
#!/bin/bash # For a Window Maker menu for removable media. # # This script will generate sub-menus for any device mounted # under /media. You can browse the device in a file manager or # unmount it. # # It will ignore the "cd", "dvd", and "fl" directories. # # It uses "emelFM2" file manager to browse the media. cd /media echo \"Media\" MENU for i in * do if ["$i" != "*" ] && [ "$i" != "cd" ] && [ "$i" != "dvd" ] && [ "$i" != "fl" ] then echo \"Browse $i\" EXEC \"emelfm2 -1 \'/media/$i\'\" fi done for i in * do if ["$i" != "*" ] && [ "$i" != "cd" ] && [ "$i" != "dvd" ] && [ "$i" != "fl" ] then echo \"Unmount $i\" EXEC \"udiskie-umount \'/media/$i\'\" fi done echo \"Eject Disc\" EXEC \"eject --traytoggle\" echo \"Media\" END
udisk2 with NTFS support
Maybe is a bug from KDE or the udisk pack, but for testing is quite simple.
install archlinux using the official guide
then
pacman -Syu
pacman -S plasma-meta kate dolphin konsole sddm
(just because i do use kde-plasma, didn't check others)
edit sddm options as per wiki instructions, activate it, and restart machine, log to kde, and try to access any ntfs volume. It won't access it.
check the joutnalctl log and you will find the udisk error.
Try the fix #2. it will work. And trying the fix #1 (install ntfs-3g) will work too, but operations via FUSE will be quite slower under kde-plasma.
It seems a bug with udisk2. i've seen it with xfs file systems, but i don't have any system here to check. Stargeizer (talk) 02:50, 11 February 2025 (UTC)
- I have no issues with solid/udisks2 mounting NTFS volumes without ntfs-3g and without a
/etc/udisks2/mount_options.conf
file. - Are you sure you're seeing the exact errors as in udisks#NTFS mount failing? NTFS3 supports
windows_names
since Linux 6.2. Is your system up to date? - -- nl6720 (talk) 10:32, 11 February 2025 (UTC)
- Yes, freshly installed system as of yesterday.
- I'm not the only one tho. But then again, it doesn't seems to happen to everyone for some reason.
- https://bugs.kde.org/show_bug.cgi?id=445468
- (last comment is me, also asking for confirmation)
- it may well be a kde bug, tho. I cannot reformat my machine again for now.
- Is this bug still active?
- There are plans to enabling CONFIG_NTFS_FS=m (alias for read only ntfs3 mount for linux>=6.9 for mount command) for kernel packages, and splitting ntfsprogs part from ntfs-3g.
- Will those change produce negative changes? oech3 (talk) 06:21, 29 April 2025 (UTC)
After some hours of sleep, i do realize that i might have been too trigger happy to edit the wiki, with a solution for a problem before checking if the problem is ocurring for everyone rather than ocurring for only some users, and i do apologize for that. If you think that this doesn't belong here, feel free to rollback the canges, i don't mind. Stargeizer (talk) 13:29, 11 February 2025 (UTC)
- AFAIK all the involved parts (Linux, util-linux, udisks2) should have already done their part to fix this issue. Unless you're using a kernel older than 6.2, it makes no sense to get an error about
windows_names
. I suggest you create a topic in the forums. Perhaps someone there will be able to help you get to the bottom of this. -- nl6720 (talk) 11:40, 13 February 2025 (UTC)
mount_options.conf or mount.options.conf?
This paragraph:
/etc/udisks2/mount.options.conf.example
to /etc/udisks2/mount.options.conf
But the next line says use /etc/udisks2/mount_options.conf
Are they both valid? Latios (talk) 13:30, 2 September 2025 (UTC)
- No, it's a typo, should be
mount_options
. [1] - Hanabishi (talk) 13:45, 2 September 2025 (UTC)