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