Announcement

**GreyGeek** · Sep 14, 2010, 10:22 AM

Re: Lucid permissions problems for usb

Let's check a couple of things.

First, with the USB stick plugged in paste the contents of the fstab file in your next mgs (did it change? It shouldn't.)

Secondly, while it is plugged in do "df -aT" in a Konsole and report that. That will tell me what type of connection your usb stick created. Snowhog encountered your problem on a USB HD drive but his fix may apply in your case. The thread is here.

Third, make sure you are a member of the plugdev group by using Kuser. (Don't change anything if you are, but add yourself to that group if you are not already in it.)

You, or a kernel update, may have corrupted the udev rules and reinstalling udev may fix matters.

Udev is a collection of tools and a daemon to manage events received from the kernel and deal with them in user-space. Primarily this involves creating and removing device nodes in /dev when hardware is discovered or removed from the system. Udev is explained here.

Events are received via kernel netlink messaged and processed according to rules in /etc/udev/rules.d and /lib/udev/rules.d, altering the name of the device node, creating additional symlinks or calling other tools and programs including those to load kernel modules and initialise the device.

Or, since HAL is still working, you may want to consider installing pmount.

pmount is a wrapper around the standard mount program which permits normal users to mount removable devices without a matching /etc/fstab entry. .....

This package also contains a wrapper "pmount-hal" which reads some information like device labels and mount options from hal and passes them to pmount. Install the package "hal" if you want to use this feature.
....

**oshunluvr** · Sep 14, 2010, 03:52 PM

Re: Lucid permissions problems for usb

And, by the way, this 'he' is a 'she'!

Sorry, I assumed "Bernard" rather than "Bernice" - I humbly beg forgiveness

Anyway, Bernie (ette!

) humor me once more by checking the contents of /media again before and after plugging in your usb stick. Also, open a terminal and type dmesg |tail -n 10 immediately after plugging it in.

**bernieszu** · Sep 15, 2010, 02:56 AM

Re: Lucid permissions problems for usb

Thanks Greygeek and Oshunluvr,

Sorry for this long post, but I think it's best to work through your suggestions step by step and post the results.

Greygeek,

Your first suggestion:

fstab contents with no usb in
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sda1 :
UUID=948fb0d0-7875-4137-8365-aff054b7c890 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# Entry for /dev/sda5 :
UUID=21d2d5ee-52c7-4166-960c-6b4ef6b12aac none swap sw 0 0
/dev/hda /media/cdrom0 auto user,atime,noauto,rw,dev,exec,suid 0 0

fstab contents with usb in
# /etc/fstab: static file system information.
#
# -- This file has been automaticly generated by ntfs-config --
#
# <file system> <mount point> <type> <options> <dump> <pass>

proc /proc proc defaults 0 0
# Entry for /dev/sda1 :
UUID=948fb0d0-7875-4137-8365-aff054b7c890 / ext3 nouser,defaults,errors=remount-ro,atime,auto,rw,dev,exec,suid 0 1
# Entry for /dev/sda5 :
UUID=21d2d5ee-52c7-4166-960c-6b4ef6b12aac none swap sw 0 0
/dev/hda /media/cdrom0 auto user,atime,noauto,rw,dev,exec,suid 0 0

So, there is no change.

Your second suggestion:

result of doing df -aT in Konsole
Filesystem Type 1K-blocks Used Available Use% Mounted on
/dev/sda1 ext3 152538080 91404180 53385352 64% /
proc proc 0 0 0 - /proc
none sysfs 0 0 0 - /sys
none fusectl 0 0 0 - /sys/fs/fuse/connections
none debugfs 0 0 0 - /sys/kernel/debug
none securityfs 0 0 0 - /sys/kernel/security
none devtmpfs 476144 264 475880 1% /dev
none devpts 0 0 0 - /dev/pts
none tmpfs 480368 84 480284 1% /dev/shm
none tmpfs 480368 200 480168 1% /var/run
none tmpfs 480368 0 480368 0% /var/lock
none tmpfs 480368 0 480368 0% /lib/init/rw
binfmt_misc
binfmt_misc 0 0 0 - /proc/sys/fs/binfmt_misc
/dev/sdb1 vfat 1005680 751472 254208 75% /media/usb0

Snowhog's fix doesn't seem to be available to me because right clicking on the mount point folder doesn't provide the options he describes (Root Actions > Ownership to...) I have never seen those options in dolphin! I tried this in dolphin as user and in dolphin as root = no difference in the options provided when I right click on the folder.

Your third suggestion:
Yes, I checked and I am definitely a member of plugdev group
I have reinstalled udev. Will try pmount if that doesn't work for me.

Oshunluvr

Output from ls -l /media with no usb connected

total 40
lrwxrwxrwx 1 root root 6 2007-09-11 13:03 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2007-09-11 13:03 cdrom0
drwxr-xr-x 2 root root 4096 2007-09-30 00:07 tsaihong
lrwxrwxrwx 1 root root 4 2007-09-26 22:16 usb -> usb0
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb0
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb1
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb2
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb3
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb4
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb5
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb6
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb7

output from dmesg |tail -n 10 immediately after plugging usb in

[ 3629.149961] scsi 5:0:0:0: Direct-Access SD/MMC Card Reader 1.00 PQ: 0 ANSI: 0
[ 3629.154821] sd 5:0:0:0: Attached scsi generic sg2 type 0
[ 3629.528845] sd 5:0:0:0: [sdb] 2012160 512-byte logical blocks: (1.03 GB/982 MiB)
[ 3629.530954] sd 5:0:0:0: [sdb] Write Protect is off
[ 3629.530962] sd 5:0:0:0: [sdb] Mode Sense: 03 00 00 00
[ 3629.530966] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 3629.542082] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 3629.542097] sdb: sdb1
[ 3629.556221] sd 5:0:0:0: [sdb] Assuming drive cache: write through
[ 3629.556233] sd 5:0:0:0: [sdb] Attached SCSI removable disk

