`mkdir /run/user/1000/: permission denied` after WSL 2.0.0 #10498

felipecrs · 2023-09-19T15:59:04Z

Windows Version

Microsoft Windows [Version 10.0.22631.2338]

WSL Version

2.0.0.0

Are you using WSL 1 or WSL 2?

WSL 2
WSL 1

Kernel Version

5.15.123.1-1

Distro Version

Ubuntu 22.04

Other Software

No response

Repro Steps

I'm sorry but I'm not sure if this issue happened after upgrading to 2.0.0 or after running wsl --manage Ubuntu --set-sparse true, since I did both at once.

Some programs I have, like chezmoi, is now failing:

$ chezmoi update
chezmoi: mkdir /run/user/1000/: permission denied

Expected Behavior

To work as it did before.

Actual Behavior

$ chezmoi update
chezmoi: mkdir /run/user/1000/: permission denied

Diagnostic Logs

No logs.

This is apparently related to /run/user/1000 owner become root when pre mount a vhdx disk before start the wsl system #10473, but since my problem happened after upgrading to 2.0.0 I'm reporting it separately.

The workaround is to:

sudo mkdir /run/user/1000 && sudo chmod 700 /run/user/1000 && sudo chown $(whoami): /run/user/1000

Which I saw somewhere but I don't remember where.

The text was updated successfully, but these errors were encountered:

benhillis · 2023-09-19T21:10:12Z

Do you have systemd enabled?

felipecrs · 2023-09-19T21:16:16Z

Yes, I forgot to mention that.

felipecrs · 2023-09-20T14:06:16Z

Just to mention, this issue happened again out of the blue after booting up my WSL today. I suspect it's perhaps to the automatic disk sparsing.

Previously I tested wsl --shutdown many times and it didn't trigger the issue after fixing the directory permissions manually.

luis-aranda · 2023-09-22T05:36:38Z

I have the same issue. The workaround for me is to remove systemd in /etc/wsl.conf

Also setting the permission works with something like "chmod 700 $XDG_RUNTIME_DIR" but this doesn't persist in new sessions after closing the current session

OneBlue · 2023-09-22T19:48:26Z

@felipecrs: Can you share the output of ls -la /run/user and share boot logs for when you see this issue ?

/logs

microsoft-github-policy-service · 2023-09-22T19:48:32Z

Hello! Could you please provide more logs to help us better diagnose your issue?

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 scipt will output the path of the log file once done.

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

Click here for more info on logging

Thank you!

felipecrs · 2023-09-22T20:38:37Z

Will do, as soon as I can reproduce the issue again. As mentioned, it seems to happen randomly after fixing the permissions manually. Rebooting WSL or Windows does not immediately trigger the issue, apparently.

felipecrs · 2023-09-23T04:07:35Z

I was really not able to reproduce this issue today. Yesterday it happened multiple times.

@luis-aranda if you are still experiencing this, please share the logs as @OneBlue asked if you don't mind.

felipecrs · 2023-09-25T23:25:09Z

After upgrading to 2.0.1 I was able to reproduce this issue again. I'm working to capture the logs.

felipecrs · 2023-09-25T23:28:10Z

After wsl --shutdown to enable debugConsole I can no longer see the issue. Odd!

felipecrs · 2023-09-25T23:37:36Z

Ok, issue happened again while WSL was even running. A restart isn't required to trigger the issue apparently.

❯ chezmoi cd
chezmoi: mkdir /run/user/1000/: permission denied
❯ ls -la /run/user/1000
ls: cannot access '/run/user/1000': No such file or directory
❯ sudo ls -la /run/user
total 0
drwxr-xr-x  2 root root  40 Sep 25 20:30 .
drwxr-xr-x 29 root root 780 Sep 25 20:29 ..

WslLogs-2023-09-25_20-35-57.zip

asampal · 2023-09-27T00:16:32Z

Also have been getting asimilar error, (org.gnome.Nautilus:1046): dconf-CRITICAL **: 20:13:44.733: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly., since 2.0.0. Noticed it when running nautilus &. Terminal spews this as you move the cursor over the UI.

