Rebooted my other desktop, Bach, after installing the latest package of
updates, but it failed before reaching the login screen, with the screen
showing 5 messages like "[FAILED] Failed to start MySQL database server"
(I thought the screen messages were dmesg messages but I can't find the
failure messages in that or syslog)
Anyway, I can't find any reason for it not to complete the boot process.
Any suggestions please?
--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 05/10/2021 14:38, Grimble wrote:
> Started in safe mode, found I can start up the GUi as root (startx), so it must be something with the main user account.

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On Tue, 05 Oct 2021 09:38:52 -0400, Grimble <grimble@nomail.afraid.org> wrote:

> Rebooted my other desktop, Bach, after installing the latest package of
> updates, but it failed before reaching the login screen, with the screen
> showing 5 messages like "[FAILED] Failed to start MySQL database server"
> (I thought the screen messages were dmesg messages but I can't find the
> failure messages in that or syslog)
> Anyway, I can't find any reason for it not to complete the boot process.
> Any suggestions please?

When that error shows up, switch to a text login terminal such as alt+ctrl+f3
Login as root, then use "journalctl -b --no-h" to view the boot journal entries.
(the no-h is short for no-hostname so the lines displayed are shorter)

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org> wrote:

> On 05/10/2021 14:38, Grimble wrote:
>> Started in safe mode, found I can start up the GUi as root (startx), so it must be something with the main user account.

Is ~/.Xauthority owned by root? It must be owned by the user for X to be able to use
it. As root run "chown grimble:grimble /home/grimble/.Xauthority", replacing
grimble by the actual user id.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 05/10/2021 17:51, David W. Hodgins wrote:
> On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>
> wrote:
>
>> On 05/10/2021 14:38, Grimble wrote:
>>> Started in safe mode, found I can start up the GUi as root (startx),
>>> so it must be something with the main user account.
>
> Is ~/.Xauthority owned by root? It must be owned by the user for X to be
> able to use
> it. As root run "chown grimble:grimble /home/grimble/.Xauthority",
> replacing
> grimble by the actual user id.
>
> Regards, Dave Hodgins
>
Thanks, Dave, but it's already owned by me.

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 05/10/2021 17:51, David W. Hodgins wrote:
> On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>
> wrote:
>
>> On 05/10/2021 14:38, Grimble wrote:
>>> Started in safe mode, found I can start up the GUi as root (startx),
>>> so it must be something with the main user account.
>
> Is ~/.Xauthority owned by root? It must be owned by the user for X to be
> able to use
> it. As root run "chown grimble:grimble /home/grimble/.Xauthority",
> replacing
> grimble by the actual user id.
>
> Regards, Dave Hodgins
>
Xorg.0.log ends with an EE message:
Logitech USB Keyboard: client bug: event processing lagging behind by
15ms, your system is too slow
followed by 4 messages relating to "Logitech USB Keyboard: device
removed" and 7 messages saying UnloadModule: "libinput" and "Server
terminated successfully....."
There are Google entries for both these messages, but I can't see how
they relate to my situation.
Since the keyboard/mouse worked OK when I was logged in as "root", it
seems I must recreate my user Xorg environment. How would I do that?

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 05/10/2021 17:51, David W. Hodgins wrote:
> On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>
> wrote:
>
>> On 05/10/2021 14:38, Grimble wrote:
>>> Started in safe mode, found I can start up the GUi as root (startx),
>>> so it must be something with the main user account.
>
> Is ~/.Xauthority owned by root? It must be owned by the user for X to be
> able to use
> it. As root run "chown grimble:grimble /home/grimble/.Xauthority",
> replacing
> grimble by the actual user id.
>
> Regards, Dave Hodgins
>
Xorg.0.log ends with an EE message:
Logitech USB Keyboard: client bug: event processing lagging behind by
15ms, your system is too slow
followed by 4 messages relating to "Logitech USB Keyboard: device
removed" and 7 messages saying UnloadModule: "libinput" and "Server
terminated successfully....."
There are Google entries for both these messages, but I can't see how
they relate to my situation.
Since the keyboard/mouse worked OK when I was logged in as "root", it
seems I must recreate my user Xorg environment. How would I do that?

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On Thu, 07 Oct 2021 14:31:31 +0100, Grimble wrote:

