Jim Dean wrote: > I've experienced the same problem > > dmesg reports segfault in libdbus-glib-1.so.2.1.0 > > Yeah, I get a whole slew of these, too: [14974.648595] udisks-daemon[15939]: segfault at 18 ip 0000003b0ac0aba8 sp 00007fff474c2a70 error 4 in libdbus-glib-1.so.2.1.0[3b0ac00000+21000] However, later down in the messages: [31273.879055] usb 2-6: new high speed USB device using ehci_hcd and address 4 [31273.995140] usb 2-6: New USB device found, idVendor=067b, idProduct=2506 [31273.995146] usb 2-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [31273.995150] usb 2-6: Product: Mass Storage Device [31273.995153] usb 2-6: Manufacturer: Prolific Technology Inc. [31273.995156] usb 2-6: SerialNumber: 0 [31273.997764] scsi10 : usb-storage 2-6:1.0 [31275.033677] scsi 10:0:0:0: Direct-Access ST320082 2A 3.01 PQ: 0 ANSI: 0 [31275.038895] sd 10:0:0:0: Attached scsi generic sg3 type 0 [31275.040775] sd 10:0:0:0: [sdc] 390721968 512-byte logical blocks: (200 GB/186 GiB) [31275.041641] sd 10:0:0:0: [sdc] Write Protect is off [31275.041646] sd 10:0:0:0: [sdc] Mode Sense: 03 00 00 00 [31275.041649] sd 10:0:0:0: [sdc] Assuming drive cache: write through [31275.045935] sd 10:0:0:0: [sdc] Assuming drive cache: write through [31275.045944] sdc: sdc1 < sdc5 > [31275.067269] sd 10:0:0:0: [sdc] Assuming drive cache: write through [31275.067275] sd 10:0:0:0: [sdc] Attached SCSI disk So it seems to see the drive, but Device Manager doesn't mount it, like it used to. _______________________________________________ kde mailing list kde@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/kde New to KDE4? - get help from http://userbase.kde.org
