vscode-remote-release icon indicating copy to clipboard operation
vscode-remote-release copied to clipboard

Cannot install Tunnels as a service: Error creating dbus session

Open iqnite opened this issue 6 months ago • 6 comments

  • VSCode Version: 1.100.2
  • Local OS Version: Windows 11 24H2
  • Remote OS Version: Raspberry Pi OS 12.11
  • Remote Extension/Connection Type: Remote - Tunnels
  • Logs: See below

Steps to Reproduce:

  1. On a machine running Debian, run sudo code tunnel service install
  2. The command will fail with this error:
*
* Visual Studio Code Server
*
* By using the software, you agree to
* the Visual Studio Code Server License Terms (https://aka.ms/vscode-server-license) and
* the Microsoft Privacy Statement (https://privacy.microsoft.com/en-US/privacystatement).
*
[2025-06-02 21:58:47] error Error creating dbus session. This command uses systemd for managing services, you should check that systemd is installed and under your user.If running `systemctl status` works, systemd is ok, but your session dbus may not be. You might need to:

- Install the `dbus-user-session` package, and reboot if it was not installed
- Start the user dbus session with `systemctl --user enable dbus --now`.

The error encountered was: I/O error: No such file or directory (os error 2)
  1. Follow the instructions shown in the error message
  2. You will still get the error

Does this issue occur when you try this locally?: N/A Does this issue occur when you try this locally and all extensions are disabled?: Yes

iqnite avatar Jun 02 '25 20:06 iqnite

What is the systemctl status dbus?

connor4312 avatar Jun 03 '25 22:06 connor4312

sudo systemctl status dbus returns the following:

● dbus.service - D-Bus System Message Bus
     Loaded: loaded (/lib/systemd/system/dbus.service; static)
     Active: active (running) since Mon 2025-06-02 21:17:48 CEST; 1 day 10h ago
TriggeredBy: ● dbus.socket
       Docs: man:dbus-daemon(1)
   Main PID: 479 (dbus-daemon)
      Tasks: 1 (limit: 3913)
        CPU: 5.673s
     CGroup: /system.slice/dbus.service
             └─479 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Jun 02 21:19:07 philipp-raspi dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.15' (uid=0 pid=692 comm="/usr/sbin/cupsd -l")
Jun 02 21:19:07 philipp-raspi dbus-daemon[479]: [system] Successfully activated service 'org.freedesktop.ColorManager'
Jun 02 22:41:00 philipp-raspi dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.32' (uid=1000 pid=1163 comm="/usr/bin/wf-panel-pi")
Jun 02 22:41:00 philipp-raspi dbus-daemon[479]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jun 02 22:41:41 philipp-raspi dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.11' (uid=0 pid=625 comm="/usr/sbin/NetworkManager --no-daemon")
Jun 02 22:41:41 philipp-raspi dbus-daemon[479]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jun 02 22:42:21 philipp-raspi dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.timedate1' unit='dbus-org.freedesktop.timedate1.service' requested by ':1.55' (uid=1000 pid=4259 comm="timedatectl status")
Jun 02 22:42:21 philipp-raspi dbus-daemon[479]: [system] Successfully activated service 'org.freedesktop.timedate1'
Jun 02 22:42:21 philipp-raspi dbus-daemon[479]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.54' (uid=1000 pid=4245 comm="gui-updater")
Jun 02 22:42:21 philipp-raspi dbus-daemon[479]: [system] Successfully activated service 'org.freedesktop.PackageKit'

iqnite avatar Jun 04 '25 05:06 iqnite

Oh, sorry wrong command -- we need systemctl --user status dbus to make sure your user dbus is running

connor4312 avatar Jun 04 '25 15:06 connor4312

Oh, sorry wrong command -- we need systemctl --user status dbus to make sure your user dbus is running


Failed to connect to bus: No medium found

iqnite avatar Jun 04 '25 15:06 iqnite

You'll want to make sure dbus is running under your user to use the install command. systemctl --user enable dbus --now should have given you an error when you ran it.

connor4312 avatar Jun 04 '25 15:06 connor4312

systemctl --user enable dbus --now

Yes, I get the same error after this command.

iqnite avatar Jun 04 '25 16:06 iqnite

Having the exact same issue, Ubuntu on WSL tunnel worked no problem with the previous version but now fails

MaurGi avatar Aug 28 '25 18:08 MaurGi