Bug 1141884 - Compositor broken with 30bpp
Compositor broken with 30bpp
Status: NEW
Classification: openSUSE
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: KDE Workspace (Plasma)
Current
x86-64 Other
: P5 - None : Major (vote)
: ---
Assigned To: E-Mail List
E-mail List
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-07-17 15:15 UTC by Mike Decker
Modified: 2019-07-19 19:53 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments
30-bit color window decorations without compositing (2.83 MB, image/jpeg)
2019-07-17 15:15 UTC, Mike Decker
Details
qdbus-qt5 org.kde.KWin /KWin supportInformation (4.15 KB, text/plain)
2019-07-19 19:49 UTC, Mike Decker
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Decker 2019-07-17 15:15:05 UTC
Created attachment 810757 [details]
30-bit color window decorations without compositing

With 30-bit color depth on X11, upon boot the screen remains black with only mouse pointer.  If compositor disabled, then desktop appears (albeit with window decorations incorrectly rendered.)  

This issue didn't exist until July ~10 after updating Tumbleweed.  Prior to that, Compositor & 30-bit color worked fine since January.

I was able to get a useable desktop via
$ qdbus-qt5 org.kde.KWin /Compositor suspend
and then I disabled compositor in system settings.

With compositing off, window decorations have wrong colors and garbled text. (I'm not sure if this was the case previously, as I always used compositing) Picture attached.  30-bit rendering within applications, such as Gimp, still appears to work correctly.

30-bit color config:
 /etc/X11/xorg.conf.d/50-screen.conf
    Section "Screen"
        Identifier "Default Screen"
        DefaultDepth 30
    EndSection

 /etc/X11/xorg.conf.d/10-amdgpu.conf
    Section "OutputClass"
            Identifier "AMDgpu"
            MatchDriver "amdgpu"
            Driver "amdgpu"
            Option "TearFree" "true"
    EndSection

/var/log/Xorg.0.log excerpt:
[    15.368] (II) AMDGPU: Driver for AMD Radeon:
        All GPUs supported by the amdgpu kernel driver
[    15.368] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[    15.368] (II) FBDEV: driver for framebuffer: fbdev
[    15.368] (II) VESA: driver for VESA chipsets: vesa
[    15.379] (II) AMDGPU(0): [KMS] Kernel modesetting enabled.
[    15.379] (WW) Falling back to old probe method for modesetting
[    15.380] (WW) Falling back to old probe method for fbdev
[    15.380] (II) Loading sub module "fbdevhw"
[    15.380] (II) LoadModule: "fbdevhw"
[    15.380] (II) Loading /usr/lib64/xorg/modules/libfbdevhw.so
[    15.380] (II) Module fbdevhw: vendor="X.Org Foundation"
[    15.380]    compiled for 1.20.5, module version = 0.0.2
[    15.380]    ABI class: X.Org Video Driver, version 24.0
[    15.381] (II) AMDGPU(0): Creating default Display subsection in Screen section
        "Default Screen" for depth/fbbpp 30/32
[    15.381] (**) AMDGPU(0): Depth 30, (--) framebuffer bpp 32
[    15.381] (II) AMDGPU(0): Pixel depth = 30 bits stored in 4 bytes (32 bpp pixmaps)
[    15.381] (==) AMDGPU(0): Default visual is TrueColor
[    15.381] (II) Applying OutputClass "AMDgpu" options to /dev/dri/card0
[    15.381] (**) AMDGPU(0): Option "TearFree" "true"
[    15.381] (==) AMDGPU(0): RGB weight 101010
[    15.381] (II) AMDGPU(0): Using 10 bits per RGB (8 bit DAC)
[    15.381] (--) AMDGPU(0): Chipset: "AMD Radeon (TM) RX 460 Graphics" (ChipID = 0x67ef)

/var/log/messages excerpt:

2019-07-13T07:32:31.634596-04:00 katie-box ksplashqml[1718]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 8)
2019-07-13T07:32:31.635086-04:00 katie-box ksplashqml[1718]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 2)
2019-07-13T07:32:31.694899-04:00 katie-box ksplashqml[1718]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 8)
2019-07-13T07:32:31.695581-04:00 katie-box ksplashqml[1718]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 2)

Jul 13 15:41:49 katie-box kwin_x11[1782]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 8)
Jul 13 15:41:49 katie-box kwin_x11[1782]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 2)
Jul 13 15:41:52 katie-box kwin_x11[1782]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 8)
Jul 13 15:41:52 katie-box kwin_x11[1782]: qt.glx: qglx_findConfig: Failed to finding matching FBConfig (10 10 10 2)
Jul 13 15:41:54 katie-box kwin_x11[1782]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9054, resource id: 77595112, major code: 18 (ChangeProperty), minor code: 0
Jul 13 15:41:54 katie-box kwin_x11[1782]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 9059, resource id: 79691787, major code: 18 (ChangeProperty), minor code: 0

The FBConfig error messages have littered my log since January, but I included them as they may still be pertinent..  The XOrg log indicates 10-10-10-2 would be the expected framebuffer format.  Not sure why it's looking for 10-10-10-8. 38-bit pixels eh?
Comment 1 Mike Decker 2019-07-18 13:02:12 UTC
Background on 30bpp:
https://wiki.gentoo.org/wiki/30bpp

I also created a new user & logged in, but the same behavior occurs; black screen when compositor is running.

I also tried resetting to Defaults all Desktop Effects, and I tried disabling all of those that were uncheckable.  No change.

If there is some way to log additional information that may be insightful, let me know.

I would verify this behavior with a fresh install (+ 30bpp config), except this is my wife's daily workstation and it would be disruptive to make such changes.  If someone else can verify this is reproducible, that would be awesome sauce.
Comment 2 Mike Decker 2019-07-19 19:49:58 UTC
Created attachment 811076 [details]
qdbus-qt5 org.kde.KWin /KWin supportInformation

This is the output of 
$ qdbus-qt5 org.kde.KWin /KWin supportInformation
Comment 3 Mike Decker 2019-07-19 19:53:08 UTC
After setting compositor backend to XRender and enabling, the desktop would appear but it would freeze up after a minute.  After a fresh reboot, however, it's been running stable.  OpenGL backends still produce a black screen.