Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............

So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a "reconfigure" option in systemd commands.
--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2022-01-05, Grimble <[email protected]> wrote:

Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............

So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a "reconfigure" option in systemd commands.

No idea what that means. You could look into the logs to see what it it
might be complaining about. journalctl


--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Wed, 05 Jan 2022 08:01:57 -0500, Grimble <[email protected]> wrote:

Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile: The default is the current profile.
[ OK ]
Checking for new hardware [ OK ]
[ OK ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............

So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a "reconfigure" option in systemd commands.

# grep -Iir reconfigure /lib/systemd/* /lib/systemd/system/mandriva-everytime.service:Description=Reconfigure the system on administrator request

As that finished ok, that is not the problem.

What dm (display manager) is being used? Check /etc/sysconfig/desktop.

I'd try installing a different one such as lxdm, then either use "mcc/Boot/Setup Display Manger" to make it active, or just edit the desktop file
to have ...
# cat /etc/sysconfig/desktop
DISPLAYMANAGER=lxdm

Regards, Dave Hodgins

--- MBSE BBS v1.0.7.22 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 07/01/2022 06:02, David W. Hodgins wrote:

On Wed, 05 Jan 2022 08:01:57 -0500, Grimble <[email protected]> wrote:

Booting with any initial selection, the last systemd messages are:
Starting Reconfigure the system on administrator request...
Starting netprofile:  The default is the current profile.
                                                            [  OK  ]
Checking for new hardware                                  [  OK  ]
[  OK  ] Finished Reconfigure the system on administrator request.
You are in emergency mode. After logging in, type ............

So: what is this administrator request? Google finds nothing, and I
didn't edit any part of the grub commands. I can find no mention of a
"reconfigure" option in systemd commands.

# grep -Iir reconfigure /lib/systemd/* /lib/systemd/system/mandriva-everytime.service:Description=Reconfigure
the system on administrator request

As that finished ok, that is not the problem.

OK, I recognise that is not a/the problem

What dm (display manager) is being used? Check /etc/sysconfig/desktop.

I'd try installing a different one such as lxdm, then either use "mcc/Boot/Setup Display Manger" to make it active, or just edit the
desktop file
to have ...
# cat /etc/sysconfig/desktop
DISPLAYMANAGER=lxdm

Regards, Dave Hodginsssdm was the DM; changed it to lxdm with no effect.

Xorg.0.log contains an error messge:
(EE) dbus-core: error connecting to system bus:......(Failed to connect
to socket /run/dbus/system_bus_socket: No such file or directory)
followed by Open PCI failed (var/run/acpid.socket) (No such file or directory).
The last entry on the log is the same dbus-core message, which is being
added to every 10 seconds.
I notice no log message has been added to syslog since 3 January! Does
syslog need dbus?
As I've alrady said: if I do systemctl start dbus.service, the GUI
session is immediately killed and the screen reverts to the emergency
mode screen and the system requires a cold start.
I can su to my home account (didn't ask for a password!)
Incidentally, cifs.mount failed with error code -101, so perhaps
whatever the samba problem was, the new kernel, 5.15.11, hasn't
corrected it.
( I loaded up the LIVE system which ran without apparent problem. I
didn't go on to install it)
--
Grimble
Registered Linux User #450547
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Tue, 11 Jan 2022 08:34:33 -0500, Grimble <[email protected]> wrote:

Xorg.0.log contains an error messge:
(EE) dbus-core: error connecting to system bus:......(Failed to connect
to socket /run/dbus/system_bus_socket: No such file or directory)
followed by Open PCI failed (var/run/acpid.socket) (No such file or directory).
The last entry on the log is the same dbus-core message, which is being added to every 10 seconds.
I notice no log message has been added to syslog since 3 January! Does
syslog need dbus?

The dbus program is used by various daemons to talk to each other, as well as by
desktop environments such as kde plasma and gnome. I have no idea why it might be
failing on that system. It is a critical service.

On my system ...
[root@x3 ~]# systemctl status dbus.socket
● dbus.socket - D-Bus System Message Bus Socket
Loaded: loaded (/usr/lib/systemd/system/dbus.socket; static)
Active: active (running) since Sat 2022-01-08 18:13:45 EST; 2 days ago
Triggers: ● dbus.service
Listen: /run/dbus/system_bus_socket (Stream)
CGroup: /system.slice/dbus.socket

Jan 08 18:13:45 x3.hodgins.homeip.net systemd[1]: Listening on D-Bus System Message Bus Socket.
[root@x3 ~]# systemctl status dbus.service
● dbus.service - D-Bus System Message Bus
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: active (running) since Sat 2022-01-08 18:13:45 EST; 2 days ago TriggeredBy: ● dbus.socket
Docs: man:dbus-daemon(1)
Main PID: 1122 (dbus-daemon)
Tasks: 1 (limit: 19119)
Memory: 8.8M
CPU: 24.481s
CGroup: /system.slice/dbus.service
└─1122 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation --syslog-only

Jan 11 04:02:04 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1318' (uid=9 pi>
Jan 11 04:02:04 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 11 12:26:23 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1474' (uid=0 pi>
Jan 11 12:26:23 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 11 16:05:38 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1552' (uid=0 pi>
Jan 11 16:05:38 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Successfully activated service 'org.freedesktop.hostname1'
Jan 11 16:25:26 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service' requested by ':1.1569' (uid=500 pi>
Jan 11 16:25:26 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Successfully activated service 'org.freedesktop.machine1'
Jan 11 16:31:04 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Activating via systemd: service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostname1.service' requested by ':1.1572' (uid=0 pi>
Jan 11 16:31:04 x3.hodgins.homeip.net dbus-daemon[1122]: [system] Successfully activated service 'org.freedesktop.hostname1'

Try booting to run level 3. Is dbus running ok then?

Regards, Dave Hodgins

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 11/01/2022 21:51, David W. Hodgins wrote:

On Tue, 11 Jan 2022 08:34:33 -0500, Grimble <[email protected]> wrote:

Xorg.0.log contains an error messge:
(EE) dbus-core: error connecting to system bus:......(Failed to connect
to socket /run/dbus/system_bus_socket: No such file or directory)
followed by Open PCI failed (var/run/acpid.socket) (No such file or
directory).
The last entry on the log is the same  dbus-core message, which is being
added to every 10 seconds.
I notice no log message has been added to syslog since 3 January! Does
syslog need dbus?

The dbus program is used by various daemons to talk to each other, as
well as by
desktop environments such as kde plasma and gnome. I have no idea why it might be
failing on that system. It is a critical service.

[snip]

Try booting to run level 3. Is dbus running ok then?

Regards, Dave Hodgins

No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)

It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation, something else nasty might happen that'll waste hours more of my time.

Regards,
--
Grimble
Machine 'Bach' running Plasma 5.20.4 on 5.15.6-desktop-2.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2022-01-12, Grimble <[email protected]> wrote:

On 11/01/2022 21:51, David W. Hodgins wrote:

Try booting to run level 3. Is dbus running ok then?

Regards, Dave Hodgins

No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)

Hm, are the permission OK
find /lib/systemd -name \*dbus\* -ls
Are they all readable by everyone, especially the ones in
/lib/systemd/user
Are all the files
ls -l /usr/bin/dbus*
readable and executable by everyone?

It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem arose on the first reboot after a kernel update on a new installation, something else nasty might happen that'll waste hours more of my time.

Since it seems that noone else has the problem, there is something
strange about your system. root works you say. If you get another user,
do you get the same problem when you log in to that user?

Regards,

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Wed, 12 Jan 2022 10:26:03 -0500, Grimble <[email protected]> wrote:

No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)

