Summary: | Chromium freezes the whole of KDE UI after resume and network change | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | skaumo |
Component: | general | Assignee: | Unassigned bugs <unassigned-bugs-null> |
Status: | RESOLVED DOWNSTREAM | ||
Severity: | critical | ||
Priority: | NOR | ||
Version First Reported In: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Gentoo Packages | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
skaumo
2017-04-06 22:06:19 UTC
Reassigning to more general component. No indication that this is an issue in KWin. I do not see how Chromium freezes is a bug that should be handled in the KDE bug tracker. The Chromium report you mentioned was reported for Windows, and is several years old, so you should file a new Chromium ticket with _your_ issue. I agree and understand if Chromium freezes on its own it's clearly a Chromium issue. However, if the whole of KDE freezes as a result, there may be room for improvement in KDE, as well. As a user I would expect to be able to kill the application. Normally, frozen applications cause a pop-up window to appear, confirm it is not responding, and ask if I want to wait longer or kill it. The bug I linked above is for reference and context. Reported on Windows, but also happening on Linux if you read through the comments. They just didn't bother fixing it, apparently. |