Summary: | plasma crashs on start every time | ||
---|---|---|---|
Product: | [Frameworks and Libraries] print-manager | Reporter: | Markus Rathgeb <maggu2810> |
Component: | general | Assignee: | Daniel Nicoletti <dantti12> |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | fabian, kde, kde, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=326289 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Markus Rathgeb
2019-07-03 06:18:10 UTC
While reading the stacktrace myself and realized the last method "JobModel::updateJob(int, KCupsJob const&)" I opened "127.0.0.1:631" the CUPS webpage. I cancelled all remaining print jobs. After that the plasmashell seems to work again. For me the problem is now resolved, but the potential error still exists in the code base. I don't think the state of the printers should be able to crash the whole plasmashell and stops them from working... Do you agree that we should keep that bug report open until the cause is really solved? Isn't it a problem of the "print-manager" AND "plasmashell"? * The print-manager should not crash * The plasmashell should not crash if the print-manager crashes Any applet can bring plasma shell down. That's not ideal, but fixing is not really within the scope of a bug. This is purely a print-manager problem. Please install debug symbols for print-manager and upload a new trace. As a temporary workaround disable/remove that plasmoid. >> I cancelled all remaining print jobs. >> After that the plasmashell seems to work again. > This is purely a print-manager problem. Please install debug symbols for print-manager and upload a new trace. Wired, as I already applied the workaround described above (cancelled all print jobs). I cannot reproduce the error adding new print jobs to that printer anymore. If I am able to trigger the crash again, I will add further traces. *** This bug has been marked as a duplicate of bug 326289 *** |