Good evening, I’m having some issues with Spectacle after doing a fresh install of Arch Linux and Plasma 6. Whenever I try to launch Spectacle (key combo or from the search menu), I get an error in the bottom right corner that says Could not activate remote peer 'org.kde.spectacle': startup job failed and I’m not sure what could possibly be causing this. I have tried reinstalling Spectacle many times now, and nothing has fixed it. I even tried on X11 instead of Wayland, same result. I get the same message, regardless of what I do. Is this a known issue? And if so, what would the solution be (if there is one)?
Replying to bump this. I’m having a similar issue on bazzite stable running KDE Plasma 6.1.1. When trying to start Spectacle, I got a notification reading
“Launching Spectacle failed
Remote peer disconnected.”
I read somewhere about clearing the .cache, but as a noobie linux user I’m not quite sure how to do that.
This is a 2 months old post though. I have no problems on Arch Linux, I suspect it is a packaging issue in your distro. Maybe they don’t use the latest qt6 or something. What do you get if you start spectacle from terminal?
I appreciate your reply. Terminal output looks like this.
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
kpipewire_vaapi_logging: VAAPI: Mesa Gallium driver 24.1.2 for AMD Radeon RX 6750 XT (radeonsi, navi22, LLVM 18.1.6, DRM 3.57, 6.9.6-201.fsync.fc40.x86_64) in use for device "/dev/dri/renderD128"
LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:8, but the hw limit is 128:2
LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:16, but the hw limit is 128:2
Aborted (core dumped)
Hello,
I have the same problem on Bazzite KDE. My terminal output:
libva info: VA-API version 1.21.0
libva info: Trying to open /usr/lib64/dri-nonfree/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri-freeworld/radeonsi_drv_video.so
libva info: Trying to open /usr/lib64/dri/radeonsi_drv_video.so
libva info: Found init function __vaDriverInit_1_21
libva info: va_openDriver() returns 0
kpipewire_vaapi_logging: VAAPI: Mesa Gallium driver 24.1.2 for AMD Radeon RX 6700 XT (radeonsi, navi22, LLVM 18.1.6, DRM 3.57, 6.9.6-201.fsync.fc40.x86_64) in use for device "/dev/dri/renderD128"
LLVM failed to compile a shader correctly: SGPR:VGPR usage is 32:8, but the hw limit is 128:2
LLVM failed to compile a shader correctly: SGPR:VGPR usage is 48:8, but the hw limit is 128:2
Aborted (core dumped)
I don’ have those LLVM errors. My suspicions are probably correct, I found this for you that you should probably follow:
https://www.reddit.com/r/Fedora/comments/1drz4d6/spectacle_died/
I have found the culprit. If you use the freeworld VAAPI package
mesa-va-drivers-freeworld, this package has not been updated yet
1 Like
It seems that the bug has been fixed already in MESA, but the Bazzite dev messed up keypair rotation so Bazzite wasn’t updating itself properly. Works for me after running the command there.
curl -sL https://fix.universal-blue.org/ | sudo bash
expiriencing the same with plasmashell 6.1.3
Spectacle works when I trigger it from terminal but it doesn’t when launched using (Super+Shift+P) or from application launcher.
This is output from the terminal when spectacle is launched:
libva info: VA-API version 1.22.0
libva info: Trying to open /usr/lib64/dri-nonfree/asahi_drv_video.so
libva info: Trying to open /usr/lib64/dri-freeworld/asahi_drv_video.so
libva info: Trying to open /usr/lib64/dri/asahi_drv_video.so
libva info: va_openDriver() returns -1
kpipewire_vaapi_logging: VAAPI: Failed to initialize display
kpipewire_vaapi_logging: DRM device not found
Please ask if you want me to post org.kde.spectacle.desktop file.
thanks in advance (:
Hi! Are you getting the same message as the person who started this thread, the “Could not activate remote peer ‘org.kde.spectacle’: startup job failed” notification?