вс, 20 сент. 2020 г. в 15:37, Ashley Dixon <a...@suugaku.co.uk>:
>
> On Sun, Sep 20, 2020 at 02:23:58PM +0300, gevisz wrote:
> > вс, 20 сент. 2020 г. в 14:09, gevisz <gev...@gmail.com>:
> > > When installing my new Gentoo installation, I tried to make it as
> > > close to the old one as it was possible, and it is strange to me that
> > > the new one does not have a dbus startup in its runlevels. (As far as
> > > I remember, in both cases I needed dbus to switch keyboard layout in
> > > Awesome, and it did on both systems before the last update.)
> > >
> > > Probably, my first try should be to add dbus to the default runlevel
> > > on my new Gentoo installation.
> >
> > Yes, after adding dbus to default runlevel, the xorg-server started.
>
> It would be very peculiar if D-Bus was removed from your runlevels; it's
> more
> probable that a service implicitly starting D-Bus as a dependency via `need`
> was
> changed during your system upgrade. Regardless, since the service was
> never
> starting, the socket file was never being created. X should probably try
> and
> start the D-Bus service when it initialises, either as a part of the
> Gentoo
> patchset, or as a bug to upstream. The BlueZ bluetooth service does this,
> for
> example [1]:
>
> depend() {
> after coldplug
> need dbus localmount hostname
> }
>
> Anyway, glad to see it fixed.
>
> [1]
> https://gitweb.gentoo.org/repo/gentoo.git/tree/net-wireless/bluez/files/bluetooth-init.d-r4
>
My guess was that it is /etc/X11/xinit/xinitrc.d/80-dbus that started
dbus on the problem computer but for some reason stopped to do it
after the system update, but of course it may be because of changed
dependency of the OpenRC dependencies.
Anyway, thank you once more for your help!
