❦ 23 September 2021 15:37 +01, Simon McVittie: > I see from your initial bug report that you are using systemd as pid 1, > systemd --user, and dbus-user-session (i.e. dbus-daemon --session is > running as a systemd --user unit). Is that correct?
Yes. > What desktop environment are you using? Or if you have made your own > desktop environment from individual components, what are the major > components like window manager and session manager (if any)? lightdm with autologin to Xsession which chains to systemd --user which spawns i3 and various other stuff. > It might be helpful to run the affected GTK app with G_MESSAGES_DEBUG=all > in the environment. This doesn't work for gnome-terminal because > gnome-terminal is weird, but gnome-terminal -vv is close enough. I am using my own terminal and since it is a "GTK application" (it has a daemon mode), I think it may be like gnome-terminal, but the very first terminal is "normal". > Most components that talk to xdg-desktop-portal only do so when they find > that they're running as a Flatpak app, or maybe some other sandboxed app > framework like Snap. Just to rule some things out: are you launching > Flatpak and/or Snap apps? Or if not, do you have environment variable > GTK_USE_PORTAL set? No Flatpak on boot. I am using some later. Let me reboot at the end of the day with just xdg-desktop-portal in verbose mode, it may be enough to find the cause. If not, I will apply your other tricks. -- If you tell the truth you don't have to remember anything. -- Mark Twain