wsl 2 - Getting “Failed to connect to the bus: Could not parse server address” error when launching google chrome or any electron app #7915

mwoodpatrick · 2022-01-10T22:10:42Z

Version

Windows version: 10.0.22000.376

WSL Version

WSL 2
WSL 1

Kernel Version

5.10.74.3

Distro Version

20.04.3 LTS (Focal Fossa)

Other Software

electron 16.0.6 or Google chrome Version 97.0.4692.71 (Official Build) (64-bit)

Repro Steps

Install and start google chrome on wsl2 and start

Expected Behavior

browser should come up without error

Actual Behavior

google-chrome
[8405:8442:0110/140553.266744:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8405:8441:0110/140553.276538:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:8441:0110/140553.277982:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:8441:0110/140553.329491:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:8441:0110/140553.329632:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:8476:0110/140553.499766:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8405:8476:0110/140553.499863:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8405:8476:0110/140553.500048:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8405:8476:0110/140553.500124:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8405:8476:0110/140553.500170:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[8448:8448:0110/140555.058357:ERROR:sandbox_linux.cc(378)] InitializeSandbox() called with multiple threads in process gpu-process.
[8405:8441:0110/140636.457250:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:8441:0110/140636.457371:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[8405:9002:0110/140641.065898:ERROR:chrome_browser_main_extra_parts_metrics.cc(227)] START: ReportBluetoothAvailability(

Diagnostic Logs

No response

mwoodpatrick · 2022-01-10T22:12:54Z

Note chrome and electron apps do start but they give the above errors

benhillis · 2022-01-11T22:07:22Z

@mwoodpatrick - are you using WSLg or a third party xserver on Windows?

mwoodpatrick · 2022-01-11T22:53:59Z

wslg, xdpyinfo shows

name of display: :0
version number: 11.0
vendor string: Microsoft Corporation
vendor release number: 12010000
maximum request size: 16777212 bytes
motion buffer size: 256
bitmap unit, bit order, padding: 32, LSBFirst, 32
image byte order: LSBFirst

mwoodpatrick · 2022-01-11T23:08:30Z

starting dbus using

sudo service dbus start

did not help

ssbarnea · 2022-01-31T17:04:57Z

That error is making our GHA workflows hard to debug as there are tons of it. If anyone know a workaround for it it would be great.

mbwhite · 2022-03-04T09:27:37Z

Likewise I'm seeing a lot of these errors, when running test on our Electron based app.

The cyrpress test tool makes reference to it in http://www.apimirror.com/cypress/guides/guides/debugging,
And there is some hope offered here https://x410.dev/cookbook/wsl/setting-up-wsl-for-linux-gui-apps/

I would hope that the new WSLg will help here; or use multipass rather WSL.

rajann44 · 2022-04-11T21:16:05Z

I am getting these error with Cypress + Github Actions. Any solution for this?

OmarLomsadze · 2022-05-20T12:43:57Z

any updates?

RestOp · 2022-06-11T22:20:36Z

also interesting

PLopezD · 2022-06-21T19:08:36Z

Would also appreciate some help with this - im running into the same issue

StephaneRavet · 2022-06-22T11:05:55Z

Same error with a fresh WSL install.

npx cypress open
[842:0622/130355.318602:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[842:0622/130355.318681:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[1017:0622/130355.388099:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[1017:0622/130355.390256:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[842:0622/130356.093104:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[842:0622/130356.100823:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
^C[1017:0622/130359.490904:ERROR:connection.cc(66)] X connection error received.
[1017:0622/130359.490881:ERROR:connection.cc(66)] X connection error received.

I tried distros : Ubuntu22, Ubuntu20, Debian. The same.

elsaco · 2022-06-22T16:20:57Z

Here are steps to get dbus functionality on Win10/WSL:

- set `DISPLAY` env variable
- start `dbus` service
- set `XDG_RUNTIME_DIR` env variable
- start `dbus` user session

This will fix ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

Sample run on Win10 and vcxsrv using current WSL endpoint IP address:

- export DISPLAY=172.19.48.1:0
- sudo service dbus start
- export XDG_RUNTIME_DIR=/run/user/$(id -u)
- sudo mkdir $XDG_RUNTIME_USER
- sudo chmod 700 $XDG_RUNTIME_DIR
- sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
- export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
- dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

This can be added to .profile or .bashrc however the IP changes with every WSL restart. Win11 users don't need to worry about setting DISPLAY it's done by wslg.

When lauching google-chrome there are no more dbus errors, just some power daemon related (ignore them) and some extension not being supported:

tux@RIPPER:~$ google-chrome
[1603:1687:0622/090500.809467:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809580:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809665:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1643:1643:0622/090501.718820:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

And if you install upower the only error when starting google-chrome is:

tux@RIPPER:~$ google-chrome
[2313:2313:0622/092753.743901:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

ayushverma14 · 2022-07-08T07:23:01Z

I am trying to launch vs code installed on wsl ubuntu installed on windows machine .Getting the same error and vs code is unable to start

[18017:0708/124642.570768:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[18017:0708/124642.570908:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[18017:0708/124642.572659:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[18017:0708/124642.572681:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[18017:0708/124642.628617:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[main 2022-07-08T07:16:42.707Z] [File Watcher (node.js)] Request to start watching: /home/ayusver/.config/Code/User (excludes: <none>, includes: <all>),/home/ayusver/.config/Code/User/settings.json (excludes: <none>, includes: <all>)
[main 2022-07-08T07:16:42.719Z] Sending env to running instance...
[main 2022-07-08T07:16:42.720Z] [File Watcher (node.js)] Started watching: '/home/ayusver/.config/Code/User'
[main 2022-07-08T07:16:42.721Z] [File Watcher (node.js)] Error: ENOENT: no such file or directory, stat '/home/ayusver/.config/Code/User/settings.json'
[main 2022-07-08T07:16:42.827Z] Sent env to running instance. Terminating...
[main 2022-07-08T07:16:42.828Z] Lifecycle#kill()
[main 2022-07-08T07:16:42.828Z] Lifecycle#onWillShutdown.fire()

StephaneRavet · 2022-07-08T09:19:18Z

I am trying to launch cypress from my wsl project :

npx cypress open
[2069:0708/111639.476991:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2069:0708/111639.477091:ERROR:bus.cc(397)] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2069:0708/111639.480470:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2069:0708/111639.480516:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2069:0708/111639.575912:WARNING:bluez_dbus_manager.cc(248)] Floss manager not present, cannot set Floss enable/disable.
[2241:0708/111639.606803:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[2241:0708/111639.609824:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
[2069:0708/111640.314047:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[2069:0708/111640.441276:ERROR:bus.cc(397)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

ms0uto · 2022-09-26T18:48:31Z

Launching chromium from void linux causes the same behaviour.

[6769:6795:0926/204512.848653:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

[6769:6795:0926/204512.848734:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

[6769:6795:0926/204512.848775:ERROR:bus.cc(399)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

Jester3141 · 2022-10-20T22:16:19Z

I had this issue and it turned out that SELinux was causing chrome not to be able to access certain things through dbus. (errors were seen in the dbus log noting the selinux/chrome connection) Solutions are to either, add the appropriate selinux permissions to chrome or to disable selinux.

desaijay315 · 2022-10-21T08:15:13Z

Is this issue resolved? After installing google-chrome , getting the below issue

desaijay315 · 2022-10-21T08:15:34Z

I had this issue and it turned out that SELinux was causing chrome not to be able to access certain things through dbus. (errors were seen in the dbus log noting the selinux/chrome connection) Solutions are to either, add the appropriate selinux permissions to chrome or to disable selinux.

@Jester3141 - Ill give this a try

StephaneRavet · 2022-10-24T13:07:48Z

Cypress now launches correctly after migrating to Windows 11 (which adds WSLg).

sam-mfb · 2022-10-27T18:12:54Z

Here are steps to get dbus functionality on Win10/WSL:
- set `DISPLAY` env variable
- start `dbus` service
- set `XDG_RUNTIME_DIR` env variable
- start `dbus` user session
This will fix ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

Sample run on Win10 and vcxsrv using current WSL endpoint IP address:
- export DISPLAY=172.19.48.1:0
- sudo service dbus start
- export XDG_RUNTIME_DIR=/run/user/$(id -u)
- sudo mkdir $XDG_RUNTIME_USER
- sudo chmod 700 $XDG_RUNTIME_DIR
- sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
- export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
- dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

Is line 4 a typo, i.e., should it be sudo mkdir $XDG_RUNTIME_DIR?

mikaello · 2022-11-10T15:20:28Z

Here are steps to get dbus functionality on Win10/WSL:
...

This seems to help, but does not work completely, I now got errors like:

[5675:7:1110/161554.189115:ERROR:command_buffer_proxy_impl.cc(128)] ContextResult::kTransientFailure: Failed to send GpuControl.CreateCommandBuffer.
[1110/161556.373605:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_cur_freq: No such file or directory (2)
[1110/161556.373667:ERROR:file_io_posix.cc(144)] open /sys/devices/system/cpu/cpu0/cpufreq/scaling_max_freq: No such file or directory (2)

... and the webpage crashes. Has someone solved this?

I am running google-chrome in Docker in WSL through xserver.

Grkmus · 2022-11-24T10:17:29Z

I have a similar problem. I am running cypress via wsl2 with GUI. It actually opens but after running couple of tests, it become really slow and eventually does not respond at all. When I check the wsl2 console I see this message Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix") Any update on this?

joracine · 2022-12-04T03:04:12Z

Figured out how to fix this part:

This is because you're using the wrong IP. When entering the IP, make sure to use the Windows IP, not the IP from ifconfig or hostname within the WSL, as this is a WM's IP. Here's an update config ready for bashrc that also fixes the USER typo:

export DISPLAY=$(cat /etc/resolv.conf | grep nameserver | awk '{print $2}'):0.0
sudo service dbus restart
export XDG_RUNTIME_DIR=/run/user/$(id -u)
if [ -d "@XDG_RUNTIME_DIR" ]
then
  sudo mkdir $XDG_RUNTIME_DIR
  sudo chmod 700 $XDG_RUNTIME_DIR
  sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
fi
export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

SirLouen · 2022-12-22T16:41:56Z

$ sudo service dbus start
Redirecting to /bin/systemctl start dbus.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

How can you start dbus without systemd?

elsaco · 2022-12-22T17:09:32Z

@SirLouen if you type systemctl cat dubs.service there are the ExecStart and ExecReload commands. Also dbus-daemon --help will show the options for starting the daemon.

SirLouen · 2022-12-22T17:46:37Z

@SirLouen if you type systemctl cat dubs.service there are the ExecStart and ExecReload commands. Also dbus-daemon --help will show the options for starting the daemon.

$ sudo systemctl cat dbus.service
System has not been booted with systemd as init system (PID 1). Can't operate.
Failed to connect to bus: Host is down

elsaco · 2022-12-22T17:51:40Z

@SirLouen you could just look at the unit file in /lib/systemd/system/dbus.service:

elsaco@RIPPER:~$ cat /lib/systemd/system/dbus.service
[Unit]
Description=D-Bus System Message Bus
Documentation=man:dbus-daemon(1)
Requires=dbus.socket
# Do not stop on shutdown
DefaultDependencies=no
Wants=sysinit.target
After=sysinit.target basic.target

[Service]
ExecStart=@/usr/bin/dbus-daemon @dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only
ExecReload=/usr/bin/dbus-send --print-reply --system --type=method_call --dest=org.freedesktop.DBus / org.freedesktop.DBus.ReloadConfig
OOMScoreAdjust=-900

SirLouen · 2022-12-22T18:13:05Z

cat /lib/systemd/system/dbus.service

Not exactly there

$ cat /etc/systemd/system/dbus.service
[Unit]
Description=D-Bus System Message Bus
Documentation=man:dbus-broker-launch(1)
DefaultDependencies=false
After=dbus.socket
Before=basic.target shutdown.target
Requires=dbus.socket
Conflicts=shutdown.target

[Service]
Type=notify
Sockets=dbus.socket
OOMScoreAdjust=-900
LimitNOFILE=16384
ProtectSystem=full
PrivateTmp=true
PrivateDevices=true
ExecStart=/usr/bin/dbus-broker-launch --scope system --audit
ExecReload=/usr/bin/busctl call org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus ReloadConfig

[Install]
Alias=dbus.service

$ /usr/bin/dbus-broker-launch --scope system --audit
No listener socket inherited

wwjll · 2023-03-23T07:42:11Z

I tried

export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=:0

then I can launch chrome window in my win11. And using xrdp and xfce4 seems a reliable solution if you want a full desktop of your wsl2 .

Creeki · 2023-03-23T15:04:54Z

I tried
export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=:0
then I can launch chrome window in my win11. And using xrdp and xfce4 seems a reliable solution if you want a full desktop of your wsl2 .

Thanks you so much @wwjll !! It also makes the microsoft-edge works in my win11!

SuperBeagleDog · 2023-07-26T08:33:51Z

I tried
export LIBGL_ALWAYS_INDIRECT=1
export DISPLAY=:0
then I can launch chrome window in my win11. And using xrdp and xfce4 seems a reliable solution if you want a full desktop of your wsl2 .

Worked for me too, thank you, you saved my day.

3xploiton3 · 2023-08-25T11:48:19Z

open vs code, or code-oss using kali linux give us this error

[4081:0825/183951.012712:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/183951.015442:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/183958.526565:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/183958.528552:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/184002.551679:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/184002.555458:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/184024.138150:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")
[4081:0825/184024.141588:ERROR:bus.cc(398)] Failed to connect to the bus: Could not parse server address: Unknown address type (examples of valid types are "tcp" and on UNIX "unix")

kevin-coppens · 2023-11-24T23:08:13Z

I fixed it by following this : https://learn.microsoft.com/en-us/windows/wsl/tutorials/gui-apps

and then: sudo apt-get install dbus-x11

boamorte666 · 2023-11-27T04:47:04Z

Windows 11 - Ubuntu - WSL 2 - Clean Install

wget https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb
sudo dpkg -i google-chrome-stable_current_amd64.deb
sudo apt install --fix-broken -y
sudo dpkg -i google-chrome-stable_current_amd64.deb

I'm just do this:

sudo apt install upower
export XDG_RUNTIME_DIR=/run/user/$(id -u)
export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

shrikantbmali · 2024-01-11T10:21:32Z

Just restart your PC.

Juulaps · 2024-01-11T14:25:23Z

Here are steps to get dbus functionality on Win10/WSL:

- set `DISPLAY` env variable
- start `dbus` service
- set `XDG_RUNTIME_DIR` env variable
- start `dbus` user session

This will fix ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

Sample run on Win10 and vcxsrv using current WSL endpoint IP address:

- export DISPLAY=172.19.48.1:0
- sudo service dbus start
- export XDG_RUNTIME_DIR=/run/user/$(id -u)
- sudo mkdir $XDG_RUNTIME_USER
- sudo chmod 700 $XDG_RUNTIME_DIR
- sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
- export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
- dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

This can be added to .profile or .bashrc however the IP changes with every WSL restart. Win11 users don't need to worry about setting DISPLAY it's done by wslg.

When lauching google-chrome there are no more dbus errors, just some power daemon related (ignore them) and some extension not being supported:

tux@RIPPER:~$ google-chrome
[1603:1687:0622/090500.809467:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809580:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809665:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1643:1643:0622/090501.718820:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

And if you install upower the only error when starting google-chrome is:

tux@RIPPER:~$ google-chrome
[2313:2313:0622/092753.743901:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

Thanks! On Windows 11 (OS Build 22631.2861) + Ubuntu 22.04.3 I only needed to start the dbus user session to resolve the errors. The environment variables are already set out of the box. And the dbus service was already started (checked with systemctl status dbus).

dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

I do still get 2 Vulkan errors but those seems to be ignorable.

fdciabdul · 2024-02-11T19:17:07Z

same issue here

xavier-fenton · 2024-04-23T07:22:53Z

any solution to the problem?

WuYeqi · 2024-05-30T07:49:23Z

Here are steps to get dbus functionality on Win10/WSL:以下是在 Win10/WSL 上获取 dbus 功能的步骤：
- set `DISPLAY` env variable
- start `dbus` service
- set `XDG_RUNTIME_DIR` env variable
- start `dbus` user session
This will fix ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory 这将修复 ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/user/1000/bus: No such file or directory

Sample run on Win10 and vcxsrv using current WSL endpoint IP address:示例运行 Win10 和 vcxsrv 使用当前 WSL 终结点 IP 地址：
- export DISPLAY=172.19.48.1:0
- sudo service dbus start
- export XDG_RUNTIME_DIR=/run/user/$(id -u)
- sudo mkdir $XDG_RUNTIME_USER
- sudo chmod 700 $XDG_RUNTIME_DIR
- sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
- export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
- dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &
This can be added to .profile or .bashrc however the IP changes with every WSL restart. Win11 users don't need to worry about setting DISPLAY it's done by wslg.这可以添加到 IP 中 .profile ，或者 .bashrc IP 会随着每次 WSL 重启而更改。Win11 用户无需担心将其设置为 DISPLAY 由 wslg 完成。

When lauching google-chrome there are no more dbus errors, just some power daemon related (ignore them) and some extension not being supported:启动 google-chrome 时，不再 dbus 有错误，只是一些与电源守护程序相关的错误（忽略它们）和一些不支持的扩展：
tux@RIPPER:~$ google-chrome
[1603:1687:0622/090500.809467:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.DBus.Properties.Get: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809580:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.GetDisplayDevice: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1603:1687:0622/090500.809665:ERROR:object_proxy.cc(623)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
[1643:1643:0622/090501.718820:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.
And if you install upower the only error when starting google-chrome is:
tux@RIPPER:~$ google-chrome
[2313:2313:0622/092753.743901:ERROR:gpu_memory_buffer_support_x11.cc(44)] dri3 extension not supported.

There is a small error in the code here

This will work。Thank you very much, I spent several days trying to find a way to solve this problem

batata004 · 2024-06-04T02:11:51Z

Any news? I am still facing this same error message on Centos Stream 9.

qingpu-y · 2024-08-15T16:39:58Z

try {apt-get install dbus-x11 dbus}
try {services dbus start}
1. Failed to connect to the bus: Failed to connect to socket /run/user/0/bus: No such file or directory
dbus-launch and export {output DBUS_SESSION_BUS_ADDRESS}
1. [32374:32485:0815/162322.776073:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.UPower.EnumerateDevices: object_path= /org/freedesktop/UPower: org.freedesktop.DBus.Error.ServiceUnknown: The name org.freedesktop.UPower was not provided by any .service files
{apt install upower}

sshveta · 2024-11-01T18:40:15Z

sudo service dbus start

export XDG_RUNTIME_DIR=/run/user/$(id -u)
sudo mkdir $XDG_RUNTIME_USER
sudo chmod 700 $XDG_RUNTIME_DIR
sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

This worked for me .

alexanderilyin · 2024-11-10T06:29:00Z

@Juulaps seems you had small typo:

 sudo service dbus start
 export XDG_RUNTIME_DIR=/run/user/$(id -u)
-sudo mkdir $XDG_RUNTIME_USER
+sudo mkdir $XDG_RUNTIME_DIR
 sudo chmod 700 $XDG_RUNTIME_DIR
 sudo chown $(id -un):$(id -gn) $XDG_RUNTIME_DIR
 export DBUS_SESSION_BUS_ADDRESS=unix:path=$XDG_RUNTIME_DIR/bus
 dbus-daemon --session --address=$DBUS_SESSION_BUS_ADDRESS --nofork --nopidfile --syslog-only &

but it solved by errors. Thanks!

mwoodpatrick changed the title ~~wsl 2 - Getting “Failed to connect to the bus: Could not parse server address” error when launch electron -~~ wsl 2 - Getting “Failed to connect to the bus: Could not parse server address” error when launching google chrome or any electron app Jan 10, 2022

benhillis added the needs-author-feedback label Jan 11, 2022

ghost removed the needs-author-feedback label Jan 11, 2022

iongion mentioned this issue Aug 2, 2022

Windows 11 - WSL2 - Ubuntu 22 iongion/container-desktop#101

Closed

ronblum mentioned this issue Dec 21, 2022

Errors running RStudio under CentOS7 with and without --no-sandbox option rstudio/rstudio#12472

Open

4 tasks

Timmmm mentioned this issue Aug 13, 2023

Blank window when running from dev container due to dbus issue microsoft/vscode#190345

Closed

kachick mentioned this issue May 8, 2024

Fix CI kachick/vscode-extension-yamlfmt#1

Closed

ronblum mentioned this issue Aug 27, 2024

rstudio desktop d-bus error on wsl2 rstudio/rstudio#15091

Closed

wintonzheng mentioned this issue Oct 1, 2024

Failed to create browser in Windows WSL Docker Skyvern-AI/skyvern#733

Closed

paciox mentioned this issue Nov 26, 2024

Is possible to do anything beside fiddling with firefox and excel? anthropics/anthropic-quickstarts#197

Open

wsl 2 - Getting “Failed to connect to the bus: Could not parse server address” error when launching google chrome or any electron app #7915

wsl 2 - Getting “Failed to connect to the bus: Could not parse server address” error when launching google chrome or any electron app #7915

Comments

mwoodpatrick commented Jan 10, 2022

Version

WSL Version

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

mwoodpatrick commented Jan 10, 2022

benhillis commented Jan 11, 2022

mwoodpatrick commented Jan 11, 2022

mwoodpatrick commented Jan 11, 2022

ssbarnea commented Jan 31, 2022

mbwhite commented Mar 4, 2022

rajann44 commented Apr 11, 2022

OmarLomsadze commented May 20, 2022

RestOp commented Jun 11, 2022

PLopezD commented Jun 21, 2022

StephaneRavet commented Jun 22, 2022 • edited Loading

elsaco commented Jun 22, 2022 • edited Loading

ayushverma14 commented Jul 8, 2022

StephaneRavet commented Jul 8, 2022

ms0uto commented Sep 26, 2022 • edited Loading

Jester3141 commented Oct 20, 2022

desaijay315 commented Oct 21, 2022

desaijay315 commented Oct 21, 2022

StephaneRavet commented Oct 24, 2022

sam-mfb commented Oct 27, 2022

mikaello commented Nov 10, 2022 • edited Loading

Grkmus commented Nov 24, 2022

joracine commented Dec 4, 2022 • edited Loading

SirLouen commented Dec 22, 2022

elsaco commented Dec 22, 2022

SirLouen commented Dec 22, 2022

elsaco commented Dec 22, 2022

SirLouen commented Dec 22, 2022

wwjll commented Mar 23, 2023

Creeki commented Mar 23, 2023 • edited Loading

SuperBeagleDog commented Jul 26, 2023

3xploiton3 commented Aug 25, 2023 • edited Loading

kevin-coppens commented Nov 24, 2023

boamorte666 commented Nov 27, 2023

shrikantbmali commented Jan 11, 2024

Juulaps commented Jan 11, 2024 • edited Loading

fdciabdul commented Feb 11, 2024

xavier-fenton commented Apr 23, 2024

WuYeqi commented May 30, 2024

batata004 commented Jun 4, 2024

qingpu-y commented Aug 15, 2024 • edited Loading

sshveta commented Nov 1, 2024

alexanderilyin commented Nov 10, 2024

StephaneRavet commented Jun 22, 2022 •

edited

Loading

elsaco commented Jun 22, 2022 •

edited

Loading

ms0uto commented Sep 26, 2022 •

edited

Loading

mikaello commented Nov 10, 2022 •

edited

Loading

joracine commented Dec 4, 2022 •

edited

Loading

Creeki commented Mar 23, 2023 •

edited

Loading

3xploiton3 commented Aug 25, 2023 •

edited

Loading

Juulaps commented Jan 11, 2024 •

edited

Loading

qingpu-y commented Aug 15, 2024 •

edited

Loading