WSL sometimes gives dconf error when it boots after Windows boot

[maicol07]

Windows Version

Microsoft Windows [Version 10.0.23606.1000]

WSL Version

2.0.15.0

Are you using WSL 1 or WSL 2?

• WSL 2
• WSL 1

Kernel Version

5.15.133.1-1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

Boot Windows and open WSL (or a graphical app with WSLg)

Expected Behavior

No errors

Actual Behavior

Gives dconf errors in the shell:

(process:1209): dconf-WARNING **: 11:05:45.029: failed to commit changes to dconf: Could not connect: No such file or directory

(process:1212): dconf-WARNING **: 11:05:45.031: failed to commit changes to dconf: Could not connect: No such file or directory
Welcome to fish, the friendly interactive shell
Type help for instructions on how to use fish

(process:1304): dconf-WARNING **: 11:05:46.140: failed to commit changes to dconf: Could not connect: No such file or directory

(process:1307): dconf-WARNING **: 11:05:46.141: failed to commit changes to dconf: Could not connect: No such file or directory

(process:1310): dconf-WARNING **: 11:05:46.143: failed to commit changes to dconf: Could not connect: No such file or directory

After running a command:

(process:1733): dconf-CRITICAL **: 11:06:24.137: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1733): dconf-CRITICAL **: 11:06:24.137: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1733): dconf-CRITICAL **: 11:06:24.138: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1733): dconf-CRITICAL **: 11:06:24.138: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1733): dconf-WARNING **: 11:06:24.138: failed to commit changes to dconf: Could not connect: No such file or directory

(process:1737): dconf-CRITICAL **: 11:06:24.139: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1737): dconf-CRITICAL **: 11:06:24.139: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1737): dconf-CRITICAL **: 11:06:24.139: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1737): dconf-CRITICAL **: 11:06:24.139: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1737): dconf-WARNING **: 11:06:24.139: failed to commit changes to dconf: Could not connect: No such file or directory

(process:1740): dconf-CRITICAL **: 11:06:24.140: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1740): dconf-CRITICAL **: 11:06:24.141: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1740): dconf-CRITICAL **: 11:06:24.141: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1740): dconf-CRITICAL **: 11:06:24.141: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(process:1740): dconf-WARNING **: 11:06:24.141: failed to commit changes to dconf: Could not connect: No such file or directory

Also WSLg apps are glitched

Diagnostic Logs

WslLogs-2023-12-29_10-25-48.zip

[github-actions]

Hi I'm an AI powered bot that finds similar issues based off the issue title.

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. Thank you!

Open similar issues:

• WSL Ubuntu behaving weirdly after Windows startup (#5059), similarity score: 0.77

Closed similar issues:

• Windows Server kernel error caused by WSL (#7576), similarity score: 0.78
• some problem with wsl startup (#9841), similarity score: 0.77
• WSL startup problem (#8534), similarity score: 0.77
• Error 0xffffffff starting WSL from WT (#9875), similarity score: 0.76

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

[OneBlue]

Thank you @maicol07. Do you have systemd enabled in your distro ?

[maicol07]

Thank you @maicol07. Do you have systemd enabled in your distro ?

Yes

[OneBlue]

Do you still see those errors with systemd disabled ?

[maicol07]

I'll let you know in some days

[maicol07]

@OneBlue so it seems I don't get the error anymore but WSLg apps can't start (i.e. xclock), which might be related to the dbus and glitching issue from the OP.

[koppor]

I do have systemd enabled and I see the same issue, too. (Currently, I don't know how to disable systemd).

My application is an alpha version of GitButler.

[maicol07]

@koppor add the following to /etc/wsl.conf to disable systemd:

[boot]
systemd=false

[koppor]

Same behavior with

[boot]
systemd=false

[DavyG-SSG]

Hi @koppor, I don't know if that will help you, but I had the same issue and many problems with some apps, like Gedit or Tilix, not saving my configuration.
I found this on stack overflow : https://stackoverflow.com/questions/20285697/error-in-spawning-a-dbus-launch-what-is-that
I added this line to my .bashrc :
export $(dbus-launch)

It solved all of my problems :)

[maicol07]

I confirm @DavyG-SSG fix works! I don't know if it's a temporary fix or not, but it works!

[b14ckyy]

I have the same issue and can confirm the fix from @DavyG-SSG
A permanent fix on WSL side would be nice though as I have not had this issue before december with the same application.

[awakecoding]

I'm hitting the same problem here with Ubuntu 22.04 in WSL and Remote Desktop Manager for Linux, but I guess all applications using dconf are equally affected. Both workarounds of disabling systemd or adding export $(dbus-launch) to .bashrc worked. We do need a proper fix though