On 12/17/2019 10:17 AM, Pierre Labastie via blfs-dev wrote:
Le 16/12/2019 à 21:26, Douglas R. Reno via blfs-dev a écrit :
On 12/16/19 2:18 PM, Pierre Labastie via blfs-dev wrote:
Le 16 déc. 2019 16:47, Xi Ruoyao via blfs-dev
<[email protected]> a écrit :
On 2019-12-16 09:11 -0600, Douglas R. Reno via blfs-dev wrote:
On 12/16/19 3:19 AM, Pierre Labastie via blfs-dev wrote:
Hi,
I had 3 working BLFS builds of Gnome desktop over Sysv, but
somewhere between
one week ago and now, gdm got broken and does not start anymore
(begins
stating, but stops with a message "Oh no ! something has gone
wrong, contact a
system administrator" (how helpful !). I have not
been able to get useful messages from /var/log/gdm, but what I see
now in the
logs is that there are messages from the X server, which weren't
one week ago
(I think gdm was starting directly on wayland). Maybe it has
something to do
with this message from the log file:
gnome-session-binary[1370]: WARNING: Falling back to non-systemd
startup
procedure due to error:
GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown:
The name org.freedesktop.systemd1 was not provided by any .service
files.
I have no time to investigate more, because I have to leave for a
few days.
I'm around two days out on my SysV system. I should be able to look
into
it a couple days from now.
I think it may be related to one of the updates I did recently. One
suspect could be gnome-desktop. I don't think I updated GDM
recently,
but it could also be gnome-session or gnome-control-center.
If I trust the message, it comes from "gnome-session-binary".
I remember once I upgraded gnome-desktop then seen "Oh no" from GDM.
Then I fixed that by rebuilding GDM.
I've tried that, and even built a fresh system, but nothing worked.
Note that I can start gnome from command line, with startx and "exec
gnome-session" in .xinitrc.
Hi Pierre,
I've traced it down to a problem in elogind, and have begun working
on a fix.
elogind is only setup to read one line from the session data in
/run/systemd/sessions. GNOME was using the improper behavior
previously, and was fixed as part of gnome-session-3.34.2. elogind
has to be adapted to read more than the first line of that file:
"# This is private data. Do not parse."
Won't result in a valid UID after all :-)
Sure :) Thanks for investigating this.
Actually, there is a PR at elogind:
https://github.com/elogind/elogind/pull/142/commits/2b08527c0c939aebfd0ecd04a639cb6435c3f8ef
I guess a sed should do. Note also that 241.4 is out. Looks like the
currency script does not take it.
Ready to address this in build tonight so...Ugh. I'm sure there is
probably something shorter:
sed -e '/^#include "dirent-util.h"/a#include "env-file.h"' \
-e 's/read_one_line_file(p, \&/parse_env_file(NULL, p, "UID", \&/' \
-i src/basic/cgroup-util.c
:-) And I just saw the replies in book. Oh well, I went exactly literal.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
