Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread gevisz
вс, 20 сент. 2020 г. в 15:37, Ashley Dixon :
>
> On Sun, Sep 20, 2020 at 02:23:58PM +0300, gevisz wrote:
> > вс, 20 сент. 2020 г. в 14:09, gevisz :
> > > 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!



Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread Ashley Dixon
On Sun, Sep 20, 2020 at 02:23:58PM +0300, gevisz wrote:
> вс, 20 сент. 2020 г. в 14:09, gevisz :
> > 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

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA



signature.asc
Description: PGP signature


Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread gevisz
вс, 20 сент. 2020 г. в 14:09, gevisz :
>
> вс, 20 сент. 2020 г. в 12:20, Ashley Dixon :
> >
> > 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
> >



Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread gevisz
вс, 20 сент. 2020 г. в 12:20, Ashley Dixon :
>
> 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.

> 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
>



Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread Ashley Dixon
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?
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.

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].  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



signature.asc
Description: PGP signature


Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread gevisz
вс, 20 сент. 2020 г. в 11:27, Ashley Dixon :
>
> On Sun, Sep 20, 2020 at 11:00:20AM +0300, gevisz wrote:
> > After a system update on 18.09.2020 of my Gentoo system, the
> > xorg-server failed to start with the following (last) error message:
> > dbus-core: error connecting to system bus:
> > org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket
> > /run/dbus/system_bus_socket: No such file or directory)
>
> Was the D-Bus package (sys-apps/dbus) touched during your system update?  If 
> so,
> did you reboot your system after the upgrade?  This  is  unlikely  to  fix  
> your
> issue, although there have been some reports (years ago)  of  the  D-Bus  
> socket
> file not being recreated until rebooting.

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.



Re: [gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread Ashley Dixon
On Sun, Sep 20, 2020 at 11:00:20AM +0300, gevisz wrote:
> After a system update on 18.09.2020 of my Gentoo system, the
> xorg-server failed to start with the following (last) error message:
> dbus-core: error connecting to system bus:
> org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket
> /run/dbus/system_bus_socket: No such file or directory)

Was the D-Bus package (sys-apps/dbus) touched during your system update?  If so,
did you reboot your system after the upgrade?  This  is  unlikely  to  fix  your
issue, although there have been some reports (years ago)  of  the  D-Bus  socket
file not being recreated until rebooting.

-- 

Ashley Dixon
suugaku.co.uk

2A9A 4117
DA96 D18A
8A7B B0D2
A30E BF25
F290 A8AA



signature.asc
Description: PGP signature


[gentoo-user] Xorg does not start after a recent system update.

2020-09-20 Thread gevisz
After a system update on 18.09.2020 of my Gentoo system, the
xorg-server failed to start with the following (last) error message:
dbus-core: error connecting to system bus:
org.freedesktop.DBus.Error.FileNotFound (Failed to connect to socket
/run/dbus/system_bus_socket: No such file or directory)

Last time I updated my system on 8.08.2020 and everything worked fine.

I use startx to start xorg-server and I do not use systemd.

I still use the 4.19.86 kernel which is already out of Gentoo tree
without masking the newer ones. May it be the reason?