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.
https://bugs.kde.org/show_bug.cgi?id=385324
Vlad Zagorodniy changed:
What|Removed |Added
CC||techxga...@outlook.com
--- Comment #17 from V
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 effec
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
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 se
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 X
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
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 graphic
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:
https://bugs.kde.org/show_bug.cgi?id=385324
younker...@gmail.com changed:
What|Removed |Added
CC||younky.y...@yahoo.com
--- Comment #9 fro
https://bugs.kde.org/show_bug.cgi?id=385324
Till Schäfer changed:
What|Removed |Added
CC||till2.schaefer@uni-dortmund
|
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-setti
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 chi
https://bugs.kde.org/show_bug.cgi?id=385324
Martin Flöser changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Status|UNCONFIRMED
https://bugs.kde.org/show_bug.cgi?id=385324
Markus changed:
What|Removed |Added
Resolution|INVALID |---
Status|RESOLVED|UN
https://bugs.kde.org/show_bug.cgi?id=385324
Martin Flöser changed:
What|Removed |Added
Resolution|--- |INVALID
Status|UNCONFIRMED
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.
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 repla
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.
19 matches
Mail list logo