and Output from ls -l /media after the usb is connected (note line 5)

lrwxrwxrwx 1 root root 6 2007-09-11 13:03 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2007-09-11 13:03 cdrom0
drwxr-xr-x 2 root root 4096 2007-09-30 00:07 tsaihong
lrwxrwxrwx 1 root root 4 2007-09-26 22:16 usb -> usb0
drwxr-xr-x 14 root root 16384 1970-01-01 08:00 usb0
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb1
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb2
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb3
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb4
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb5
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb6
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb7

Will now shut down and restart and see if all this has restored my ability to write to usb as user other than root or if it has given me the right to change permissions. Will report back asap.

**bernieszu** · Sep 15, 2010, 03:09 AM

Re: Lucid permissions problems for usb

Nope,
Still no joy writing to the usb!
Will try to get to grips with the udev stuff you recommended.

**bernieszu** · Sep 15, 2010, 03:39 AM

Re: Lucid permissions problems for usb

Odd goings on!

Read the udev stuff and tried this command
:~$ apt-file list udev | grep bin

got this:
The program 'apt-file' is currently not installed. You can install it by typing:
sudo apt-get install apt-file

so did this:
:~$ sudo apt-get install apt-file

and it installed but at the end it gave me this message:

Setting up apt-file (2.3.3) ...
The system-wide cache is empty. You may want to run 'apt-file update'
as root to update the cache. You can also run 'apt-file update' as
normal user to use a cache in the user's home directory.

Then another terminal popped up and I got this message!

Warning: Could not find '/usr/sbin/su-to-root', starting '/bin/bash' instead. Please check your profile settings.

