Discussion:
[plasmashell] [Bug 391714] New: plasma crashes when looking at filetransfer in progress in statusbar
(too old to reply)
b***@kde.org
2018-03-11 16:07:08 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391714

Bug ID: 391714
Summary: plasma crashes when looking at filetransfer in
progress in statusbar
Product: plasmashell
Version: 5.12.2
Platform: Fedora RPMs
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: NOR
Component: System Tray
Assignee: plasma-***@kde.org
Reporter: ***@gmail.com
Target Milestone: 1.0

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
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-03-11 16:16:16 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391714

--- Comment #1 from ***@gmail.com ---
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?
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-03-13 07:59:05 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391714

--- Comment #2 from ***@gmail.com ---
see https://bugs.kde.org/show_bug.cgi?id=391716
as well
--
You are receiving this mail because:
You are watching all bug changes.
David Edmundson
2018-03-13 13:23:24 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391714

David Edmundson <***@davidedmundson.co.uk> changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |BACKTRACE
Status|UNCONFIRMED |NEEDSINFO
CC| |***@davidedmundson.co.uk

--- Comment #3 from David Edmundson <***@davidedmundson.co.uk> ---
Crashes should have a backtrace, otherwise we can do nothing with them.
--
You are receiving this mail because:
You are watching all bug changes.
b***@kde.org
2018-03-14 10:13:58 UTC
Permalink
Raw Message
https://bugs.kde.org/show_bug.cgi?id=391714

***@gmail.com changed:

What |Removed |Added
----------------------------------------------------------------------------
Resolution|BACKTRACE |WORKSFORME
Status|NEEDSINFO |RESOLVED

--- Comment #4 from ***@gmail.com ---
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...
--
You are receiving this mail because:
You are watching all bug changes.
Loading...