| Summary: | While mounting a slow USB device, the plasmashell and dolphin process status become "uninterruptible sleep" (freeze) | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | alexkde |
| Component: | general | Assignee: | David Edmundson <kde> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | normal | CC: | alexkde, elvis.angelaccio, kde, nate, plasma-bugs-null, postix, stefan.bruens |
| Priority: | NOR | ||
| Version First Reported In: | 5.14.0 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
gdb plasmashell backtrace
CPU load history during gdb plasmashell gdb plasmashell backtrace with dbgsyms |
||
|
Description
alexkde
2018-08-21 14:29:05 UTC
Is it Plasma that freezes or everything? Can you perhaps gdb plasmshell and see where it freezes when you plug in such a device? Created attachment 115463 [details]
gdb plasmashell backtrace
Created attachment 115464 [details]
CPU load history during gdb plasmashell
Comment on attachment 115463 [details]
gdb plasmashell backtrace
I will redo it again with debug symbols installed. :-)
Created attachment 115469 [details]
gdb plasmashell backtrace with dbgsyms
> Is it Plasma that freezes or everything? Dolphin and the Plasma panel become unresponsive, however it is still possible to switch to other still working apps like the FireFox or Konsole using Shift+Tab. > Can you perhaps gdb plasmshell and see where it freezes when you plug in such a device? I did that now, but it seems that the gdb backtrace is not very useful. However, I could now observe with htop that the main plasmashell and the dolphin process status become "D", i.e. "uninterruptible sleep" exactly during the whole freeze. Mounting the SD card of the device in the Konsole results in a freezing plasmashell as well. That means it's not Dolphin specific. @Stefan Brüns, in case you are strongly interested in debugging that issue, I could lend you my device as I am located very closely to you. :) Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! 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 mark the bug 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! 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! |