apt-file is now using the user's cache directory.
If you want to switch back to the system-wide cache directory,
run 'apt-file purge'
Downloading complete file http://hk.archive.ubuntu.com/ubuntu/...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 16.8M 100 16.8M 0 0 121k 0 0:02:22 0:02:22 --:--:-- 183k
Downloading complete file http://hk.archive.ubuntu.com/ubuntu/...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2357k 100 2357k 0 0 186k 0 0:00:12 0:00:12 --:--:-- 231k
Downloading Index http://hk.archive.ubuntu.com/ubuntu/...86.diff/Index:
No Index available.
Downloading complete file http://hk.archive.ubuntu.com/ubuntu/...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
File is up-to-date.
Downloading Index http://hk.archive.ubuntu.com/ubuntu/...86.diff/Index:
No Index available.
Downloading complete file http://hk.archive.ubuntu.com/ubuntu/...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
File is up-to-date.
Downloading complete file http://security.ubuntu.com/ubuntu/di...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 990k 100 990k 0 0 117k 0 0:00:08 0:00:08 --:--:-- 172k
Downloading Index http://security.ubuntu.com/ubuntu/di...86.diff/Index:
No Index available.
Downloading complete file http://security.ubuntu.com/ubuntu/di...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
File is up-to-date.
Downloading Index http://security.ubuntu.com/ubuntu/di...86.diff/Index:
No Index available.
Downloading complete file http://security.ubuntu.com/ubuntu/di...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
File is up-to-date.
Ignoring source without Contents File:
http://archive.canonical.com/ubuntu/...ntents-i386.gz
Downloading complete file http://archive.ubuntu.com/ubuntu/dis...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 119k 100 119k 0 0 32873 0 0:00:03 0:00:03 --:--:-- 49914
Downloading complete file http://archive.ubuntu.com/ubuntu/dis...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 2357k 100 2357k 0 0 185k 0 0:00:12 0:00:12 --:--:-- 231k
Downloading complete file http://archive.ubuntu.com/ubuntu/dis...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 990k 100 990k 0 0 55572 0 0:00:18 0:00:18 --:--:-- 80660
Ignoring source without Contents File:
http://ppa.launchpad.net/kubuntu-ppa...ntents-i386.gz
Ignoring source without Contents File:
http://deb.opera.com/opera/dists/sta...ntents-i386.gz

What is going on here?
Did I accidentally interrupt an update of something?

**Ole Juul** · Sep 15, 2010, 03:44 AM

Re: Lucid permissions problems for usb

I will read this thread when I feel better because it looks useful to me as well. However, I just got automounting working for all removable media on a Debian install using the instructions here for autofs. That was really easy, so in case it could apply here, I thought I'd mention it right now.

