Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: /tmp/.X11-unix/X0 Deleted during X11 session (Read 1544 times) previous topic - next topic
0 Members and 2 Guests are viewing this topic.

/tmp/.X11-unix/X0 Deleted during X11 session

I'm just reporting a bug that seems to be affecting Artix users only in regards to Steam. The steam bubblewrap libraries seem to require the use of /tmp/.X11-unix/X0 socket which I'm being told is created by xserver when a session starts and is supposed to exist until the session ends. I have no idea if this is accurate. Supposedly on Artix linux this file gets deleted somehow?

These are the two github issues with users that are experiencing this bug.

https://github.com/ValveSoftware/Proton/issues/5340
https://github.com/ValveSoftware/steam-runtime/issues/486

I hope this is the correct way to report a bug because the two URLs I see in this forum post no longer work: https://forum.artixlinux.org/index.php/topic,814.0.html

https://gitea.artixlinux.org/ -> registration is disabled
https://bugs.artixlinux.org/ -> 403 forbidden

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #1 –
I remember in the past there was a race condition with sddm starting which caused some sockets in /tmp to go missing. That shouldn't be an issue these days though. I'm guessing something similar is happening though. These users are starting a displaymanager on boot that has some race. The fix depends on the init system used and so on.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #2 –
Came here to clarify that this seems to happen during startup.
Logging out and in again will workaround this, as the socket is recreated and doesn't get deleted.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #3 –
I'm on Artix Linux base with OpenRC. I checked and I had lightdm set to boot runlevel. I've stepped it back to default runlevel and it seems to create /tmp/.X11-unix/X0
 

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #4 –
Ah yeah, I'm not terribly knowledgeable about the workings of the openrc bootup process, but I would assume that, in general, you shouldn't add things to the boot runlevel. Using default seems like the right fix in your case.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #5 –
Quote from: Dudemanguy – on
Ah yeah, I'm not terribly knowledgeable about the workings of the openrc bootup process, but I would assume that, in general, you shouldn't add things to the boot runlevel. Using default seems like the right fix in your case.
Correct, 99% of stuff should go in default run level. The 1 exception is elogind which should be in boot.
Chris Cromer

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #6 –
I'm on S6 and this is also happening.
But I haven't really changed anything from the defaults.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #7 –
What displaymanager are you using?

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #10 –
Quote from: venny – on
Not sure if you meant me, but in any case I'm running SDDM.

Hmm, sddm explictly depends on mount-tmpfs before starting so this shouldn't happen in theory. I'll have to double check I suppose.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #11 –
@venny:
I took some time to look into this and I couldn't reproduce with the sddm-s6 script. The /tmp/.X11-unix/ stuff is always there. Those directories are created by tmpfiles-setup which is executed on boot and always after mount-tmpfs is run. So there shouldn't be any way for this to go wrong. Are you fully up to date?

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #12 –
Yes I'm up to date and the problem persists.
For context, I installed using the previously available S6 KDE ISO and barely did anything besides enabling arch repos, installing nvidia drivers, steam and handful of other things like browser etc.
Let me know if there are any logs I can provide or other useful things.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #13 –
Quote from: venny – on
Yes I'm up to date and the problem persists.
For context, I installed using the previously available S6 KDE ISO and barely did anything besides enabling arch repos, installing nvidia drivers, steam and handful of other things like browser etc.
Let me know if there are any logs I can provide or other useful things.

Could you edit /etc/s6/current/scripts/runlevel and change
Code: [Select]
exec s6-rc -up change "$1"
to
Code: [Select]
exec s6-rc -v2 -up change "$1"
Then restart your machine and paste the contents of /run/uncaught-logs/current? Basically, I just want to see the exact ordering of your services on startup to see if something strange/wrong is happening.

Re: /tmp/.X11-unix/X0 Deleted during X11 session

