Summary: | Plasma crashed after opening an HTML5 video in Chrome | ||
---|---|---|---|
Product: | [Plasma] kwin | Reporter: | gje968 |
Component: | aurorae | Assignee: | KWin default assignee <kwin-bugs-null> |
Status: | RESOLVED UPSTREAM | ||
Severity: | crash | CC: | dv, grglsn765, KDE.Bug.Tracking.System, kenaaker, mborgnia, mo78, moi, pier_andreit, rb03884, steven, tbp001, zholeg803 |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.4.2 | ||
Target Milestone: | --- | ||
Platform: | Ubuntu | ||
OS: | Linux | ||
See Also: |
https://bugs.kde.org/show_bug.cgi?id=352259 https://bugreports.qt.io/browse/QTBUG-50368 |
||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
gje968
2016-01-22 12:11:50 UTC
Driver bug, induced by QtQuick as used by the aurorae decoration engine. The crashes should not occur with the breeze decoration. It looks a hell lot like https://bugreports.qt.io/browse/QTBUG-50368, but that's about inactive X screens - is this on bare metal or some virtual machine, vnc etc.? Also check whether all backtraces follow the same pattern or this may be a red herring on bug #352259. This is a completely native installation. Is there an update to aurorae or something that fixes this? If the presented backtrace is legit (ie. they all look like this and this is not the result from some stack corruption, check other backtraces) the bug is in the nvidia driver, triggered by QtQuick. The arorae decoration can never workaround/fix/avoid it (execpt by dropping QtQuick as backend) Because of the specific conditions, can you please attach the output of "qdbus org.kde.KWin /KWin supportInformation" FYI I'm using a GTX 960. Output of "qdbus org.kde.KWin /KWin supportInformation": https://paste.kde.org/pfa68qbgi > unredirectFullscreen: false
Nope.
btw, please leave the bug state as it is - whether the bug is in the nvidia blob or QtQuick - it's not in the aurorae engine (or any kwin)
As mentioned, resort to the breeze decoration to prevent running into this.
I actually haven't moved it, that's where DrKonqui put it. I don't see either of those under "component", and selecting qtcurve as the product (there is nothing for nvidia) still leaves only aurorae as the component. (I've never used this website before; can you tell? lol) I meant the "resolved/upstream" condition - you kept reverting it to "unconfirmed" Maybe mousewheel and stupid browser? Could happen if wheeling over the "resolved" combobox alters it instead of scrolling the page - *shrug* Yea, probably. I didn't even notice that thing. I can confirm this doesn't happen with the Breeze theme, but I really don't like the way it looks. Do all themes I download use QtQuick? Is there any way to tell if a theme uses QtQuick or not? (In reply to superrobowizard from comment #8) > Do all themes I download use QtQuick? Yes, sorry. You can alter the size of the breeze deco (and some other things, run "breeze-settings5") So I'm stuck with a theme I don't like or a theme that crashes my window manager occasionally. This doesn't sound like a good deal to me. Does only the desktop theme matter, only the window borders matter, or both? It's a qtquick related issue and will affect at least all aurorae themes (and most likely the Plastik decoration as well) no matter of any further settings. *** Bug 354467 has been marked as a duplicate of this bug. *** *** Bug 360422 has been marked as a duplicate of this bug. *** *** Bug 360703 has been marked as a duplicate of this bug. *** *** Bug 360799 has been marked as a duplicate of this bug. *** *** Bug 361023 has been marked as a duplicate of this bug. *** *** Bug 361035 has been marked as a duplicate of this bug. *** *** Bug 361287 has been marked as a duplicate of this bug. *** Same here on Arch Linux with GTX980 and proprietary Nvidia driver. *** Bug 362648 has been marked as a duplicate of this bug. *** *** Bug 363312 has been marked as a duplicate of this bug. *** *** Bug 363809 has been marked as a duplicate of this bug. *** *** Bug 364008 has been marked as a duplicate of this bug. *** *** Bug 364259 has been marked as a duplicate of this bug. *** *** Bug 364368 has been marked as a duplicate of this bug. *** *** Bug 365726 has been marked as a duplicate of this bug. *** *** Bug 366794 has been marked as a duplicate of this bug. *** *** Bug 370229 has been marked as a duplicate of this bug. *** |