| Summary: | Kwin Crashes after suspend | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | chadwick.ferguson |
| Component: | scene-opengl | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | bugs.kde.org.id324, dennwc, ivarkde, shao.lo |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.3.0 | Flags: | thomas.luebking:
NVIDIA+
|
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| See Also: |
https://bugs.kde.org/show_bug.cgi?id=344326 https://bugs.kde.org/show_bug.cgi?id=346639 |
||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
SDDM corruption
Backtrace kwin wobbly + edge flip when moving tail .xsession-errors -f > xsession-errors_kwin_sddm_suspend_resume.txt kwin bt normaloperation kwin bt while distorted Installed pertinent files kwin bt normaloperation, nearly all effects disabled kwin bt while distorted, nearly all effects disabled |
||
|
Description
chadwick.ferguson
2015-04-09 17:00:15 UTC
Created attachment 91967 [details]
SDDM corruption
This may or may not be related at all, generally when this happens I enter my password blind, hit enter, alt+shift+f12 and it goes away, alt+shift+f12 back on is fine too. Sometime kwin will crash in the midst of this.
looks like faile VBO mapping - can you please check the stock nvidia blob? likely a dupe of bug #344326 FYI 349.12-0ubuntu0~xedgers14.04.1 Created attachment 92089 [details]
Backtrace kwin wobbly + edge flip when moving
That's bug #338972 - completely unrelated. Created attachment 92091 [details]
tail .xsession-errors -f > xsession-errors_kwin_sddm_suspend_resume.txt
.xsession-errors for the following
1) tail default 10 lines
2) click Kmenu
3) move to leave tab
4) click Sleep (suspend to ram)
5) wake with key press
6) same glitch as in the image when wake
7) enter password, hit Enter to login from sddm
8) Alt+Shift+F12
9) click on konqueror that is running tail
10) Ctrl-c
Comment on attachment 92089 [details]
Backtrace kwin wobbly + edge flip when moving
Red Herring
Comment on attachment 92091 [details]
tail .xsession-errors -f > xsession-errors_kwin_sddm_suspend_resume.txt
346.59-0ubuntu1 FYI
Created attachment 92092 [details]
kwin bt normaloperation
$ sudo gdb -p `ps ax | grep kwin | cut -b 2-5 | head -n 1` -batch -ex "thread apply all bt full" > kwin-bt.txt
Created attachment 92093 [details]
kwin bt while distorted
$ sudo gdb -p `ps ax | grep kwin | cut -b 2-5 | head -n 1` -batch -ex "thread apply all bt full" > kwin-bt2.txt
So the triangle distortions were flickering until I ran this command, they stopped, then resumed after it printed its backtrace I hope its a good sign.
Created attachment 92094 [details]
Installed pertinent files
> KWin::ShowFpsEffect::paintScreen
Is running the fps effect a crucial trigger for this to happen or why is it active?
The flicker stops while gdb is running because gdb stalls the process (kwin_x11), so the compositor cannot paint anything.
no showfps is not needed. I'll try to disable everything besides compositor and see if I can get it to distort again. Created attachment 92095 [details]
kwin bt normaloperation, nearly all effects disabled
Created attachment 92097 [details]
kwin bt while distorted, nearly all effects disabled
*** Bug 346639 has been marked as a duplicate of this bug. *** Of course still present in 5.3.0 NVIDIA says branch 346 will be updated and 349 won't be when referencing this bug. nvidia says what where? I could be reading too much into it (why would they allude to the 346 btanch going to receive updates) but I filed this bug and their tech said: Did you try my suggestion to make the vesa warning go away? If that does not help: You are using driver version 349.16 and there are no further releases planned from that driver branch. Please try the current 346.59 driver available here for x64: http://www.nvidia.com/download/driverResults.aspx/83686/en-us There are updates planned for the 346 driver branch. If that driver does not help, please list the steps required to reproduce this problem. Corruption now also appears after vt switch. corruption never affects cursor. any graphical distorsion after STR, VT switch and maybe xrandr switches on nvidia is dupe of bug #344326 for pretty much sure. regular cursor is done in HW and painted into the scanout, so it's not very surprising that it's not affected by invalidated VBO data. *** Bug 350076 has been marked as a duplicate of this bug. *** I'd just like to say on Fedora 22, I'm often bitten by this to the point where I have to consciously suspend effects before manually suspending (is most helpful) otherwise, logging back in is tough because you can't see what you're doing. Usually when this type of distortion happens (changing display setups e.g., enable or disable an extra monitor), suspending and resuming effects (Shift+Alt+F12) helps resolve it. I am currently using Nvidia binary 352.30 atm but this was there when I was using Nouveau. if there is something more I can add, please help me add it. Thanks! You can either compile KWin with the patch on bug #344326 or wait for 5.4 (which includes the patch) and check for the impact. While it may be possible that you encountered similar issues with nouveau, it's rather unlikely been the very same bug (and probably not covered by the workaround which operates on gl messages to catch RAM => VRAM data transfers to reset VBOs) *** Bug 365274 has been marked as a duplicate of this bug. *** Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! 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! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now 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 Thank you for helping us make KDE software even better for everyone! |