[Workaround(s)]User UID 1000 service stop error at shutdown/restart.

LinuxLover471 · 2025-03-08 16:01:34

Hi, I hope that you are doing fine.

I have used different distros, mint, debian, endeavour and DE's like KDE Plasma, Xfce, Mate. This issue used to appear with all the distros I have ever used, even in arch linux. It doesn't matter what DE I use, it just comes back.

I used to shutdown my system with the powerbutton in the GUI menu, and when I would do that, I would sometimes get hit with a user@1000.service error in debian based distros. But in arch linux I got a similar issue with User UID1000 service error, I don't exactly remember what it was but it was similar to this old error I used to encounter. The timer would go up second by second, in a format like this- 12s/1m 28s. And it would not shutdown before reaching that timer, but sometimes it did before reaching that timer.

I also found a workaround that using sudo shutdown now results in less chances of this happening? Maybe this is a placebo effect?

Another workaround that maybe actually works is logging out and then shutting down. It never ever gave me any errors, but I don't use that very often, so not much proof.

I believe this is an issue with systemd itself as my web research says?

inxi -Fxxxz

System:
  Kernel: 6.13.5-arch1-1 arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc
  Desktop: KDE Plasma v: 6.3.2 tk: Qt v: N/A wm: kwin_x11 vt: 2 dm: SDDM
    Distro: Arch Linux
Machine:
  Type: Desktop Mobo: Gigabyte model: G31M-ES2L serial: <superuser required>
    uuid: <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
Graphics:
  Device-1: NVIDIA GK107 [GeForce GT 740] driver: nvidia v: 470.256.02
    arch: Kepler-2 pcie: speed: 2.5 GT/s lanes: 16 ports: active: none
    off: HDMI-A-1 empty: DVI-I-1,VGA-1 bus-ID: 01:00.0 chip-ID: 10de:0fc8
    class-ID: 0300
  Display: x11 server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: kwin_x11 driver: X: loaded: nvidia unloaded: modesetting
    alternate: fbdev,nouveau,nv,vesa gpu: nvidia,nvidia-nvswitch
    display-ID: :0 note: <missing: xdpyinfo/xrandr>
  Monitor-1: HDMI-A-1 model: LG (GoldStar) FHD serial: <filter>
    res: 1920x1080 dpi: 102 size: 480x260mm (18.9x10.24") diag: 546mm (21.5")
    modes: max: 1920x1080 min: 640x480
  API: OpenGL Message: Unable to show GL data. glxinfo is missing.
  Info: Tools: de: kscreen-doctor gpu: nvidia-settings,nvidia-smi x11: xprop
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.13.5-arch1-1 status: kernel-api
  Server-1: JACK v: 1.9.22 status: off
  Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
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 driver: rt2800usb type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 bus-ID: 2-6:3 chip-ID: 148f:5370
    class-ID: 0000 serial: <filter>
  IF: wlan0 state: up mac: <filter>
Drives:
  Local Storage: total: 1.38 TiB used: 20.45 GiB (1.5%)
  ID-1: /dev/sda vendor: A-Data model: SU800 size: 476.94 GiB
    speed: <unknown> tech: SSD serial: <filter> fw-rev: 8B scheme: MBR
  ID-2: /dev/sdb vendor: Toshiba model: DT01ACA100 size: 931.51 GiB
    speed: <unknown> tech: HDD rpm: 7200 serial: <filter> fw-rev: A7C0
    scheme: MBR
Partition:
  ID-1: / size: 173.1 GiB used: 16.75 GiB (9.7%) fs: ext4 dev: /dev/sda1
  ID-2: /home size: 14.66 GiB used: 3.7 GiB (25.3%) fs: ext4 dev: /dev/sda6
Swap:
  ID-1: swap-1 type: zram size: 1.91 GiB used: 0 KiB (0.0%) priority: 100
    dev: /dev/zram0
  ID-2: swap-2 type: partition size: 8 GiB used: 0 KiB (0.0%) priority: -2
    dev: /dev/sda3
Sensors:
  System Temperatures: cpu: 65.0 C mobo: N/A gpu: nvidia temp: 49 C
  Fan Speeds (rpm): N/A gpu: nvidia fan: 30%
Info:
  Memory: total: 4 GiB available: 3.82 GiB used: 2.16 GiB (56.5%)
  Processes: 177 Power: uptime: 19m states: freeze,mem,disk suspend: deep
    wakeups: 0 hibernate: platform Init: systemd v: 257 default: graphical
  Packages: pm: pacman pkgs: 804 Compilers: clang: 19.1.7 gcc: 14.2.1
    Shell: Bash v: 5.2.37 running-in: konsole inxi: 3.3.37

