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#4007 - udev-084-4 breaks USB stick automounting (and possibly more)
Attached to Project:
Arch Linux
Opened by Apollon Oikonomopoulos (apoikos) - Sunday, 19 February 2006, 22:26 GMT
Opened by Apollon Oikonomopoulos (apoikos) - Sunday, 19 February 2006, 22:26 GMT
|
DetailsYou can read the full story on the forum: http://bbs.archlinux.org/viewtopic.php?p=143669
At a glance: line 327 of udev.rules was changed from: BUS=="ide", DRIVER!="ide-cdrom", SYSFS{removable}="1", GOTO="persistent_end" to: BUS=="block", DRIVER!="ide-cdrom", SYSFS{removable}="1", GOTO="persistent_end" which, as far as I understand, refers to all removable block devices.The effect of this is that any USB device plugged in is passed down to HAL without any partition information at all, thus preventing user-space applications like ivman and KDE mediamanager from mounting the devices. It should be noted that all devices nodes are created correctly (including those of the partitions), it's just that HAL doesn't know anything about partitions. Reverting the change seems to resolve the issue, but I'm not sure it doesn't break anything else. |
This task depends upon
this rule is only a filter for the persistent stuff, if it does apply it doesn'T run the persistent part, more it is not doing.