$ whatsie
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb.
Aborted (core dumped)
Ubuntu version and kernel:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble
$ uname -a
Linux holdsworth 6.8.0-134-generic #134-Ubuntu SMP PREEMPT_DYNAMIC Fri Jun 26 18:43:11 UTC 2026 x86_64 x86_64 x86_64 GNU/Linux
pablo@holdsworth:~$ whatsie
qt.qpa.plugin: From 6.5.0, xcb-cursor0 or libxcb-cursor0 is needed to load the Qt xcb platform plugin.
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vkkhrdisplay, vnc, wayland-brcm, wayland-egl, wayland, xcb.
Aborted (core dumped)
Snap info:
$ snap info whatsie
name: whatsie
summary: Feature rich WhatsApp Client for Linux Desktop
publisher: keshavbhatt (keshavnrj✪)
store-url: https://snapcraft.io/whatsie
contact: keshavnrj@gmail.com
license: MIT
description: |
Whatsie is a Lightweight, feature-rich WhatsApp web client written in Qt QWebEngine Library.
...
commands:
- whatsie
snap-id: WwwfGkUJunYzwImtdN2JlOU6UjnvkSD9
tracking: latest/stable
refresh-date: 2026-04-03
channels:
latest/stable: 5.1.0 2026-04-03 (185) 1.02MB -
latest/candidate: ↑
latest/beta: ↑
latest/edge: 5.1.0 2026-04-03 (185) 1.02MB -
installed: 5.1.0 (185) 1.02MB -
pablo@holdsworth:~$
pablo@holdsworth:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.4 LTS
Release: 24.04
Codename: noble
I had this with the MusicBrainz picard snap, since some time failing like this on X11. I don’t know when this changed, but in my case the snap was missing the libxcb-shape0 package.
If you are a user trying to get this snap running, I don’t know if there is a way to solve this from outside, except for the workaround of running under wayland instead of x11. In this case best report this to the maintainer of the flatpak snap.
the content snap which is use by whatsie currently 6.11, in the past 6.10.
Probably they dropped
libx11-xcb-dev and libx11-xcb1, which they added back now.
The strange part about this snapcraft extension thing now is they can introduce breaking changes and can break working snaps with changes like these.
The thing is developers asked to use extensions in their snapcraft.yaml like this:
extensions:
kde-neon-6
Now this uses content snap kf6-core24 which in our case was using Qt 6.10 earlier but now they bumped to Qt 6.11 where they dropped few libraries.
This make all snaps using this extension fail.
Good find, this really looks like the change that triggered this failing. Good to see they add it back.
And those Qt updates are really dangerous, yes. This easily breaks applications. In my case (MusicBrainz Picard) was not that much affected by the version change, as it uses PyQt and it was still able to run with the changed Qt 6.11 binaries. But it failed to load the bundled QtMultimedia plugins, which were compiled against the previous Qt 6.10. So still needs a snap rebuild to recover functionality.
I mean flatpak provide versioning of SDK and runtime eg org.kde.Platform//6.10 . While in case of snapcraft extension it seems there is no way to pin version. This leads to unknowingly using different SDK and runtime version. This is major issue with re-producibility. It feels like snapcraft’s KDE extension follows a rolling SDK (6.10→6.11 is a surprise update that was delivered to all snaps using this extension).
@papibe Can you try to update the runtime snap manually if the issue has not already fixed for you.
It’s best to recompile with same QT version than kf6-core24.
Snapcraft doesn’t allow to install multiple snaps(-libraries) versions like QT6.
Snapcraft doesn’t allow to specify which snap channel to use for a plug provider.
I don’t think it’s possible to superseed the kf6-core24-sdk used by kde-neon-6 extension, and how would it be managed.
I’m not sure if it’s possible to check runtime version installed (kf6-core24 version) from a snap (?) to prevent error.
With extension, it should build and aim for the same Qt libraries.
The issue is:
Today you built your snap with sdk 6.10 → this works with runtime 6.10 fine
Next morning someone update the runtime to 6.11 → people get new runtime updates, but the app binary was built against 6.10. This causes issues.
Qt itself is backward compatible across version 6 but other runtime dependencies if removed from runtime content snap, the app will not work. Which is the case here.
Oh, yes. My bad, too many things in parallel