[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #18 from Vlad Zagorodniy --- *** Bug 401410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 Vlad Zagorodniy changed: What|Removed |Added CC||techxga...@outlook.com --- Comment #17 from Vlad Zagorodniy --- *** Bug 401410 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #16 from YAFU --- @Markus, Thank you very much for the workaround. I have the same problem in Kubuntu 18.04. Currently 390.48 nvidia driver installed. Most of the time when I resume/wake up PC from sleep/suspend to RAM, I get "Desktop effects were restarted due to a graphics reset" message and the composition breaks down, it starts blinking/flickering in Brisa window decorator title bar, the task manager in panel starts to work wrong, some applications are not shown and panel becomes full transparent. It is really annoying. Running Markus script returns everything to normal. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #15 from Markus --- Updated to nvidia-drivers-390.12, now the pipeline workaround does no longer work for me. Because kwin is unable to recover from the graphics reset I created a small script in ~/.config/autostart/ that will restart kwin to enable compositing again. Its working fine for me and at least reduces the impact of the Xid 31. #!/bin/sh touch /tmp/restart_kwin while true do if test -e /tmp/restart_kwin then rm /tmp/restart_kwin ( kwin_x11 --replace 2>&1 | while read line do if test "_$line" = "_kwin_core: Failed to initialize compositing, compositing disabled" then touch /tmp/restart_kwin fi done ) &> /dev/null & fi sleep 1 done -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #14 from younker...@gmail.com --- (In reply to Markus from comment #13) > nvidia-settings => "X Server Display Configuration" => Button "Advanced..." > => Now you should see the two checkboxes. (The setting is per device, so you > need to set it twice if you use dualhead/twinview.) > > The cause for Xid 31 (comment#7) is very vague, so it can be kwin, it can be > the application (like konqueror/akreagtor) or the nvidia driver. Thanks a lot. I will use these 2 options to avoid this error for some time. Just hope these 2 options will not impact the performance of CUDA as I bought this nvidia card to use for my machine learning stuff. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #13 from Markus --- nvidia-settings => "X Server Display Configuration" => Button "Advanced..." => Now you should see the two checkboxes. (The setting is per device, so you need to set it twice if you use dualhead/twinview.) The cause for Xid 31 (comment#7) is very vague, so it can be kwin, it can be the application (like konqueror/akreagtor) or the nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #12 from younker...@gmail.com --- btw, this maybe an issue of kwin. As the issue happens, the mouse cursor is still able to move, which means the driver still works, but just the application calls something which cause the GPU memory states error, right? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #11 from younker...@gmail.com --- (In reply to Markus from comment #10) > Yes I still have this problem. > Those pipeline setting prevents it. (At cost of performance.) > > I still think its at least two bugs: > 1. Recovery from the graphics reset is not working. (kwin bug?) > 2. Graphics reset itself: Intended behaviour of driver: "Typically these are > application-level bugs, but can also be driver bugs or hardware bugs." So it > can be nvidia and/or "application" (kwin, or what ever application uses the > hw directly) But how do you enable the 2 options through nvidia-settings. I can't see it from the GUI, and when I use the command line nvidia-settings -q all, I can't see these 2 options either. Thanks -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #10 from Markus --- Yes I still have this problem. Those pipeline setting prevents it. (At cost of performance.) I still think its at least two bugs: 1. Recovery from the graphics reset is not working. (kwin bug?) 2. Graphics reset itself: Intended behaviour of driver: "Typically these are application-level bugs, but can also be driver bugs or hardware bugs." So it can be nvidia and/or "application" (kwin, or what ever application uses the hw directly) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 younker...@gmail.com changed: What|Removed |Added CC||younky.y...@yahoo.com --- Comment #9 from younker...@gmail.com --- (In reply to Markus from comment #8) > https://devtalk.nvidia.com/default/topic/1023621/linux/frequent-kwin- > compositing-failure-with-associated-xid-31-error/post/5207959/ > Setting "Force Composition Pipeline" and "Force Full Composition Pipeline" > in nvidia-settings works as workaround. (reduce performance) Do you still have the issue? I still have the issues which is annoying. I have posted some update on the devtalk.nvidia thread, but seems no nvidia people care about it. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #8 from Markus --- https://devtalk.nvidia.com/default/topic/1023621/linux/frequent-kwin-compositing-failure-with-associated-xid-31-error/post/5207959/ Setting "Force Composition Pipeline" and "Force Full Composition Pipeline" in nvidia-settings works as workaround. (reduce performance) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #7 from Markus --- http://docs.nvidia.com/deploy/xid-errors/index.html#topic_2 XID 31: Fifo: MMU Error This event is logged when a fault is reported by the MMU, such as when an illegal address access is made by an applicable unit on the chip Typically these are application-level bugs, but can also be driver bugs or hardware bugs. When this event is logged, NVIDIA recommends the following: * Run the application in cuda-gdb or cuda-memcheck , or * Run the application with CUDA_DEVICE_WAITS_ON_EXCEPTION=1 and then attach later with cuda-gdb, or * File a bug if the previous two come back inconclusive to eliminate potential NVIDIA driver or hardware bug. Note: The cuda-memcheck tool instruments the running application and reports which line of code performed the illegal read. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 Martin Flöser changed: What|Removed |Added Resolution|--- |DUPLICATE Status|UNCONFIRMED |RESOLVED --- Comment #6 from Martin Flöser --- *** This bug has been marked as a duplicate of bug 385291 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 Markus changed: What|Removed |Added Resolution|INVALID |--- Status|RESOLVED|UNCONFIRMED --- Comment #5 from Markus --- 1. The message states that the effect were restarted. (Which is wrong, they are not restarted. I am left a static "desktop", new windows are not shown in the taskbar.) 2. The recovery after such an intended reset is not working. (Restarting kwin does work though.) 3. What I think is interesting, that the reset is happening when konqueror starts. (Without any open page being rendered.) And not when using any fancy 3d applications. So you are sure that the reset is about something wrong in driver, that can not be caused by userland? (I cannot judge what kind of error would issue such a reset.) 1 and 2 ares still valid for kwin, I think. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 Martin Flöser changed: What|Removed |Added Resolution|--- |INVALID Status|UNCONFIRMED |RESOLVED --- Comment #4 from Martin Flöser --- Graphics reset is something the graphics driver reports to KWin. This is intended behavior (restart instead of crash). That the driver triggers graphics resets is something you need to report to your driver. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #3 from Markus --- Created attachment 108140 --> https://bugs.kde.org/attachment.cgi?id=108140&action=edit qdbus org.kde.KWin /KWin org.kde.KWin.supportInformation -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #2 from Markus --- Created attachment 108139 --> https://bugs.kde.org/attachment.cgi?id=108139&action=edit kwin_x11 log output Replace kwin, then started konqueror via alt+f2 a few times until the message is displayed. (After that I replaced kwin again.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 385324] kwin: Desktop effects were restarted due to a graphics reset
https://bugs.kde.org/show_bug.cgi?id=385324 --- Comment #1 from Markus --- Shift+Alt+F12 of course. -- You are receiving this mail because: You are watching all bug changes.