Later; (couldn't sleep). I read all that and still don't quite understand the configuration. However, FYI I just had the same permissions problem (as alluded to in previous paragraph) and the solution was not actually "permissions" as such, but the UID and GID in a config file... just a thought.

**vbgunz** · Sep 15, 2010, 07:58 AM

Re: Lucid permissions problems for usb

I don't come with a solution *but* pretty much the exact same problem. The problem I have is so identical I've followed every post in here for a solution. If it helps, I've noticed this behavior *after* installing a new media bay with 4 usb ports. Before installing the new media bay, the same system identified the same usb sticks without a problem. I am in the plugdev group and will post the output of various commands found on this thread.

If I manually and simply mount /dev/sdh1 /dir I can access the files but cannot do anything with them. Only visiting the files in kdesudo konqueror help me do anything. I am on Kubuntu 10.04 and this behavior is currently seen in KDE 4.5.1 (backports) and on both kernels (2.6.32-24) and mainline kernel 2.6.36-rc4. If it means anything, I believe a while back I installed the scsiadd program *but* only to help me mount esata disk without problems (success).

sudo fdisk -luc

Code:

Disk /dev/sda: 60.0 GB, 60022480896 bytes
255 heads, 63 sectors/track, 7297 cylinders, total 117231408 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: 0x03fee3e4

  Device Boot   Start     End   Blocks  Id System
/dev/sda1      2048  25167871  12582912  82 Linux swap / Solaris
/dev/sda2    25167872  117231407  46031768  83 Linux

Disk /dev/sdb: 640.1 GB, 640135028736 bytes
255 heads, 63 sectors/track, 77825 cylinders, total 1250263728 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: 0x000d5ffd

  Device Boot   Start     End   Blocks  Id System
/dev/sdb1       63 1019565224  509782581  83 Linux
/dev/sdb2  * 1019566080 1250260991  115347456  7 HPFS/NTFS

Disk /dev/sdh: 4016 MB, 4016046080 bytes
90 heads, 25 sectors/track, 3486 cylinders, total 7843840 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/sdh1      8192   7843839   3917824  b W95 FAT32

cat /etc/mtab

Code:

/dev/sda2 / ext4 rw,noatime,discard,data=writeback,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
none /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
none /dev devtmpfs rw,mode=0755 0 0
none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
none /dev/shm tmpfs rw,nosuid,nodev 0 0
none /var/run tmpfs rw,nosuid,mode=0755 0 0
none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0
none /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
/dev/sdb2 /media/windows fuseblk rw,nosuid,nodev,noatime,allow_other,blksize=4096,default_permissions 0 0
/dev/sdb1 /home ext4 rw,noatime,data=writeback 0 0
/dev/sdg1 /media/snapshot-root ext4 ro 0 0
/dev/sdg2 /media/snapshot-home ext4 ro 0 0
/dev/sdg3 /media/snapshot-windows fuseblk ro,nosuid,nodev,allow_other,blksize=4096 0 0

cat /etc/fstab

Code:

# /etc/fstab: static file system information.
#
# Use 'blkid -o value -s UUID' to print the universally unique identifier
# for a device; this may be used with UUID= as a more robust way to name
# devices that works even if disks are added and removed. See fstab(5).

# OFFICIAL SYSTEM SETTINGS
# NOTE: sudo tune2fs -o journal_data_writeback /dev/sda2
# <file system> <mount point>  <type> <options>    <dump> <pass>
proc                    /proc      proc  nodev,noexec,nosuid 0    0
UUID=4fc3b475-04dd-4ed4-9c4a-842580b40bf6  /        ext4  discard,data=writeback,noatime,errors=remount-ro  0  1
UUID=4421208e-5cd2-4b81-80e6-832110832d4d  /home      ext4  data=writeback,noatime,defaults  0  2
UUID=36981B2A981AE7DF            /media/windows ntfs  noatime,defaults,nls=utf8,umask=007,gid=46 0  0
UUID=060a53a8-fea1-464b-b699-2c1d9ffc19de  none      swap  discard,sw 0  0

sudo blkid

Code:

/dev/sda1: UUID="060a53a8-fea1-464b-b699-2c1d9ffc19de" TYPE="swap" 
/dev/sda2: UUID="4fc3b475-04dd-4ed4-9c4a-842580b40bf6" TYPE="ext4" 
/dev/sdb1: UUID="4421208e-5cd2-4b81-80e6-832110832d4d" TYPE="ext4" 
/dev/sdb2: UUID="36981B2A981AE7DF" TYPE="ntfs" 
/dev/sdh1: UUID="79F6-FDCE" TYPE="vfat"

ls -l /media/

Code:

total 32
drwxr-xr-x 6 root root   4096 2010-09-07 00:41 snapshot-home
drwxr-xr-x 23 root root   4096 2010-09-14 16:04 snapshot-root
drwxrwxrwx 1 root root  12288 2010-09-11 03:51 snapshot-windows
drwxrwx--- 1 root plugdev 12288 2010-09-11 03:51 windows

df -aT

Code:

Filesystem  Type  1K-blocks   Used Available Use% Mounted on
/dev/sda2   ext4  45306098  6491072 36513438 16% /
proc     proc      0     0     0  - /proc
none     sysfs      0     0     0  - /sys
none    fusectl      0     0     0  - /sys/fs/fuse/connections
none    debugfs      0     0     0  - /sys/kernel/debug
none  securityfs      0     0     0  - /sys/kernel/security
none   devtmpfs   4058768    288  4058480  1% /dev
none    devpts      0     0     0  - /dev/pts
none     tmpfs   4097732    840  4096892  1% /dev/shm
none     tmpfs   4097732    164  4097568  1% /var/run
none     tmpfs   4097732     0  4097732  0% /var/lock
none     tmpfs   4097732     0  4097732  0% /lib/init/rw
/dev/sdb2 fuseblk  115347452 55219244 60128208 48% /media/windows
/dev/sdb1   ext4  501782436 158925508 317367800 34% /home
/dev/sdg1   ext4  45309360  9071856 33935912 22% /media/snapshot-root
/dev/sdg2   ext4  501782896 159005628 317288120 34% /media/snapshot-home
/dev/sdg3 fuseblk  115347452 40551716 74795736 36% /media/snapshot-windows

dmesg |tail -n 10

Code:

[11574.612466] scsi 13:0:0:0: Direct-Access   JetFlash Transcend 4GB  8.07 PQ: 0 ANSI: 2
[11574.613541] sd 13:0:0:0: Attached scsi generic sg8 type 0
[11574.617745] sd 13:0:0:0: [sdh] 7843840 512-byte logical blocks: (4.01 GB/3.74 GiB)
[11574.619903] sd 13:0:0:0: [sdh] Write Protect is off
[11574.619913] sd 13:0:0:0: [sdh] Mode Sense: 03 00 00 00
[11574.619919] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.623535] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.920536] sdh: sdh1
[11574.922263] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.922275] sd 13:0:0:0: [sdh] Attached SCSI removable disk