It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation, something else nasty might happen that'll waste hours more of my time.

Either a reinstall, or open a bug report, and attach the output of
"journalctl -b --no-hostname |xz >journal.xz".

Regards, Dave Hodgins

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 12/01/2022 17:58, David W. Hodgins wrote:

On Wed, 12 Jan 2022 10:26:03 -0500, Grimble <[email protected]> wrote:

No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)

It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation,
something else nasty might happen that'll waste hours more of my time.

Either a reinstall, or open a bug report, and attach the output of "journalctl -b --no-hostname |xz >journal.xz".

Regards, Dave Hodgins

Thanks, William, David. I've chosen to re-install. As I said, nothing
gets written to syslog, so there's little to put in a bug report.
The first steps of re-install have gone OK, so for the next day or so,
I'll be recreating my personal work space.
--
Grimble
Machine 'mozart' running Plasma 5.20.4 on 5.15.11-desktop-3.mga8 kernel.
Mageia release 8 (Official) for x86_64

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On 2022-01-12, grimble <[email protected]> wrote:

On 12/01/2022 17:58, David W. Hodgins wrote:

On Wed, 12 Jan 2022 10:26:03 -0500, Grimble <[email protected]>
wrote:

No difference:
Loaded: loaded (/usr/lib/systemd/system/dbus.service; static)
Active: inactive (dead)

It seems such a bizarre error that I have little option but to
re-install, but I'm worried that, without a solution, since the problem
arose on the first reboot after a kernel update on a new installation,
something else nasty might happen that'll waste hours more of my time.

Either a reinstall, or open a bug report, and attach the output of
"journalctl -b --no-hostname |xz >journal.xz".

Regards, Dave Hodgins

Thanks, William, David. I've chosen to re-install. As I said, nothing
gets written to syslog, so there's little to put in a bug report.
The first steps of re-install have gone OK, so for the next day or so,
I'll be recreating my personal work space.

systemd does not write to syslog. It writes to journal, and you see via journalctl
You can get the old style syslog by installing and running rsyslogd.
Then you will get the files like /var/log/syslog, /var/log/messages, ...


--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)

On Wed, 12 Jan 2022 15:08:23 -0500, William Unruh <[email protected]> wrote:

systemd does not write to syslog. It writes to journal, and you see via journalctl
You can get the old style syslog by installing and running rsyslogd.
Then you will get the files like /var/log/syslog, /var/log/messages, ...

Without dbus, there's likely little being written to the journal either.

Regards, Dave Hodgins

--- MBSE BBS v1.0.7.24 (GNU/Linux-x86_64)
* Origin: A noiseless patient Spider (2:250/1@fidonet)