felipecrs · 2023-09-28T17:34:49Z

I gotta say that after unregistering my WSL instance and starting from scratch I'm no longer having this issue.

In the meantime I had also upgraded to 2.0.1, so maybe it also fixed it.

g2flyer · 2023-10-05T20:24:33Z

FYI: i see also a similar issue: since quite a while, after starting wsl i initially get the "normal" /usr/user/1000 for default user but then fairly quickly something removes the whole directory with all files. A 'ssh localhost' does recreate them and from then on all the files stay as expected (to the extent i have to stay logged in via ssh, as soon as i log out the files get quickly removed). And yes, i also have systemd enabled (and currently run it with wsl 2.0.4.0 ...)

felipecrs · 2023-10-05T21:09:28Z

An update on my side: I deleted my whole distro (wsl --unregister) and reinstalled it. I'm no longer facing this issue after doing that. Several days have passed already.

g2flyer · 2023-10-10T16:47:09Z

FYI: realized only now that this is a duplicate of #10496 and #10552. Disabling systemd-networkd.disable as mentioned there solves the issue. Additionally, as discussed there (and in related issue https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/2036358), this is more a ubuntu/systemd issue than a WSL2 issue, so probably this issue could be closed?

dan788 · 2023-10-20T23:58:42Z

add this start up script to your .profile
start_script.txt
sudo -i
chown 1000:1000 /run/user/1000
logout
env | grep DBUS
should show DBUS_STARTER_ADDRESS=unix:path=/run/user/1000/bus
hope this helps

appselskapet · 2023-12-02T01:00:39Z

@dan788 this worked for me. Thanks alot. Do you have a brief explanation what it does?

georgejean · 2023-12-08T13:53:30Z

@appselskapet See here.

aruprakshit · 2024-09-26T07:53:31Z

I have this error too.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble
$ emacs .

(emacs:3234): dconf-CRITICAL **: 13:12:43.450: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.451: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.451: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.452: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.452: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.453: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.454: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.454: unable to create directory '/run/user/1000/dconf': Permission denied.  dconf will not work properly.

xarthurx · 2024-10-11T08:34:47Z

I have this error too.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble
$ emacs .

(emacs:3234): dconf-CRITICAL **: 13:12:43.450: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.451: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.451: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.452: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.452: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.453: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.454: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

(emacs:3234): dconf-CRITICAL **: 13:12:43.454: unable to create directory '/run/user/1000/dconf': Permission denied. dconf will not work properly.

Same here.

Adhjie · 2024-11-17T02:08:41Z

add this start up script to your .profile start_script.txt sudo -i chown 1000:1000 /run/user/1000 logout env | grep DBUS should show DBUS_STARTER_ADDRESS=unix:path=/run/user/1000/bus hope this helps

Hi, I follow your guide. But my ubuntu session start with this error

-bash: /home/adhjie/.start_script.txt: line 1: syntax error near unexpected token `$'\r''
'bash: /home/adhjie/.start_script.txt: line 1: `sudo_autopasswd()

How to get it to work?
you guys? @georgejean @appselskapet

I came here from this error in my Ubuntu, sudo -H apt upgrade, sadly upgrade also my GUI apps with sudo, even tho i already install pcmanfm-qt using just apt install
so the og error that leads me to this run/user/1000 problem is this

QStandardPaths: error creating runtime directory '/run/user/1000/' (Permission denied)

benhillis added the needs-author-feedback label Sep 19, 2023

ghost changed the title ~~mkdir /run/user/1000/: permission denied after WSL 2.0.0 and wsl --manage Ubuntu --set-sparse true~~ mkdir /run/user/1000/: permission denied after WSL 2.0.0 Sep 19, 2023

microsoft-github-policy-service bot removed the needs-author-feedback label Sep 19, 2023

microsoft-github-policy-service bot added the needs-author-feedback label Sep 22, 2023

microsoft-github-policy-service bot removed the needs-author-feedback label Sep 22, 2023

xudyang1 mentioned this issue Jan 26, 2024

