Ubuntu
kde4libs package

  1. Bug #269615
  2. Comment #9

Comment 9 for bug 269615

Revision history for this message
TWO (two) wrote :

I am running the Kubuntu Intrepid Ibex Beta with KDE 4.1.2 and I have noticed this problem as well.

I have three partitions on my hard disk; ext3 (Linux), FAT32 (shared) and NTFS (Windows.) I cannot access the FAT32 or NTFS partitions even though they have icons in the sidebar of Dolphin. Neither of the partitions appear under /media/.

If I run 'sudo dolphin' in Konsole, then I'm able to access the partitions after entering a password prompt. I am still able to access the partitions even if I close down Dolphin, run 'sudo -k' then reopen it. However, once I restart the session and I am unable to access them.

Interestingly enough, I am unable to access the memory card on my camera under any circumstances. The camera appears under Dolphin, however on clicking on the icon, I am presented with the following message at the bottom of the window:

"An error occurred while accessing 'Volume (vfat)', the system responded: mount: wrong fs type, bad option, bad superblock on /dev/sdb1, missing codepage or helper program, or other error
in some cases useful info is found in syslog-
try
dmesg | tail or so"

Running the command in the Konsole gives the following message:

dmesg | tail
[ 497.829070] ISOFS: Unable to identify CD-ROM format.
[ 503.956036] FAT: utf8 is not a recommended IO charset for FAT filesystems, filesystem will be case sensitive!
[ 513.165814] UDF-fs: No VRS found
[ 513.350693] ISOFS: Unable to identify CD-ROM format.
[ 553.066840] UDF-fs: No VRS found
[ 553.254451] ISOFS: Unable to identify CD-ROM format.
[ 586.909581] UDF-fs: No VRS found
[ 587.093323] ISOFS: Unable to identify CD-ROM format.
[ 701.433464] UDF-fs: No VRS found
[ 701.617837] ISOFS: Unable to identify CD-ROM format.

That means nothing to me. Trying "dmesg | so" gives a 'command not found' error message.

I don't know if this is significant, but up until Hardy Heron, those different partitions were identified with an /sda/ sequence and the same was true during the installation process, but now they are now identified by 'disk,' 'disk-1,' etc.