Skip to content

Unable to launch certain flatpaks - workaround by modifing X11 permissions #515

Closed

Description

@goebbe

I am using Linux Mint 22.3 Cinnamon Edition on X11 using
Software Manger 8.4.0.

To get recent versions of certain apps/ software, I often install flatpaks (flathub) via the Software Manager.
Recently I discovered that some of my flapak-Apps, which I used successfully in the past, suddenly stopped launching.

I had this issue with the following apps:
Okular
Kate
Xournal++

When I tried to launch these apps from the terminal via flatpak run, depending on the app, different errors messages were displayed.
For me, as a user, it was not clear what caused the problems and what was the (common) cause of these different error-messages.

After some research and bug reports (e.g. for Kate) I discovered that the issue could be solved by modifying the
permissions of the described flatpaks-apps.

My Workaround:
On the command line (or using Flatseal) it is straightforward to change permissions, e.g. for Kate, the following
command resolved my issue. :
flatpak override --user --share=ipc --socket=x11 org.kde.kate

Edit: After further investigation I discovered, that once the issue was solved, and the apps started again, I could revert the permissions to their default.
So whatever caused the issue, even though I could solve the problem by modifying the permissions, the apps continued launching successfully, after reverting to the default permissions.

To conclude, it is unclear if the Software Manger could solve this problem.
Perhaps the issue is caused by my specific setup - or it is an issue of flatpak itself?

Activity

  1. changed the title [-]Cannot launch certain flatpaks after install, due to new default permissions (missing access to X11)[/-] [+]Unable to launch certain flatpaks after install, due to new default permissions (missing access to X11)[/+] on Sep 27, 2026
  2. changed the title [-]Unable to launch certain flatpaks after install, due to new default permissions (missing access to X11)[/-] [+]Unable to launch certain flatpaks - workaround by modifing X11 permissions[/+] on Oct 3, 2026
  3. goebbe commented on Nov 17, 2026

    @goebbe
    Author

    Since I ran again into a similar issue, with a newly installed app, I tried to investigate the source of the problem.

    I tried to run the app IngeTrazo, using flatpak run com.ingetrazo.IngeTrazo.
    However, I got the following error message:

    flatpak run fails: Gtk-Message: Failed to load module "xapp-gtk3-module"

    Here is the link to my upstream bug report for IngeTrazo: ingelibre/ingetrazo#499

    This time I tried to trace the root cause of the problem, with the help of Gemini.
    It appears that my specific bug was likely to be caused by a corrupt font cache.

    Here is what Gemini wrote:
    The specific memory offset in your stack trace (libc.so.6 + 0x423f0) points precisely to a known fontconfig bug currently affecting Linux systems.
    A recent update (frequently linked to a Google Chrome update) is generating corrupted font cache files on the host OS.
    When a Flatpak Qt6 application tries to parse these corrupted files to draw its interface, the font engine inside the sandbox panics and crashes instantly.

    To fix this, wipe the corrupted font caches from both your system and the Flatpak sandbox, and force them to regenerate cleanly. Run these commands one by one in your terminal:

    # 1. Delete your host user's font cache
    rm -rf ~/.cache/fontconfig
    # 2. Delete IngeTrazo's isolated font cache
    rm -rf ~/.var/app/com.ingetrazo.IngeTrazo/cache/fontconfig
    # 3. Force rebuild the host font cache cleanly
    fc-cache -f -v
    # 4. Force rebuild the Flatpak's font cache
    flatpak run --command=fc-cache com.ingetrazo.IngeTrazo -f -v

    I wiped and rebuild the cache of fontconfig as suggested, and this indeed solved the problem for me! And I could succefully start Inge Trazo by typing flatpak run com.ingetrazo.IngeTrazo

    So now I wonder if my problems, not being able to launch various flatpak apps, have been due to the same underlying issue, i.e. a corrupted fontconfig cache.

    If the analysis of Gemini is correct, there is probably nothing Linux Mint or mintinstall can do about.
    Therefore I will close the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions