Bug 386472 - Plasma crashed when connecting USB device
Summary: Plasma crashed when connecting USB device
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: 5.11.2
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2017-11-02 18:00 UTC by Christian
Modified: 2018-10-29 02:08 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Traybar Icon for devices (458 bytes, image/png)
2017-11-13 18:03 UTC, Christian
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Christian 2017-11-02 18:00:04 UTC
I wanted to plug-in my USB Harddrive today. When the popup of the device manager was about to appear, plasmashell showed an empty window instead and crashed. All I could do was a "killall plasmashell" and then "/usr/bin/plasmashell" to start it again. Second try, crashed again. It wrote "trying to show an empty dialog" to the konsole.

The USB Drive got mounted anyway, I can access it normally after restarting plasma.

"/var/log/syslog" says:
Nov  2 18:54:45 glaze kernel: [ 2107.551585] usb 2-1.2: new high-speed USB device number 9 using ehci-pci
Nov  2 18:54:45 glaze kernel: [ 2107.646695] usb 2-1.2: New USB device found, idVendor=0480, idProduct=a00c
Nov  2 18:54:45 glaze kernel: [ 2107.646701] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  2 18:54:45 glaze kernel: [ 2107.646705] usb 2-1.2: Product: External USB 3.0
Nov  2 18:54:45 glaze kernel: [ 2107.646708] usb 2-1.2: Manufacturer: TOSHIBA
Nov  2 18:54:45 glaze kernel: [ 2107.646711] usb 2-1.2: SerialNumber: 20131215081964
Nov  2 18:54:45 glaze kernel: [ 2107.647082] usb-storage 2-1.2:1.0: USB Mass Storage device detected
Nov  2 18:54:45 glaze kernel: [ 2107.647245] scsi host10: usb-storage 2-1.2:1.0
Nov  2 18:54:45 glaze mtp-probe: checking bus 2, device 9: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.2"
Nov  2 18:54:45 glaze mtp-probe: bus: 2, device: 9 was not an MTP device
Nov  2 18:54:48 glaze kernel: [ 2110.626059] scsi 10:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
Nov  2 18:54:48 glaze kernel: [ 2110.626676] sd 10:0:0:0: Attached scsi generic sg2 type 0
Nov  2 18:54:48 glaze kernel: [ 2110.629000] sd 10:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
Nov  2 18:54:48 glaze kernel: [ 2110.629867] sd 10:0:0:0: [sdb] Write Protect is off
Nov  2 18:54:48 glaze kernel: [ 2110.629878] sd 10:0:0:0: [sdb] Mode Sense: 23 00 00 00
Nov  2 18:54:48 glaze kernel: [ 2110.630729] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov  2 18:54:48 glaze kernel: [ 2110.647272]  sdb: sdb1
Nov  2 18:54:48 glaze kernel: [ 2110.651497] sd 10:0:0:0: [sdb] Attached SCSI disk
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: "/org/freedesktop/UDisks2/drives/TOSHIBA_External_USB_3_2e0_20131215081964" has new interfaces: ("org.freedesktop.UDisks2.Drive")
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: org.kde.baloo: "/org/freedesktop/UDisks2/drives/TOSHIBA_External_USB_3_2e0_20131215081964"
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: QObject::connect: invalid null parameter
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: "/org/freedesktop/UDisks2/block_devices/sdb" has new interfaces: ("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.PartitionTable")
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: org.kde.baloo: "/org/freedesktop/UDisks2/block_devices/sdb"
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: QObject::connect: invalid null parameter
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: "/org/freedesktop/UDisks2/block_devices/sdb1" has new interfaces: ("org.freedesktop.UDisks2.Block", "org.freedesktop.UDisks2.Filesystem", "org.freedesktop.UDisks2.Partition")
Nov  2 18:54:48 glaze org.kde.runners.baloo[1417]: org.kde.baloo: "/org/freedesktop/UDisks2/block_devices/sdb1"

