Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

MULTIPLE DBUS STILL NEEDS WORK #12017

Open
1 of 2 tasks
stevebovy opened this issue Sep 10, 2024 · 5 comments
Open
1 of 2 tasks

MULTIPLE DBUS STILL NEEDS WORK #12017

stevebovy opened this issue Sep 10, 2024 · 5 comments

Comments

@stevebovy
Copy link

Windows Version

10.0.19045.4842

WSL Version

2.3.17.0

Are you using WSL 1 or WSL 2?

  • WSL 2
  • WSL 1

Kernel Version

5.15.153.1-2

Distro Version

No response

Other Software

No response

Repro Steps

It is now 2024, and upon revisiting this issue, I wish to complement both ubuntu and wsl for their efforts to address this issue.

BUT, after re-examining the state of this issue I have discovered a new question:

When I start a BRAND NEW vm ubunto session I discover the following which looks on the surface
to be excellent:

bovy@DEVDESKSJB:$ ps -ael | grep dbus
4 S 102 259 1 1 80 0 - 2193 - ? 00:00:00 dbus-daemon
0 S 1000 493 426 0 80 0 - 2075 - ? 00:00:00 dbus-daemon
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ set | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/
total 0
drwxr-xr-x 3 root root 60 Sep 10 13:15 .
drwxr-xr-x 20 root root 580 Sep 10 13:15 ..
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 1000
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/1000
total 0
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 .
drwxr-xr-x 3 root root 60 Sep 10 13:15 ..
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 bus
drwxr-xr-x 4 bovy bovy 80 Sep 10 13:15 dbus-1
drwx------ 2 bovy bovy 140 Sep 10 13:15 gnupg
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 pipewire-0
-rw-rw---- 1 bovy bovy 0 Sep 10 13:15 pipewire-0.lock
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 pk-debconf-socket
drwx------ 2 bovy bovy 80 Sep 10 13:15 pulse
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 snapd-session-agent.socket
drwxr-xr-x 5 bovy bovy 140 Sep 10 13:15 systemd
lrwxrwxrwx 1 root root 31 Sep 10 13:15 wayland-0 -> /mnt/wslg/runtime-dir/wayland-0
lrwxrwxrwx 1 root root 36 Sep 10 13:15 wayland-0.lock -> /mnt/wslg/runtime-dir/wayland-0.lock
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/1000/bus
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 /run/user/1000/bus
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:~$ ls -al /run/user/1000/dbus-1
total 0
drwxr-xr-x 4 bovy bovy 80 Sep 10 13:15 .
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 ..
drwxr-xr-x 2 bovy bovy 40 Sep 10 13:15 service
drwx------ 2 bovy bovy 40 Sep 10 13:15 services

BUT:

After I start a gnome-terminal, an additional unnecessary dbus daemon is started:

bovy@DEVDESKSJB:~$ gnome-terminal &
[1] 1475

bovy@DEVDESKSJB:~$ ps -ael | grep dbus
4 S 102 259 1 0 80 0 - 2193 - ? 00:00:00 dbus-daemon
0 S 1000 493 426 0 80 0 - 2144 - ? 00:00:00 dbus-daemon
0 S 1000 1504 1498 0 80 0 - 2075 - ? 00:00:00 dbus-daemon

bovy@DEVDESKSJB:~$

I do not understand why or how this is happening, Or how it can be FIXED

Expected Behavior

I expect their to be ONLY ONE user space --session dbus daemon

Not TWO, ONLY ONE

Actual Behavior

After I start a gnome-terminal, an additional unnecessary dbus daemon is started:

bovy@DEVDESKSJB:~$ gnome-terminal &
[1] 1475

bovy@DEVDESKSJB:~$ ps -ael | grep dbus
4 S 102 259 1 0 80 0 - 2193 - ? 00:00:00 dbus-daemon
0 S 1000 493 426 0 80 0 - 2144 - ? 00:00:00 dbus-daemon
0 S 1000 1504 1498 0 80 0 - 2075 - ? 00:00:00 dbus-daemon

AN EXTRA USER SPACE DBUS DAEMON IS BEING CREATED

Diagnostic Logs

