Bug 303999

Summary: usb stick not automounted
Product: [openSUSE] openSUSE 10.3 Reporter: Klaus Singvogel <kssingvo>
Component: KDEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED DUPLICATE QA Contact: E-mail List <qa-bugs>
Severity: Major    
Priority: P5 - None CC: coolo, dmueller, snwint, wstephenson
Version: Beta 2   
Target Milestone: ---   
Hardware: 32bit   
OS: openSUSE 10.3   
Whiteboard:
Found By: Development Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Klaus Singvogel 2007-08-23 18:46:09 UTC
I'm running KDE...

When attaching my old USB (>1.5 years old) stick to my PC it gets not mounted into the filesystem. This stick worked flawless with hotplug in openSUSE 10.2, and openSUSE 10.1.

The kernel detects the USB stick:
 dmesg | tail
-------------------------------------------------------------------
usb-storage: device found at 5
usb-storage: waiting for device to settle before scanning
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
scsi 4:0:0:0: Direct-Access     LEXAR    GEYSER JUMPDRIVE 1.00 PQ: 0 ANSI: 1 CCS
sd 4:0:0:0: [sdc] 503808 512-byte hardware sectors (258 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 4:0:0:0: [sdc] Assuming drive cache: write through
sd 4:0:0:0: [sdc] 503808 512-byte hardware sectors (258 MB)
sd 4:0:0:0: [sdc] Write Protect is off
sd 4:0:0:0: [sdc] Mode Sense: 23 00 00 00
sd 4:0:0:0: [sdc] Assuming drive cache: write through
 sdc: sdc1
sd 4:0:0:0: [sdc] Attached SCSI removable disk
sd 4:0:0:0: Attached scsi generic sg4 type 0
usb-storage: device scan complete
-------------------------------------------------------------------

not mounted:
-------------------------------------------------------------------
 mount
/dev/sda6 on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
/dev/sda7 on /CD type ext3 (rw)
/dev/sdb5 on /abuild type ext3 (rw)
/dev/sdb1 on /old/10.0 type ext3 (rw)
/dev/sdb2 on /old/10.2 type ext3 (rw)
/dev/sda1 on /old/data type ext3 (rw)
/dev/sdb6 on /space type ext3 (rw)
/dev/sdb7 on /space/filme type ext3 (rw)
securityfs on /sys/kernel/security type securityfs (rw)
[...]
-------------------------------------------------------------------

But found via ls:
-------------------------------------------------------------------
 ls -ls /dev/disk/by-label/*
lrwxrwxrwx 1 root root 10 Aug 23 20:34 /dev/disk/by-label/KLAUS256 -> ../../sdc1
-------------------------------------------------------------------
Comment 1 Stephan Kulow 2007-08-24 06:44:34 UTC
try lshal --monitor instead and if that shows something, reassign it to component KDE and this is not critical. ugly, but not critical
Comment 2 Klaus Singvogel 2007-08-24 11:33:15 UTC
will do on Monday
Comment 3 Klaus Singvogel 2007-08-27 12:30:54 UTC
Yes, it shows something. On plugin as well as on removal.


-------------------------------------------------------------------
 lshal --monitor
Start monitoring devicelist:
-------------------------------------------------
14:29:04.993: usb_device_5dc_300_5DD2BC121653012 added
14:29:05.389: usb_device_5dc_300_5DD2BC121653012_if0 added
14:29:06.050: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host added
14:29:06.062: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host_scsi_device_lun0 added
14:29:06.074: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host_scsi_device_lun0_scsi_generic added
14:29:06.204: storage_serial_LEXAR_GEYSER_JUMPDRIVE_5DD2BC121653012_0_0 added
14:29:06.258: volume_uuid_1CEB_172C added

14:29:12.515: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host_scsi_device_lun0_scsi_generic removed
14:29:12.520: volume_uuid_1CEB_172C removed
14:29:12.521: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host_scsi_device_lun0 removed
14:29:12.525: usb_device_5dc_300_5DD2BC121653012_if0_scsi_host removed
14:29:12.527: storage_serial_LEXAR_GEYSER_JUMPDRIVE_5DD2BC121653012_0_0 removed
14:29:12.528: usb_device_5dc_300_5DD2BC121653012_if0 removed
14:29:12.530: usb_device_5dc_300_5DD2BC121653012 removed
-------------------------------------------------------------------

changed component: hotplug -> KDE as said
Comment 4 Will Stephenson 2007-08-27 13:37:28 UTC
Reproduced
Comment 5 Steffen Winterfeldt 2007-08-29 14:49:39 UTC
*** Bug 304479 has been marked as a duplicate of this bug. ***
Comment 6 Will Stephenson 2007-08-30 10:17:11 UTC
Reproduced, but I don't get any output from lshal --monitor so I don't know that it's KDE's fault
Comment 7 Dirk Mueller 2007-08-30 10:19:45 UTC
thats a different bug then. 

can you attach lshal output of volume_uuid_1CEB_172C ?

does it just not work with that particular usb stick or in general?
Comment 8 Klaus Singvogel 2007-08-30 10:27:39 UTC
Used my 2nd USB stick, and I am able to reproduce it:

-------------------------------------------------------------------
 lshal --monitor

Start monitoring devicelist:
-------------------------------------------------
12:25:52.733: usb_device_ea0_6803_95F17023BAD7249 added
12:25:52.944: usb_device_ea0_6803_95F17023BAD7249_if0 added
12:25:53.572: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host added
12:25:53.584: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host_scsi_device_lun0 added
12:25:53.597: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host_scsi_device_lun0_scsi_generic added
12:25:53.847: storage_serial_TYPHOON_MemoryAdapter_95F17023BAD7249_0_0 added
12:25:53.986: volume_uuid_1DFE_1631 added
12:26:06.630: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host_scsi_device_lun0_scsi_generic removed
12:26:06.633: volume_uuid_1DFE_1631 removed
12:26:06.634: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host_scsi_device_lun0 removed
12:26:06.636: usb_device_ea0_6803_95F17023BAD7249_if0_scsi_host removed
12:26:06.638: storage_serial_TYPHOON_MemoryAdapter_95F17023BAD7249_0_0 removed
12:26:06.638: usb_device_ea0_6803_95F17023BAD7249_if0 removed
12:26:06.640: usb_device_ea0_6803_95F17023BAD7249 removed

-------------------------------------------------------------------
Comment 9 Dirk Mueller 2007-08-30 11:02:18 UTC
do you also get an error about "unknown hal error" in ~/.xsession-errors from kded?
Comment 10 Dirk Mueller 2007-08-30 11:31:52 UTC

*** This bug has been marked as a duplicate of bug 306288 ***
Comment 11 Klaus Singvogel 2007-08-30 11:33:54 UTC
Just for sake of completeness:
No, no "unknown hal error" in ~/.xsession-errors from kded found.