Also the timer in the error is variable, it sometimes goes to 1min 20s or something, and sometimes up to 2m.

Links-
To a post in arch linux that is kind of related to this issue.
https://bbs.archlinux.org/viewtopic.php?id=227446
My own post when I used to use debian.
https://forums.debian.net/viewtopic.php?t=161517

Thanks,
LL

Last edited by LinuxLover471 (2025-03-16 06:59:36)

seth · 2025-03-08 21:38:40

Another workaround that maybe actually works is logging out and then shutting down.

KDE/SDDM had that a lot but afaiu it wa eventually fixed in sddm - is the delay recorded in the journal of the previous boot?

sudo journalctl -b | curl -F 'file=@-' 0x0.st

LinuxLover471 · 2025-03-09 09:51:14

seth wrote:

Another workaround that maybe actually works is logging out and then shutting down.
KDE/SDDM had that a lot but afaiu it wa eventually fixed in sddm - is the delay recorded in the journal of the previous boot?
sudo journalctl -b | curl -F 'file=@-' 0x0.st

Unfourtunately, I had posted the issue a little bit after the actual problem, if you could tell me some keyword to search for with -u, then I can give some output, until then, I will try to recreate the issue or get the logs after the issue strikes again

Thanks,
LL

LinuxLover471 · 2025-03-09 11:26:17

I just got a slow restart so I guess the error happened, I extracted the logs by using sudo journalctl -b -1 | curl -F 'file=@-' 0x0.st

Here is what I got-
http://0x0.st/8u5x.txt

Here is the boot right now, probably doesn't matter at all.
http://0x0.st/8u5v.txt

Also I was doing some stress testing using geekbench.

Thanks,
LL

seth · 2025-03-09 15:12:28

Mar 09 16:46:53 G31M-ES2L systemd[543]: Stopping KDE Window Manager...
…
Mar 09 16:46:53 G31M-ES2L sddm[488]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Mar 09 16:46:53 G31M-ES2L sddm[488]: Auth: sddm-helper (--socket /tmp/sddm-auth-672d500d-4a2f-4b82-b0a6-f9811d0c7550 --id 1 --start /usr/bin/startplasma-x11 --user ak) crashed (exit code 1)
Mar 09 16:46:53 G31M-ES2L sddm[488]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
Mar 09 16:46:53 G31M-ES2L sddm[488]: Auth: sddm-helper exited with 1
…
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]: XIO:  fatal IO error 4 (Interrupted system call) on X server ":0"
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]:       after 51 requests (51 known processed) with 0 events remaining.
Mar 09 16:46:53 G31M-ES2L kwin_x11[768]: The X11 connection broke: I/O error (code 1)
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: State 'stop-sigterm' timed out. Killing.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Killing process 768 (kwin_x11) with signal SIGKILL.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Killing process 812 (n/a) with signal SIGKILL.
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Main process exited, code=killed, status=9/KILL
Mar 09 16:48:23 G31M-ES2L systemd[543]: plasma-kwin_x11.service: Failed with result 'timeout'.

kwin_x11 (the window manager) doesn't terminate, even though the X11 server is gone.
dr. konqi doesn't kick in (this was also an issue because it kept the session open/renewed it/whatever)

Dod you use the latest repo sddm?

pacman -Qikk sddm

LinuxLover471 · 2025-03-09 16:35:34

seth wrote:

Dod you use the latest repo sddm?
pacman -Qikk sddm

Yes, I installed it directly from pacman repositories and not from testing or AUR.

Output of pacman -Qikk sddm-

Name            : sddm
Version         : 0.21.0-6
Description     : QML based X11 and Wayland display manager
Architecture    : x86_64
URL             : https://github.com/sddm/sddm
Licenses        : GPL-2.0-only
Groups          : None
Provides        : display-manager
Depends On      : bash  gcc-libs  glibc  libxau  libxcb  pam  qt6-base  qt6-declarative  systemd-libs  ttf-font  xorg-server  xorg-xauth
Optional Deps   : qt5-declarative: for using Qt5 themes
Required By     : sddm-kcm
Optional For    : None
Conflicts With  : None
Replaces        : None
Installed Size  : 5.27 MiB
Packager        : Antonio Rojas <arojas@archlinux.org>
Build Date      : Wed 08 Jan 2025 01:36:50 PM IST
Install Date    : Mon 24 Feb 2025 10:26:33 AM IST
Install Reason  : Explicitly installed
Install Script  : No
Validated By    : Signature

sddm: 251 total files, 0 altered files

Thanks,
LL

seth · 2025-03-09 21:05:51

