Bug 439442 – sys-fs/udisks-1.0.4-r3: doesn't detect label and doesn't correctly set mount point permissions

• Status: RESOLVED WORKSFORME
• Product: Gentoo Linux

[Description Amadeusz Żołnowski (RETIRED) 2012-10-23 19:05:04 UTC]

udisks doesn't display device label anymore. I have recently updated udev from sys-fs/udev-171-r8 to sys-fs/udev-194.

$ udisks --show-info /dev/sdc1 | grep label
  label:                       
    label:               

$ sudo blkid /dev/sdc1
/dev/sdc1: LABEL="GOODRAM_APZ" UUID="5AA1-3522" TYPE="vfat"

Another problem is that mount point permissions aren't correctly set anymore:

$ udisks --mount /dev/sdc1 
Mounted /org/freedesktop/UDisks/devices/sdc1 at /media/disk

$ ls -l 
total 4
drwxr-xr-x 2 root root 4096 Jan  1  1970 disk

It has been mounted with regular user but the user cannot write there.

Reproducible: Always

[Comment 1 Amadeusz Żołnowski (RETIRED) 2012-10-23 19:07:05 UTC]

Created attachment 327248 [details]
emerge --info sys-fs/udisks sys-fs/udev

[Comment 2 Amadeusz Żołnowski (RETIRED) 2012-10-23 19:10:59 UTC]

Samuli, I'm CC'ing you, because this directly affects bashmount.  It is where I have noticed the problem in the first place.  Maybe you have an idea what's going on.

[Comment 3 Amadeusz Żołnowski (RETIRED) 2012-10-23 19:34:31 UTC]

It's OK, sorry. udev restart or reboot was required about which I have totally forgot. :-)

[Comment 4 Samuli Suominen (RETIRED) 2012-10-23 20:23:45 UTC]

(In reply to comment #2)
> Samuli, I'm CC'ing you, because this directly affects bashmount.  It is
> where I have noticed the problem in the first place.  Maybe you have an idea
> what's going on.

If bashmount gets a bug, it will be lastrited for still using the obsolete udisks:0 as opposed to maintained udisks:2

As in, udisks:0 is _completely dead codebase_ and if there are unupdated programs that break and is still using it, they will be punted

But I'm glad you solved your problem for now