Some of my KDE apps aren’t working properly. Some apps just glitch in a way where part of the app is “transparent” and glitchy (for example, falkon). Other apps just crash when I lunch them (example: marble).
falkon not working properlly:
1 Like
I am seeing something similar on Falkon, GhostWriter and KMail.
A couple of questions:
-
Are you on Plasma 6.3.4?
-
Is the screenshot from Wayland? What do you see if you open the glitchy apps in X11?
For the record, here is my post about this issue:
1 Like
It looks like a rendering issue. You can get info about it, for example, by using the optimus-manager script system-info.sh
For that type into the terminal:
curl --silent https://raw.githubusercontent.com/Askannz/optimus-manager/refs/heads/master/system-info.sh | bash &> ~/system-info.txt
And share the result with us.
My video card is an AMD.
- Download the script.
- In the
mainFunctioncomment out any function with the namenvidiaoroptimus. - Run the script.
Hi! That issue almost looks similar to ones that popped up for a while where a GPU shader cache got into a bad state after Mesa updates, and caused rendering issues in Chromium browsers: Chromium-based browsers display garbled web pages after Mesa is updated - Fedora Discussion
Does the issue occur on a freshly created user account on your device, by chance? I wonder if maybe there are some equivalent shader caches for either Qt or Mesa that could be susceptible to the same issue now?
1 Like
Does the issue occur on a freshly created user account on your device, by chance?
In my case, yes.
Ah, I see. This is why qTerminal is behaving weirdly on my system.
qTerminal is a pure qt6 app. Also I’m using nvidia.
=== inxi ===
System:
Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64
Desktop: KDE Plasma v: 6.3.4 Distro: Zenned
Machine:
Type: Laptop System: LENOVO product: 81Y4 v: IdeaPad Gaming 3 15IMH05
serial: <superuser required>
Mobo: LENOVO model: LNVNB161216 v: NO DPK serial: <superuser required> UEFI: LENOVO v: EGCN40WW
date: 11/15/2022
Graphics:
Device-1: Intel CometLake-H GT2 [UHD Graphics] driver: i915 v: kernel
Device-2: NVIDIA TU117M [GeForce GTX 1650 Mobile / Max-Q] driver: nvidia v: 570.133.07
Device-3: Creative Live! Cam Sync 1080p V2 driver: snd-usb-audio,uvcvideo type: USB
Device-4: Chicony Integrated Camera driver: uvcvideo type: USB
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6 driver: X:
loaded: modesetting,nvidia gpu: i915,nvidia,nvidia-nvswitch resolution: 1: N/A 2: N/A
API: EGL v: 1.5 drivers: iris,nouveau,nvidia,swrast platforms: gbm,x11,surfaceless,device
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 570.133.07 renderer: NVIDIA GeForce
GTX 1650/PCIe/SSE2
API: Vulkan v: 1.4.309 drivers: N/A surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor
gpu: nvidia-smi wl: wayland-info x11: xdpyinfo, xprop, xrandr
Sensors:
System Temperatures: cpu: 56.0 C pch: 59.0 C mobo: N/A
Fan Speeds (rpm): N/A
Repos:
Active pacman repo servers in: /etc/pacman.conf
1: https: //express-repository.eu-central-1.linodeobjects.com/packages
Active pacman repo servers in: /etc/pacman.d/mirrorlist
1: https: //johannesburg.mirror.pkgbuild.com/$repo/os/$arch
2: https: //de.arch.niranjan.co/$repo/os/$arch
3: https: //at.arch.niranjan.co/$repo/os/$arch
4: https: //taipei.mirror.pkgbuild.com/$repo/os/$arch
5: https: //singapore.mirror.pkgbuild.com/$repo/os/$arch
=== display manager ===
sddm
=== lspci ===
00:02.0 VGA compatible controller: Intel Corporation CometLake-H GT2 [UHD Graphics] (rev 05)
01:00.0 VGA compatible controller: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] (rev a1)
=== xrandr providers ===
Providers: number : 2
Provider 0: id: 0x1b7 cap: 0x1, Source Output crtcs: 4 outputs: 1 associated providers: 1 name:NVIDIA-0
Provider 1: id: 0x1ff cap: 0x2, Sink Output crtcs: 3 outputs: 1 associated providers: 1 name:modesetting
=== glxinfo offloaded ===
server glx vendor string: NVIDIA Corporation
client glx vendor string: NVIDIA Corporation
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce GTX 1650/PCIe/SSE2
=== kernel errors ===
Jan 28 19:43:58 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 19:43:58 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 19:53:56 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 20:31:40 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 20:31:40 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 20:34:53 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 20:34:53 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
Jan 28 20:39:31 Ultra kernel: [drm:drm_new_set_master] *ERROR* [nvidia-drm] [GPU ID 0x00000100] Failed to grab modeset ownership
@tortoise501 Can you please open Info Centre and press the “Copy Details” button, and paste the result here?
In particular, I’d like to know if you are using Qt 6.9.
A temporary workaround could be to run affected applications with the following env:
QTWEBENGINE_CHROMIUM_FLAGS="--disable-gpu --disable-gpu-compositing" <application>
substituting <application> with whatever application.
Paul is reporting this to Qt, but it’ll be useful to know if you also have an AMD GPU.
The Qt engineers bumped this bug to “critical” so hopefully we will have a solution soon.
2 Likes
I have the same issues as reported by Paul_Brown, with the same invisible screen using Wayland and the same artifacts using Xorg. The issues appear on Falkon and KMail. I am using AMD graphics card.
The info centre details:
Operating System: Arch Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.13.8-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 24 × 12th Gen Intel® Core™ i9-12900K
Memory: 31.1 Gio of RAM
Graphics Processor 1: AMD Radeon RX 6700 XT
Graphics Processor 2: Intel® UHD Graphics 770
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7D32
System Version: 1.0
I can reproduce this issue in various Qt-WebEngine based apps on my KDE Plasma and AMD/ Intel based system:
Operating System: Manjaro Linux
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.12.22-1-MANJARO (64-bit)
Graphics Platform: Wayland
Processors: 6 × Intel® Core™ i5-8600K CPU @ 3.60GHz
Memory: 31.2 GiB of RAM
Graphics Processor 1: AMD Radeon RX 6800
Graphics Processor 2: Intel® UHD Graphics 630
Manufacturer: Micro-Star International Co., Ltd.
Product Name: MS-7B46
System Version: 1.0
But not on my Gnome - Intel based Laptop:
# System Details Report
---
## Report details
- **Date generated:** 2025-04-08 17:47:01
## Hardware Information:
- **Hardware Model:** Lenovo Lenovo Yoga C940-14IIL
- **Memory:** 16.0 GiB
- **Processor:** Intel® Core™ i7-1065G7 × 8
- **Graphics:** Intel® Iris® Plus Graphics (ICL GT2)
- **Disk Capacity:** 1.0 TB
## Software Information:
- **Firmware Version:** AUCN57WW
- **OS Name:** Manjaro Linux
- **OS Build:** rolling
- **OS Type:** 64-bit
- **GNOME Version:** 48
- **Windowing System:** Wayland
- **Kernel Version:** Linux 6.6.86-1-MANJARO
In both cases, I am using a fully updated Manjaro Linux Unstable and Wayland.
Not quite sure if it’s really AMD- or KDE-specific.
It’s not. It is a Qt 6.9.0 bug and has been reported and confirmed.
I’m facing the same issue with an AMD RX 6400 in Akregator. The problem does not occur when I switch to iGPU (Intel 630). It also works when using the following environment variables:
QMLSCENE_DEVICE=softwarecontext akregator
MESA_LOADER_DRIVER_OVERRIDE=zink akregator
I can confirm that both of this workarounds yeah… work 
Using ZapZap for testing, where the QTWEBENGINE_CHROMIUM_FLAGS didn’t change anything.
1 Like