| Summary: | No screencast/window thumbnail functionality works | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | matti-brandmaier |
| Component: | screencasting | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | cwo.kde, nate, qydwhotmail, vlad.zahorodnii, xaver.hugl |
| Priority: | NOR | ||
| Version First Reported In: | 6.3.2 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: |
screenshot of missing preview in icon only task manager
screenshot of missing previews in overview missing previews in task switcher journalctl logs for spectacle under x11 and wayland |
||
|
Description
matti-brandmaier
2025-03-01 16:15:07 UTC
Created attachment 179009 [details]
screenshot of missing previews in overview
Created attachment 179010 [details]
missing previews in task switcher
Thank you for the bug report! Window thumbnails use the same infrastructure as screen recording,and the icon fallback typically happens when there is something wrong with that. Can you test whether screen recording (e.g. with Spectacle) works, and report your PipeWire version? Can you check `journalctl --follow` while starting a screen recording and see if there is an error message being printed? Hey, thank you for the fast response! I attached a textfile with the journalctl outputs for screenrecording with spectacle under both x11 and wayland. On X11, I just got an error saying screenrecording is not supported under X11, on wayland however it seemed to be working. I also tried to record with OBS, under X11 the screencapture(pipewire) option did not work, under wayland however it did. My pipewire version: pipewire Compiled with libpipewire 1.2.7 Linked with libpipewire 1.2.7 The only thing I tinkered with regarding pipewire was installing pipewire-jack. When I run "pipewire" in the terminal, I get a bunch of red text - however audio-wise everything seems to run fine on my side.. [E][00977.844507] mod.protocol-native | [module-protocol-: 784 lock_socket()] server 0x5a497716c110: unable to lock lockfile '/run/user/1000/pipewire-0.lock': Resource temporarily unavailable (maybe another daemon is running) [E][00977.844567] pw.conf | [ conf.c: 603 load_module()] 0x5a497714c360: could not load mandatory module "libpipewire-module-protocol-native": Resource temporarily unavailable [E][00977.845036] default | [ pipewire.c: 124 main()] failed to create context: Resource temporarily unavailable Created attachment 179049 [details]
journalctl logs for spectacle under x11 and wayland
... the weird output after running "pipewire" in the terminal just seems mean that pipewire is already running and I, by that command, tried to run another "instance" of pipewire, which ofc doesnt work. Sorry for the confusion! Seems like something is wrong with your GPU's ability to display screencasts, which is re-used for the affected functionality. anything you could advise me to do/try to get more insights? Screencasting works fine for me through applications, whether it is OBS, discord etc.. (In reply to cwo from comment #3) > Window thumbnails use the same infrastructure as screen recording,and the > icon fallback typically happens when there is something wrong with that. Can > you test whether screen recording (e.g. with Spectacle) works, and report > your PipeWire version? Can you check `journalctl --follow` while starting a > screen recording and see if there is an error message being printed? They do, but the overview and task switcher don't. It's really odd that they're all affected at the same time. (In reply to matti-brandmaier from comment #8) > anything you could advise me to do/try to get more insights? Screencasting > works fine for me through applications, whether it is OBS, discord etc.. One thing you can try is to make a new user account and check if it also happens there - to figure out if it's config related, or a more system wide issue. Thank you for the advice! Ive been able to fix the issue by resetting my .config through the files provided by /etc/skel, as after creating a new user for testing, everything worked fine with this one. Still a mystery what caused that after all, as the only thing I ever really did to customize was installing the orchis theme for KDE. Thank you guys for your time! Was it a global theme? Can you find the URL for it? (In reply to Nate Graham from comment #11) > Was it a global theme? Can you find the URL for it? Yes, I used this one: https://aur.archlinux.org/packages/plasma6-themes-orchis-kde-git I also have a copy of the "faulty" .config folder, in case there's the need to check something. Ok yeah, that's a lot of stuff. I suspect it pulled in something that broke system package functionality. That's the danger of using AUR content! |