Bug 512676

Summary:	unable to use flatpak ONLY in wayland session
Product:	[I don't know] kde	Reporter:	otaolafr <otaola.franc>
Component:	general	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DOWNSTREAM
Severity:	grave	CC:	sitter
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description otaolafr 2025-11-27 12:41:48 UTC

SUMMARY
Hello,
since one of the last updates of my system (migration to kde 6.5) on my tuxedos system. it broke prusa slicer flatpak application, when I launch it it simply does not start (no window appear) I notice that this is happening only in wayland session.

STEPS TO REPRODUCE
1. launch prusa slicer 2.4.0 flatpak version in wayland

OBSERVED RESULT
the application simply does not open at all. when I run:
`flatpak run -v com.prusa3d.PrusaSlicer`
I am getting:
```
F: No installations directory in /etc/flatpak/installations.d. Skipping
F: Opening system flatpak installation at path /var/lib/flatpak
F: Opening user flatpak installation at path /home/franco/.local/share/flatpak
F: Opening user flatpak installation at path /home/franco/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: Skipping parental controls check for app/com.prusa3d.PrusaSlicer/x86_64/stable since parental controls are disabled globally
F: Opening user flatpak installation at path /home/franco/.local/share/flatpak
F: Opening system flatpak installation at path /var/lib/flatpak
F: /var/lib/flatpak/runtime/org.gnome.Platform/x86_64/48/8380a2e259833616fbeec86e0f46821df7b52e7820c1f3773aebde8c9db1b9b5/files/lib32 does not exist
F: Cleaning up unused container id 2126117808
F: Cleaning up per-app-ID state for com.prusa3d.PrusaSlicer
F: Allocated instance id 2304779705
F: Add defaults in dir /com/prusa3d/PrusaSlicer/
F: Add locks in dir /com/prusa3d/PrusaSlicer/
F: Allowing homedir access
F: Not sharing "/run/media" with sandbox: Unable to open path "/run/media": No such file or directory
F: Allowing x11 access
F: Running 'bwrap --args 40 -- xdg-dbus-proxy --args=42'
F: Running 'bwrap --args 40 -- entrypoint'
--------------------------------------------------------------------------
Message: 08:31:42: Starting PrusaSlicer flatpak with entrypoint script
--------------------------------------------------------------------------
Gtk-Message: 08:31:43.067: Failed to load module "colorreload-gtk-module"
Gtk-Message: 08:31:43.067: Failed to load module "window-decorations-gtk-module"
```
if I change my session to X11, the application works correctly

EXPECTED RESULT
that the application windows opens

SOFTWARE/OS VERSIONS
Operating System: TUXEDO OS 
KDE Plasma Version: 6.5.2
KDE Frameworks Version: 6.19.0
Qt Version: 6.9.2
Kernel Version: 6.14.0-116036-tuxedo (64-bit)
Graphics Platform: X11
Processors: 16 × 12th Gen Intel® Core™ i5-12500H
Memory: 64 GiB of RAM (62,5 GiB usable)
Graphics Processor 1: NVIDIA T600 Laptop GPU
Graphics Processor 2: Intel® Iris® Xe Graphics
Manufacturer: Dell Inc.
Product Name: Precision 3571

ADDITIONAL INFORMATION
i run before this issue, flatpak update (getting nothing to update) restarted the pc also, the issue is still there.

Comment 1 Harald Sitter 2025-11-28 10:26:41 UTC

You'll want to report this to the flatpak repository (I presume flathub?). Also, do make sure you haven't allowed the app to run with a wayland socket in the past. It very clearly is not wayland compatible.

Comment 2 otaolafr 2025-11-28 12:17:34 UTC

(In reply to Harald Sitter from comment #1)
> You'll want to report this to the flatpak repository (I presume flathub?).
> Also, do make sure you haven't allowed the app to run with a wayland socket
> in the past. It very clearly is not wayland compatible.

hello,
okey I will! thanks for the recommendation!
i havent allowed ? what do you mean? i did not change anything from my side, it was working, i update/upgrade my system (it was a big one, i think for going to 6.5) and after that it stopped working on the wayland session where it worked before, also did not change any settings or parameters from my side.