Application is not started in Wayland

[svatas]

I am on Linux (Tuxedo OS based on Ubuntu 24.04 and Wayland, KDE Plasma 6.2.4).

I am using flatpack for installing Gear Lever. Version 2.2.1 and newer does not start in Wayland. When I switch to X11 session, it is working as a charm.

The last working version is 2.2.0 which I downgraded to. Since 2.2.1 it is not working in Wayland.

There is nothing special in a log.

Was there any special change between versions 2.2.0 and 2.2.1?

[hexahigh]

The only major change between 2.2.0 and 2.2.1 is the Gnome runtime version being increased from 46 to 47.
I have never used Tuxedo OS and have no idea how it works but I recommend updating your system packages and seeing if that fixes it.

[FlamingPhoenix40]

After my old PopOS 22.04 install finally gave up the ghost when updating, I decided to change to Kubuntu 24.10. I normally use TheAssassin/AppImageLauncher, but that hasn't been updated in quite a while. Found this app, and have the same issue as svatas. Will not launch the Flatpak. Maybe the output of the terminal will help. My system is currently up to date.

$ flatpak run it.mijorus.gearlever
Logging to file /home/phoenix/.var/app/it.mijorus.gearlever/cache/logs/gearlever.log
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:782: FINISHME: support YUV colorspace with DRM format modifiers
MESA-INTEL: warning: ../src/intel/vulkan/anv_formats.c:814: FINISHME: support more multi-planar formats with DRM modifiers
Gdk-Message: 20:33:36.022: Error 71 (Protocol error) dispatching to Wayland display.

I'll also add the logfile I see mentioned in that output.
gearlever.log

[hexahigh]

That is very similar to an error I have received in the past.
I got this error when trying to run any GTK app through Flatpak. I was using Fedora 41 (GNOME 47) on Wayland with an Nvidia GPU.

Are you using an Nvidia GPU?

[SugarRayLua]

Hi, @svatas.

I'm on Tuxedo OS same as you (24.04, KDE same version running Wayland). I recently started trying apps to automatically put my App Images in the KDE Application Launch menu and haven't actually been able to get any of them to work. All my regular apps get installed in the menu fine (e.g. standard apt installations as well as flathub). I tried another app which seemed to detect and create desktop files and place them in correct folders, but the actual appimages never showed up in the KDE Launch menu. I saw Gear Lever recommended and tried it, and everything also seemed to go fine (i.e. able to add an App Image, and "install" it per the screen, and it shows up in the correct AppImage directory, and I'm able to launch the app fine from Gear Lever), but it also never shows up in the KDE Application Launch menu nor does the app show up on the Gear Lever screen when I launch Gear Lever.

You mentioned though that with the newest Gear Level your App Images don't launch-- mine seem to. Do your apps show up in your KDE Application Launch menu? I tried downgrading to Gear Lever 2.20 as you mentioned but had the same problem (AppImages open but don't show up in my Launch menu even after restarting the OS).

Any suggestions? I'm not sure why our systems would be difference running the same OS?

Thanks! :-)

[FlamingPhoenix40]

That is very similar to an error I have received in the past. I got this error when trying to run any GTK app through Flatpak. I was using Fedora 41 (GNOME 47) on Wayland with an Nvidia GPU.

Are you using an Nvidia GPU?

Actually, yes I am. I am running a laptop with Nvidia optimus graphics. The way the manufacturer set up the output for external displays, is that it's the NVIDIA handling it, and because I always use an external monitor at home, it's basically always active. Am writing this reply on my Windows install atm, but from the top of my head I believe the NVIDIA driver is set to on-demand mode, and Intel mode is not selectable.

[SugarRayLua]

Dear All,

Since I couldn't figure out why two versions of gearlever weren't working for installing my AppImages in my KDE Wayland setup (and strangely apparently is partially working in @svatas's similar setup), I decided to read up more on the XDG standard for desktop entry files and specifically for KDE's instructions on creating a desktop file. I learned that although both GNOME and KDE adhere to the same XDG desktop standard, KDE uses different applications then GNOME to actually open and add files referenced by .desktop files to the KDE application launcher. I tried a similar app (go-appimage) and was having the same difficulty in having the KDE Application Launcher recognize the .desktop files that app or gearlevel creates and stores in appropriate paths to be recognized (e.g. ~/.loca/share/applications). In my search, I did though find a reference to the simple "dex" app .desktop file creator, and after I figured out how to install and use that, I was able to have the dex app create a desktop file for my App Images which the KDE application launcher did recognize and add to the KDE launcher menu. Using the dex method does take more steps (the gearlever process looks much simpler); however, since I don't have that many AppImages to install in my KDE launcher, I'm comfortable using the following steps in dex to install my App Images in my KDE system:

(sudo apt install dex [from repository])

1. Download AppImage of interest and make executable (e.g. chmod)
2. Place it in a folder where you'd like to store AppImages (e.g. ~/AppImages)
3. cd to directory where you'd like desktop file to be installed that will be automatically detected and added to KDE Application Launcher menu (e.g. ~/.local/share/applications)
4. dex -c /pathToWhereAppImageIsStored (e.g. ~/AppImages/AppImageOfInterest.AppImage)
5. cd back to folder where AppImage itself is stored and type:
   ./AppImageOfInterest.AppImage --appimage-extract
   That will unsquash the squashfs filesystem into a directory which inside will contain a .DirIcon which is the png for the app
   Rename the .DirIcon as a .png file for step 7) below
   *Correction: it appears that the squashfs directory also might contain an "icons" file that also has .png icons can choose for the AppImage icon in the KDE Application Launcher
6. Go to the KDE Application Launcher and you should see AppImageOfInterest installed on the menu.
   Right-click on the menu item and select "Edit Application"
7. On the AppImageOfInterest Application window, click on the blank picture (square); that will open a file menu picker, and you can navigate to the .DirIcon (renamed as a .png) and choose that .png to be the icon associated with the installed AppImage on the KDE Application menu

Lots more steps but the above method consistently works for me in my setup for now. Perhaps in the future, I'll get more time to more closely dissect what the differences are between the .desktop files that gearlever creates and those that dex creates to perhaps determine why the gearlevel .desktop files aren't loading in my KDE Application Launcher

Fyi, and have a good week.