| View previous topic :: View next topic |
| Author |
Message |
mhzuchini
n00b
Joined: 30 Nov 2017
Posts: 2
|
 Posted: Tue Nov 27, 2018 2:55 pm Post subject: systemd-logind can't start because /run/dbus does not exist |
 |
|
[Moderator note: This post and the first response were originally attached to systemd-logind can't start because /run/dbus does not exist. These posts deal with Sabayon, but the original thread did not. -Hu]
| tinloaf wrote: | Hi.
My system has trouble booting. It can all be traced back to systemd-logind (and some other services) not starting, because they can't find a dbus socket under /run/dbus:
[...]
Looking at my system, the dbus socket is correctly created under /var/run/dbus - just not symlinked (or whatever) to /run/dbus. As soon as I create the symlink myself (i.e., "link -s /var/run/dbus /run/dbus"), everything starts and works.
[...]
|
Hi, @tinloaf.
So I updated my Sabayon Linux yesterday and... ran into the exactly same trouble...
As soon as I've created the symlink to /var/run/dbus, the Linux box immediatelly prompted me with my Gnome login and everything worked...
Will try to investigate what could possibly be wrong. But many thanks for the advice!
In my case, I've create the symlink :
| Code: | | ln -s /var/run/dbus /run/dbus |
and then
| Code: | | systemctl start systemd-logind.service |
and 'voilá'! It works. At least until next reboot... this fix didn't last a reboot... which means I must do it again until I find what gone wrong... |
|
| Back to top |
|
 |
denijane
n00b
Joined: 22 Jul 2014
Posts: 14
|
| Posted: Tue Dec 04, 2018 1:34 am Post subject: |
|
|
Hi, mihzuchini, did you find out what went wrong? I just updated my sabayon and i have the same problem (I think).
It tells me that it failed to mount sysroot, gives me IRQ error and the laptop is unusable. It's very scary.
How did you manage reaching a console, it takes me 5 minutes just to reach login screen. I managed to log in couple of times, but after a minute the system goes unresponsive. It's a nightmare . As soon as I can I'll try your solution.
But I'm pretty sure that kernel updates are not supposed to do that.
Edit: nope, it didn't work. I managed to login and to create the symlink but everything is still awfully slow. If you could give me an idea how to find out what's wrong, I'd be very grateful. |
|
| Back to top |
|
|
mike155
Advocate
Joined: 17 Sep 2010
Posts: 4438
Location: Frankfurt, Germany
|
| Posted: Tue Dec 04, 2018 11:41 pm Post subject: |
|
|
| mhzuchini wrote: | In my case, I've create the symlink :
| Code: | | ln -s /var/run/dbus /run/dbus |
|
I don't know Sabayon and probably can't help you.
But... On most machines running Systemd, /var/run is a symlink to /run.
For that reason, it should not be necessary or even possible to create a symlink '/var/run/dbus -> /run/dbus', since /var/run/dbus and /run/dbus should be the same directory.
If I were you, I would try to find out why /var/run is not a symlink to /run on your machine.
Please remember that I don't know Sabayon and that I could be wrong. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Unsupported Software
