Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Some flatpak applications need more than 90 seconds to start and hog a cpu core when "isolate workspaces" is enabled #2192

Open
crazy-weasel opened this issue Oct 10, 2024 · 4 comments
Labels

Comments

@crazy-weasel
Copy link

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.

@archekb
Copy link

archekb commented Oct 13, 2024

Ubuntu 24.10 the same problem.
Ubuntu 24.04 have no problem.

@charlesg99
Copy link
Member

I don't think this is related to dash to panel. Starting apps is done by gnome shell, and the delay before the chromium window appears isn't affected by dash to panel in any way. I don't use snaps or flatpaks, but I would guess this delay is caused by the fact that the application hasn't been started yet. In your test, try a third time after re enabling workspace isolation.

@archekb
Copy link

archekb commented Jan 19, 2025

Hi, @charlesg99

Unfortunately, this is bug of Dash to Panel, because, the same function Isolate Workspaces at Ubuntu Dock works fine. Yesterday I tried debug it, by this script:

#!/bin/sh -e

#export G_MESSAGES_DEBUG=all
export MUTTER_DEBUG_DUMMY_MODE_SPECS=1366x768
export SHELL_DEBUG=all

dbus-run-session -- gnome-shell --nested --wayland

and only one difference between on and off Isolate Workspaces is

F: Can't get document portal: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message recipient disconnected from message bus without replying

I didn't found any solution and yesterday reinstall Ubuntu back to 24.04 and now Dash to Panel with Isolate Workspaces works ok for me.

@archekb
Copy link

archekb commented Jan 29, 2025

@charlesg99 One more, maybe you're right, if you unpin the App from the panel and run it from gnome app screen, result will the same, about 90 seconds, but if we turn off Isolate Workspaces at Dash To Panel it will start immediately. With Ubuntu dock apps runs immediately, not matter is Isolate Workspaces turned on or off.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants