WSL: Failed to connect to bus: No such file or directory

Windows Version

Microsoft Windows [Version 10.0.22635.3640]

WSL Version

2.2.4.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

Debian Sid

Other Software

No response

Repro Steps

  1. Fully shutdown WSL
  2. start wsl (slowly to startup ~10s)
  3. check on dmesg

Expected Behavior

Not shown the error and startup faster

Actual Behavior

[    3.101163] Failed to connect to bus: No such file or directory
[    3.358417] Failed to connect to bus: No such file or directory
[    3.620951] Failed to connect to bus: No such file or directory
[    3.885758] Failed to connect to bus: No such file or directory
[    4.146125] Failed to connect to bus: No such file or directory
[    4.405763] Failed to connect to bus: No such file or directory
[    4.661344] Failed to connect to bus: No such file or directory
[    4.865303] misc dxg: dxgk: dxgkio_is_feature_enabled: Ioctl failed: -22
[    4.870424] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.870990] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.871448] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.872131] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[    4.874075] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.874821] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.875557] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -22
[    4.876400] misc dxg: dxgk: dxgkio_query_adapter_info: Ioctl failed: -2
[    4.916190] Failed to connect to bus: No such file or directory
[    5.171256] Failed to connect to bus: No such file or directory
[    5.427397] Failed to connect to bus: No such file or directory
[    5.683769] Failed to connect to bus: No such file or directory
[    5.940100] Failed to connect to bus: No such file or directory
[    6.196674] Failed to connect to bus: No such file or directory
[    6.453576] Failed to connect to bus: No such file or directory
[    6.710390] Failed to connect to bus: No such file or directory
[    6.970699] Failed to connect to bus: No such file or directory
[    7.228377] Failed to connect to bus: No such file or directory
[    7.486034] Failed to connect to bus: No such file or directory
[    7.748179] Failed to connect to bus: No such file or directory
[    8.005552] Failed to connect to bus: No such file or directory
[    8.265451] Failed to connect to bus: No such file or directory
[    8.522279] Failed to connect to bus: No such file or directory
[    8.784220] Failed to connect to bus: No such file or directory
[    9.047631] Failed to connect to bus: No such file or directory
[    9.308141] Failed to connect to bus: No such file or directory
[    9.568661] Failed to connect to bus: No such file or directory
[    9.831443] Failed to connect to bus: No such file or directory
[   10.095917] Failed to connect to bus: No such file or directory
[   10.355075] Failed to connect to bus: No such file or directory
[   10.612391] Failed to connect to bus: No such file or directory
[   10.871735] Failed to connect to bus: No such file or directory
[   11.134293] Failed to connect to bus: No such file or directory
[   11.392979] Failed to connect to bus: No such file or directory
[   11.655457] Failed to connect to bus: No such file or directory
[   11.917953] Failed to connect to bus: No such file or directory
[   12.179918] Failed to connect to bus: No such file or directory
[   12.442001] Failed to connect to bus: No such file or directory
[   12.702894] Failed to connect to bus: No such file or directory
[   12.962935] Failed to connect to bus: No such file or directory
[   12.965135] WSL (2) ERROR: WaitForBootProcess:3342: /sbin/init failed to start within 10000
[   12.965137] ms
[   12.975594] WSL (2): Creating login session for zed

Diagnostic Logs

No response

About this issue

Most upvoted comments

For me the problem was solved by doing this:

[10569:0827/004757.735915:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

can be fixed by adding these lines to ~/.bashrc

if [ -z "$DBUS_SESSION_BUS_ADDRESS" ]; then
    dbus-daemon --session --address=unix:path=/run/user/1000/bus --fork
    export DBUS_SESSION_BUS_ADDRESS="unix:path=/run/user/1000/bus"
fi

The issue is that when running program, it expects the socket to be located at a fixed path in /run/user/1000/bus, which doesn’t work in WSL2 where the socket is instead created as an abstract socket and is found under /tmp

dbus-launch --sh-syntax --exit-with-session
DBUS_SESSION_BUS_ADDRESS='unix:abstract=**/tmp/dbuslADZpPMOKJ,guid=55593467f737024f5f2ed7c566cd08fd**';
export DBUS_SESSION_BUS_ADDRESS;
DBUS_SESSION_BUS_PID=11021;
DBUS_SESSION_BUS_WINDOWID=6291457;

I use arch,same error encountered,how did you solve it