Reply #14 –
The contents are as follows:
Code: [Select]
@400000006206917e378ccbaf s6-rc: info: service cronie: starting
@400000006206917e378eda22 s6-rc: info: service s6rc-fdholder: starting
@400000006206917e3791402b s6-rc: info: service s6rc-oneshot-runner: starting
@400000006206917e37c4ed87 s6-rc: info: service cronie successfully started
@400000006206917e37ed2142 s6-rc: info: service s6rc-oneshot-runner successfully started
@400000006206917e37f8b408 s6-rc: info: service rc-local: starting
@400000006206917e37fa5cd2 s6-rc: info: service sysctl: starting
@400000006206917e37fcaf21 s6-rc: info: service net-lo: starting
@400000006206917e37ff2d62 s6-rc: info: service mount-tmpfs: starting
@400000006206917e380185fb s6-rc: info: service mount-procfs: starting
@400000006206917e38038361 s6-rc: info: service lvm2-pvscan: starting
@400000006206917e3805b3e1 s6-rc: info: service lvm2-monitor: starting
@400000006206917e3808af64 s6-rc: info: service hwclock: starting
@400000006206917e38630f73 s6-rc: info: service s6rc-fdholder successfully started
@400000006206917e3865ef93 s6-rc: info: service udevd-log: starting
@400000006206917e3868925c s6-rc: info: service syslog-ng-log: starting
@400000006206917e386b4375 s6-rc: info: service lvmpolld-log: starting
@400000006206917e386e47ab s6-rc: info: service dmesg-log: starting
@400000006206917e38711841 s6-rc: info: service dbus-log: starting
@400000006206917e387403ca s6-rc: info: service bluetoothd-log: starting
@400000006206917e3876dacb s6-rc: info: service acpid-log: starting
@400000006206917e3879fa51 s6-rc: info: service NetworkManager-log: starting
@400000006206917e388138dd s6-rc: info: service mount-procfs successfully started
@400000006206917e3883cbf0 s6-rc: info: service mount-sysfs: starting
@400000006206917e38875b8e s6-rc: info: service mount-devfs: starting
@400000006206917e3889d96a s6-rc: info: service mount-cgroups: starting
@400000006206917e388ce82b s6-rc: info: service hostname: starting
@400000006206917e388f9e7e s6-rc: info: service binfmt: starting
@400000006206917e38c38daf s6-rc: info: service sysctl successfully started
@400000006206917e390d9c31 s6-rc: info: service net-lo successfully started
@400000006206917e39203b2a s6-rc: info: service hwclock successfully started
@400000006206917e393a8f48 s6-rc: info: service mount-tmpfs successfully started
@400000006206917e39570d11 s6-rc: info: service binfmt successfully started
@400000006206917e397d9234 s6-rc: info: service hostname successfully started
@400000006206917e39a2c252 s6-rc: info: service dbus-log successfully started
@400000006206917e39a4d93a s6-rc: info: service dbus-srv: starting
@400000006206917e39b0dfc1 s6-rc: info: service acpid-log successfully started
@400000006206917e39b383db s6-rc: info: service acpid-srv: starting
@400000006206917e39b4290e s6-rc: info: service syslog-ng-log successfully started
@400000006206917e39b74cd5 s6-rc: info: service syslog-ng-srv: starting
@400000006206917e39b85c37 s6-rc: info: service lvmpolld-log successfully started
@400000006206917e39b8641a s6-rc: info: service dmesg-log successfully started
@400000006206917e39ba35fa s6-rc: info: service dmesg-srv: starting
@400000006206917e39bfed3e s6-rc: info: service bluetoothd-log successfully started
@400000006206917e39bff2d2 s6-rc: info: service NetworkManager-log successfully started
@400000006206917e39bff57f s6-rc: info: service mount-sysfs successfully started
@400000006206917e39d46651 s6-rc: info: service udevd-log successfully started
@400000006206917e39e6cfc6 s6-rc: info: service acpid-srv successfully started
@400000006206917e39f40519 s6-rc: info: service syslog-ng-srv successfully started
@400000006206917e39f40d9f s6-rc: info: service dmesg-srv successfully started
@400000006206917e3a138fd0 s6-rc: info: service mount-devfs successfully started
@400000006206917e3a20c6f9 s6-rc: info: service network-detection: starting
@400000006206917e3a20ce26 s6-rc: info: service kmod-static-nodes: starting
@400000006206917e3a20d2fc s6-rc: info: service agetty-tty6: starting
@400000006206917e3a20d87c s6-rc: info: service agetty-tty5: starting
@400000006206917e3a20dd00 s6-rc: info: service agetty-tty4: starting
@400000006206917e3a5c5578 s6-rc: info: service agetty-tty3: starting
@400000006206917e3a5c5e5f s6-rc: info: service agetty-tty2: starting
@400000006206917e3a5c62b4 s6-rc: info: service agetty-tty1: starting
@400000006206917e3a5c66d0 s6-rc: info: service agetty-serial: starting
@400000006206917e3a5c6b56 s6-rc: info: service agetty-tty6 successfully started
@400000006206917e3a87c1d1 s6-rc: info: service agetty-tty5 successfully started
@400000006206917e3a87cb47 s6-rc: info: service agetty-tty4 successfully started
@400000006206917e3a87cfd0 s6-rc: info: service agetty-tty2 successfully started
@400000006206917e3a87d3f7 s6-rc: info: service agetty-tty1 successfully started
@400000006206917e3a87d807 s6-rc: info: service agetty-tty3 successfully started
@400000006206917e3ab15b2c s6-rc: info: service network-detection successfully started
@400000006206917e3ab16382 s6-rc: info: service agetty-serial successfully started
@400000006206917f002cecf2 s6-rc: info: service kmod-static-nodes successfully started
@400000006206917f00319545 s6-rc: info: service tmpfiles-dev: starting
@400000006206917f00d7dfe4 s6-rc: info: service tmpfiles-dev successfully started
@400000006206917f01113920 s6-rc: info: service dbus-srv successfully started
@400000006206917f0115ce72 s6-rc: info: service elogind: starting
@400000006206917f011a4a45 s6-rc: info: service cupsd: starting
@400000006206917f011a4d49 s6-rc: info: service bluetoothd-srv: starting
@400000006206917f0123185a s6-rc: info: service NetworkManager-srv: starting
@400000006206917f0143f3c9 s6-rc: info: service cupsd successfully started
@400000006206917f0149f8fd s6-rc: info: service bluetoothd-srv successfully started
@400000006206917f0149ffe6 s6-rc: info: service NetworkManager-srv successfully started
@400000006206917f01532aaa s6-rc: info: service elogind successfully started
@400000006206917f0318c015 s6-rc: info: service mount-cgroups successfully started
@400000006206917f031e7901 s6-rc: info: service udevd-srv: starting
@400000006206917f034e43fe s6-rc: info: service udevd-srv successfully started
@400000006206917f03535c1d s6-rc: info: service udevadm: starting
@400000006206917f04d2a5a4 s6-rc: info: service lvm2-pvscan successfully started
@400000006206917f0997d9c0 s6-rc: info: service lvm2-monitor successfully started
@400000006206917f0e7fdd05 s6-rc: info: service rc-local successfully started
@400000006206918e1dd40822 s6-rc: info: service udevadm successfully started
@400000006206918e1de0244f s6-rc: info: service modules: starting
@400000006206918e1de02d8e s6-rc: info: service cryptsetup: starting
@400000006206918e1df7861d s6-rc: info: service sddm: starting
@400000006206918e1df78f98 s6-rc: info: service lvmpolld-srv: starting
@400000006206918e1e35780f s6-rc: info: service sddm successfully started
@400000006206918e1e3b2846 s6-rc: info: service lvmpolld-srv successfully started
@400000006206918e23701941 s6-rc: info: service cryptsetup successfully started
@400000006206918e239f863c s6-rc: info: service modules successfully started
@400000006206918e23a57749 s6-rc: info: service mount-filesystems: starting
@400000006206918e24cdcd56 s6-rc: info: service mount-filesystems successfully started
@400000006206918e24d28f0f s6-rc: info: service remount-root: starting
@400000006206918e24d71e1d s6-rc: info: service mount-net: starting
@400000006206918e252a47a1 s6-rc: info: service mount-net successfully started
@400000006206918e25632ef5 s6-rc: info: service remount-root successfully started
@400000006206918e256f8947 s6-rc: info: service tmpfiles-setup: starting
@400000006206918e256f92c2 s6-rc: info: service sysusers: starting
@400000006206918e256f985f s6-rc: info: service swap: starting
@400000006206918e259d47aa s6-rc: info: service random-seed: starting
@400000006206918e259d5495 s6-rc: info: service locale: starting
@400000006206918e259d5b0a s6-rc: info: service console-setup: starting
@400000006206918e259d6011 s6-rc: info: service cleanup: starting
@400000006206918e25d70c22 s6-rc: info: service swap successfully started
@400000006206918e2615ea58 s6-rc: info: service cleanup successfully started
@400000006206918e26382185 s6-rc: info: service tmpfiles-setup successfully started
@400000006206918e2650190a s6-rc: info: service locale successfully started
@400000006206918e266d842b s6-rc: info: service random-seed successfully started
@400000006206918e26dc0b1f s6-rc: info: service sysusers successfully started
@400000006206918e272dd6aa s6-rc: info: service console-setup successfully started