вс, 20 сент. 2020 г. в 14:09, gevisz <gev...@gmail.com>: > > вс, 20 сент. 2020 г. в 12:20, Ashley Dixon <a...@suugaku.co.uk>: > > > > On Sun, Sep 20, 2020 at 11:59:10AM +0300, gevisz wrote: > > > Thank you for your reply. Yes, I tried it after a reboot. > > > As to your first question, I will look into logs and report it a bit > > > later. > > > > 1) Could you confirm that `/run/dbus/system_bus_socket` doesn't exist? > > Thank you for your reply and the tips. > > /run/dbus directory does not exist on the computer where xorg-server > does not start, which probably means that it does not run. (At the > same time, /run/dbus/system_bus_socket does exit on another my Gentoo > box that I last updated 1.5 years ago and that has no problem starting > xorg-server. It still has default/linux/amd64/17.0/desktop (stable) > profile.) > > Also, I cannot find a link to dbus from any of my /etc/runlevels on my > problem computer though such a link exists from > /etc/runlevels/default/dbus to /etc/init.d/dbus on my old Gentoo > installation. > > On both my Gentoo installations exist /etc/X11/xinit/xinitrc.d/80-dbus > file that promises to launch a session dbus instance. > > 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. Thank you. Still do not understand how it worked without it before. Will look into logs and post to this thread any other problems xorg-server reports, if any, later. > > 2) Please post the full logs of the X server, usually at > > `/var/log/Xorg.0.log`. > > 3) The output of `emerge --info x11-base/xorg-server` would be nice. > > Will come soon. :) > > > I ask for (3), because if you have the `systemd` OR `elogind` flags set on > > your > > X server package, `--enable-systemd-login` will be passed to the > > configure > > script, which is known to cause this problem [1]. > > Thank you for the tip and the links. > > On both my systems (the old and the new one) I do have elogind > installed as it is needed for Skype. > On the old system, xorg-server still does not have an elogind use > flag, while the new one has it and it is set on. > > > From the relevant ebuild [2]: > > > > if use systemd || use elogind; then > > XORG_CONFIGURE_OPTIONS+=( > > "--enable-systemd-logind" > > "--disable-install-setuid" > > "$(use_enable suid suid-wrapper)" > > ) > > else > > XORG_CONFIGURE_OPTIONS+=( > > "--disable-systemd-logind" > > "--disable-suid-wrapper" > > "$(use_enable suid install-setuid)" > > ) > > fi > > > > [1] https://gitlab.freedesktop.org/xorg/xserver/-/issues/554 > > [2] > > https://gitweb.gentoo.org/repo/gentoo.git/tree/x11-base/xorg-server/xorg-server-1.20.9.ebuild#n179 > > > > -- > > > > Ashley Dixon > > suugaku.co.uk > > > > 2A9A 4117 > > DA96 D18A > > 8A7B B0D2 > > A30E BF25 > > F290 A8AA > >
