see also: https://bugs.kde.org/show_bug.cgi?id=391714 krusader-2.6.1-0.24.beta2.gitcb7711f8.fc27.x86_64 was causing this, downgrade to krusader-2.6.1-0.23.beta2.gitce6372fe.fc27.x86_64 seems to solve the problem. Copying and stopping transfers is working again Still, an annoying bug esp. if it kills plasma this easily
Is it reproducible every time? Can you check if it happens with long copy operations on local files? If you wait for copy operation to finish, is there a crash with subsequent operations on local files? Do you have symlinks among the files you copy? What does it mean, Plasma crashes completely? Do you see black desktop with windows or sddm is shown instantly? The difference between the two versions of krusader is only related to local files, not remote, however we may reveal a Plasma bug for some reason.
I have tried to figure out what exactly happened: fact is, the X server crashed - that is what we can find in the journalctl repeatedly (since i was just logging in again after the incident) And, as i am using krusader (and the fish/copy operation) quite often, i am using 0.23 since then. Meanwhile, i found another step to reproduce the probem: As it turns out, simply watching videos in a browser (firefox and chrome) are killing the X server as well. So, maybe this isn't simply related to krusader, but to something more severe in plasma/X. What i tried to do was downgrading - mesa to 17.2.2 - kwin and plasma to 5.11 but the problem is still there. My environment is a lenovo t420 machine, i7, intel graphics (only). I could not reproduce this problem with the crashing X on a more current machine (t470), but i had problems with krusader 0.24 on both. Both T's are configured similarly, fedora 27 including fedora-testing repos. Any idea what i could do the rbing the t420 back to a working state (that is, any hints what downgrade could help isolating the problem?)
.
Thanks for additional info. Please answer the questions from comment #1 one by one. Ideally, provide a backtrace.
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, if necessary, i'll open a new ticket.