Bugzilla – Bug 201648
USB Mass Storage devices no longer automount
Last modified: 2006-10-15 18:25:22 UTC
When 10.1 was first released, the USB MS automount feature worked fine. In my case, inserting a CF memory card into an external reader device would cause the card to be recognized and mounted at /media/NIKON_D70S since it is a camera card. After doing all of the recent updates of the product, including to KDE 3.5.4, this feature no longer works. Now the card is recognized, but no longer automounts. It *can* be mounted by root and it then works correctly. I have observed this 'breakage' on two different machines both running 10.1 with all updates applied. This may be a duplicate of bug 181845 but I couldn't find a way to add comments to that bug.
That's exactly what happens in my case. I'm using a USB pen drive (the very same gadget I started using with Suse9.0) and it was always working properly. I'm not using KDE or Gnome, but rather is pure X11 windows manager (WindowMaker), thus I don't use all fancy and heavy whistles from rich desktop's system. However, starting with Suse10.1 my flesh pen drive is no longer automatically mounted, although it is recognized and can be mount manual % mount /dev/sdb1 /mnt command is executed. Same device is totally fine on the next laptop of mine (same IBM kind, but with SuSe10.0) Looks like, actually as the bug is dup. of 181845
(In reply to comment #1) > I'm not using KDE or Gnome, but rather is pure X11 windows manager > (WindowMaker) Automount of removable media/volumes is no longer supported without KDE/GNOME since 10.1 or 10.0 .
(In reply to comment #0) > After doing all of the recent updates of the product, including to KDE 3.5.4, > this feature no longer works. Now the card is recognized, but no longer > automounts. It *can* be mounted by root and it then works correctly. What mean "the card is recognized"? Please attach output of lshal and the output generated by this: start lshal --monitor and udevmonitor on an other xterm insert the CF Card in the Reader wait some seconds and attach the output of both
(In reply to comment #2) > (In reply to comment #1) > > I'm not using KDE or Gnome, but rather is pure X11 windows manager > > (WindowMaker) > > Automount of removable media/volumes is no longer supported without KDE/GNOME > since 10.1 or 10.0 . > Seems like you guys are moving towards MS Windows! Cool, very smart! Every system thing has to be done by a window manager and if some suckers aren't willing to use KDE or Gnome - well, it's there own fault. Wow! So, in other words OpenSuse 10.1+ is no longer compatible with other Linuxes and thus, even worst, with other Unixes. Hmm, for the lack of better terms - it's sucks! In my understanding, the future releases will be widening the gap and I think it's a sign for OpenSuse users to start migrating away from Novell's brand! Great! Thanks for the notice!
(In reply to comment #4) > Seems like you guys are moving towards MS Windows! Cool, very smart! Every > system thing has to be done by a window manager and if some suckers aren't > willing to use KDE or Gnome - well, it's there own fault. Wow! Sorry, but only KDE/GNOME are supported desktops and we don't mean autofs with automount. You can install and use ivman if you take a look at SDB: http://en.opensuse.org/SDB:Automount_CD/DVD_with_ivman . > So, in other words OpenSuse 10.1+ is no longer compatible with other Linuxes > and thus, even worst, with other Unixes. Hmm, for the lack of better terms - > it's sucks! > > In my understanding, the future releases will be widening the gap and I think > it's a sign for OpenSuse users to start migrating away from Novell's brand! > Great! Thanks for the notice! Sorry, but I never heared such a complete bullshit. The most other actual distributions do the same as we do in our products.
(In reply to comment #5) > (In reply to comment #4) > > Seems like you guys are moving towards MS Windows! Cool, very smart! Every > > system thing has to be done by a window manager and if some suckers aren't > > willing to use KDE or Gnome - well, it's there own fault. Wow! > > Sorry, but only KDE/GNOME are supported desktops and we don't mean autofs with > automount. You can install and use ivman if you take a look at SDB: > http://en.opensuse.org/SDB:Automount_CD/DVD_with_ivman . YES! This is exactly my point: core system functionality is getting moved to a window manager. It stinks. I just had posted a note on SlashDot and hopefully it makes people think about staying with OpenSuse...
Sorry, but what's your problem? We go with this issue the same way as all other distributions and the major desktops KDE and gnome. This is _no_ SUSE specific behavior. Btw. There was _no_ core system functionality removed.
(In reply to comment #7) > Sorry, but what's your problem? We go with this issue the same way as all other > distributions and the major desktops KDE and gnome. This is _no_ SUSE specific > behavior. > > Btw. There was _no_ core system functionality removed. > Well, I have no problem - thanks for asking. If ALL distros are going like this then it means that Linux starts limiting the users' choices by some hand picked features. basically, it sounds like "if you want to be able to automount USB device you better go with KDE or set some 3rd party package to help under other window managers" It raises two questions: 1) making automounting to be a feature of window manager is wrong and architecturally unsound. 2) what about users who aren't using any X env.? You know, these nerd'ish command line oriented geeks?
Konstantin, would you please use the opensuse mailinglist for your windowmaker problem instead of hijacking this report? Your problem has nothing to do with the initial report because windowmaker does not seem to use hal at all. Why do you refuse reading the article about setting up ivman? Or you might want to suggest using hal to the windowmaket developers - this is state of the art today, not any out-of-tree kernel modules like subfs, what we had before. The Slashdot thing and any MS Windows comparisons will not get your issue resolved faster, better or whatever. And ivman works just fine without any window manager. What you are suggesting here is something like subfs, but this has been dropped for a reason - stuff like this will never make it into the mainline kernel and is therefore unworkable.
(In reply to comment #8) > 2) what about users who aren't using any X env.? You know, these nerd'ish > command line oriented geeks? They can use ivman, automount via autofs, add the needed line to /etc/fstab and can call last but not least the mount command by hand if they are command line oriented ppl. And sorry, but this was the last comment to this kind of useless discussion. I have to work on the real problem of the bug from the initial comment and not to waste my time.
Created attachment 100077 [details] Output of lshal and udevmonitor
Re: Comment #3. By recognized, I mean that the card is seen by the system and designated as /dev/sdg1 (on my sys) but that the USB mounting to /media that used to take place does not happen anymore. This is a change from when 10.1 was first released. /dev/sdg1 *can* be mounted manually, thus the device is known to the system. Have attached the output requested.
I need also the output of lshal from the machine with the CF Card inside after lshal --monitor printed the info about adding the volume. Did you some KDE updates? From which source/repository?
I'm seeing precisely the same behavior as Bruce reported. Inserting a previously automounted SD card no longer works. It stopped working after upgrading from KDE 3.5.1 to KDE 3.5.4 "release 88.1" from http://ftp.gwdg.de/pub/opensuse/repositories/KDE:/KDE3/SUSE_Linux_10.1. Output from "udevmonitor" and "lshal --monitor" follow. Notice that when the dialog box to view the SD card's contents opens, the command executed was "umount" rather than "mount." That doesn't seem right. $ sudo udevmonitor udevmonitor prints the received event from the kernel [UEVENT] and the event which udev sends out after rule processing [UDEV] UEVENT[1160023147.743158] add@/block/sdb/sdb1 <- inserted SD card UDEV [1160023147.995241] add@/block/sdb/sdb1 UEVENT[1160023148.353044] umount@/block/sdb/sdb1 <- dialog to view contents UDEV [1160023148.353725] umount@/block/sdb/sdb1 UEVENT[1160023165.302393] umount@/block/sdb/sdb1 <- Clicked "OK" button UDEV [1160023165.303114] umount@/block/sdb/sdb1 UEVENT[1160023288.372767] remove@/block/sdb/sdb1 <- removed SD card UDEV [1160023288.375665] remove@/block/sdb/sdb1 $ sudo lshal --monitor Start monitoring devicelist: ------------------------------------------------- volume_uuid_3414_7CE5 added <- inserted SD card volume_uuid_3414_7CE5 removed <- removed SD card
Sorry, but updates from this repository are not supported for 10.1. If the volume is detected by HAL and displayed in the output of lshal (search in "lshal | less" e.g. for volume_uuid_3414_7CE5). If everything is correct in HAL this is maybe a KDE problem. If you can reproduce this with current 10.2 Alpha 4/5 version, please reopen the bug and assign to the KDE maintainers.
Quick update: I removed the KDE 3.5.4 from the repo listed Comment #14 and installed the KDE at http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/ and automounting of USB thumb drives and random CDs and DVDs started working again.
As far as I can tell, I do *not* have the repository mentioned in #14 in my Smart setup. I just upgraded to 3.5.5 using Smart and the problem is *not* resolved for me. One reason I haven't commented when asked where I got my upgrade to 3.5.4 is that I DON"T KNOW. With the new update setups of ZEN and Smart and the whole mish-hmash that updating has turned into, it is very hard to tell where any particular update came from and what are good repositories and what are no-no's. It's a zoo out there in update-land.
(In reply to comment #17) > As far as I can tell, I do *not* have the repository mentioned in #14 in my > Smart setup. You have, because that's where KDE 3.5.5 comes from. > I just upgraded to 3.5.5 using Smart and the problem is *not* > resolved for me For smart, please do: smart channel --show in order to find out which repositories you are using. > One reason I haven't commented when asked where I got my > upgrade to 3.5.4 is that I DON"T KNOW. Not good... You should't use repositories you don't know. > With the new update setups of ZEN and > Smart and the whole mish-hmash that updating has turned into, it is very hard > to tell where any particular update came from and what are good repositories > and what are no-no's. It's a zoo out there in update-land. Not a "zoo problem in update-land" because neither smart nor "ZEN" have unsupported repositories in their default setup. Unsupported repositories can get there only if the user adds them on his own. It's really simple, there are exactly three supported repositories for SUSE 10.1: http://download.opensuse.org/distribution/SL-10.1/inst-source http://download.opensuse.org/distribution/SL-10.1/non-oss-inst-source http://ftp.suse.com/pub/suse/update/10.1 And their mirrors, of course. Every other repository is unsupported.
Well gee... I got into 10.1 early on when nothing in the update realm was working. I'd start over and do a fresh install, but then, nothing would work again although maybe by now there is enough documentation to get things fixed ok. Ya gotta admit, it was a real mess during the first month and I guess I'm paying the price.