> On 05/10/2021 17:51, David W. Hodgins wrote:
>> On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>
>> wrote:
>>
>>> On 05/10/2021 14:38, Grimble wrote:
>>>> Started in safe mode, found I can start up the GUi as root (startx),
>>>> so it must be something with the main user account.
>>
>> Is ~/.Xauthority owned by root? It must be owned by the user for X to
>> be able to use it. As root run "chown grimble:grimble
>> /home/grimble/.Xauthority", replacing grimble by the actual user id.
>>
>> Regards, Dave Hodgins
>>
> Xorg.0.log ends with an EE message:
> Logitech USB Keyboard: client bug: event processing lagging behind by
> 15ms, your system is too slow followed by 4 messages relating to
> "Logitech USB Keyboard: device removed" and 7 messages saying
> UnloadModule: "libinput" and "Server terminated successfully....."
> There are Google entries for both these messages, but I can't see how
> they relate to my situation.
> Since the keyboard/mouse worked OK when I was logged in as "root", it
> seems I must recreate my user Xorg environment. How would I do that?

If the problem is within root permissions, perhaps you should take a look
at

man Xorg.wrap
and
man Xorg # with particular attention to -conf* sections.

Cheers!

jim b.

--
UNIX is not user-unfriendly, it merely
expects users to be computer friendly.

On Thu, 07 Oct 2021 08:57:01 -0400, Grimble <grimble@nomail.afraid.org> wrote:

> On 05/10/2021 17:51, David W. Hodgins wrote:
>> On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>
>> wrote:
>>
>>> On 05/10/2021 14:38, Grimble wrote:
>>>> Started in safe mode, found I can start up the GUi as root (startx),
>>>> so it must be something with the main user account.
>>
>> Is ~/.Xauthority owned by root? It must be owned by the user for X to be
>> able to use
>> it. As root run "chown grimble:grimble /home/grimble/.Xauthority",
>> replacing
>> grimble by the actual user id.
>>
>> Regards, Dave Hodgins
>>
> Xorg.0.log ends with an EE message:
> Logitech USB Keyboard: client bug: event processing lagging behind by
> 15ms, your system is too slow
> followed by 4 messages relating to "Logitech USB Keyboard: device
> removed" and 7 messages saying UnloadModule: "libinput" and "Server
> terminated successfully....."
> There are Google entries for both these messages, but I can't see how
> they relate to my situation.
> Since the keyboard/mouse worked OK when I was logged in as "root", it
> seems I must recreate my user Xorg environment. How would I do that?

I believe that is indicating a hardware problem. Something is causing an extremely
large number of hardware interrupts, and the cpu simply can not keep up processing
them.

I've seen that with poor hardware connections - poor connections between a plug
and socket), broken wire in a usb cable making intermittent high resistance
connections, but also in devices with a low battery, such as a wireless mouse.
It can also sometimes be fixed by re-seating things like pcie cards.

