Spectacle segfaults after recent update

[bitmage]

Currently Spectacle is segfaulting on launch. I’m running 24.0.1, all up to date. Running Wayland. I get this message popping up in a notification window when I press prnt scr:

Message recipient disconnected from the message bus without replying.

I see some similar issues where Plasma applications are segfaulting:

Plasma applications are crashing (segmentation fault core dumped)

x11 is not working properly after the 2 most recent updates. Any qt/plasma application crashes. Resetting plasma config to default didn’t help. I receive the following error message: segmentation fault (core dumped) And the meta key no longer opens the Application dashboard. Instead, it opens the application menu.

All/Most Qt applications SEGFAULT after pamac update

I’ve updated my system today using pamac update. I do this frequently, so there are no big leaps between updates. Besides this, I’ve also tried several torrent clients. qbittorrent has never worked on my system, but that didn’t bother me because I used other clients. Today I tried installing deluge, which surprisingly didn’t work. As a last client, I tried transmission, by transmission-cli and transmission-qt. After this everything broke. $ dolphin zsh: segmentation fault (core dumped) dolph…

As other users suggest I’ve tried removing files in .local, .cache and .config having anything to do with “kde”, “plasma”, or “spectacle”. Uninstalled and reinstalled Spectacle. Rebooted my computer. Still get segfault on launch.

dmesg shows:

[  658.607537] Thread (pooled)[5115]: segfault at d8 ip 00007f0a5983cab4 sp 00007f0a355f7d78 error 4 in libX11.so.6.4.0[7f0a5982d000+8b000]
[  658.607543] Code: 84 00 00 00 00 00 f3 0f 1e fa 8b 47 1c c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa 8b 47 74 c3 0f 1f 84 00 00 00 00 00 f3 0f 1e fa <48> 8b 87 d8 00 00 00 c3 0f 1f 40 00 f3 0f 1e fa 48 63 f6 48 c1 e6

I don’t see anything particularly helpful from running the app with gdb.

Any ideas how I can get screenshots working again? Unlike these other threads I linked to, other Plasma/QT apps are working fine for me, it appears to be just Spectacle that’s broken.

Update: Spectacle does work when I reboot into X11 instead of Wayland. That’s not ideal, but good to know I have a workaround.

[linux-aarhus]

Quite strange - as spectacle work on my systems - I am guessing the only difference is our branches.

Spectacle version 24.05.0-1 is the defacto state of spectacle also upstream.

With relation to a plasma reset - it seems you have tried everything.

The only idea left is that - if your housecleaning was done inside a plasma session - as opposed to logging off and switch to a TTY - plasma may have cached configs which is then written to disk - with the settings causing the crash.

This is pure speculation.

I would log out - switch to a TTY - login as my user - remove the ~/.cache and the spectacle related files.

• file ~/.config/spectaclerc
• folder ~/.local/share/spectacle

Then refresh user-space

systemctl soft-reboot

Login and retry the screenshot

testing and unstable branches is update more frequently than stable.

Looking at announce

• stable snap at May 29.
• testing snap at June 3.

unstable had several syncs since - latest today - but nothing that seems to be related to spectacle - plasma-workspace is the only candidate.

[bitmage]

This is still busted. I have to log into Wayland to use screen recording with Kooha, and log into X11 to use Spectacle.

I tried the stuff you mentioned with cache clearing to no avail.

[ydar]

I also still cannot get it to work while in a Wayland session. I’m using Plasma 6.1.4, Spectacle 24.05.2-1

Spectacle not working in Wayland isn’t a big deal for me since I primarily use X11 right now; but I was curious if other screenshot apps work, and I found Flameshot works.

[BG405]

@ydar

and I found Flameshot works

Something I was going to recommend, at least as a temporary workaround until what I assume is a bug in the currently-used kernel is fixed (I had issues with one of the 6.6 series, albeit unrelated). Certainly worth testing with another kernel e.g. linux61 LTS.

[linux-aarhus]

@BG405

Certainly worth testing with another kernel e.g. linux61 LTS.

The kernel has nothing to do with this - at least I cannot see the connection - perhaps that is just me

@ydar

I also still cannot get it to work while in a Wayland session. I’m using Plasma 6.1.4, Spectacle 24.05.2-1

That is really strange - I do as well

Created just now using spectacle

06:28:27 ○ [fh@tiger] ~
 $ spectacle --version
spectacle 24.05.2

Just a wild thought - is it gpu related ?

• nvidia gpu
• amd gpu

[MrLavender]

No problem here with Spectacle on Wayland, I use it all the time. Stable branch + AMD gpu.

If you are on Nvidia then - Spectacle segfaulting on wayland plasma 6 - Help - KDE Discuss

Following the link there to the bug report;

This is caused by the libva-vdpau-driver package on Arch. Removing that should fix it

[ydar]

I have an Nvidia GPU

[qruqs]

X11 options you might optionally try:

1. recordmydesktop
2. vlc

I had to install option 1. because I am (currently at least) on x11. I tried wayland and though it worked, I concluded there were heaps of settings I needed to do to make it look they way I like it. I though: “some other day.” Lazy old dog, you know.
“recordmydesktop” needs some settings, so read all about it in man. Good tool, works fine.

Option 2. might also be used:
https://www.vlchelp.com/how-to-record-desktop/
I’ve tried it for fun and though it works for me, I couldn’t get the mouse pointer trick working (supply the full path to the image if you want to try).
No audio either, but that could be me not knowing how to set it up properly. Like I said, just tried it for fun.