Looks like https://github.com/sddm/sddm/issues/1783 - seems https://github.com/sddm/sddm/pull/1445 hasn't fixed everything here.
Also https://bbs.archlinux.org/viewtopic.php?pid=2229103

LinuxLover471 · 2025-03-10 03:28:34

seth wrote:

Looks like https://github.com/sddm/sddm/issues/1783 - seems https://github.com/sddm/sddm/pull/1445 hasn't fixed everything here.
Also https://bbs.archlinux.org/viewtopic.php?pid=2229103

So I should create a new issue in github? I am not exactly familiar with it.

Also the second post that you mentioned has exactly the same problems I have.

Thanks,
LL

seth · 2025-03-10 07:47:00

You could just hook onto the existing bug.
To mitiate the annoying timeout, see https://github.com/sddm/sddm/issues/181 … 1778697279 but try to edit the plasma-kwin_x11.service instead.

LinuxLover471 · 2025-03-13 03:20:54

seth wrote:

You could just hook onto the existing bug.

I created a new issue https://github.com/sddm/sddm/issues/2058 and I got sent here because they said it was an issue with kde plasma and not sddm. I watched yesterday that there was an update for kwin. Maybe that will fix it? But still I am pretty sure it didn't get fixed.

seth wrote:

To mitiate the annoying timeout, see https://github.com/sddm/sddm/issues/181 … 1778697279 but try to edit the plasma-kwin_x11.service instead.

When I tried to change the service to plasma-kwin_x11.service, it says that the file doesn't exist. (/etc/systemd/system/plasma-kwin_x11.service.d/override.conf) Should I create a new directory for that?

I think I will also post about this issue on bugs.kde.org

Thanks,
LL

seth · 2025-03-13 08:10:06

https://wiki.archlinux.org/title/System … ided_units

https://github.com/sddm/sddm/issues/1783 starts w/ "I recently switched to DisplayServer=x11 from DisplayServer=x11-rootless and I encounter the issue"
Does that match your situation?
https://wiki.archlinux.org/title/SDDM#Rootless

LinuxLover471 · 2025-03-13 14:30:17

seth wrote:

https://github.com/sddm/sddm/issues/1783 starts w/ "I recently switched to DisplayServer=x11 from DisplayServer=x11-rootless and I encounter the issue"
Does that match your situation?
https://wiki.archlinux.org/title/SDDM#Rootless

No, it doesn't match my situation, I am using what is provided by kwin/plasma by default, I didn't switch from x11-rootless to x11, or vice versa.

Also the service does not have any files, is creating a file by forcing worth it? I heard that forcing anything is not right...

[ak@G31M-ES2L ~]$ systemctl edit --full plasma-kwin_x11.service
No files found for plasma-kwin_x11.service.
Run 'systemctl edit --force --full plasma-kwin_x11.service' to create a new unit.

Thanks,
LL

seth · 2025-03-13 14:51:51

https://archlinux.org/packages/extra/x86_64/kwin/ ships /usr/lib/systemd/user/plasma-kwin_x11.service so it's a user service.

systemctl --user edit --full plasma-kwin_x11.service

What does /usr/lib/sddm/sddm.conf.d/default.conf look like?

LinuxLover471 · 2025-03-14 16:02:23

seth wrote:

https://archlinux.org/packages/extra/x86_64/kwin/ ships /usr/lib/systemd/user/plasma-kwin_x11.service so it's a user service.
systemctl --user edit --full plasma-kwin_x11.service

Thanks for telling me that, I did not know that there are separate user services for the system itself. I added the timeout option under the already present [Service] tab.

Contents of /usr/lib/sddm/sddm.conf.d/default.conf-

[Autologin]
# Whether sddm should automatically log back into sessions when they exit
Relogin=false

# Name of session file for autologin session (if empty try last logged in)
Session=

# Username for autologin session
User=


[General]
# Which display server should be used.
# Valid values are: x11, x11-user, wayland. Wayland support is experimental
DisplayServer=x11

# Comma-separated list of environment variables to be set
GreeterEnvironment=

# Halt command
HaltCommand=/usr/bin/systemctl poweroff

# Input method module
InputMethod=

# Comma-separated list of Linux namespaces for user session to enter
Namespaces=

# Initial NumLock state. Can be on, off or none.
# If property is set to none, numlock won't be changed
# NOTE: Currently ignored if autologin is enabled.
Numlock=none

# Reboot command
RebootCommand=/usr/bin/systemctl reboot


[Theme]
# Current theme name
Current=

# Cursor size used in the greeter
CursorSize=

# Cursor theme used in the greeter
CursorTheme=

