Bug 148507

Summary: No mount of media at all: usb, cd, dvd
Product: [openSUSE] SUSE Linux 10.1 Reporter: Joachim Reichelt <Joachim.Reichelt>
Component: KDEAssignee: E-mail List <kde-maintainers>
Status: RESOLVED WORKSFORME QA Contact: E-mail List <qa-bugs>
Severity: Normal    
Priority: P5 - None CC: marc.collin
Version: Beta 2   
Target Milestone: ---   
Hardware: 32bit   
OS: Other   
Whiteboard:
Found By: Beta-Customer Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Joachim Reichelt 2006-02-06 20:35:54 UTC 
After update from 10.0 to 10.1b2 no media at all are mounted in kde.
Media are recognized by the kernel.

usb 2-1: new full speed USB device using uhci_hcd and address 2
usb 2-1: new device found, idVendor=0930, idProduct=6533
usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3
usb 2-1: Product: DataTraveler 2.0
usb 2-1: Manufacturer: Kingston
usb 2-1: SerialNumber: 07D1025042E058EA
usb 2-1: configuration #1 chosen from 1 choice
scsi4 : SCSI emulation for USB Mass Storage devices
usb-storage: device found at 2
usb-storage: waiting for device to settle before scanning
  Vendor: Kingston  Model: DataTraveler 2.0  Rev: 6.00
  Type:   Direct-Access                      ANSI SCSI revision: 02
SCSI device sdh: 1001472 512-byte hdwr sectors (513 MB)
sdh: Write Protect is off
sdh: Mode Sense: 0b 00 00 08
sdh: assuming drive cache: write through
SCSI device sdh: 1001472 512-byte hdwr sectors (513 MB)
sdh: Write Protect is off
sdh: Mode Sense: 0b 00 00 08
sdh: assuming drive cache: write through
 sdh: sdh1
sd 4:0:0:0: Attached scsi removable disk sdh
sd 4:0:0:0: Attached scsi generic sg7 type 0
usb-storage: device scan complete
Comment 1 Stephan Kulow 2006-02-06 20:51:48 UTC 
try beta3
Comment 2 Marc collin 2006-04-02 03:20:03 UTC 
get same problem with beta 9

in kde, there is a windows who let me open the drive..... after it said me i don't have right to access the drive
Comment 3 Stephan Kulow 2006-04-11 09:20:58 UTC 
#2 is something different I'm sure. Please open a new bug report with lshal output and what drive creates the problem