Version: (using KDE 4.1.3) Installed from: SuSE RPMs In KDE 4 drives (DVD, SD-Cards, USB-Sticks) are not automatically mounted, so that they can be adressed directly over the Desktop-Icon.First you have to open the drive content with Doplphin, which leads to automounting the drives.Also the Eject-Button of the DVD-Drive is out of function, while the drive is still mounted (I have to Eject with Dolphin). I would prefer, if drives would automatically be mounted (like in KDE 3.5) and accessible by the Desktop (without using Dolphin first). Also pressing the EJECT-Button should automatically unmount the drive of open the hardware-drive. Thanks Terranarion!
> I would prefer, if drives would automatically be mounted (like in KDE 3.5) KDE 3.5 does not mount automatically the drives when they are plugged/inserted, but you always have to double click on their icon or tell to mount them in the "new media" dialog it popups. > accessible by the Desktop (without using Dolphin first) There is a "Device Manager" widget for Plasma, much like KDE 3.5's mediamanager applet for the panel.
> KDE 3.5 does not mount automatically the drives when they are plugged/inserted Really?! I remembered otherwise, but I used 3.5 only for a short period of time, so probably you are right with that. I think I know the widget you mentioned.But it would imho be much more intuitive and easier, if the drives would automatically be mounted, so that their contents are simply accessible by klicking on Desktop -> Drive XY. Interestingly, drives are not unmounted by klicking the Eject-Button at my Harware-Drive, neither does the Disk eject (first I have to unmont with Dolphin).Thats imho also not very comfortable. ;)
> KDE 3.5 does not mount automatically the drives when they are plugged/inserted In KDE 3.5.x clicking on the mount tab in device options for specific drives - there is a check box for "automount" every time the device is inserted.
(In reply to comment #1) > There is a "Device Manager" widget for Plasma, much like KDE 3.5's mediamanager > applet for the panel. > Which requires me to start Dolphin to actually mount device. I have no use for Dolphin at all; what I'd expect is plain "Mount" option. Of course even better would be to make it freely comfigurable (which action start for which media).
*** This bug has been confirmed by popular vote. ***
It is a really good news that this is being confirmed as a bug. It is really annoying when you start you pc and amarok is not able to find your collection because you didn't mounted manually your external drive! And it is useless to mention non-kde4 apps which requires you to mount the dirve manually either!
I've just been bitten by this bug as well! Music collections on external hard-drives are a pretty common use case these days.
I searched not long ago for a way to mount a device to a specific mount point using. I found how to do so and while I was searching I discovered an HAL flag which tells the higher layers if a device should be automounted or not. This property is "storage.automount_enabled_hint". I believe KDE should use it and provide a way to configure a mount point and the automount flag for any device as there is no GUI for HAL I believe it would be a first. Should the use of the flag be a part of Solid and the GUI added to devicenotifier or should both be in devicenotifier ? If somebody is willing to code this I would be happy to help. For the specific mount point thing you can see what I wrote about it on the Arch Wiki: http://wiki.archlinux.org/index.php/HAL#Mount_a_device_to_a_specific_mount_point
It would be nice to be able to have a default preference of whether to automount a newly plugged in device, but also assign a preference to every specific device. E.g. I don't like it it to automount CDs (everything starts shaking) and most USB storage devices but I would like it to automount a specific USB stick. As far as I know every USB device has a unique ID that could be used for this. I think HAL is perfectly capable of handling this, so all that is needed is a UI. Also the "Recently Plugged Devices" notifier really needs an option to mount a device WITHOUT opening dolphin.
Also the "Recently Plugged Devices" notifier really needs an option to mount a device WITHOUT opening dolphin. Yes, I think even without the automount behavior this would be a big help.
+1 for allowing to change the default policy +1 for adding the "mount" button" I don't like when someone thinks they know better what is best for me, that's why I use KDE (and GNU/Linux, of course). Let's stay this way... BTW, I'm thinking about the time (person-hours) we spent on this bug... We could have coded the patch already, and proposed it here :) Cheers, Marko
+1 for adding the mount option from the "New Device Notifier" pop-up. +1 for having an automount option for specific devices. The first time I used it, that's exactly what I expected and I even tried to right-click the new drive expecting to select Mount. I was okay with it for a while as I used Dolphin as my default file browser but I've run into a few problems with it and I've switched to Krusader. Now, having to open Dolphin and close it a second later in order to mount my USB stick is quite annoying and feels very windozesqe because there are no options to change it. Dax
openSUSE had this as downstream patch for KDE 3.5. If one right-clicked the device and opened it's properties there was a "mount options" tab that allowed to set: - path where it was mounted - charset to use - whether to mount it with sync or async (not sure those are the right terms, one owuld write to the stick immediately, the other wait) - automount on/off for that stick I can understand that the default remains not to automount because that might be a security issue and cause issues, if one has more than one user working on that computer, i.e. the computer would not know which user the stick belongs to. However the latter is not that important for the many users that use their computer just on their own. So if they set-up the stick to automount the first time they plug it in, it's their own fault if it causes issues later on when other users are logged in as well.
*** This bug has been marked as a duplicate of bug 164053 ***