pixi hangs indefinitely when a FastX session exists unless `export DBUS_SESSION_BUS_ADDRESS=/dev/null`

[70Gage70]

Checks

• [x] I have checked that this issue has not already been reported.

• [x] I have confirmed this bug exists on the latest version of pixi, using pixi --version.

Reproducible example

Commands I ran and their output:

# AFTER FRESH INSTALL
❯ pixi search ripgrep
Using channels: conda-forge
⠴ loading all package names
# hangs indefinitely

Then,

export DBUS_SESSION_BUS_ADDRESS=/dev/null
# pixi search ripgrep works now

pixi.toml/pyproject.toml file that reproduces my issue:

# I guess anything?

pixi info output:

System
------------
       Pixi version: 0.59.0
           Platform: linux-64
   Virtual packages: __unix=0=0
                   : __linux=4.18.0=0
                   : __glibc=2.28=0
                   : __cuda=12.3=0
                   : __archspec=1=icelake
          Cache dir: /home/MORGRIDGE/gbonner/.cache/rattler/cache
       Auth storage: /home/MORGRIDGE/gbonner/.rattler/credentials.json
   Config locations: No config files found

Global
------------
            Bin dir: /home/MORGRIDGE/gbonner/.pixi/bin
    Environment dir: /home/MORGRIDGE/gbonner/.pixi/envs
       Manifest dir: /home/MORGRIDGE/gbonner/.pixi/manifests/pixi-global.toml

Other files (e.g. script files, source files, etc.):

Issue description

I'm extremely unqualified to diagnose this, but pixi works out of the box with no additional configuration on one of our servers and not on the other one. The only difference is that I use FastX on the one where export DBUS_SESSION_BUS_ADDRESS=/dev/null is required. When a FastX session doesn't exist, pixi appears to just work.

Expected behavior

Either just work, or hint that this could be the problem somewhere

[Hofer-Julian]

The only place where I can think that we use d-bus is for our keyring. I could try to use d-spy to figure out if something is going wrong there https://apps.gnome.org/Dspy/

[baszalmstra]

Did you get a chance to try @Hofer-Julian ? Otherwise maybe @70Gage70 could try?

[Hofer-Julian]

Sorry, I meant to type:

You, @70Gage70, could try to use d-spy to figure out if something is going wrong there https://apps.gnome.org/Dspy/