# Number of users to use as threshold
# above which avatars are disabled
# unless explicitly enabled with EnableAvatars
DisableAvatarsThreshold=7

# Enable display of custom user avatars
EnableAvatars=true

# Global directory for user avatars
# The files should be named <username>.face.icon
FacesDir=/usr/share/sddm/faces

# Font used in the greeter
Font=

# Theme directory path
ThemeDir=/usr/share/sddm/themes


[Users]
# Default $PATH for logged in users
DefaultPath=/usr/local/sbin:/usr/local/bin:/usr/bin

# Comma-separated list of shells.
# Users with these shells as their default won't be listed
HideShells=

# Comma-separated list of users that should not be listed
HideUsers=

# Maximum user id for displayed users
MaximumUid=60513

# Minimum user id for displayed users
MinimumUid=1000

# Remember the session of the last successfully logged in user
RememberLastSession=true

# Remember the last successfully logged in user
RememberLastUser=true

# When logging in as the same user twice, restore the original session, rather than create a new one
ReuseSession=true


[Wayland]
# Path of the Wayland compositor to execute when starting the greeter
CompositorCommand=weston --shell=kiosk

# Enable Qt's automatic high-DPI scaling
EnableHiDPI=true

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/wayland-session

# Comma-separated list of directories containing available Wayland sessions
SessionDir=/usr/local/share/wayland-sessions,/usr/share/wayland-sessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/wayland-session.log


[X11]
# Path to a script to execute when starting the display server
DisplayCommand=/usr/share/sddm/scripts/Xsetup

# Path to a script to execute when stopping the display server
DisplayStopCommand=/usr/share/sddm/scripts/Xstop

# Enable Qt's automatic high-DPI scaling
EnableHiDPI=true

# Arguments passed to the X server invocation
ServerArguments=-nolisten tcp

# Path to X server binary
ServerPath=/usr/bin/X

# Path to a script to execute when starting the desktop session
SessionCommand=/usr/share/sddm/scripts/Xsession

# Comma-separated list of directories containing available X sessions
SessionDir=/usr/local/share/xsessions,/usr/share/xsessions

# Path to the user session log file
SessionLogFile=.local/share/sddm/xorg-session.log

# Path to Xephyr binary
XephyrPath=/usr/bin/Xephyr

Thanks,
LL

seth · 2025-03-15 08:11:45

DisplayServer=x11

Try "x11-user"

LinuxLover471 · 2025-03-15 15:52:44

seth wrote:

DisplayServer=x11
Try "x11-user"

Tried it, nothing changes, though thanks to the .service workaround, it shut down somewhat instantly, about 5 or something seconds for sure.

Here is the logs-
http://0x0.st/8Q1K.txt

Thanks,
LL

seth · 2025-03-15 16:00:18

Applied, so you're indeed not in the ballpark of that SDDM bug.

Ftr, https://bugs.kde.org/show_bug.cgi?id=501433

LinuxLover471 · 2025-03-15 16:05:20

seth wrote:

Ftr, https://bugs.kde.org/show_bug.cgi?id=501433

It's actually me who reported this bug, sorry for not telling about this earlier.

Thanks
LL

seth · 2025-03-15 16:28:14

I know, it's really just "for the records"

LinuxLover471 · 2025-03-17 11:56:31

In case if someone does not want to read the whole thread, there are 2 workaround so far.

1. You can shutdown the system after logging out, this evades the issue completely in my case.

2. You can edit a service by using-

systemctl --user edit --full plasma-kwin_x11.service

After this add "TimeoutStopSec=3s" under the [Service] tab. This will minimize the issue and the service will take only 3 seconds to turn off, you can try lower settings if you want, just don't set it too low.

Sincerely,
LL

Arch Linux

#1 2025-03-08 16:01:34

[Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#2 2025-03-08 21:38:40

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#3 2025-03-09 09:51:14

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#4 2025-03-09 11:26:17

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#5 2025-03-09 15:12:28

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#6 2025-03-09 16:35:34

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#7 2025-03-09 21:05:51

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#8 2025-03-10 03:28:34

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#9 2025-03-10 07:47:00

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#10 2025-03-13 03:20:54

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#11 2025-03-13 08:10:06

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#12 2025-03-13 14:30:17

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#13 2025-03-13 14:51:51

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#14 2025-03-14 16:02:23

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#15 2025-03-15 08:11:45

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#16 2025-03-15 15:52:44

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#17 2025-03-15 16:00:18

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#18 2025-03-15 16:05:20

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#19 2025-03-15 16:28:14

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

#20 2025-03-17 11:56:31

Re: [Workaround(s)]User UID 1000 service stop error at shutdown/restart.

Board footer