KDE Plasma, boot errors

alex4buba · 10-21-2023, 04:45 PM

My new HP Probook died and I was forced to reinstall KDE and all my programs, about 2 days wasted, good I have a daily backup.

But, it started with several indications that something is wrong, I can experience now some of that again. During boot time, I can see several flashes of errors, but they go too fast to see what they are.

Where is the log of the boot process that I can search through to see what those errors are?

Thanks for any help

mrmazda · 10-21-2023, 05:34 PM

Most of the boot messages appear in dmesg, which you'll want to use less to sift through. Some may appear using sudo journalctl. /var/log/sddm.log also may have clues. If you want to see the boot messages during boot you have several options. Hitting the ESC key should clear the bootsplash. At the Grub menu striking the E key and removing quiet and splash=silent before proceeding should produce most messages for that one boot, but you may need also appending one of the following to the end of the linu line: noplymouth, plymouth=0 or plymouth.enable=0. Uninstalling plymouth will disable GUI boot until the login greeter starts. Permanent quiet & splash=silent removal and/or plymouth disabling is done in /etc/default/grub and followed by regenerating grub.cfg.

michaelk · 10-21-2023, 05:44 PM

Look at the output of the command:
journalctl -b

alex4buba · 10-21-2023, 05:58 PM

Quote:

Originally Posted by mrmazda

Most of the boot messages appear in dmesg, which you'll want to use less to sift through. Some may appear using sudo journalctl. /var/log/sddm.log also may have clues. If you want to see the boot messages during boot you have several options. Hitting the ESC key should clear the bootsplash. At the Grub menu striking the E key and removing quiet and splash=silent before proceeding should produce most messages for that one boot, but you may need also appending one of the following to the end of the linu line: noplymouth, plymouth=0 or plymouth.enable=0. Uninstalling plymouth will disable GUI boot until the login greeter starts. Permanent quiet & splash=silent removal and/or plymouth disabling is done in /etc/default/grub and followed by regenerating grub.cfg.

Executing sudo journalctl, I get this output:

Code:

Oct 21 18:02:23 alexe kernel: microcode: microcode updated early to revision 0x4119, date = 2023-06-06
Oct 21 18:02:23 alexe kernel: Linux version 6.2.0-33-generic (buildd@lcy02-amd64-073) (x86_64-linux-gnu-gcc-11 (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #33~22.0>
Oct 21 18:02:23 alexe kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-6.2.0-33-generic root=UUID=d4b05b1e-24b1-4aef-a262-a147cb30b886 ro quiet splash vt.handoff=7
Oct 21 18:02:23 alexe kernel: KERNEL supported cpus:
Oct 21 18:02:23 alexe kernel:   Intel GenuineIntel
Oct 21 18:02:23 alexe kernel:   AMD AuthenticAMD
Oct 21 18:02:23 alexe kernel:   Hygon HygonGenuine
Oct 21 18:02:23 alexe kernel:   Centaur CentaurHauls
Oct 21 18:02:23 alexe kernel:   zhaoxin   Shanghai  
Oct 21 18:02:23 alexe kernel: BIOS-provided physical RAM map:
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009efff] usable
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x000000000009f000-0x00000000000fffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x0000000000100000-0x00000000698b0fff] usable
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x00000000698b1000-0x000000006f913fff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x000000006f914000-0x000000006fb13fff] ACPI NVS
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x000000006fb14000-0x000000006fbfefff] ACPI data
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x000000006fbff000-0x000000006fbfffff] usable
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x000000006fc00000-0x0000000075ffffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x0000000077400000-0x00000000777fffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x0000000078000000-0x00000000807fffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x00000000c0000000-0x00000000cfffffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x00000000fed20000-0x00000000fed7ffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Oct 21 18:02:23 alexe kernel: BIOS-e820: [mem 0x0000000100000000-0x000000087f7fffff] usable
Oct 21 18:02:23 alexe kernel: NX (Execute Disable) protection: active
Oct 21 18:02:23 alexe kernel: efi: EFI v2.70 by HP
Oct 21 18:02:23 alexe kernel: efi: ACPI=0x6fbfe000 ACPI 2.0=0x6fbfe014 TPMFinalLog=0x6fa90000 SMBIOS=0x6a024000 ESRT=0x6a022198 MEMATTR=0x62f8a018 MOKvar=0x6a07a000 RNG=0x6fb41018 TPMEventLog=0x5c8>
lines 1-27

But, none of the above looks to me like an error?

Then, I scrolled further down, found some lines in blue, yellow, red, white... attaching the file with the first 1000 lines...

Sorry, but I have no idea what is dmesg or any of the othersuggestions...

Thank you

mrmazda · 10-21-2023, 08:07 PM

What exactly are the symptoms that lead you to post here?

Your log shows:
708 lines containing string failed (mostly from Dolphin)
76 lines containing string plasma (mostly from plasmashell)
54 lines containing string error

This log looks like only a tail end, not complete from startup.

Dmesg is a command that shows what the kernel has found fit to report. Redirect it to a file for sharing. Pipe it to less for simple viewing. If you find Xorg.0.log in /var/log/ or ~/.local/share/xorg/ and upload it we may be able to spot more clues. ~/.xsession-errors should also contain clues and/or outright errors.

alex4buba · 10-21-2023, 09:47 PM

Quote:

Originally Posted by mrmazda

What exactly are the symptoms that lead you to post here?

Your log shows:
708 lines containing string failed (mostly from Dolphin)
76 lines containing string plasma (mostly from plasmashell)
54 lines containing string error

This log looks like only a tail end, not complete from startup.

Dmesg is a command that shows what the kernel has found fit to report. Redirect it to a file for sharing. Pipe it to less for simple viewing. If you find Xorg.0.log in /var/log/ or ~/.local/share/xorg/ and upload it we may be able to spot more clues. ~/.xsession-errors should also contain clues and/or outright errors.

I am a very basic user of Linux and most of the things you suggested went over my head.

1) I looked in sddm.log, it is EMPTY
2) I found Xorg.0.log and attached it
3) No idea how to use "less", please instruct me

I hope you can make some sense out of any of that.

Many thanks

mrmazda · 10-21-2023, 11:28 PM

When you don't know how to use a command, use the man command on it first. That way you shouldn't need to ask for help with it:

Code:

man less

The log seems to suggest possible input device trouble with touchpad and/or perhaps a joystick?: FeiYing Model SAILI Simulator - XTR5.5+G2+FMS Controller. This I suppose could be caused by Plasma trouble. It may be something running an extra updating session might clear up.

I don't have any Plasma-specific ideas except the clearing the cache sometimes straightens out its foibles. To do that, log out of Plasma and log in some other session type, e.g. on a vtty (Ctrl-Alt-F3 to switch to it; Alt-F7, Alt-F1 or possibly Alt-F2 to return to GUI) or some DE session other than Plasma. Then delete the entire content of ~/.cache/ before logging back into Plasma.