Bug 204893 - unable to mount usb key
Summary: unable to mount usb key
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Unspecified
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-23 18:47 UTC by BRULE Herman
Modified: 2018-02-23 21:19 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
screenshot (25.79 KB, image/png)
2009-08-23 18:48 UTC, BRULE Herman
Details
screenshot (240.20 KB, image/png)
2009-09-04 23:32 UTC, BRULE Herman
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BRULE Herman 2009-08-23 18:47:52 UTC
Version:            (using KDE 4.3.0)
Installed from:    Gentoo Packages

Hello, I'm unable to mount my usb key after few mount (bad and safely removing).
See the attached screenshot.
Thanks to solve it.
Comment 1 BRULE Herman 2009-08-23 18:48:21 UTC
Created attachment 36393 [details]
screenshot
Comment 2 FiNeX 2009-08-23 21:23:31 UTC
Can you reproduce the bug at will? When you've that dialog, would you like to check the "mount" command ?
Comment 3 BRULE Herman 2009-08-23 21:27:02 UTC
No, I have sometime this bug (every 10 ~ 15 mount).
Mount command work, I need use it because KDE can't mount the usb key.
Comment 4 FiNeX 2009-08-25 13:39:27 UTC
Next time you'll have this bug, please check what "mount" command prints (without parameters). Moreover you could check if the device is correctly identified using dmesg. Thanks
Comment 5 BRULE Herman 2009-09-04 23:31:43 UTC
I had re this bug, my command AFTER mount manualy show:
192.168.0.10:/mnt/nfs/bureau-nfs/ on / type nfs (rw,remount,noatime,proto=tcp,addr=192.168.0.10)
proc on /proc type proc (rw,nosuid,nodev,noexec,relatime)
sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)
udev on /dev type tmpfs (rw,nosuid,relatime,size=10240k,mode=755)
devpts on /dev/pts type devpts (rw,nosuid,noexec,relatime,gid=5,mode=620)
shm on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
usbfs on /proc/bus/usb type usbfs (rw,noexec,nosuid,devmode=0664,devgid=85)
192.168.0.10:/mnt/nfs/distfiles/ on /usr/portage/distfiles type nfs (rw,noexec,nosuid,nodev,noatime,proto=tcp,addr=192.168.0.10)
192.168.0.10:/mnt/nfs/world/ on /mnt/nfs/world type nfs (rw,noatime,proto=tcp,addr=192.168.0.10)
192.168.0.10:/mnt/nfs/read/ on /mnt/nfs/read type nfs (rw,noatime,proto=tcp,addr=192.168.0.10)
192.168.0.10:/mnt/nfs/perso/ on /mnt/nfs/perso type nfs (rw,noatime,proto=tcp,addr=192.168.0.10)
/dev/sda on /media/fat type vfat (rw)
My dmesg:
usb 1-4.3: new full speed USB device using ehci_hcd and address 6
usb 1-4.3: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 6
usb-storage: waiting for device to settle before scanning
usb-storage: device scan complete
scsi scan: INQUIRY result too short (5), using 36
scsi 4:0:0:0: Direct-Access     GENERIC  USB DISK DEVICE  1.00 PQ: 0 ANSI: 0 CCS
sd 4:0:0:0: Attached scsi generic sg0 type 0
sd 4:0:0:0: [sda] 992993 512-byte hardware sectors: (508 MB/484 MiB)
sd 4:0:0:0: [sda] Write Protect is off
sd 4:0:0:0: [sda] Mode Sense: 00 c0 00 00
sd 4:0:0:0: [sda] Assuming drive cache: write through
sd 4:0:0:0: [sda] Assuming drive cache: write through
 sda:
sd 4:0:0:0: [sda] Attached SCSI removable disk
And screen shot, the order of the screen shot:
1) try via device notifier, this error
2) mount via konsole
3) open konqueror via devices notifier (device notifier know that it's mount)
See the attached file
Comment 6 BRULE Herman 2009-09-04 23:32:16 UTC
Created attachment 36698 [details]
screenshot
Comment 7 Boudewijn Charite 2010-12-18 11:04:08 UTC
I have similar problems since recent updates I cant moubt usb devices any more. Not my Canon EOS350 camera, not my usb memory sticks and not my mobilephone.

I got Unkonwn error code 150
I/O problem
Please send a full bug report at ....
Comment 8 Ben Creasy 2018-02-23 21:19:25 UTC
If this is happening with KDE 5, please leave a comment.