Bug 391714 - plasma crashes when looking at filetransfer in progress in statusbar
Summary: plasma crashes when looking at filetransfer in progress in statusbar
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: System Tray (show other bugs)
Version: 5.12.2
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-11 16:07 UTC by slartibart70
Modified: 2018-03-14 10:13 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description slartibart70 2018-03-11 16:07:08 UTC
Hi,
i;m using krusader to transfer files using the 'fish' protocol between two machines. So, the copy job is running, and we got the notification either in the krusader icon (green shadow advancing) and in the networkmanager in the systemtray.
Just open the networkmanager-notification while the copy-job is running, we see the progress bar and the 'details' chevron on the right to it. Click on it... and that's it. Plasma crashes completely (but at least we come up again to the sddm login screen)

Expected behaviour:
The 'details' chevron should open some details of the running copy-job, like filename and transfer speed. Also you should have the pause/stop buttons to cancel a running copy job

This was working properly before upgrade to 5.12/5.44 frameworks
Comment 1 slartibart70 2018-03-11 16:16:16 UTC
Missing info:
i was unsing krusader-2.6.1-0.24.beta2.gitcb7711f8.fc27.x86_64 and now downgraded to krusader-2.6.1-0.23.beta2.gitce6372fe.fc27.x86_64
which seems to work better

BUT... i wouldn't expect one single program (krusader) to kill the whole plasma session? Even if it is/was buggy?
Comment 2 slartibart70 2018-03-13 07:59:05 UTC
see https://bugs.kde.org/show_bug.cgi?id=391716
as well
Comment 3 David Edmundson 2018-03-13 13:23:24 UTC
Crashes should have a backtrace, otherwise we can do nothing with them.
Comment 4 slartibart70 2018-03-14 10:13:58 UTC
Hi all,
i have re-initialized the t420 to an initial fedora27 state, with current updates.
Whatever happened, now this machine works as it should, no idea what was really the cause for the crashes.
Sorry for the confusion, but i think it would be ok to close this bug.
I will definitely check for the krusader problems later on...