**vbgunz** · Sep 15, 2010, 08:01 AM

Re: Lucid permissions problems for usb

I've just noticed I have a .hal-mtab file in /media. Wasn't hal deprecated or something?

**GreyGeek** · Sep 15, 2010, 08:13 AM

Re: Lucid permissions problems for usb

Originally posted by bernieszu

Odd goings on!

Read the udev stuff and tried this command
:~$ apt-file list udev | grep bin

got this:
The program 'apt-file' is currently not installed. You can install it by typing:
sudo apt-get install apt-file

so did this:
:~$ sudo apt-get install apt-file

and it installed but at the end it gave me this message:

Setting up apt-file (2.3.3) ...
The system-wide cache is empty. You may want to run 'apt-file update'
as root to update the cache. You can also run 'apt-file update' as
normal user to use a cache in the user's home directory.

Then another terminal popped up and I got this message!

Warning: Could not find '/usr/sbin/su-to-root', starting '/bin/bash' instead. Please check your profile settings.

apt-file is now using the user's cache directory.
If you want to switch back to the system-wide cache directory,
run 'apt-file purge'

su-to-root is a program which is called when an app you are using (as a user) requires root permission. Apt-get is such a program. It needs write access to /var/cache/apt/. That su-to-root could not be found indicates that at least one binary in /usr/bin has been moved, deleted or renamed.
One now wonders how many other utilities have suffered a similar fate.

Downloading complete file http://hk.archive.ubuntu.com/ubuntu/...ntents-i386.gz
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
........
What is going on here?
Did I accidentally interrupt an update of something?

Apt-file, after it was installed, failed to get root rights so it created a cache file in your home account. No index files were available because your home account cache is new.

I am going to make some assumptions here. Your /media directory contains "mounted" USB devices such that all of the /dev USB sockets are used, resulting in the system resorting to a link, usb -> usb0
The media directory should be empty when no CDROM or USB stick is loaded. The file /etc/mtab is a dynamic list of MOUNTED file systems. Mine, without any external devices loaded, looks like this:

jerry@sonyvgnfw140e:~$ cat /etc/mtab
/dev/sda1 / ext4 rw,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
none /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
none /dev devtmpfs rw,mode=0755 0 0
none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
none /dev/shm tmpfs rw,nosuid,nodev 0 0
none /var/run tmpfs rw,nosuid,mode=0755 0 0
none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0
none /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
jerry@sonyvgnfw140e:~$

When I plug in a USB stick an entry, similar to yours (from df -aT)

/dev/sdb1 vfat 1005680 751472 254208 75% /media/usb0

will be appended to the end of /etc/mtab so that apps will know what is mounted.
The mount point (/media/usb0) will exist and it is through it that I can access content on the USB stick. When I unmount the usb stick (via either Dolphin or the Device-notification in the system tray) the entry in /etc/mtab is removed and the /media/usb0 mount point is umounted and removed.

That your usb mount points under /media still exist, even though I'd wager that they are not in /etc/mtab, indicates either that you did not unmount them before you removed them or that your udev rules are corrupted or missing. This may explain why Snowhog's right click actions suggestion didn't work (or your Dolphin isn't configured for them) and the fix I pointed to here may not help. Considering the su-to-root situation, I suspect corruption or destruction of either the files or your ext3 file system on /dev/sda1.

I also noticed that one mounted file system is binfmt_misc. That is commonly used to allow java programs to pass directly to Java Virtual Machines. Another common usage is to execute PE executables (compiled for MS-DOS or Microsoft Windows) through Wine. For example, the following line will run DOS and Windows EXE files (identified by the "MZ" type code) using Wine:

OSWin:M::MZ::/usr/bin/wine:

To run EXE (.NET) files with Mono[1][2]:
:CLR:M::MZ::/usr/bin/mono:

Windows executables run via WINE are not know, if they are malicious, to affect more than the WINE directory and its contents. Running .NET EXE's using mono is a different ball game, and one of several reasons why I refuse to allow Mono on my system.

