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