bovy@DEVDESKSJB:$ ps -ael | grep dbus
4 S 102 259 1 1 80 0 - 2193 - ? 00:00:00 dbus-daemon
0 S 1000 493 426 0 80 0 - 2075 - ? 00:00:00 dbus-daemon
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ set | grep DBUS
DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/
total 0
drwxr-xr-x 3 root root 60 Sep 10 13:15 .
drwxr-xr-x 20 root root 580 Sep 10 13:15 ..
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 1000
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/1000
total 0
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 .
drwxr-xr-x 3 root root 60 Sep 10 13:15 ..
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 bus
drwxr-xr-x 4 bovy bovy 80 Sep 10 13:15 dbus-1
drwx------ 2 bovy bovy 140 Sep 10 13:15 gnupg
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 pipewire-0
-rw-rw---- 1 bovy bovy 0 Sep 10 13:15 pipewire-0.lock
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 pk-debconf-socket
drwx------ 2 bovy bovy 80 Sep 10 13:15 pulse
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 snapd-session-agent.socket
drwxr-xr-x 5 bovy bovy 140 Sep 10 13:15 systemd
lrwxrwxrwx 1 root root 31 Sep 10 13:15 wayland-0 -> /mnt/wslg/runtime-dir/wayland-0
lrwxrwxrwx 1 root root 36 Sep 10 13:15 wayland-0.lock -> /mnt/wslg/runtime-dir/wayland-0.lock
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:$ ls -al /run/user/1000/bus
srw-rw-rw- 1 bovy bovy 0 Sep 10 13:15 /run/user/1000/bus
bovy@DEVDESKSJB:$

bovy@DEVDESKSJB:~$ ls -al /run/user/1000/dbus-1
total 0
drwxr-xr-x 4 bovy bovy 80 Sep 10 13:15 .
drwxr-xr-x 6 bovy bovy 260 Sep 10 13:15 ..
drwxr-xr-x 2 bovy bovy 40 Sep 10 13:15 service
drwx------ 2 bovy bovy 40 Sep 10 13:15 services
@github-actions GitHub Actions
Copy link

Logs are required for review from WSL team

If this a feature request, please reply with '/feature'. If this is a question, reply with '/question'.
Otherwise please attach logs by following the instructions below, your issue will not be reviewed unless they are added. These logs will help us understand what is going on in your machine.

How to collect WSL logs

Download and execute collect-wsl-logs.ps1 in an administrative powershell prompt:

Invoke-WebRequest -UseBasicParsing "https://raw.githubusercontent.com/microsoft/WSL/master/diagnostics/collect-wsl-logs.ps1" -OutFile collect-wsl-logs.ps1
Set-ExecutionPolicy Bypass -Scope Process -Force
.\collect-wsl-logs.ps1

The script will output the path of the log file once done.

If this is a networking issue, please use collect-networking-logs.ps1, following the instructions here

Once completed please upload the output files to this Github issue.

Click here for more info on logging
If you choose to email these logs instead of attaching to the bug, please send them to [email protected] with the number of the github issue in the subject, and in the message a link to your comment in the github issue and reply with '/emailed-logs'.

View similar issues

Please view the issues below to see if they solve your problem, and if the issue describes your problem please consider closing this one and thumbs upping the other issue to help us prioritize it!

Closed similar issues:

Note: You can give me feedback by thumbs upping or thumbs downing this comment.

@stevebovy
Copy link
Author

WslLogs-2024-09-10_13-49-15.zip

Here is a log with the wsl actions I have used to create this issue

@github-actions GitHub Actions
Copy link

Diagnostic information 
.wslconfig found
Detected appx version: 2.3.17.0

@OneBlue
Copy link
Collaborator

OneBlue commented Sep 10, 2024

@stevebovy: Does this happen every time you start gnome terminal or only once ? I'd be curious to see if gnome-terminal has logic to start a new dbus session under some specific conditions.

@stevebovy
Copy link
Author

Thanks, for your response.

It only happens ONCE, but I think the same thing happens if I run "thunar" so it is not unique to
one specific gnome app.

If this is a WAS, could someone please share with me an explanation of why this behavior is taking place.

Thanks very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@stevebovy @OneBlue