https://bugs.kde.org/show_bug.cgi?id=485845
Bug ID: 485845
Summary: kwin hangs and glitches when using desktop portal
Classification: Plasma
Product: xdg-desktop-portal-kde
Version: 6.0.4
Platform: Mageia RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: plasma-b...@kde.org
Reporter: alvisebruni...@gmail.com
CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org
Target Milestone: ---
Created attachment 168712
--> https://bugs.kde.org/attachment.cgi?id=168712&action=edit
log from journalctl, some repeated messages are omitted
SUMMARY
When opening a file from telegram-desktop from flatpak, the desktop portal
should open a prompt asking which application to open it with. Instead, the
entire desktop freezes, the gpu usage ramps up, and the screen gets filled with
graphic artifacts. I was not able to replicate this on other applications but I
doubt that telegram has the power to cause this behaviour.
I'm not sure if this is the desktop portal's or kwin's fault.
STEPS TO REPRODUCE
1. Send a file with telegram
2. Click "open with"
3. The desktop is frozen and in a few seconds it will start glitching
OBSERVED RESULT
The desktop is frozen and filled with artifacts
EXPECTED RESULT
I get a desktop portal prompt
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 39
(available in About System)
KDE Plasma Version: 6.0.4 (from copr)
KDE Frameworks Version: 6.1.0
Qt Version: 6.6.2
ADDITIONAL INFORMATION
I installed plasma 6 from this copr:
https://copr.fedorainfracloud.org/coprs/solopasha/kde6/ if this is not
reproducible I will post there.
Sometimes I'm able to switch to a tty, if I do, I'm able to run glmark2_drm so
I doubt it's the gpu that's broken. If I do a soft-reboot with systemd, the
system recovers. I don't know how to properly restart just the desktop on
wayland, but I would try that. If I just kill plasmadesktop and kwin_wayland
and let them get restarted on their own it doesn't recover properly.
With nvtop on tty I can see the gpu usage is at 100%, on one occasion it also
filled the vram, but the entire system started misbehaving (couldn't connect
with ssh, the prompt on the tty froze).
I found some seemingly related logs on journalctl, they are attached.
This is what I found, but if needed I will provide more info.
--
You are receiving this mail because:
You are watching all bug changes.