"/var/log/kern.log" says:
Nov  2 18:54:45 glaze kernel: [ 2107.551585] usb 2-1.2: new high-speed USB device number 9 using ehci-pci
Nov  2 18:54:45 glaze kernel: [ 2107.646695] usb 2-1.2: New USB device found, idVendor=0480, idProduct=a00c
Nov  2 18:54:45 glaze kernel: [ 2107.646701] usb 2-1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3
Nov  2 18:54:45 glaze kernel: [ 2107.646705] usb 2-1.2: Product: External USB 3.0
Nov  2 18:54:45 glaze kernel: [ 2107.646708] usb 2-1.2: Manufacturer: TOSHIBA
Nov  2 18:54:45 glaze kernel: [ 2107.646711] usb 2-1.2: SerialNumber: 20131215081964
Nov  2 18:54:45 glaze kernel: [ 2107.647082] usb-storage 2-1.2:1.0: USB Mass Storage device detected
Nov  2 18:54:45 glaze kernel: [ 2107.647245] scsi host10: usb-storage 2-1.2:1.0
Nov  2 18:54:48 glaze kernel: [ 2110.626059] scsi 10:0:0:0: Direct-Access     TOSHIBA  External USB 3.0 5438 PQ: 0 ANSI: 6
Nov  2 18:54:48 glaze kernel: [ 2110.626676] sd 10:0:0:0: Attached scsi generic sg2 type 0
Nov  2 18:54:48 glaze kernel: [ 2110.629000] sd 10:0:0:0: [sdb] 1953525164 512-byte logical blocks: (1.00 TB/932 GiB)
Nov  2 18:54:48 glaze kernel: [ 2110.629867] sd 10:0:0:0: [sdb] Write Protect is off
Nov  2 18:54:48 glaze kernel: [ 2110.629878] sd 10:0:0:0: [sdb] Mode Sense: 23 00 00 00
Nov  2 18:54:48 glaze kernel: [ 2110.630729] sd 10:0:0:0: [sdb] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
Nov  2 18:54:48 glaze kernel: [ 2110.647272]  sdb: sdb1                                                                                                                                                                                      
Nov  2 18:54:48 glaze kernel: [ 2110.651497] sd 10:0:0:0: [sdb] Attached SCSI disk
Comment 1 David Edmundson 2017-11-03 00:51:51 UTC
If there's a crash I need to see the backtrace, which can be found with the sad face icon in the system tray after a crash.

I can't do much otherwise, sorry.
Comment 2 Christian 2017-11-03 19:17:58 UTC
Never mind. For some reason I can't explain it works today. I had mounted it on my synology, unmounted it and plugged it back to my notebook. And now it works as intended, doesn't crash plasma.

But as a sidenode: Since plasmashell froze completely, there was no "sad face" icon. Can I extract the mentioned backtrace from elsewhere?
Comment 3 Christian 2017-11-13 18:01:12 UTC
I'm sorry to reopen this. But the hang does occur again. Sometimes plasma hangs on plugging in a USB harddrive or my tablet (via usb), sometimes it does not hang. However, the drive is mounted a can use it normally after killing and restarting plasma. Plasma will hang again if I click the device-icon in the traybar again.

As previously mentioned, since plasma gets unresponsive there is no "sad-face-icon" I could click. Can you give me details on how I can access the backtrace on another way?
Comment 4 Christian 2017-11-13 18:03:34 UTC
Created attachment 108839 [details]
Traybar Icon for devices

I mean this icon. When I click on it, plasma crashes again.
Comment 5 Christian 2017-11-18 14:04:26 UTC
*push*
Comment 6 Christian 2017-11-19 11:18:58 UTC
This also happens when i'm mounting a cd rom.
Comment 7 Christoph Feck 2017-11-24 01:21:40 UTC
If this is reproducible, install debug information packages for Qt and Plasma, and try to run plasmashell with gdb in Konsole.

Please see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 8 Christian 2017-11-28 21:03:48 UTC
Seemed to be a problem with the NFS mounting. A while ago I mounted some directories of my synology via NFS. Since I uncommented these lines, the crashes doesn't appear any more.

I will put them in again and try to get some meaningful debug-infos.
Comment 9 Andrew Crouthamel 2018-09-28 03:18:56 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 10 Andrew Crouthamel 2018-10-29 02:08:41 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!