Nvim always logs server_start:164 error in WSL (SOLVED: permissions issue) neovim/neovim#26058

Closed

github-actions bot mentioned this issue Mar 10, 2024

Unable to run WSL2 as LocalSystem user #11280

Closed

2 tasks

Ramilito mentioned this issue Mar 27, 2024

jobstart() does not set $NVIM environment variable if /run/user/1000 is not accessible neovim/neovim#27962

Open

akinomyoga mentioned this issue Apr 16, 2024

[WSL] ble.sh breaks on start and does not let me type in the console akinomyoga/ble.sh#426

Closed

wngtk mentioned this issue May 8, 2024

error: Can't create the symlink for multishells at "/run/user/1000/fnm_multishells/3628_1715158318789". Maybe there are some issues with permissions for the directory? No such file or directory (os error 2) Schniz/fnm#1119

Open

akinomyoga mentioned this issue Jun 2, 2024

podman - XDG_RUNTIME_DIR directory "/mnt/wslg/runtime-dir" is not owned by the current user #11542

Open

2 tasks

akinomyoga mentioned this issue Jun 20, 2024

Daemon socket should be in $XDG_RUNTIME_DIR atuinsh/atuin#2153

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`mkdir /run/user/1000/: permission denied` after WSL 2.0.0 #10498

`mkdir /run/user/1000/: permission denied` after WSL 2.0.0 #10498

felipecrs commented Sep 19, 2023

benhillis commented Sep 19, 2023

felipecrs commented Sep 19, 2023

felipecrs commented Sep 20, 2023

luis-aranda commented Sep 22, 2023 •

edited

Loading

OneBlue commented Sep 22, 2023

microsoft-github-policy-service bot commented Sep 22, 2023

felipecrs commented Sep 22, 2023

felipecrs commented Sep 23, 2023

felipecrs commented Sep 25, 2023

felipecrs commented Sep 25, 2023

felipecrs commented Sep 25, 2023

asampal commented Sep 27, 2023 •

edited

Loading

felipecrs commented Sep 28, 2023

g2flyer commented Oct 5, 2023

felipecrs commented Oct 5, 2023

g2flyer commented Oct 10, 2023

dan788 commented Oct 20, 2023

appselskapet commented Dec 2, 2023

georgejean commented Dec 8, 2023

aruprakshit commented Sep 26, 2024

xarthurx commented Oct 11, 2024

Adhjie commented Nov 17, 2024

mkdir /run/user/1000/: permission denied after WSL 2.0.0 #10498

mkdir /run/user/1000/: permission denied after WSL 2.0.0 #10498

Comments

felipecrs commented Sep 19, 2023

Windows Version

WSL Version

Are you using WSL 1 or WSL 2?

Kernel Version

Distro Version

Other Software

Repro Steps

Expected Behavior

Actual Behavior

Diagnostic Logs

benhillis commented Sep 19, 2023

felipecrs commented Sep 19, 2023

felipecrs commented Sep 20, 2023

luis-aranda commented Sep 22, 2023 • edited Loading

OneBlue commented Sep 22, 2023

microsoft-github-policy-service bot commented Sep 22, 2023

felipecrs commented Sep 22, 2023

felipecrs commented Sep 23, 2023

felipecrs commented Sep 25, 2023

felipecrs commented Sep 25, 2023

felipecrs commented Sep 25, 2023

asampal commented Sep 27, 2023 • edited Loading

felipecrs commented Sep 28, 2023

g2flyer commented Oct 5, 2023

felipecrs commented Oct 5, 2023

g2flyer commented Oct 10, 2023

dan788 commented Oct 20, 2023

appselskapet commented Dec 2, 2023

georgejean commented Dec 8, 2023

aruprakshit commented Sep 26, 2024

xarthurx commented Oct 11, 2024

Adhjie commented Nov 17, 2024

`mkdir /run/user/1000/: permission denied` after WSL 2.0.0 #10498

`mkdir /run/user/1000/: permission denied` after WSL 2.0.0 #10498

luis-aranda commented Sep 22, 2023 •

edited

Loading

asampal commented Sep 27, 2023 •

edited

Loading