Since upgrading to SuSe 11.4 I’ve noticed that whenever I insert removable media I now get asked for root authentication before mounting! This is a real pain and I cant find any way to change this - anyone have any ideas??
Thanks
Chris
On 09/09/2011 10:16 AM, shadychris wrote:
>
> Since upgrading to SuSe 11.4 I’ve noticed that whenever I insert
> removable media I now get asked for root authentication before mounting!
> This is a real pain and I cant find any way to change this - anyone
> have any ideas??
i’m not seeing that here so one a few things must have occurred (this is
probably not an exhaustive list of the possibilities):
-faulty upgrade (which approved/supported way did you follow,
http://tinyurl.com/35p966c or http://tinyurl.com/6kvoflv?) for example,
there have been changes with HAL, how it works or does not (i do not
remember exactly) with USB/etc…perhaps something got left in the
corners when you upgraded, if you didn’t correctly?
-changes made to file/file system security (some or all of AppArmor,
PolicyKit or YaST > Security & Users or . . .??)
-inadvertent file system configuration corruption (had any hard resets
or other event which might corrupt config files?)
-maybe you have mixed in some incompatible software from factory or ?
-maybe you have retained an old, or edited your new fstab?
please show us the terminal output from
df -h
cat /proc/partitions
cat /etc/fstab
mount
sudo /sbin/fdisk -l
zypper lr -d
copy/paste the in/output back to this thread using the instructions
here: http://goo.gl/i3wnr
–
DD
Caveat
openSUSE®, the “German Automobiles” of operating systems
Hi,
Thanks for replying.
I didn’t use the ‘live’ method, but rather downloaded the media and ran the upgrade from the verified DVD.
I have read of others experiencing the same problem and answers point to Policy Kit being the culprit - but the resolutions offered seem extremely complex.
Here are the outputs (with a usb stick mounted)
cforrest@PHY-Katana:~> df -h
Filesystem Size Used Avail Use% Mounted on
rootfs 158G 24G 127G 16% /
devtmpfs 3.9G 328K 3.9G 1% /dev
tmpfs 4.0G 1.2M 4.0G 1% /dev/shm
/dev/md1 158G 24G 127G 16% /
/dev/md2 298G 4.7G 278G 2% /free
/dev/sdc1 230G 88G 130G 41% /public
/dev/md3 230G 78G 141G 36% /backup
/dev/sdd1 3.9G 56M 3.8G 2% /media/482D-9E3D
cforrest@PHY-Katana:~> cat /proc/partitions
major minor #blocks name
8 0 488386584 sda
8 1 4200966 sda1
8 2 167774827 sda2
8 3 316408207 sda3
8 16 488386584 sdb
8 17 4200966 sdb1
8 18 167774827 sdb2
8 19 316408207 sdb3
8 32 244198584 sdc
8 33 244188000 sdc1
8 64 244198584 sde
8 65 244196001 sde1
8 80 244198584 sdf
8 81 244196001 sdf1
9 0 4200952 md0
9 1 167774752 md1
9 2 316408068 md2
9 3 244195864 md3
8 48 4030464 sdd
8 49 4030448 sdd1
cforrest@PHY-Katana:~> cat /etc/fstab
/dev/md0 swap swap defaults 0 0
/dev/md1 / ext4 acl,user_xattr 1 1
/dev/md2 /free ext4 defaults 1 2
/dev/disk/by-id/ata-WDC_WD2500SD-01KCC0_WD-WCAL77606627-part1 /public ext3 defaults 1 2
proc /proc proc defaults 0 0
sysfs /sys sysfs noauto 0 0
debugfs /sys/kernel/debug debugfs noauto 0 0
usbfs /proc/bus/usb usbfs noauto 0 0
devpts /dev/pts devpts mode=0620,gid=5 0 0
/dev/md3 /backup ext3 defaults 1 2
cforrest@PHY-Katana:~> mount
devtmpfs on /dev type devtmpfs (rw,relatime,size=4056664k,nr_inodes=1014166,mode=755)
tmpfs on /dev/shm type tmpfs (rw,relatime)
devpts on /dev/pts type devpts (rw,relatime,gid=5,mode=620,ptmxmode=000)
/dev/md1 on / type ext4 (rw,relatime,user_xattr,acl,barrier=1,data=ordered)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
debugfs on /sys/kernel/debug type debugfs (rw,relatime)
/dev/md2 on /free type ext4 (rw,relatime,barrier=1,data=ordered)
/dev/sdc1 on /public type ext3 (rw,relatime,errors=continue,commit=15,barrier=1,data=ordered)
/dev/md3 on /backup type ext3 (rw,relatime,errors=continue,commit=15,barrier=1,data=ordered)
securityfs on /sys/kernel/security type securityfs (rw,relatime)
fusectl on /sys/fs/fuse/connections type fusectl (rw,relatime)
/dev/sdd1 on /media/482D-9E3D type vfat (rw,nosuid,nodev,relatime,uid=1000,gid=100,fmask=0022,dmask=0077,codepage=cp437,iocharset=iso8859-1,shortname=mixed,showexec,utf8,errors=remount-ro,uhelper=udisks)
cforrest@PHY-Katana:~> sudo /sbin/fdisk -l
root's password:
Disk /dev/sda: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0009f03f
Device Boot Start End Blocks Id System
/dev/sda1 * 63 8401994 4200966 fd Linux raid autodetect
/dev/sda2 8401995 343951649 167774827+ fd Linux raid autodetect
/dev/sda3 343951650 976768064 316408207+ fd Linux raid autodetect
Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0007c4ac
Device Boot Start End Blocks Id System
/dev/sdb1 63 8401994 4200966 fd Linux raid autodetect
/dev/sdb2 * 8401995 343951649 167774827+ fd Linux raid autodetect
/dev/sdb3 343951650 976768064 316408207+ fd Linux raid autodetect
Disk /dev/sdc: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0008fc0c
Device Boot Start End Blocks Id System
/dev/sdc1 16065 488392064 244188000 83 Linux
Disk /dev/sde: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00056fe9
Device Boot Start End Blocks Id System
/dev/sde1 63 488392064 244196001 fd Linux raid autodetect
Disk /dev/sdf: 250.1 GB, 250059350016 bytes
255 heads, 63 sectors/track, 30401 cylinders, total 488397168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0f4a2415
Device Boot Start End Blocks Id System
/dev/sdf1 63 488392064 244196001 fd Linux raid autodetect
Disk /dev/md0: 4301 MB, 4301774848 bytes
2 heads, 4 sectors/track, 1050238 cylinders, total 8401904 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md0 doesn't contain a valid partition table
Disk /dev/md1: 171.8 GB, 171801346048 bytes
2 heads, 4 sectors/track, 41943688 cylinders, total 335549504 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md1 doesn't contain a valid partition table
Disk /dev/md2: 324.0 GB, 324001861632 bytes
2 heads, 4 sectors/track, 79102017 cylinders, total 632816136 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md2 doesn't contain a valid partition table
Disk /dev/md3: 250.1 GB, 250056564736 bytes
2 heads, 4 sectors/track, 61048966 cylinders, total 488391728 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Disk /dev/md3 doesn't contain a valid partition table
Disk /dev/sdd: 4127 MB, 4127195136 bytes
16 heads, 32 sectors/track, 15744 cylinders, total 8060928 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000
Device Boot Start End Blocks Id System
/dev/sdd1 * 32 8060927 4030448 b W95 FAT32
cforrest@PHY-Katana:~> zypper lr -d
# | Alias | Name | Enabled | Refresh | Priority | Type | URI | Service
--+------------------------------------+------------------------------------+---------+---------+----------+----------+------------------------------------------------------------------------------------------+--------
1 | 11.4 | 11.4 | Yes | Yes | 99 | rpm-md | ftp://download.nvidia.com/opensuse/11.4/ |
2 | PK_TMP_DIR | PK_TMP_DIR | Yes | Yes | 99 | plaindir | dir:///var/tmp/TmpDir.UnoLbH |
3 | openSUSE-11.4-11.4-0 | openSUSE-11.4-11.4-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-PIONEER_DVD-RW_DVR-116D |
4 | openSUSE-11.4-NonOSS-Add-on_11.4-0 | openSUSE-11.4-NonOSS-Add-on 11.4-0 | Yes | Yes | 99 | yast2 | http://www.mirrorservice.org/sites/download.opensuse.org/distribution/11.4/repo/non-oss/ |
5 | openSUSE-11.4_11.4-0 | openSUSE-11.4 11.4-0 | Yes | Yes | 99 | yast2 | http://www.mirrorservice.org/sites/download.opensuse.org/distribution/11.4/repo/oss/ |
6 | repo-source | openSUSE-11.4-Source | No | Yes | 99 | NONE | http://download.opensuse.org/source/distribution/11.4/repo/oss/ |
7 | update | update | Yes | Yes | 99 | rpm-md | http://www.mirrorservice.org/sites/download.opensuse.org/update/11.4/ |
On 09/09/2011 02:36 PM, shadychris wrote:
>
> 2 | PK_TMP_DIR | PK_TMP_DIR | Yes | Yes | 99 | plaindir | dir:///var/tmp/TmpDir.UnoLbH |
> 3 | openSUSE-11.4-11.4-0 | openSUSE-11.4-11.4-0 | Yes | No | 99 | yast2 | cd:///?devices=/dev/disk/by-id/ata-PIONEER_DVD-RW_DVR-116D |
based on my questions you answered (few) and the system output you gave
(all) i’m pretty much stumped…hopefully someone else will chime in
here, with a good answer…or better question…
but, i do see what i think is evidence of an aborted or errored out
install or update…that repo #2 (PK_TMP_DIR) shouldn’t normally be
there…no telling how large it is, i’d suggest you use YaST > Software
Repository to delete repo #2 and enable the ability for /tmp to be
emptied on every boot, see the how-to here: http://tinyurl.com/yzmzp5b
and, if while in YaST you disable repo #3 it won’t ask you to load the
dvd…of course, instead you would have to download things on the disk
again, if asked for…so…
oh, and it is interesting (to me) that you don’t have packman
enabled…but, that is perfectly ok…
hope for a real guru to happen along with good info for you…
–
DD
openSUSE®, the “German Automobiles” of operating systems
Well thanks for your time in trying - and also the useful tip for getting tmp to empty at boot.
I have no idea how or where the PK_TMP_DIR repo came from - it wasn’t there when I first set the other repos up!
As I mentioned it does seem quite a few people are having the same problem - the authentication window that opens also has a link under the details tab http://udisks.freedesktop.org/wiki/
however that is a ‘405 not found’ page
After doing a google for "suse 11.4 - authentication is required to mount the device " I found this https://bbs.archlinux.org/viewtopic.php?id=112465 but when I checked my polkit file it seems it is OK.
I have also checked Appamor - something I have never used or configured - it was set to enabled in the AA control centre so I disabled it but still no change - root password is still needed to mount a usb drive, or as I have just discovered also optical discs. Further googling on this reveals that this is also affecting users with the USB mount problem and also means it is all but impossible to burn optical discs… what a nightmare!! Why oh why did I select to upgrade instead of my usual route of fresh install… 
On 09/09/2011 03:56 PM, shadychris wrote:
> I have no idea how or where the PK_TMP_DIR repo came from - it wasn’t
> there when I first set the other repos up!
no, it is a left over from a failed install or update…it the process
completes then both the stuff in tmp and the listing in the repos is
removed by yast…
> Why oh why did I select to upgrade instead of my usual
> route of fresh install…
as mentioned i’m not seeing the problem here, and i did what i usually
do (backup of data and a full format of /, /home and /swap and complete
install…then build up the apps and finally merge in the data…
that takes a little longer but it usually results in
stable/predictable/reliable from day one. (which is what i like)
–
DD
Caveat-Hardware-Software-
openSUSE®, the “German Automobiles” of operating systems
Solved!!
Under Yast>Security centre and Hardening>Miscellaneous Settings the file permissions were set to ‘secure’ lowering this setting to ‘easy’ seems to have solved the problem… usb sticks and DVD’s can now be mounted in Dolphin without the annoyance of being asked for root password 
On 09/09/2011 06:06 PM, shadychris wrote:
>
> file permissions were set to ‘secure’ lowering this setting to ‘easy’
> seems to have solved the problem…
happy you found the problem…but, that setting is “easy” in a default
install…so, you might need to find out who or why it was changed…
–
DD
openSUSE®, the “German Automobiles” of operating systems