| Summary: | Krusader crashes on unstable connections | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Leon <support> |
| Component: | general | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | justin.zobel, kde, kde, krusader-bugs-null, plasma-bugs-null |
| Priority: | NOR | Keywords: | drkonqi |
| Version First Reported In: | 5.18.5 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
Leon
2020-10-12 05:38:05 UTC
Wait, I moved this to krusader because of the title, but the backtrace is from plasma? Did Krusader or plasma crash? It is not really very visible when it goes wrong. There would just be this notification (sad face) that pops up to say something went wrong and I should report it. Plasma continues as normal, and krusader does not crash or close. I can still perform some tasks, except on any open editors or trying to reconnect to any servers. that portion of krusader is not ok anymore after the poppup. If it has any other adverse effects on the plasma shell, I have not come across it yet. It does not look like it, but it could be affected in an area where I do not access or feel it. But clearly plasma is not happy in some area. It could be that whatever happens has an adverse effect on krusader, but maybe krusader is just an unfortunate victim, and not the cause. 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! Information provided Thank you for reporting this crash 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 crash with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you! I changed my inline editor to Kdevelop a few months ago, and it seems that it crashes less. It did die again a few days ago, but I was unable to replicate it now. I tried to simulate connection issues, but till now has not crashed. In all, it does appear to crash less now. I will have to work with it hard again and report when it crashes. Thanks for the update Leon, I'll close this report for now. If the issue returns please feel free to reopen this bug report or a new one. |