Bug 466317 - Entire windows randomly black
Summary: Entire windows randomly black
Status: RESOLVED DUPLICATE of bug 466771
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.26.5
Platform: Manjaro Linux
: NOR major
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-02-23 18:55 UTC by php4fan
Modified: 2023-06-12 21:46 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description php4fan 2023-02-23 18:55:49 UTC
SUMMARY

It has happened to me twice in the last few minutes that some windows were completely black when opened or focused.


STEPS TO REPRODUCE & OBSERVED RESULT
1.  gave focus to TortoiseHg's window which was already open and previously minified. The window was black (with the border and top bar visible though. After minimizing and refocusing it, it went back to normal.
2. I deleted a few selected files with shift+Del from within a folder in Dolphin, which results in a popup showing up to ask for confirmation. The inside of the popup was completely black. I hit Esc and repeated the operation and this time the popup showed up normally.

In both cases I forgot to try to resize the windows (probably possible only in the first case) and I think I also didn't try moving them around.

EXPECTED RESULT

Obviously no window should ever be black.

Note that this is critical because, even though most of the time closing and reopening the window will fix it, that's not  guaranteed to be something that you can always do.

SOFTWARE/OS VERSIONS
Operating System: Manjaro Linux
KDE Plasma Version: 5.26.5
KDE Frameworks Version: 5.102.0
Qt Version: 5.15.8
Kernel Version: 6.0.19-3-MANJARO (64-bit)
Graphics Platform: X11
Processors: 8 × Intel® Core™ i7-1065G7 CPU @ 1.30GHz
Memory: 7.3 GiB of RAM
Graphics Processor: Mesa Intel® Iris® Plus Graphics
Manufacturer: LENOVO
Product Name: 81WE
System Version: IdeaPad 3 15IIL05
Comment 1 php4fan 2023-03-05 17:05:38 UTC
This keeps happening. Sometimes, instead of an entire window, it's a submenu of a dropdown menu of some application, such as PhpStorm, that is fully black.

In at least one occasion, closing and reopening the same submenu alone would not fix the issue, but minimizing and then restoring the whole window of the affected application did.
Comment 2 Craig Howard 2023-03-21 05:59:07 UTC
I've observed the same.  It usually manifests in one of two ways:

* a completely black window, usually a desktop notification
* a window that won't repaint, sometimes the screen lock

I run X11 and cannot switch to wayland, because my workflow relies on barriers/barrierc, which are X11 only at the moment.  This is on a desktop with a single monitor.  Note that kwin --replace does not mitigate the issue.  Neither does loginctl unlock-session (the mouse pointer changes and I can click, but the screen is not updated).  I see this once every few days, I will try restarting plasmashell next time it occurs.

There's a reddit thread with two others observing the same behaviour: https://www.reddit.com/r/kdeneon/comments/11x2oxd/notification_appears_black_and_after_that_the/

My system details are below.  I started observing this in neon a month or two ago; I'm not sure exactly when.  I'm not sure what other debugging information would be useful; let me know.  Nothing jumps out at me in journalctl.  I've seen a few cores in plasmashell, but they don't seem to correlate to this issue.

Operating System: KDE neon 5.27
KDE Plasma Version: 5.27.2
KDE Frameworks Version: 5.103.0
Qt Version: 5.15.8
Kernel Version: 5.19.0-35-generic (64-bit)
Graphics Platform: X11
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 62.7 GiB of RAM
Graphics Processor: AMD Radeon RX 6750 XT
Manufacturer: Gigabyte Technology Co., Ltd.
Product Name: X570 AORUS ELITE
System Version: -CF
Comment 3 Craig Howard 2023-03-23 17:26:50 UTC
This just happened to me again; the screen locker was up and the screen lock window froze.  For the first time I was able to recover without a reboot.

From a console:

export DISPLAY=:0
loginctl unlock-session 1
killall plasmashell
kstart plasmashell &
kwin --replace &
Comment 4 Nacho 2023-05-11 10:29:53 UTC
I have exactly the same issue, and it doesn't seem to happen due to any particular application, although in my case the notifications that go black are usually from Slack and Spotify. I've seen other people with similar issues using Discord, so perhaps it's related to Electron. In my particular case, it's usually happening after 4-5 hours of work.

I've using the same laptop for years and I've began to see this problem just in the last months, but couldn't say exactly when started.

Specs: 
SO: Kubuntu 22.04
KDE Plasma version: 5.24.7
KDE Frameworks Version: 5.92.0
Qt Version: 5.15.3
Kernel Version: 5.19.0-41-generic
Processors: 16xIntel Code i7-10875H CPU @2.30Ghz
Memory: 32 Gb
Graphics: Mesa Intel UHD and Nvidia Geforce RTX 2060 (using Nvidia propietary driver, with Nvdia On Demand)
Comment 5 Kishore Gopalakrishnan 2023-05-20 12:47:55 UTC
This seems related to https://bugs.kde.org/show_bug.cgi?id=457847#c8
Are any of you using mesa >= 22.3?
Comment 6 Craig Howard 2023-05-21 05:52:58 UTC
(In reply to Kishore Gopalakrishnan from comment #5)
> This seems related to https://bugs.kde.org/show_bug.cgi?id=457847#c8
> Are any of you using mesa >= 22.3?

No.  I'm on 22.2.5-0ubuntu0.1~22.04.1

I've disabled notifications through kde connect, which is where I get the vast majority of my notification popups and I've not had a problem since I did that.  Seems highly likely it's something to do with notifications.
Comment 7 Kishore Gopalakrishnan 2023-05-21 06:03:04 UTC
Please change the status if this is still reproducible with mesa >= 22.3 (see https://bugs.kde.org/show_bug.cgi?id=457847#c22)

*** This bug has been marked as a duplicate of bug 457847 ***
Comment 8 Nacho 2023-05-22 11:36:00 UTC
Same for me, Mesa 22.2.5, but not using KDE Connect at all
Comment 9 php4fan 2023-06-05 16:10:24 UTC
I have mesa 23.0.3-1 and yet I am still observing this as described in my original report.

Either this is not really a duplicate of 457847, or it is not fixed.

Actually, now that I read 457847, I don't know why this got marked as duplicate. I see no similarity whatsoever between what is described in the two issues.

What I observe is what I described in the originla report and my first comment; none of the other issues that have been commented by other users.
Comment 10 Craig Howard 2023-06-06 05:25:03 UTC
FWIW, since I installed mesa from ppa:kisak/kisak-mesa (currently 23.1.1) I've not been able to reproduce.  It's been over a week, so I believe that's a fix.  It's entirely possible my original "me too" was on the wrong issue though.
Comment 11 David Edmundson 2023-06-12 21:46:16 UTC

*** This bug has been marked as a duplicate of bug 466771 ***