I am curious. What uses are you making of WINE or Mono?

Regardless, at this point my advice is to do a fresh re-install from a verified CDROM of Kubuntu LL 10.4, upgraded to KDE 4.5.1.

**vbgunz** · Sep 15, 2010, 08:30 AM

Re: Lucid permissions problems for usb

Wow. I just solved my problem. Not sure *but* before attempting this I did the following so I am not sure if it helped

Code:

sudo apt-get install --reinstall udev ureadahead

The ureadahead re-installation I did only because on every boot I kept seeing a ureadahead terminated exit status 5. The thing I did though that immediately showed results was checking Device Notifier. When I went to its settings, for some odd reason I was only showing "Non-removable media". I changed it to "all" and my usb stick popped up right away. I went to access it and sure enough as me "not sudo" I was able to modify my usb stick in any way I wanted.

Can you believe it? Of course Bernie may have a completely different issue *but* we both until this point had the exact same problems. Maybe it is somehow related?

**GreyGeek** · Sep 15, 2010, 08:48 AM

Re: Lucid permissions problems for usb

Originally posted by vbgunz

I don't come with a solution *but* pretty much the exact same problem. The problem I have is so identical I've followed every post in here for a solution. If it helps, I've noticed this behavior *after* installing a new media bay with 4 usb ports. Before installing the new media bay, the same system identified the same usb sticks without a problem. I am in the plugdev group and will post the output of various commands found on this thread.

If I manually and simply mount /dev/sdh1 /dir I can access the files but cannot do anything with them. Only visiting the files in kdesudo konqueror help me do anything. I am on Kubuntu 10.04 and this behavior is currently seen in KDE 4.5.1 (backports) and on both kernels (2.6.32-24) and mainline kernel 2.6.36-rc4. If it means anything, I believe a while back I installed the scsiadd program *but* only to help me mount esata disk without problems (success).

sudo fdisk -luc
....
Device Boot Start End Blocks Id System
/dev/sdh1 8192 7843839 3917824 b W95 FAT32[/code]

fdisk shows /dev/sdh1 is physically attached and is a FAT32 type fs.

cat /etc/mtab

Code:

/dev/sda2 / ext4 rw,noatime,discard,data=writeback,errors=remount-ro 0 0
proc /proc proc rw,noexec,nosuid,nodev 0 0
none /sys sysfs rw,noexec,nosuid,nodev 0 0
none /sys/fs/fuse/connections fusectl rw 0 0
none /sys/kernel/debug debugfs rw 0 0
none /sys/kernel/security securityfs rw 0 0
none /dev devtmpfs rw,mode=0755 0 0
none /dev/pts devpts rw,noexec,nosuid,gid=5,mode=0620 0 0
none /dev/shm tmpfs rw,nosuid,nodev 0 0
none /var/run tmpfs rw,nosuid,mode=0755 0 0
none /var/lock tmpfs rw,noexec,nosuid,nodev 0 0
none /lib/init/rw tmpfs rw,nosuid,mode=0755 0 0
/dev/sdb2 /media/windows fuseblk rw,nosuid,nodev,noatime,allow_other,blksize=4096,default_permissions 0 0
/dev/sdb1 /home ext4 rw,noatime,data=writeback 0 0
/dev/sdg1 /media/snapshot-root ext4 ro 0 0
/dev/sdg2 /media/snapshot-home ext4 ro 0 0
/dev/sdg3 /media/snapshot-windows fuseblk ro,nosuid,nodev,allow_other,blksize=4096 0 0

BUT, /etc/mtab shows that /dev/sdh1 is NOT mounted. Either its contents were captured while /dev/sdh1 was not mounted or you have a problem in your system.

cat /etc/fstab

Code:

# /etc/fstab: static file system information.
...

Fstab won't contain manually or automounted devices unless the user manually edits it and adds those lines. There are no lines for /dev/sdh1

sudo blkid

Code:

...
/dev/sdh1: UUID="79F6-FDCE" TYPE="vfat"

ls -l /media/

Code:

total 32
.....
drwxrwx--- 1 root plugdev 12288 2010-09-11 03:51 windows

Plugdev? Are YOU and the user "usbmux" members of plugdev?

