Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#6205 - eject doesn't handle mountpoints containing spaces properly
Attached to Project:
Arch Linux
Opened by Apollon Oikonomopoulos (apoikos) - Saturday, 13 January 2007, 09:39 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 13 January 2007, 21:12 GMT
Opened by Apollon Oikonomopoulos (apoikos) - Saturday, 13 January 2007, 09:39 GMT
Last edited by Roman Kyrylych (Romashka) - Saturday, 13 January 2007, 21:12 GMT
|
Detailseject uses /proc/mounts to determine a given device's mountpoint. However, whitespaces are replaced with '\040' in /proc/mounts, which leads to eject trying to unmount an invalid mountpoint (e.g. "/media/a\040mountpoint" instead of "/media/a mountpoint". This is especially annoying combined with the default hal + pmount behaviour of mounting devices according to their volume labels, which may contain whitespaces (especially in the case of CDs). The solution and the relevant patch was given by the gentoo developers here: http://bugs.gentoo.org/151257. I've tried it and sofar it works fine.
|
This task depends upon
Comment by Roman Kyrylych (Romashka) -
Saturday, 13 January 2007, 21:13 GMT
I confirm this bug too.