| 1 |
вс, 20 сент. 2020 г. в 12:20, Ashley Dixon <ash@××××××××××.uk>: |
| 2 |
> |
| 3 |
> On Sun, Sep 20, 2020 at 11:59:10AM +0300, gevisz wrote: |
| 4 |
> > Thank you for your reply. Yes, I tried it after a reboot. |
| 5 |
> > As to your first question, I will look into logs and report it a bit later. |
| 6 |
> |
| 7 |
> 1) Could you confirm that `/run/dbus/system_bus_socket` doesn't exist? |
| 8 |
|
| 9 |
Thank you for your reply and the tips. |
| 10 |
|
| 11 |
/run/dbus directory does not exist on the computer where xorg-server |
| 12 |
does not start, which probably means that it does not run. (At the |
| 13 |
same time, /run/dbus/system_bus_socket does exit on another my Gentoo |
| 14 |
box that I last updated 1.5 years ago and that has no problem starting |
| 15 |
xorg-server. It still has default/linux/amd64/17.0/desktop (stable) |
| 16 |
profile.) |
| 17 |
|
| 18 |
Also, I cannot find a link to dbus from any of my /etc/runlevels on my |
| 19 |
problem computer though such a link exists from |
| 20 |
/etc/runlevels/default/dbus to /etc/init.d/dbus on my old Gentoo |
| 21 |
installation. |
| 22 |
|
| 23 |
On both my Gentoo installations exist /etc/X11/xinit/xinitrc.d/80-dbus |
| 24 |
file that promises to launch a session dbus instance. |
| 25 |
|
| 26 |
When installing my new Gentoo installation, I tried to make it as |
| 27 |
close to the old one as it was possible, and it is strange to me that |
| 28 |
the new one does not have a dbus startup in its runlevels. (As far as |
| 29 |
I remember, in both cases I needed dbus to switch keyboard layout in |
| 30 |
Awesome, and it did on both systems before the last update.) |
| 31 |
|
| 32 |
Probably, my first try should be to add dbus to the default runlevel |
| 33 |
on my new Gentoo installation. |
| 34 |
|
| 35 |
> 2) Please post the full logs of the X server, usually at `/var/log/Xorg.0.log`. |
| 36 |
> 3) The output of `emerge --info x11-base/xorg-server` would be nice. |
| 37 |
|
| 38 |
Will come soon. :) |
| 39 |
|
| 40 |
> I ask for (3), because if you have the `systemd` OR `elogind` flags set on your |
| 41 |
> X server package, `--enable-systemd-login` will be passed to the configure |
| 42 |
> script, which is known to cause this problem [1]. |
| 43 |
|
| 44 |
Thank you for the tip and the links. |
| 45 |
|
| 46 |
On both my systems (the old and the new one) I do have elogind |
| 47 |
installed as it is needed for Skype. |
| 48 |
On the old system, xorg-server still does not have an elogind use |
| 49 |
flag, while the new one has it and it is set on. |
| 50 |
|
| 51 |
> From the relevant ebuild [2]: |
| 52 |
> |
| 53 |
> if use systemd || use elogind; then |
| 54 |
> XORG_CONFIGURE_OPTIONS+=( |
| 55 |
> "--enable-systemd-logind" |
| 56 |
> "--disable-install-setuid" |
| 57 |
> "$(use_enable suid suid-wrapper)" |
| 58 |
> ) |
| 59 |
> else |
| 60 |
> XORG_CONFIGURE_OPTIONS+=( |
| 61 |
> "--disable-systemd-logind" |
| 62 |
> "--disable-suid-wrapper" |
| 63 |
> "$(use_enable suid install-setuid)" |
| 64 |
> ) |
| 65 |
> fi |
| 66 |
> |
| 67 |
> [1] https://gitlab.freedesktop.org/xorg/xserver/-/issues/554 |
| 68 |
> [2] https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/xorg-server-1.20.9.ebuild#n179 |
| 69 |
> |
| 70 |
> -- |
| 71 |
> |
| 72 |
> Ashley Dixon |
| 73 |
> suugaku.co.uk |
| 74 |
> |
| 75 |
> 2A9A 4117 |
| 76 |
> DA96 D18A |
| 77 |
> 8A7B B0D2 |
| 78 |
> A30E BF25 |
| 79 |
> F290 A8AA |
| 80 |
> |
Archives