Automounting of additional partitions on local hard disks not working in Karmic - regression?

Ari Torhamo ari.torhamo at
Wed Nov 4 10:03:43 GMT 2009


I have three local hard disks on my system and one or more ext
partitions on all of them. All of these partitions used to automount
during boot in previous Ubuntu versions. Now, in Karmic, I always have
to give my password before accessing them for the first time after

Am I experiencing a bug, or is this an intentional change of behaviour?
If it's intentional, it's into worse from my point of view. For example,
if I forget to mount the partitions before starting Transmission, it
won't see the unfinished files. When I mount the partitions,
Transmission want's to scan through all the files to see if they are
good. This isn't fun, when I happen to have 30 GB of unaccomplished
files :-/

Another problem is that my back-up software wont do the scheduled
back-ups unless the partitions are mounted, because it can't see the
back-up folders. So now I should always remember to click on the
partition icons before starting to do other things with my computer. 

I just spent a few hours and found out how to get the partitions to
mount automatically (I
edited /usr/share/polkit-1/actions/org.freedesktop.consolekit.policy).
Many less experienced users won't be able to find the solution at all.
Instead they'll just try to remember to manually mount the partitions
every time the system has booted to avoid the mentioned problems. I
found several people experiencing the same, but no information on
whether this is an intentional change made to Karmic. There are a couple
of bug reports in Launchpad which are close to this, but not quite
similar. I didn't want to file another report before asking other's
whether they are experiencing this behaviour, whether they know the
behaviour is intentional and whether there's a good reason for it.


Ari Torhamo

More information about the sounder mailing list