Kbuntu slow booting desktop and taskbar

Johng · 09-01-2022, 11:10 PM

Booting Kbuntu 22.04.1 LTS used to be quite quick, but is now taking longer, and staggered, ie the desktop, desktop folder and taskbar do not appear simutaneously, sometimes the taskbar can be seconds later.

I ran a command I found on a forum with title "Taskbar (KDE) shows after a long delay since update")

Code:

$ sudo journalctl -b -1 | egrep kglobalaccel
Sep 02 09:37:21 john-Z87-D3HP dbus-daemon[1107]: [session uid=1000 pid=1107] Activating via systemd: service name='org.kde.kglobalaccel' unit='plasma-kglobalaccel.service' requested by ':1.14' (uid=1000 pid=1325 comm="/usr/bin/kded5 " label="unconfined")
Sep 02 09:37:21 john-Z87-D3HP dbus-daemon[1107]: [session uid=1000 pid=1107] Successfully activated service 'org.kde.kglobalaccel'
Sep 02 13:40:22 john-Z87-D3HP kglobalaccel5[1339]: The X11 connection broke (error 1). Did the X11 server die?
Sep 02 13:40:22 john-Z87-D3HP systemd[1075]: plasma-kglobalaccel.service: Main process exited, code=exited, status=1/FAILURE
Sep 02 13:40:22 john-Z87-D3HP systemd[1075]: plasma-kglobalaccel.service: Failed with result 'exit-code'.

What does this all mean, and how do I restore the booting process?

pan64 · 09-02-2022, 12:26 AM

Something went wrong. Did you change anything in your system? You need to check the log of Xorg (X11 server). Why is it died?

Johng · 09-02-2022, 03:57 AM

Thank you pan64

I have not intentionally changed anything other than apply regular updates. I have looked at Xlog.0.log and see no errors.

I rebooted the system and pressed esc key to look for clues. This had the effect of almost instant boot time, except the taskbar, which did not appear until six seconds after the desktop appeared.

I then looked at dsmeg, where there were two abnormalities:

Quote:

[ 3.574933] at24 0-0051: supply vcc not found, using dummy regulator
[ 3.575515] at24 0-0051: 256 byte spd EEPROM, read-only
[ 3.578168] at24 0-0053: supply vcc not found, using dummy regulator
[ 3.584138] at24 0-0053: 256 byte spd EEPROM, read-only

Quote:

[ 0.999104] ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\PMIO) (20210730/utaddress-204)
[ 0.999111] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 0.999114] ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.999117] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 0.999118] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.999120] ACPI Warning: SystemIO range 0x0000000000001C30-0x0000000000001C3F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.999122] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 0.999123] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001C3F (\GPRL) (20210730/utaddress-204)
[ 0.999126] ACPI Warning: SystemIO range 0x0000000000001C00-0x0000000000001C2F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\GPR) (20210730/utaddress-204)
[ 0.999128] ACPI: OSL: Resource conflict; ACPI support missing from driver?
[ 0.999128] lpc_ich: Resource conflict(s) found affecting gpio_ich
[ 1.001339] e1000e: Intel(R) PRO/1000 Network Driver

Does any of this help?

and, have posted this in the wrong forum??