Comment 65 for bug 1951491

This happened to me on a fresh install of Xubuntu 22.04 when using X2Go. Local sessions don't have this problem. I can work around it by setting the environment variable (as specified in message 31) DBUS_SESSION_BUS_ADDRESS before running firefox.

I'd like to get this fixed as we use X2go extensively at my office, and we'll be stuck on Ubuntu 20.04 until this is fixed. It sounds like a new x2go (bug) integration issue starting with 22.04.

Tim Richardson is probably right that X2go is not doing something the way systemd expects, and that therefore x2go is 'old'. Is there a 'new' remote access tool that is known to work?

I rather like x2go and would love to port the 'new' solution to x2go if I knew what exactly needed to be done.

I looked here for information about what the right way to do this, but it's not clear from that page where to go for the steps I need: https://www.freedesktop.org/software/systemd/man/systemd-logind.service.html

I also looked in the the source for x2go:
https://code.x2go.org/releases/source/
But I have yet to find the code responsible for this bug or any clue about what it should be changed to.

I also find related bug reports dating back many years, but it's just clues, not a clear explanation of what's being done 'the old way' and what the new way should look like:
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1046

I'm looking for a bug report for this bug on the x2go side, but I can't find one. Does anyone know if one is open, or should I open a fresh one?

The closest related bug report I could find was this:
https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=814

Once I have a proper bug report found/opened, if anyone with a slightly deeper knowledge of how to fix this could give me some clues of where to look or what to fix, that would be great.