[Workaround]Slow restart and shutdown in Debian 12, KDE Plasma

[GroudonandKyogre]

Hi, I hope that you are doing well.
Now, I was just casually using my system one day, and when I restart my computer to boot into windows, my computer showed some job@1000 error and a timer which kept increasing till 1min28sec, I don't exactly remember when this happened but it has been a while, I don't know why, but my system used to show which services are starting and turning off when I turn on or off my system. But now it doesn't. Now, it just shows a few lines about drive and amount of blocks or so, this error has happened occasionaly when restarting and turning my system on.
Also yesterday when shutting it down, I had a glance that it showed some watchdog error, there were two lines, however the system shut down instantly.
Here is my inxi -Fxxxxz output-

Code: Select all

System:
  Kernel: 6.1.0-28-amd64 arch: x86_64 bits: 64 compiler: gcc v: 12.2.0
    Desktop: KDE Plasma v: 5.27.5 tk: Qt v: 5.15.8 wm: kwin_x11 vt: 7 dm: SDDM
    Distro: Debian GNU/Linux 12 (bookworm)
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required>
    BIOS: Award v: FI date: 08/09/2010
CPU:
  Info: quad core model: Intel Core2 Quad Q9550 bits: 64 type: MCP
    smt: <unsupported> arch: Penryn rev: A cache: L1: 256 KiB L2: 12 MiB
  Speed (MHz): avg: 2833 min/max: N/A cores: 1: 2833 2: 2833 3: 2833 4: 2833
    bogomips: 22667
  Flags: ht lm nx pae sse sse2 sse3 sse4_1 ssse3 vmx
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02
    arch: Kepler pcie: speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:0fc8 class-ID: 0300
  Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9
    compositor: kwin_x11 driver: X: loaded: nvidia gpu: nvidia display-ID: :0
    screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 101 s-size: 483x261mm (19.02x10.28")
    s-diag: 549mm (21.61")
  Monitor-1: HDMI-0 res: 1920x1080 hz: 100 dpi: 102
    size: 480x260mm (18.9x10.24") diag: 546mm (21.49") modes: N/A
  API: OpenGL v: 4.6.0 NVIDIA 470.256.02 renderer: NVIDIA GeForce GT
    740/PCIe/SSE2 direct-render: Yes
Audio:
  Device-1: Intel NM10/ICH7 Family High Definition Audio
    vendor: Gigabyte GA-D525TUD driver: snd_hda_intel v: kernel bus-ID: 00:1b.0
    chip-ID: 8086:27d8 class-ID: 0403
  Device-2: NVIDIA GK107 HDMI Audio driver: snd_hda_intel v: kernel pcie:
    speed: 2.5 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0e1b class-ID: 0403
  API: ALSA v: k6.1.0-28-amd64 status: kernel-api
  Server-1: PulseAudio v: 16.1 status: active
Network:
  Device-1: Qualcomm Atheros AR8131 Gigabit Ethernet
    vendor: Gigabyte GA-G31M-ES2L driver: atl1c v: kernel pcie: speed: 2.5 GT/s
    lanes: 1 port: bf00 bus-ID: 03:00.0 chip-ID: 1969:1063 class-ID: 0200
  IF: enp3s0 state: down mac: <filter>
  Device-2: Ralink RT5370 Wireless Adapter type: USB driver: rt2800usb
    bus-ID: 5-5:2 chip-ID: 148f:5370 class-ID: 0000 serial: <filter>
  IF: wlxc83a35c9505a state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 20.99 GiB (1.5%)
  ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
    speed: <unknown> type: HDD rpm: 7200 serial: <filter> rev: A7C0 scheme: MBR
  ID-2: /dev/sdb vendor: A-Data model: SU800 size: 476.94 GiB
    speed: <unknown> type: SSD serial: <filter> rev: 8B scheme: MBR
Partition:
  ID-1: / size: 173.1 GiB used: 14.98 GiB (8.7%) fs: ext4 dev: /dev/sdb1
  ID-2: /home size: 14.66 GiB used: 6.01 GiB (41.0%) fs: ext4 dev: /dev/sdb6
Swap:
  ID-1: swap-1 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sdb3
Sensors:
  System Temperatures: cpu: 51.0 C mobo: N/A gpu: nvidia temp: 38 C
  Fan Speeds (RPM): N/A gpu: nvidia fan: 30%
Info:
  Processes: 160 Uptime: 13m wakeups: 0 Memory: 3.82 GiB
  used: 1.79 GiB (46.7%) Init: systemd v: 252 target: graphical (5)
  default: graphical Compilers: gcc: 12.2.0 alt: 12 Packages: pm: dpkg
  pkgs: 1656 Shell: Bash v: 5.2.15 running-in: konsole inxi: 3.3.26
ak@debian:~/Downloads$ 

Thanks in advance,
GK

[Hallvor]

Please post the output (as root or sudo) of

Code: Select all

systemd-analyze

and

Code: Select all

systemd-analyze blame

[GroudonandKyogre]

Here is the output of systemd-analyze as root-

Code: Select all

ak@debian:~$ sudo systemd-analyze
[sudo] password for ak: 
Startup finished in 2.536s (kernel) + 7.558s (userspace) = 10.095s 
graphical.target reached after 6.935s in userspace.

Here is the output of systemd-analyze blame as root-

Code: Select all

ak@debian:~$ sudo systemd-analyze blame
6.119s systemd-modules-load.service
1.262s systemd-timesyncd.service
 905ms apt-daily.service
 810ms dev-sdb1.device
 591ms ananicy.service
 591ms man-db.service
 475ms systemd-random-seed.service
 425ms systemd-journal-flush.service
 312ms systemd-udevd.service
 307ms user@1000.service
 257ms udisks2.service
 207ms accounts-daemon.service
 198ms power-profiles-daemon.service
 157ms systemd-udev-trigger.service
 155ms avahi-daemon.service
 155ms networking.service
 145ms dbus.service
 141ms systemd-logind.service
 131ms keyboard-setup.service
 129ms systemd-journald.service
 114ms systemd-fsck@dev-disk-by\x2duuid-ccd6f42f\x2d52b2\x2d4baf\x2d8b45\x2ddeaca7bf1ffb.service
 104ms zramswap.service
  86ms apparmor.service
  83ms modprobe@drm.service
  68ms upower.service
  67ms e2scrub_reap.service
  62ms systemd-tmpfiles-setup.service
  61ms NetworkManager.service
  54ms nvidia-persistenced.service
  51ms systemd-sysusers.service
  46ms wpa_supplicant.service
  44ms dev-disk-by\x2duuid-83d4174e\x2db7e7\x2d4781\x2d8076\x2d7526da36a14a.swap
  43ms polkit.service
  41ms systemd-remount-fs.service
  39ms systemd-tmpfiles-setup-dev.service
  38ms modprobe@dm_mod.service
  38ms console-setup.service
  36ms ifupdown-pre.service
  31ms modprobe@fuse.service
  26ms systemd-binfmt.service
  25ms dev-hugepages.mount
  24ms dev-mqueue.mount
  23ms lm-sensors.service
  23ms sys-kernel-debug.mount
  23ms modprobe@efi_pstore.service
  22ms sys-kernel-tracing.mount
  20ms modprobe@loop.service
  19ms kmod-static-nodes.service
  19ms modprobe@configfs.service
  18ms home.mount
  16ms systemd-tmpfiles-clean.service
  14ms user-runtime-dir@1000.service
  12ms systemd-update-utmp.service
  11ms proc-sys-fs-binfmt_misc.mount
  10ms systemd-update-utmp-runlevel.service
   8ms systemd-sysctl.service
   8ms systemd-user-sessions.service
   7ms rtkit-daemon.service
   7ms systemd-rfkill.service
   5ms sys-fs-fuse-connections.mount
   3ms sys-kernel-config.mount

[Dai_trying]

I had a similar problem when shutting down/restarting when I had liferea (an rss reader) running in the background, I guessed it was preventing something from stopping and caused the shutdown/restart to stall while it checked or did something (not really sure what was actually happening tbh) but after removing the program or simply making sure it had quit my problem went away, so my advice would be to look for a program that is running that may be preventing shutdown of the system.

Of course this might not be related to your problem but was so similar that I had to mention it. YMMV

NOTE: liferea has an option to keep running when the main window is closed but an icon in the taskbar is shown.

[GroudonandKyogre]

I had a similar problem when shutting down/restarting when I had liferea (an rss reader) running in the background, I guessed it was preventing something from stopping and caused the shutdown/restart to stall while it checked or did something (not really sure what was actually happening tbh) but after removing the program or simply making sure it had quit my problem went away, so my advice would be to look for a program that is running that may be preventing shutdown of the system.

Of course this might not be related to your problem but was so similar that I had to mention it. YMMV

NOTE: liferea has an option to keep running when the main window is closed but an icon in the taskbar is shown.

I have installed kde-plasma with absolutely nothing, I don't even have the default firefox, I am using the version firefox provides. I had installed my KDE plasma with kde-plasma-desktop method. I will try to find any useless program and remove it. Although I have very minimal apps that are installed by me, most are itself embedded.
Thanks for the suggestion and your 2 cents,
GK

[GroudonandKyogre]

I found a workaround to this issue, if you log out and then shutdown it does not give the error anymore.
Also I had did a reinstall.

[LouisR4]

I found a workaround to this issue, if you log out and then shutdown it does not give the error anymore.
Also I had did a reinstall.

Is it really that simple?

[Dai_trying]

I found a workaround to this issue, if you log out and then shutdown it does not give the error anymore.
Also I had did a reinstall.

Logging out may close an application that is causing the actual problem I think, I do not use Plasma so cannot help with narrowing down the culprit.

[GroudonandKyogre]

Some time ago I had checked the journalctl logs and they showed that blue.z (bluetooth) was not working properly or smth.
So I just log out everytime now.

[None1975]

A similar problem was present in Debian 11 with the Mate desktop environment.

If you log out, the computer shuts down very quickly, and if you try to shut it down using the Mate menu, you have to wait a minute and a half for it to shut down. Of course, you can configure everything so that you don't have to wait so long, but this is not a solution.

[GroudonandKyogre]

Maybe this is what is causing the issue? This is an older log-

Code: Select all

Jan 22 20:22:54 debian systemd[655]: plasma-kwin_x11.service: Failed with result 'timeout'.

[None1975]

Maybe this is what is causing the issue? This is an older log-

Maybe so, maybe not. As far as I can tell, this error message is usually the cause.

Code: Select all

A stop job is running for User Manager for UID 1000

[Dai_trying]

Could both messages be linked? I mean the stop job for User manager could be the job that is trying to shutdown plasma-kwin service and fails after a timeout which then releases the shutdown to continue? Not really sure but it's kinda how I read it...

[GroudonandKyogre]

I went through my logs and found something-

Code: Select all

Jan 22 20:22:54 debian systemd[655]: plasma-kwin_x11.service: Failed with result 'timeout'.
Jan 21 20:31:59 debian pulseaudio[695]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jan 21 17:47:40 debian pulseaudio[686]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jan 21 15:04:50 debian systemd[651]: plasma-kwin_x11.service: Failed with result 'timeout'.
Jan 21 14:39:14 debian pulseaudio[667]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jan 21 14:19:50 debian pulseaudio[692]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
Jan 21 13:35:41 debian kded5[811]: kf.bluezqt: PendingCall Error: "Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)"
Jan 21 13:35:41 debian pulseaudio[709]: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

Most of the problem seems to be coming through blue.z (bluetooth) I have it disabled maybe enabling it will help?
Also the problem has not appeared for a few days I now shutdown normally but this issue is definetly not fixed as I did not do anything noticeable.

[None1975]

Could both messages be linked? I mean the stop job for User manager could be the job that is trying to shutdown plasma-kwin service and fails after a timeout which then releases the shutdown to continue? Not really sure but it's kinda how I read it...

Yes.

[GroudonandKyogre]

The problem occured again, with the same error-

Code: Select all

Jan 30 22:06:42 debian systemd[670]: plasma-kwin_x11.service: Failed with result 'timeout'.

What is the problem with this service? I don't understand, this issue used to happen with XFCE too, I think that there is a problem with X11 itself?

[Dai_trying]

The issue would be a different one on Xfce unless you have both DE's installed, Xfce itself does not have plasma-kwin_x11.service. X11 (with Xfce) is working fine for me on several machines.