Debugging that type of problem involves disconnecting all hardware that is not
essential for booting, and then (assuming the problem doesn't show in that case)
reconnecting one thing at a time until the problem recurs.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 05/10/2021 14:38, Grimble wrote:
Since the first posts, I've had to replace the power supply and one of
my raid disks on that machine. Unfortunately, neither action was
relevant to the problem. The boot process doesn't reach the user logon
screen, and Xorg.0.log contains a couple of messages :
timer event0 debounce......system is too slow.
I've swapped over the mouse and keyboard without success.
However I can boot into level 3, so all my background scripts and
backups are being executed OK.
The "too slow" message also appeared in the Xorg log of a System Rescue
session. Google posts seem to involve libinput, but I don't seem to have
that installed on my system.

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 21/10/21 01:21, Grimble wrote:
> On 05/10/2021 14:38, Grimble wrote:
> Since the first posts, I've had to replace the power supply and one of
> my raid disks on that machine. Unfortunately, neither action was
> relevant to the problem. The boot process doesn't reach the user logon
> screen, and Xorg.0.log contains a couple of messages :
> timer event0 debounce......system is too slow.
> I've swapped over the mouse and keyboard without success.
> However I can boot into level 3, so all my background scripts and
> backups are being executed OK.
> The "too slow" message also appeared in the Xorg log of a System Rescue
> session. Google posts seem to involve libinput, but I don't seem to have
> that installed on my system.
>
>
I think that you can forget about mysql being the problem. I have never
had a bootup stopped for that reason. The "system too slow" sounds like
a better clue, but what is slowing it down? I have had KDE fail to
start because some permissions in /var were wrong, but yours sounds
different.

A couple of days ago, I had a bug fixed by my usual, well-tried,
"upgrade" reinstall. Since you are going down the upgrade path, nothing
seems to happen until the bootloader is reinstalled, but that process
corrects any quirky errors like yours. If it is something like a wrong
file ownership or permission, that may be enough to fix it.

On Wed, 20 Oct 2021 10:21:08 -0400, Grimble <grimble@nomail.afraid.org> wrote:

> On 05/10/2021 14:38, Grimble wrote:
> Since the first posts, I've had to replace the power supply and one of
> my raid disks on that machine. Unfortunately, neither action was
> relevant to the problem. The boot process doesn't reach the user logon
> screen, and Xorg.0.log contains a couple of messages :
> timer event0 debounce......system is too slow.
> I've swapped over the mouse and keyboard without success.
> However I can boot into level 3, so all my background scripts and
> backups are being executed OK.
> The "too slow" message also appeared in the Xorg log of a System Rescue
> session. Google posts seem to involve libinput, but I don't seem to have
> that installed on my system.

Looks like the most common cause is problems with the nvidia driver for that
particular video card.

Try switching to the nouveau if currently using the nvidia driver, or if currently
using the nouveau driver, switching to the nvidia driver. If neither of those
work, try the vesa driver.

Regards, Dave Hodgins

--
Change dwhodgins@nomail.afraid.org to davidwhodgins@teksavvy.com for
email replies.

On 20/10/2021 18:11, David W. Hodgins wrote:
> On Wed, 20 Oct 2021 10:21:08 -0400, Grimble <grimble@nomail.afraid.org>
> wrote:
>
>> On 05/10/2021 14:38, Grimble wrote:
>> Since the first posts, I've had to replace the power supply and one of
>> my raid disks on that machine. Unfortunately, neither action was
>> relevant to the problem. The boot process doesn't reach the user logon
>> screen, and Xorg.0.log contains a couple of messages :
>> timer event0 debounce......system is too slow.
>> I've swapped over the mouse and keyboard without success.
>> However I can boot into level 3, so all my background scripts and
>> backups are being executed OK.
>> The "too slow" message also appeared in the Xorg log of a System Rescue
>> session. Google posts seem to involve libinput, but I don't seem to have
>> that installed on my system.
>
> Looks like the most common cause is problems with the nvidia driver for
> that
> particular video card.
>
> Try switching to the nouveau if currently using the nvidia driver, or if
> currently
> using the nouveau driver, switching to the nvidia driver. If neither of
> those
> work, try the vesa driver.
>
> Regards, Dave Hodgins
>
Dave, the video device is reported by lspci as
AMD/ATI Cedar RADEON HD 5400/6300/7300 Series.
drakx11 only gives me the option RADEON HD 5000 to HD6300 to give a
"working" test. If I select VESA, vesa or the other RADEON HD5000 entry,
it gives me an EE error.
/var/log/Xorg.0.log.old contains no error messages (ie the Too slow
messages have gone)
/var/log/Xorg.0.log is empty

(Other errors reported earlier were corrected with minor changes to
permissions/ownership)

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.70-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 30/10/21 01:58, Grimble wrote:

> Dave, the video device is reported by lspci as
> AMD/ATI Cedar RADEON HD 5400/6300/7300 Series.
> drakx11 only gives me the option RADEON HD 5000 to HD6300 to give a
> "working" test. If I select VESA, vesa or the other RADEON HD5000 entry,
> it gives me an EE error.
> /var/log/Xorg.0.log.old contains no error messages (ie the Too slow
> messages have gone)
> /var/log/Xorg.0.log is empty
>
> (Other errors reported earlier were corrected with minor changes to
> permissions/ownership)
>

Can you boot a live version of the OS
That would isolate the faults to your configuration somewhere
My version is much as yours except for the Nvidia driver
--
faeychild
Running plasmashell 5.20.4 on 5.10.75-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 30/10/2021 22:14, faeychild wrote:
> On 30/10/21 01:58, Grimble wrote:
>
>> Dave, the video device is reported by lspci as
>> AMD/ATI Cedar RADEON HD 5400/6300/7300 Series.
>> drakx11 only gives me the option RADEON HD 5000 to HD6300 to give a
>> "working" test. If I select VESA, vesa or the other RADEON HD5000
>> entry, it gives me an EE error.
>> /var/log/Xorg.0.log.old contains no error messages (ie the Too slow
>> messages have gone)
>> /var/log/Xorg.0.log is empty
>>
>> (Other errors reported earlier were corrected with minor changes to
>> permissions/ownership)
>>
>
>
> Can you boot a live version of the OS
> That would isolate the faults to your configuration somewhere
>   My version is much as yours except for the Nvidia driver
Thank you for the suggestion. I have now got around to booting the live
version, with no apparent problems.
So I am no further forward in working out why the boot process doesn't
end up with a log-on screen. Live version works, System Rescue works,
startx as root works from level 3;
Do I actually have a Display (Window) Manager defined for my userid?
Presumably they are listed per user; where?

--
Grimble
Machine 'Haydn' running Plasma 5.20.4 on 5.10.78-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64

On 11/13/21 08:22, Grimble wrote:
> On 30/10/2021 22:14, faeychild wrote:
>> On 30/10/21 01:58, Grimble wrote:
>>
>>> Dave, the video device is reported by lspci as
>>> AMD/ATI Cedar RADEON HD 5400/6300/7300 Series.
>>> drakx11 only gives me the option RADEON HD 5000 to HD6300 to give a
>>> "working" test. If I select VESA, vesa or the other RADEON HD5000
>>> entry, it gives me an EE error.
>>> /var/log/Xorg.0.log.old contains no error messages (ie the Too slow
>>> messages have gone)
>>> /var/log/Xorg.0.log is empty
>>>
>>> (Other errors reported earlier were corrected with minor changes to
>>> permissions/ownership)
>>>
>>
>>
>> Can you boot a live version of the OS
>> That would isolate the faults to your configuration somewhere
>>    My version is much as yours except for the Nvidia driver
> Thank you for the suggestion. I have now got around to booting the live
> version, with no apparent problems.
> So I am no further forward in working out why the boot process doesn't
> end up with a log-on screen. Live version works, System Rescue works,
> startx as root works from level 3;
> Do I actually have a Display (Window) Manager defined for my userid?
> Presumably they are listed per user; where?
>
Over here in PCLinuxOS we have a script called simply "Redo
Bootloader" which might help. Maybe one of the Mageia wizards
can take a look at it and move it over to your repositories
if it seems useful.

bliss-- brought to you by the power and ease of PCLinuxOS and a minor
case of Hypergraphia

--
bliss dash SF 4 ever at dslextreme dot com

On 14/11/21 03:22, Grimble wrote:

>> Can you boot a live version of the OS
>> That would isolate the faults to your configuration somewhere
>>    My version is much as yours except for the Nvidia driver
> Thank you for the suggestion. I have now got around to booting the live
> version, with no apparent problems.
> So I am no further forward in working out why the boot process doesn't
> end up with a log-on screen. Live version works, System Rescue works,
> startx as root works from level 3;
> Do I actually have a Display (Window) Manager defined for my userid?
> Presumably they are listed per user; where?
>

About now is where the Bit Twister steps in with a solution.
He has been fairly quiet recently. I hope he is well.

Some snippets from Bit Twisters posts

************

Ok, there are a few methods to resolve the problem. Boot runlevel 3,
log in as root, and run /usr/bin/XFdrake.

That would run the same configuration program you used via mcc.
Since gui is not running (runlevel 5) you will be navigating the
ncurses menues using tab, space bar, arrow keys, and enter depending
on where/what you are doing.

To get into runlevel 3, hit e at the grub menu, use arrow keys to get
to the end of the kernel boot line. add a space 3 ' 3' without the quotes.
then Ctrl x to start the boot, after the system completes init, you
can hit the Return/Enter key and you should see a command line prompt
for user login.

enter root Return
root_pw_here Return

XFdrake Return
>

Did a little research, updated my brain book, Commands to set DM and
login greeter for Xfce

$ uh _set_default_runlevels_5_display_manager_greeter_
<snipped above keyword string from the following lines>
mcc->Boot->Set up display manager (drakdm)
cat /etc/sysconfig/desktop
grep -Ril "Alias=display-manager.service"
/usr/lib/systemd/system/*.service
systemctl disable display-manager.service
systemctl enable lightdm.service
systemctl set-default graphical.target
systemctl status display-manager.service | grep -E "PID|nodaemon"

As a result of doing the above, I have the following:

$ cat /etc/sysconfig/desktop
DISPLAYMANAGER=lightdm

$ grep -Ril "Alias=display-manager.service"
/usr/lib/systemd/system/*.service
/usr/lib/systemd/system/lightdm.service
/usr/lib/systemd/system/xdm.service

$ systemctl status display-manager.service | grep -E "PID|nodaemon"
Main PID: 1065 (lightdm)
├─1065 /usr/sbin/lightdm -nodaemon

$ env | grep xdg | sort
XDG_CONFIG_DIRS=/etc/xdg
XDG_CURRENT_DESKTOP=XFCE
XDG_DATA_DIRS=/usr/local/share:/usr/share
XDG_GREETER_DATA_DIR=/var/lib/lightdm-data/bittwister
XDG_MENU_PREFIX=xfce-
XDG_RUNTIME_DIR=/run/user/1500
XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0
XDG_SEAT=seat0
XDG_SESSION_DESKTOP=xfce
XDG_SESSION_ID=2
XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session0
XDG_SESSION_TYPE=x11
XDG_VTNR=1

It may give you a clue
or just confuse the hell out of you :-)

--
faeychild
Running plasmashell 5.20.4 on 5.10.75-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On Sun, 14 Nov 2021 08:16:53 +1100, faeychild wrote:
> On 14/11/21 03:22, Grimble wrote:
>
>>> Can you boot a live version of the OS
>>> That would isolate the faults to your configuration somewhere
>>>    My version is much as yours except for the Nvidia driver
>> Thank you for the suggestion. I have now got around to booting the live
>> version, with no apparent problems.
>> So I am no further forward in working out why the boot process doesn't
>> end up with a log-on screen. Live version works, System Rescue works,
>> startx as root works from level 3;
>> Do I actually have a Display (Window) Manager defined for my userid?
>> Presumably they are listed per user; where?
>>
>

I have seen a problem where you can not gui login because of files
owned by root or not owned by user in user's account.

> About now is where the Bit Twister steps in with a solution.
> He has been fairly quiet recently. I hope he is well.

Getting better. Tripped in the yard and cracked a bone in right arm two
months ago. Having to hit Alt and use mouse roller to magnify screen for
reading, which works on/in Xfce DE, and typing, navigation and mouse
clicks with left hand sucks

Also getting over last eye cataract surgery last week. Have about a month
left to getting a prescription for reading glasses.

Been quiet since I had no definitive knowledge for problem solutions for
any posts.

> Some snippets from Bit Twisters posts
>
> ************
>
> Ok, there are a few methods to resolve the problem. Boot runlevel 3,
> log in as root, and run /usr/bin/XFdrake.
>
> That would run the same configuration program you used via mcc.
> Since gui is not running (runlevel 5) you will be navigating the
> ncurses menues using tab, space bar, arrow keys, and enter depending
> on where/what you are doing.
>
> To get into runlevel 3, hit e at the grub menu, use arrow keys to get
> to the end of the kernel boot line. add a space 3 ' 3' without the quotes.
> then Ctrl x to start the boot, after the system completes init, you
> can hit the Return/Enter key and you should see a command line prompt
> for user login.
>
> enter root Return
> root_pw_here Return
>
> XFdrake Return
> >
>
>
>
>
> Did a little research, updated my brain book, Commands to set DM and
> login greeter for Xfce
>
> $ uh _set_default_runlevels_5_display_manager_greeter_
> <snipped above keyword string from the following lines>
> mcc->Boot->Set up display manager (drakdm)
> cat /etc/sysconfig/desktop
> grep -Ril "Alias=display-manager.service"
> /usr/lib/systemd/system/*.service
> systemctl disable display-manager.service
> systemctl enable lightdm.service
> systemctl set-default graphical.target
> systemctl status display-manager.service | grep -E "PID|nodaemon"
>
>
> As a result of doing the above, I have the following:
>
>
>
> $ cat /etc/sysconfig/desktop
> DISPLAYMANAGER=lightdm
>
> $ grep -Ril "Alias=display-manager.service"
> /usr/lib/systemd/system/*.service
> /usr/lib/systemd/system/lightdm.service
> /usr/lib/systemd/system/xdm.service
>
> $ systemctl status display-manager.service | grep -E "PID|nodaemon"
> Main PID: 1065 (lightdm)
> ├─1065 /usr/sbin/lightdm -nodaemon
>
> $ env | grep xdg | sort
> XDG_CONFIG_DIRS=/etc/xdg
> XDG_CURRENT_DESKTOP=XFCE

You need to change your notes to have grep -i for above to work.
It worked/works for me because of my alias.
]$ alias grep
alias grep='grep --color --ignore-case'

On Sun, 14 Nov 2021 08:16:53 +1100, faeychild wrote:

--
faeychild
Running plasmashell 5.20.4 on 5.10.75-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

Hmmm, your release is getting a bit old. For example:

]$ uname -r
5.10.78-desktop-1.mga8

On 14/11/21 15:21, Bit Twister wrote:
> On Sun, 14 Nov 2021 08:16:53 +1100, faeychild wrote:
>> On 14/11/21 03:22, Grimble wrote:
>>
>>>> Can you boot a live version of the OS
>>>> That would isolate the faults to your configuration somewhere
>>>>    My version is much as yours except for the Nvidia driver
>>> Thank you for the suggestion. I have now got around to booting the live
>>> version, with no apparent problems.
>>> So I am no further forward in working out why the boot process doesn't
>>> end up with a log-on screen. Live version works, System Rescue works,
>>> startx as root works from level 3;
>>> Do I actually have a Display (Window) Manager defined for my userid?
>>> Presumably they are listed per user; where?
>>>
>>
>
> I have seen a problem where you can not gui login because of files
> owned by root or not owned by user in user's account.

Of course !! The solution you never think to try at the time

>
>> About now is where the Bit Twister steps in with a solution.
>> He has been fairly quiet recently. I hope he is well.
>
>
> Getting better. Tripped in the yard and cracked a bone in right arm two
> months ago. Having to hit Alt and use mouse roller to magnify screen for
> reading, which works on/in Xfce DE, and typing, navigation and mouse
> clicks with left hand sucks
>

Fortunately I still bounce when I fall but I notice I'm getting slower
Squatting is becoming a problem also, knees hurt- especially getting up
again

>> $ env | grep xdg | sort
>> XDG_CONFIG_DIRS=/etc/xdg
>> XDG_CURRENT_DESKTOP=XFCE
>
> You need to change your notes to have grep -i for above to work.
> It worked/works for me because of my alias.
> ]$ alias grep
> alias grep='grep --color --ignore-case'
>
>

I always end up running down a rabbit hole with you Bits

OK!! so here I go.

[faeychild@unimatrix ~]$ alias grep
alias grep='grep --color'

Well Half there

After a search I found that I don't have that alias listed in ~/.bash
profile/rc I don't have any aliases listed

So now I have cause to wonder where it is listed along with the other
aliases that are also not in ~/.bash profile/rc not in /etc/bashrc

I don't have a ~/.bash_aliases either so where are my aliases stored

[faeychild@unimatrix ~]$ ls -la .bash*
-rw-r--r-- 1 faeychild faeychild 387 Dec 16 2020 .bash_completion
-rw------- 1 faeychild faeychild 24886 Nov 14 20:12 .bash_history
-rw-r--r-- 1 faeychild faeychild 24 Dec 31 2020 .bash_logout
-rw-r--r-- 1 faeychild faeychild 402 May 14 2021 .bash_profile
-rw-r--r-- 1 faeychild faeychild 124 Dec 31 2020 .bashrc

--
faeychild
Running plasmashell 5.20.4 on 5.10.78-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

On 14/11/21 15:31, Bit Twister wrote:
> On Sun, 14 Nov 2021 08:16:53 +1100, faeychild wrote:
>
> --
> faeychild
> Running plasmashell 5.20.4 on 5.10.75-desktop-1.mga8 kernel.
> Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso
>
> Hmmm, your release is getting a bit old. For example:
>
> ]$ uname -r
> 5.10.78-desktop-1.mga8
>

updated this morning. I'm not quite on the ball Bits :-)

And now I am wandering around mumbling to myself about aliases.
It's not looking good

--
faeychild
Running plasmashell 5.20.4 on 5.10.78-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso

Bit Twister wrote on 14/11/21 3:21 pm:

> Getting better. Tripped in the yard and cracked a bone in right arm two
> months ago. Having to hit Alt and use mouse roller to magnify screen for
> reading, which works on/in Xfce DE, and typing, navigation and mouse
> clicks with left hand sucks

Almost forty-five years of left-handed, single handed (due to car
accident), and my typing hasn't gotten much better! ;-)

One advantage though!! People are often told when working on electrical
equipment, put one hand in your pocket! I don't have to worry about
that! ;-)

However, at one time I was working on a High Powered High Frequency
Transmitter .... i turned off the H.T. I turned off the L.T. I walked
around the side of the transmitter. I removed two large metal panels. I
reached into the PA to make an adjustment, my left arm touched a point
on a 4,000 V.D.C. line .... and my (non-existent) right hand reached in
to pull my left arm free!

Well, that's what my mind told me!! ;-P
--
Daniel

On Sun, 14 Nov 2021 20:17:18 +1100, faeychild wrote:
> On 14
>
>
>>> $ env | grep xdg | sort
>>> XDG_CONFIG_DIRS=/etc/xdg
>>> XDG_CURRENT_DESKTOP=XFCE
>>
>> You need to change your notes to have grep -i for above to work.
>> It worked/works for me because of my alias.
>> ]$ alias grep
>> alias grep='grep --color --ignore-case'
>>
>>
>
> I always end up running down a rabbit hole with you Bits
>
> OK!! so here I go.
>
> [faeychild@unimatrix ~]$ alias grep
> alias grep='grep --color'
>
> Well Half there
>
> After a search I found that I don't have that alias listed in ~/.bash
> profile/rc I don't have any aliases listed

you can find other aliases in /etc/profile.d/

try grep grep= /etc/profile.d/*

Keep in mind changes to files in that directory can be wipped out
during updates.

> So now I have cause to wonder where it is listed along with the other
> aliases that are also not in ~/.bash profile/rc not in /etc/bashrc
>
> I don't have a ~/.bash_aliases either so where are my aliases stored
>
> [faeychild@unimatrix ~]$ ls -la .bash*
> -rw-r--r-- 1 faeychild faeychild 387 Dec 16 2020 .bash_completion
> -rw------- 1 faeychild faeychild 24886 Nov 14 20:12 .bash_history
> -rw-r--r-- 1 faeychild faeychild 24 Dec 31 2020 .bash_logout
> -rw-r--r-- 1 faeychild faeychild 402 May 14 2021 .bash_profile
> -rw-r--r-- 1 faeychild faeychild 124 Dec 31 2020 .bashrc

~/.bashrc is where a user is to make their own aliases.

On Sat, 13 Nov 2021 11:22:59 -0500, Grimble <grimble@nomail.afraid.org> wrote:
> Do I actually have a Display (Window) Manager defined for my userid?
> Presumably they are listed per user; where?

Default for users who haven't specified one is in /etc/sysconfig/desktop. I have
# cat /etc/sysconfig/desktop
DESKTOP=Plasma
DISPLAYMANAGER=lightdm

If the DESKTOP is not specified, it's set by the dm.

Per user overrides, if wanted, go in ~/.desktop. I currently have ...
$ cat ~/.desktop
DESKTOP=Plasma

Regards, Dave Hodgins

On 14/11/21 22:14, Bit Twister wrote:

>
> you can find other aliases in /etc/profile.d/
>
> try grep grep= /etc/profile.d/*
>
>
> Keep in mind changes to files in that directory can be wipped out
> during updates.

Ah Ha

[faeychild@unimatrix ~]$ grep grep= /etc/profile.d/*
/etc/profile.d/60alias.sh:alias grep="grep --color" # colored
grep by default
/etc/profile.d/60alias.sh:alias egrep="egrep --color" # colored
grep by default
/etc/profile.d/60alias.sh:alias fgrep="fgrep --color" # colored
grep by default
[faeychild@unimatrix ~]$

Google didn't reveal that location. All the others but not that one

regards

--
faeychild
Running plasmashell 5.20.4 on 5.10.78-desktop-1.mga8 kernel.
Mageia release 8 (Official) for x86_64 installed via Mageia-8-x86_64-DVD.iso