https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #113 from Tsu Jan ---
Shouldn't the title be changed to "Black or corrupted screen on resume from
suspend with nVidia"? I had this issue with nVidia but never with Intel.
--
You are receiving this mail because:
You are watching all bug cha
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #112 from Alonso Murillo ---
Hi I am using;
Linux Mint 17.3 KDE 64bits
Kernel 3.13.0-87-generic
NVidia 340.96 (and have try other versions of it too)
Xorg 11.0
And sometimes when put computer on standby when wakes up every things looks
fin
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #111 from JS Gibson ---
Cool. Makes me look forward to the next nVidia driver.
JSG
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #110 from Thomas Lübking ---
It's probably the same issue but here affects the GL context in plasmashell
(the desktop process)
Anything you do on kwin (incl. restarting the compositor) has thus no effect.
=> You'll have to restart plasmashe
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #109 from JS Gibson ---
Comment on attachment 99461
--> https://bugs.kde.org/attachment.cgi?id=99461
Labels of desktop items in Folder View are replaced with colorful noise.
Replying to this from a email I received re: Bug 344326. I get t
https://bugs.kde.org/show_bug.cgi?id=344326
Chris changed:
What|Removed |Added
CC||emailofch...@gmail.com
--- Comment #108 from Chris ---
https://bugs.kde.org/show_bug.cgi?id=344326
Ben Cooksley changed:
What|Removed |Added
CC|rajind...@hotmail.com |
--- Comment #107 from Ben Cooksley ---
Removin
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #106 from Thomas Lübking ---
Once we reliably get aware of it, its time to wipe fbo & vbo - it's what
already happens for vbo's atm, just based on a hack interpreting a GL error
(ie. when it's actually too late)
As long as we don't map the
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #105 from Martin Gräßlin ---
> Unfortunately it's not even (yet) linked in
> https://developer.nvidia.com/nvidia-opengl-specs so far (bleeding edge beta
> feature)
I got contacted by an NVIDIA dev and have a copy of the spec.
So yes, mos
https://bugs.kde.org/show_bug.cgi?id=344326
deadite66 changed:
What|Removed |Added
CC||lee295...@gmail.com
--
You are receiving this mail
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #104 from Rafael ---
Actually, I have not "broken glass effect" (as my screencast showed) but
however I still have "noise" in all windows till I resize them.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #103 from Thomas Lübking ---
Probably. There're mentions it'd only fire on FBOs, but since those would
likely go alongside.
Unfortunately it's not even (yet) linked in
https://developer.nvidia.com/nvidia-opengl-specs so far (bleeding edge be
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #102 from Nick Guletskii ---
Could the new NV_robustness_video_memory_purge extension be used to detect when
to trigger an update?
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
JS Gibson changed:
What|Removed |Added
CC||jgibson...@gmail.com
--- Comment #101 from JS Gibso
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #100 from Thomas Lübking ---
Sure it's the same bug? Can you ping or even ssh into the woken (but black)
machine or maybe even switch the VT? Does it go away when suspending the
compositor before STR?
(Wake-up issues can have other causes, e
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #99 from Blucode ---
Bad news:
Driver Version 361.28 still has the bug with KWin : 4.11.11.
No more crazy triangles but X hang and STR or simple system shutdown may hang.
I'll have to upgrade distro for next KWin...
--
You are receiving t
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #98 from Blucode ---
I've found this talk mentioning a new nvidia driver that no longer has the
suspend-to-RAM broken :
https://devtalk.nvidia.com/default/topic/791786/linux/dpms-not-working-on-gtx980-with-displayport-connection/3
It's mainl
https://bugs.kde.org/show_bug.cgi?id=344326
Sean Mackedie changed:
What|Removed |Added
CC|colonelpani...@gmail.com|
--
You are receiving this mail because:
You a
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #97 from Thomas Lübking ---
As mentioned, there's a workaround in KWin 5.4 and up.
4.x won't see any upstream updates and the patch isn't easy to backport.
The bug is (likely) in the nvidia driver when moving VBOs between system and
video R
https://bugs.kde.org/show_bug.cgi?id=344326
Blucode changed:
What|Removed |Added
CC||bluflonal...@gmail.com
--- Comment #96 from Blucode
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #95 from Thomas Lübking ---
This bug is about resuming from STR (and nvidia), not about screen locking.
Also it's worked around in 5.4 (though kwin can still crash in the driver)
--
You are receiving this mail because:
You are watching all
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #94 from Blucode ---
Created attachment 97061
--> https://bugs.kde.org/attachment.cgi?id=97061&action=edit
Disable KDE compositor uppon lock screen (and restore state after)
Using Linux Mint 17.3 KDE Edition, I'm affected by this 1 year o
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #93 from Thomas Lübking ---
Yes, it's supposed to be work-a-rounded by the patch in comment #53 (applies to
5.4 and up)
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
Stuart Citrin changed:
What|Removed |Added
CC||ctrn...@gmail.com
--- Comment #92 from Stuart C
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #91 from Thomas Lübking ---
(In reply to Rafael from comment #88)
> But disable screenlock will not do nothing about the "bricked text", cause
> it only appears on the screenlock window.
That's ok. Basically, If you don't get the black/loc
https://bugs.kde.org/show_bug.cgi?id=344326
Rafael changed:
What|Removed |Added
Attachment #95851|Some letters are hidden |Some letters are hidden.
description|
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #90 from Rafael ---
Comment on attachment 95851
--> https://bugs.kde.org/attachment.cgi?id=95851
Some letters are hidden
It should show: "martes, 1 de diciembre de 2015" below time. And "Desbloquear"
in the button.
--
You are receiving
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #89 from Rafael ---
Created attachment 95851
--> https://bugs.kde.org/attachment.cgi?id=95851&action=edit
Some letters are hidden
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #88 from Rafael ---
Ok with STR. I must say that I ONLY have "bricky text" on the screen lock form
window. Just some hours ago I had a similar issue (see the next screenshot) but
this time I even can only enter my password in one of my moni
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #87 from Thomas Lübking ---
Suspend To Ram ;-)
Can you interact with the login screen with the bricky text?
(Either the particular greeter GL context - *in* the client - has trouble with
its glyph cache or the greeter isn't shown at all and
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #86 from Rafael ---
Created attachment 95836
--> https://bugs.kde.org/attachment.cgi?id=95836&action=edit
My second monitor (not the primary, but the VGA) was showing correctly the
text.
--
You are receiving this mail because:
You are wa
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #85 from Rafael ---
Created attachment 95835
--> https://bugs.kde.org/attachment.cgi?id=95835&action=edit
"Doubled view" on one of my two monitors in the lock out screen
I have TWO monitors, and only the default monitor showed the "double
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #84 from Rafael ---
Hi again.
Thomas Lübking , I don't know what's the meaning of STR. If you ask me if I
suspended my desktop PC on the locked screen, I should say "maybe", cause I
have a delay of 1 hour to sleep my system when afk.
--
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #83 from Thomas Lübking ---
It's related to a shader based, hyperfast multisamplig (FXAA) which, ie enabled
*while the GL context is created!*, turns the entire desktop blurry (but is
indeed especially notable on text - or other thin lines w
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #82 from Rafael ---
Thank you Ruslan Kabatsayev , but it's not the same issue. Mine only had
happened if login after wake up. The 307003 bug seems to be subpixel rendering
related.
; )
--
You are receiving this mail because:
You are watc
https://bugs.kde.org/show_bug.cgi?id=344326
Bas van Schaik changed:
What|Removed |Added
CC|b...@tuxes.nl|
--
You are receiving this mail because:
You
https://bugs.kde.org/show_bug.cgi?id=344326
Anselmo L. S. Melo (anselmolsm) changed:
What|Removed |Added
CC|anselmo...@gmail.com|
--
You are receiving this m
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #81 from Ruslan Kabatsayev ---
(In reply to Rafael from comment #79)
> Another atypical issue I saw some time in the unlock screen is "crossed
> text", that's to say, the text (and only the text) appeared like if you
> put your eyes "cross
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #80 from Thomas Lübking ---
(In reply to Rafael from comment #79)
> way to recover a visible screen. Only the cursor was visible. I needed to do
> "" to recover my desktop :(
Do you lock the screen over STR?
--
You are receiving this ma
https://bugs.kde.org/show_bug.cgi?id=344326
--- Comment #79 from Rafael ---
Usually, in Plasma, I only have a part of the windows with noise, as I told
previously. But yesterday, after wake up, the screen was in black and no way
to recover a visible screen. Only the cursor was visible. I needed
40 matches
Mail list logo
