You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
With the "Isolate Workspaces" feature enabled, some flatpak apps need >90 seconds to start. It does not matter if the application is started from the panel, or from the applications menu. If the flatpak app is started via the terminal, it starts immediately.
Linux distribution and version
Debian Testing / Trixie
GNOME Shell version
GNOME Shell 46.4
Dash-to-Panel version
63
Where was Dash-to-Panel installed from?
The GNOME extensions website
In the video:
Starting chromium at the 4 seconds mark, becomes visible at 01:43
Then disabling the feature and starting Chromium again at 01:55 and is visibly shortly after
Additional Info
Not all flatpak apps are affected. Reproducible on my machine with Chromium and Inkscape. Thunderbird starts normally, but the "Write New message" action from the context menu is also having the same issue.
The text was updated successfully, but these errors were encountered:
Describe the bug
With the "Isolate Workspaces" feature enabled, some flatpak apps need >90 seconds to start. It does not matter if the application is started from the panel, or from the applications menu. If the flatpak app is started via the terminal, it starts immediately.
Linux distribution and version
Debian Testing / Trixie
GNOME Shell version
GNOME Shell 46.4
Dash-to-Panel version
63
Where was Dash-to-Panel installed from?
The GNOME extensions website
Screenshots / Video captures
https://github.com/user-attachments/assets/923e6a94-adcd-405e-af48-22dc685394da
In the video:
Starting chromium at the 4 seconds mark, becomes visible at 01:43
Then disabling the feature and starting Chromium again at 01:55 and is visibly shortly after
Additional Info
Not all flatpak apps are affected. Reproducible on my machine with Chromium and Inkscape. Thunderbird starts normally, but the "Write New message" action from the context menu is also having the same issue.
The text was updated successfully, but these errors were encountered: