Started in safe mode, found I can start up the GUi as root (startx), so it must be something with the main user account.
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?
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.
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
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
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
On 05/10/2021 17:51, David W. Hodgins wrote:
On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>Xorg.0.log ends with an EE message:
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
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?
On 05/10/2021 17:51, David W. Hodgins wrote:
On Tue, 05 Oct 2021 12:15:09 -0400, Grimble <grimble@nomail.afraid.org>Xorg.0.log ends with an EE message:
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
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?
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.
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.
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)
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 OSThank you for the suggestion. I have now got around to booting the live version, with no apparent problems.
That would isolate the faults to your configuration somewhere
My version is much as yours except for the Nvidia driver
On 30/10/2021 22:14, faeychild wrote:
On 30/10/21 01:58, Grimble wrote:Thank you for the suggestion. I have now got around to booting the live version, with no apparent problems.
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
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?
Can you boot a live version of the OSThank you for the suggestion. I have now got around to booting the live version, with no apparent problems.
That would isolate the faults to your configuration somewhere
My version is much as yours except for the Nvidia driver
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?
On 14/11/21 03:22, Grimble wrote:
Can you boot a live version of the OSThank you for the suggestion. I have now got around to booting the live
That would isolate the faults to your configuration somewhere
My version is much as yours except for the Nvidia driver
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
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 OSThank you for the suggestion. I have now got around to booting the live
That would isolate the faults to your configuration somewhere
My version is much as yours except for the Nvidia driver
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
$ 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
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
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
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
Do I actually have a Display (Window) Manager defined for my userid? Presumably they are listed per user; where?
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.
Almost forty-five years of left-handed, single handed (due to car
accident), and my typing hasn't gotten much better! ;-)
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 30/10/2021 22:14, faeychild wrote:
On 30/10/21 01:58, Grimble wrote:Thank you for the suggestion. I have now got around to booting the live version, with no apparent problems.
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
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?
On 13/11/2021 16:22, Grimble wrote:
On 30/10/2021 22:14, faeychild wrote:Working through your suggestions (thank you for all your inputs)
On 30/10/21 01:58, Grimble wrote:Thank you for the suggestion. I have now got around to booting the live
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
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?
1. There are no files in ~ that are not owned by me.
2. cat /etc/sysconfig/desktop gives DISPLAYMANAGER=sddm
3. After booting to level 3 and logging on as me, I can su - guest.
startx now sets up a standard user session! From there I can su - graeme
and reach a recognizable version of my usual environment but without my personalisation. !!!!!!!!
Question: /usr/share/X11/dm.d contains entries for sddm.conf, gdm.conf
and xdm.conf. If I give the gdm.conf a lower number than sddm.conf, will
the system attempt to load the Gnome dm?
Working through your suggestions (thank you for all your inputs)
1. There are no files in ~ that are not owned by me.
2. cat /etc/sysconfig/desktop gives DISPLAYMANAGER=sddm
3. After booting to level 3 and logging on as me, I can su - guest.
startx now sets up a standard user session! From there I can su - graeme
and reach a recognizable version of my usual environment but without my personalisation. !!!!!!!!
Question: /usr/share/X11/dm.d contains entries for sddm.conf, gdm.conf
and xdm.conf. If I give the gdm.conf a lower number than sddm.conf, will
the system attempt to load the Gnome dm?
On Thu, 18 Nov 2021 11:17:01 -0500, Grimble <grimble@nomail.afraid.org> wrote:<snip>
In a case like that my recommendation is to boot to run level 3, loginWell, thanks to your tip Dave, I'm back with a working (user) GUI. I'll
as root,
mv /home/normaluser /home/normaluser.old
cp -r /etc/skel /home/normaluser
chown -Rc normaluser:normaluser /home/normaluser
Logout, then in as the normaluser, startx to get to a working desktop. Re-apply
the desired configuration changes using the gui, and mv the data files/directories
from /home/normaluser.old to /home/normaluser
It's a bit of a pain. You must move the .mozilla, and .thunderbird directories
before running either firefox or thunderbird or it will use new subdirectories
with different names, but it's a lot easier then digging through all of the kde or gnome config files trying to figure out which one is no longer compatible.
Regards, Dave Hodgins
Well, thanks to your tip Dave, I'm back with a working (user) GUI. I'll leave working through the many <dot> directories for another day.
Thanks to all for your support/interest.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 296 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 66:51:55 |
| Calls: | 6,654 |
| Files: | 12,200 |
| Messages: | 5,331,946 |