> As this also may imply that logging in in a tty or ssh, makes the > portals to start and this is definitely something we do not want (also > because it may create problems in case the session starts before than a > graphical one), no?
The unit still retains After=graphical-session.target, so this does not happen. I always boot into the TTY and can confirm the portal is not started after logging in there. > In general I think that If a desktop is not reaching the graphical > target, then it's not compatible with portals and it must be fixed, > rather than making the portals potentially run in environments they > should not. > > no? Hmm, even in my DWM I need the portal running in order to avoid those annoying time-outs from applications using the Gnome infrastructure, and see no side-effects from running it. Giving that those individual applications assume/request the portal at run-time, 'let them have it' I would say. Do you detect any problem that running the portal in such environments could encompass? > PS: Nathan, push the latest tag on your salsa fork as I was missing it > in the upstream branch (under debian) Pushed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2144855 Title: org.freedesktop.portal.Desktop times out To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2144855/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
