Bug 405613 - System settings displays a black screen making it impossible to access and configure anything
Summary: System settings displays a black screen making it impossible to access and co...
Status: RESOLVED FIXED
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.20.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-03-18 21:34 UTC by pauloedgarcastro
Modified: 2021-03-04 22:03 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Screenshot of application (9.53 KB, image/png)
2019-03-18 21:34 UTC, pauloedgarcastro
Details
qdbus output (4.82 KB, text/plain)
2019-06-22 14:43 UTC, pauloedgarcastro
Details
glxinfo (49.30 KB, text/plain)
2019-06-22 14:43 UTC, pauloedgarcastro
Details

Note You need to log in before you can comment on or make changes to this bug.
Description pauloedgarcastro 2019-03-18 21:34:08 UTC
Created attachment 118896 [details]
Screenshot of application

SUMMARY


STEPS TO REPRODUCE
1. Login to KDE
2. Access System settings
3. 

OBSERVED RESULT
Blacked out window and left frame

EXPECTED RESULT
Normal System settings window with configuration options

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 5.14.5
(available in About System)
KDE Plasma Version: 5.14.5
KDE Frameworks Version: 5.55.0
Qt Version: 5.11.3

ADDITIONAL INFORMATION
nouveau driver and nvidia seem to produce the same result.
Comment 1 Christoph Feck 2019-03-31 08:48:12 UTC
Can you reproduce with a freshly added user account? Or with a Live DVD?
Comment 2 Christoph Feck 2019-04-16 20:23:09 UTC
If you can provide the information requested in comment #1, please add it.
Comment 3 Christoph Feck 2019-05-11 10:09:37 UTC
To further investigate this issue, KDE developers need the information requested in comment #1. If you can provide it, or need help with finding that information, please add a comment.
Comment 4 pauloedgarcastro 2019-05-11 12:23:23 UTC
Yes. I can reproduce with a new user who never had profile in the machine.
Comment 5 Christoph Feck 2019-05-21 18:13:13 UTC
Thanks for the update; changing status.
Comment 6 Christoph Feck 2019-06-14 16:25:38 UTC
Could you please show the output of these commands:

glxinfo

qdbus org.kde.KWin /KWin supportInformation

Also, do other applications using OpenGL work correctly?
Comment 7 pauloedgarcastro 2019-06-22 14:43:15 UTC
Created attachment 121077 [details]
qdbus output
Comment 8 pauloedgarcastro 2019-06-22 14:43:32 UTC
Created attachment 121078 [details]
glxinfo
Comment 9 pauloedgarcastro 2019-06-22 14:44:26 UTC
glxgears seems to work fine.
Upgraded to F30 and the issue still persists.
Comment 10 NeoFax 2020-12-12 18:42:55 UTC
I have this exact same problem running Arch Linux on a Raspberry Pi 4 using the xf86-video-fbturbo drivers.
Comment 11 pauloedgarcastro 2021-01-23 12:03:20 UTC
Any news on this bug or any other new information I can provide other than the fact that it is still happening ?

Operating System: Fedora 32
KDE Plasma Version: 5.18.5
KDE Frameworks Version: 5.75.0
Qt Version: 5.14.2
Kernel Version: 5.7.6-201.fc32.x86_64
OS Type: 64-bit
Processors: 2 × Intel® Core™2 Duo CPU E4500 @ 2.20GHz
Memory: 7.8 GiB of RAM
Comment 12 Nate Graham 2021-01-23 22:52:51 UTC
Reminds me of Bug 424592, but that's caused by the proprietary Nvidia driver, and you have an Intel iGPU.
Comment 13 pauloedgarcastro 2021-01-23 23:55:23 UTC
I have 2 hosts exhibiting the same problem and both have NVIDIA hardware.
One uses the nouveau driver the other one the proprietary NVIDIA.
Comment 14 Nate Graham 2021-01-25 15:38:55 UTC
The ones using the proprietary Nvidia driver are probably hitting Bug 424592.
Comment 15 pauloedgarcastro 2021-03-04 22:03:59 UTC
Today I noticed that my Xorg server was running with only 16 bit depth.
As soon as I configured sddm.conf with 
```
ServerArguments=-depth 24
```
Systems settings started working again.
Weirdly this behaviour of having Xorg run with 16 bit depth seems to be specific to machines with NVIDIA cards.
Other boxes with other cards like Intel don't seem to exhibit this behaviour that was generating the issu.