df -aT
[code]Filesystem Type 1K-blocks Used Available Use% Mounted on
....

df shows no mount for /dev/sdh1

dmesg |tail -n 10

Code:

[11574.612466] scsi 13:0:0:0: Direct-Access   JetFlash Transcend 4GB  8.07 PQ: 0 ANSI: 2
[11574.613541] sd 13:0:0:0: Attached scsi generic sg8 type 0
[11574.617745] sd 13:0:0:0: [sdh] 7843840 512-byte logical blocks: (4.01 GB/3.74 GiB)
[11574.619903] sd 13:0:0:0: [sdh] Write Protect is off
[11574.619913] sd 13:0:0:0: [sdh] Mode Sense: 03 00 00 00
[11574.619919] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.623535] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.920536] sdh: sdh1
[11574.922263] sd 13:0:0:0: [sdh] Assuming drive cache: write through
[11574.922275] sd 13:0:0:0: [sdh] Attached SCSI removable disk

tail shows sdh1 was attached but df and mtab show it not mounted.

You said you mounted sdh1 manually. How?

**oshunluvr** · Sep 15, 2010, 08:55 AM

Re: Lucid permissions problems for usb

See, I still think the problem (or part of it) lies here:

Output from ls -l /media with no usb connected

total 40
lrwxrwxrwx 1 root root 6 2007-09-11 13:03 cdrom -> cdrom0
drwxr-xr-x 2 root root 4096 2007-09-11 13:03 cdrom0
drwxr-xr-x 2 root root 4096 2007-09-30 00:07 tsaihong
lrwxrwxrwx 1 root root 4 2007-09-26 22:16 usb -> usb0
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb0
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb1
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb2
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb3
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb4
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb5
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb6
drwxr-xr-x 2 root root 4096 2007-09-26 22:16 usb7

This

/dev/sdb1 vfat 1005680 751472 254208 75% /media/usb0

Tells us you're mounted at /media/usb0. I think this is the problem - it should mount it at /media/usb which has the proper permissions. At least, that is how it works on my system. All those files under /media named usbX need to be removed. I suspect they're there from past removal of the usb drive without correctly unmounting.

Again, on my system: There is nothing in /media (except cdrom and cdrom0) until a new device is plugged in or a CD or DVD is inserted. Only then does a usb and usb0 appear there.

**GreyGeek** · Sep 15, 2010, 09:01 AM

Re: Lucid permissions problems for usb

Originally posted by vbgunz

Wow. I just solved my problem. Not sure *but* before attempting this I did the following so I am not sure if it helped

Code:

sudo apt-get install --reinstall udev ureadahead

The ureadahead re-installation I did only because on every boot I kept seeing a ureadahead terminated exit status 5. The thing I did though that immediately showed results was checking Device Notifier. When I went to its settings, for some odd reason I was only showing "Non-removable media". I changed it to "all" and my usb stick popped up right away. I went to access it and sure enough as me "not sudo" I was able to modify my usb stick in any way I wanted.

Can you believe it? Of course Bernie may have a completely different issue *but* we both until this point had the exact same problems. Maybe it is somehow related?

Bernies reinstalled udev but not ureadahead. However, she is missing su-to-root, so at this point, if she want's to try reinstalling ureadahead I suggest that she open a Konsole and issue
su su -
which will switch the Konsole to a root console. Then issue
apt-get update
to refresh the system cache, followed by
apt-get -f install
to hopefully fix anything that has been borked by an incomplete upgrade or install. Then do
apt-get --reinstall ureadahead

**vbgunz** · Sep 15, 2010, 09:31 AM

Re: Lucid permissions problems for usb

I mentioned solving my problem here http://kubuntuforums.net/forums/inde...1934#msg241934

It's this thread a few post up. Not sure if it applies to Bernie but suffering the exact same behavior this fixed it for me and may in some way apply to her? Not sure, just thought I chime in with how I fixed my own problem.

**bernieszu** · Sep 15, 2010, 09:40 AM

Re: Lucid permissions problems for usb

Lots of ideas here! This looks promising, but I'm away from my kubuntu tonight so will try these tomorrow and post back as soon as I have done so. Thanks yet again.

Announcement

Lucid permissions problems for usb SOLVED!

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment

Comment