[SOLVED] Slow log-out from DE to display manager on both X11/Wayland

patchouli · 2024-09-18 16:19:43

Hi. I installed Arch on my desktop just last night. I followed the installation guide in its entirety, including the security page & general recommendations, and I'm having an odd issue when logging out on Plasma.
As per the recommendations, I use KDE Plasma and SDDM. I installed Plasma by getting plasma-desktop and then started installing different meta packages for the functionality I need and want.

When logging out, rebooting, or shutting down, almost all of the time, the screen will hang on whatever currently happens, the cursor won't move either, and after about 8-12 seconds, it will proceed to log out.
I don't know how to trace down which process/event is the reason that it hangs for so long or how to fix it.
The issue happens both on Wayland and X11 sessions.
Another observation is that sudo reboot is immediate. I get thrown to the TTY with the text output from the kernel immediately rather than hanging for 10~ seconds.

Wayland was inaccessible to me (black screen, no cursor) until I added the kernel parameter nvidia_drm.fbdev=1. X11 worked although still exhibited that issue.

Sometimes (but not nearly as consistently), log-in from SDDM to the Plasma session can also take the same amount of time, although the Plasma splash screen animates so I know the system isn't hanging when that happens.

Output from pacman -Qe:

aria2 1.37.0-1
ark 24.08.1-1
audacity 1:3.6.3-1
base 3-2
base-devel 1-2
betterbird-bin 115.15.0-2
bind 9.20.1-1
bitwarden 2024.8.1-1
bluedevil 1:6.1.5-1
breeze-grub 6.1.5-1
breeze-gtk 6.1.5-1
breeze-plymouth 6.1.5-1
calibre 7.17.0-1
colloid-nord-icon-theme-git 2024.08.31.r11.g42375ae-1
colord-kde 24.08.1-1
curl 8.10.1-1
dkms 3.0.12-1
drkonqi 6.1.5-1
duf 0.8.1-3
e2fsprogs 1.47.1-4
efivar 39-1
exfatprogs 1.2.5-1
exodus 24.33.5-1
eza 0.19.4-1
fastfetch 2.24.0-1
filelight 24.08.1-1
firefox 130.0.1-1
flatpak-kcm 6.1.5-1
fzf 0.55.0-1
gamemode 1.8.2-1
gdu 5.29.0-1
git 2.46.1-1
gsettings-qt 0.2-2
gwenview 24.08.1-1
htop 3.3.0-3
ibus 1.5.30-3
informant 0.6.0-1
intel-ucode 20240910-1
iperf3 3.17.1-1
iptables 1:1.8.10-2
iwd 2.22-1
kalk 24.08.1-1
kamera 24.08.1-1
kcolorchooser 24.08.1-1
kde-gtk-config 6.1.5-1
kde-system-meta 24.08-1
kdebugsettings 24.08.1-1
kdegraphics-thumbnailers 24.08.1-1
kdeplasma-addons 6.1.5-1
kdialog 24.08.1-1
keditbookmarks 24.08.1-1
keysmith 24.08.1-1
kfind 24.08.1-1
kgamma 6.1.5-1
kinfocenter 6.1.5-1
koko 24.08.1-1
konsole 24.08.1-1
kscreen 6.1.5-1
ksshaskpass 6.1.5-1
kteatime 24.08.1-1
kwallet-pam 6.1.5-1
kwalletmanager 24.08.0-2
kwrited 6.1.5-1
lib32-gamemode 1.8.2-1
lib32-gnutls 3.8.7-1
lib32-gst-plugins-base 1.24.7-1
lib32-gst-plugins-good 1.24.7-1
lib32-libpulse 17.0-1
lib32-mangohud 0.7.2-1
lib32-mesa-utils 9.0.0-2
lib32-nvidia-utils 560.35.03-1
lib32-sdl2 2.30.7-1
libva-nvidia-driver 0.0.12-1
libva-utils 2.22.0-1
linux 6.10.10.arch1-1
linux-firmware 20240909.552ed9b8-1
linux-headers 6.10.10.arch1-1
linux-zen 6.10.10.zen1-1
linux-zen-headers 6.10.10.zen1-1
man-db 2.13.0-1
man-pages 6.9.1-1
mangohud 0.7.2-2
markdownpart 24.08.1-1
mediainfo 24.06-1
mediainfo-gui 24.06-1
mkinitcpio-firmware 1.4.0-1
mkvtoolnix-cli 87.0-2
mkvtoolnix-gui 87.0-2
mold 2.33.0-1
mpv-full 0.38.0-1
nano 8.2-1
ncdu 2.5-1
networkmanager 1.48.10-1
nut 2.8.2-1
nvidia-dkms 560.35.03-2
nvtop 3.1.0-1
opensiddur-hebrew-fonts 1.18.6-2
openssh 9.8p1-2
osu-lazer-bin 2024.906.2-1
otf-aurulent-nerd 3.2.1-2
otf-codenewroman-nerd 3.2.1-2
otf-comicshanns-nerd 3.2.1-2
otf-commit-mono-nerd 3.2.1-2
otf-droid-nerd 3.2.1-2
otf-firamono-nerd 3.2.1-2
otf-geist-mono-nerd 3.2.1-2
otf-hasklig-nerd 3.2.1-2
otf-hermit-nerd 3.2.1-2
otf-monaspace-nerd 3.2.1-2
otf-opendyslexic-nerd 3.2.1-2
otf-overpass-nerd 3.2.1-2
oxygen 6.1.5-1
oxygen-sounds 6.1.5-1
packagekit-qt6 1.1.2-1
pacman-contrib 1.10.6-2
phonon-qt6-mpv 0.1.0-1
pipewire-alsa 1:1.2.3-1
plasma-browser-integration 6.1.5-1
plasma-desktop 6.1.5-1
plasma-disks 6.1.5-1
plasma-firewall 6.1.5-1
plasma-nm 6.1.5-1
plasma-pa 6.1.5-1
plasma-sdk 6.1.5-1
plasma-systemmonitor 6.1.5-1
plasma-thunderbolt 6.1.5-1
plasma-vault 6.1.5-1
plasma-workspace-wallpapers 6.1.5-1
plymouth-kcm 6.1.5-1
print-manager 1:6.1.5-1
qbittorrent 4.6.7-1
qt5-declarative 5.15.15+kde+r25-1
ripgrep 14.1.1-1
samba 2:4.21.0-2
sbctl 0.15.4-1
scim 1.4.18-5
sddm 0.21.0-4
sddm-kcm 6.1.5-1
snapd 2.65.1-1
spectacle 24.08.1-1
speedtest-cli 2.1.3-8
steam 1.0.0.81-2
svgpart 24.08.1-1
terminus-font 4.49.1-7
texinfo 7.1.1-1
ttf-0xproto-nerd 3.2.1-2
ttf-3270-nerd 3.2.1-2
ttf-agave-nerd 3.2.1-2
ttf-anonymouspro-nerd 3.2.1-2
ttf-arimo-nerd 3.2.1-2
ttf-bigblueterminal-nerd 3.2.1-2
ttf-bitstream-vera-mono-nerd 3.2.1-2
ttf-cascadia-code-nerd 3.2.1-2
ttf-cascadia-mono-nerd 3.2.1-2
ttf-cousine-nerd 3.2.1-2
ttf-d2coding-nerd 3.2.1-2
ttf-daddytime-mono-nerd 3.2.1-2
ttf-dejavu-nerd 3.2.1-2
ttf-envycoder-nerd 3.2.1-2
ttf-fantasque-nerd 3.2.1-2
ttf-firacode-nerd 3.2.1-2
ttf-go-nerd 3.2.1-2
ttf-gohu-nerd 3.2.1-2
ttf-hack-nerd 3.2.1-2
ttf-heavydata-nerd 3.2.1-2
ttf-iawriter-nerd 3.2.1-2
ttf-ibmplex-mono-nerd 3.2.1-2
ttf-inconsolata-go-nerd 3.2.1-2
ttf-inconsolata-lgc-nerd 3.2.1-2
ttf-inconsolata-nerd 3.2.1-2
ttf-intone-nerd 3.2.1-2
ttf-iosevka-nerd 3.2.1-2
ttf-iosevkaterm-nerd 3.2.1-2
ttf-iosevkatermslab-nerd 3.2.1-2
ttf-jetbrains-mono-nerd 3.2.1-2
ttf-lekton-nerd 3.2.1-2
ttf-liberation-mono-nerd 3.2.1-2
ttf-lilex-nerd 3.2.1-2
ttf-martian-mono-nerd 3.2.1-2
ttf-meslo-nerd 3.2.1-2
ttf-monofur-nerd 3.2.1-2
ttf-monoid-nerd 3.2.1-2
ttf-mononoki-nerd 3.2.1-2
ttf-mplus-nerd 3.2.1-2
ttf-ms-win11-auto 10.0.22631.2428-2
ttf-ms-win11-auto-japanese 10.0.22631.2428-2
ttf-ms-win11-auto-korean 10.0.22631.2428-2
ttf-ms-win11-auto-other 10.0.22631.2428-2
ttf-ms-win11-auto-sea 10.0.22631.2428-2
ttf-ms-win11-auto-thai 10.0.22631.2428-2
ttf-ms-win11-auto-zh_cn 10.0.22631.2428-2
ttf-ms-win11-auto-zh_tw 10.0.22631.2428-2
ttf-nerd-fonts-symbols 3.2.1-1
ttf-nerd-fonts-symbols-mono 3.2.1-1
ttf-noto-nerd 3.2.1-2
ttf-profont-nerd 3.2.1-2
ttf-proggyclean-nerd 3.2.1-2
ttf-recursive-nerd 3.2.1-2
ttf-roboto-mono-nerd 3.2.1-2
ttf-sharetech-mono-nerd 3.2.1-2
ttf-sourcecodepro-nerd 3.2.1-2
ttf-space-mono-nerd 3.2.1-2
ttf-terminus-nerd 3.2.1-2
ttf-tinos-nerd 3.2.1-2
ttf-ubuntu-mono-nerd 3.2.1-2
ttf-ubuntu-nerd 3.2.1-2
ttf-victor-mono-nerd 3.2.1-2
ttf-zed-mono-nerd 3.2.1-2
unigine-superposition 1.1-6
usbutils 017-1
vesktop-bin 1.5.3-1
vi 1:070224-6
vscodium-bin-features 1.82.0-4
vscodium-bin-marketplace 1.76.0-1
wacomtablet 6.1.5-1
wayland 1.23.1-1
webcord 4.10.1-1
wget 1.24.5-3
wine 9.17-1
xfsprogs 6.10.1-1
yakuake 24.08.1-1
yay 12.4.1-1
yay-debug 12.4.1-1
yaycache-hook 0.1.0-1
youtube-music-bin 3.5.3-1
yt-dlp 2024.08.06-1
zathura 0.5.8-1
zoom 6.2.0-1
zoxide 0.9.5-1
zsh 5.9-5

Here's output from systemd-analyze blame, which I believe is the amount of time it takes from boot until it reaches SDDM.

4.560s systemd-udev-settle.service
4.095s nut-driver@nutdev-usb1.service
1.414s systemd-modules-load.service
 749ms systemd-binfmt.service
 739ms systemd-resolved.service
 729ms systemd-timesyncd.service
 426ms ldconfig.service
 410ms boot.mount
 228ms nftables.service
 172ms dev-nvme0n1p3.device
 158ms nut-driver-enumerator.service
 119ms user@1000.service
  93ms systemd-tmpfiles-clean.service
  88ms nut-server.service
  78ms nut-monitor.service
  74ms systemd-rfkill.service
  70ms NetworkManager.service
  61ms systemd-udev-trigger.service
  55ms upower.service
  55ms plymouth-start.service
  46ms NetworkManager-wait-online.service
  42ms bluetooth.service
  39ms systemd-tmpfiles-setup-dev-early.service
  38ms systemd-vconsole-setup.service
  30ms systemd-sysusers.service
  30ms systemd-tmpfiles-setup.service
  29ms user-runtime-dir@1000.service
  26ms systemd-logind.service
  26ms media-extra.mount
  25ms dbus-broker.service
  25ms plymouth-quit.service
  25ms plymouth-quit-wait.service
  24ms polkit.service
  23ms systemd-journald.service
  23ms systemd-udevd.service
  23ms systemd-update-done.service
  22ms proc-sys-fs-binfmt_misc.mount
  22ms udisks2.service
  21ms systemd-journal-flush.service
  21ms systemd-random-seed.service
  19ms systemd-hostnamed.service
  17ms systemd-journal-catalog-update.service
  14ms systemd-fsck@dev-disk-by\x2duuid-9d828245\x2ddec6\x2d4fb7\x2dbbb8\x2d4c72e84ee68e.service
  12ms plymouth-read-write.service
  12ms dev-hugepages.mount
  12ms dev-mqueue.mount
  11ms sys-kernel-debug.mount
  11ms systemd-boot-random-seed.service
  10ms sys-kernel-tracing.mount
  10ms kmod-static-nodes.service
  10ms modprobe@configfs.service
  10ms systemd-userdbd.service
   9ms modprobe@drm.service
   9ms snapd.socket
   9ms modprobe@fuse.service
   9ms rtkit-daemon.service
   8ms tmp.mount
   8ms systemd-tmpfiles-setup-dev.service
   7ms var-lib-snapd-snap-bare-5.mount
   7ms var-lib-snapd-snap-core20-2379.mount
   6ms var-lib-snapd-snap-mesa\x2dcore20-165.mount
   6ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
   6ms var-lib-snapd-snap-plex\x2ddesktop-75.mount
   6ms dev-disk-by\x2duuid-1f9b2f0d\x2d591c\x2d47a7\x2d923a\x2dc740b26b4b4c.swap
   6ms var-lib-snapd-snap-gnome\x2d3\x2d38\x2d2004-143.mount
   6ms dev-loop3.device
   6ms systemd-remount-fs.service
   6ms dev-loop2.device
   6ms dev-loop6.device
   6ms dev-loop5.device
   6ms var-lib-snapd-snap-snapd-21759.mount
   5ms dev-loop4.device
   5ms systemd-udev-load-credentials.service
   5ms dev-loop1.device
   4ms systemd-update-utmp.service
   4ms dev-loop0.device
   3ms systemd-user-sessions.service
   3ms systemd-sysctl.service
   3ms modprobe@loop.service
   2ms sys-fs-fuse-connections.mount
   2ms modprobe@dm_mod.service
   2ms sys-kernel-config.mount

Some details on my system via fastfetch:

                  -`                     patchouli@patchouli
                 .o+`                    -------------------
                `ooo/                    OS: Arch Linux x86_64
               `+oooo:                   Host: MS-7D89 (1.0)
              `+oooooo:                  Kernel: Linux 6.10.10-zen1-1-zen
              -+oooooo+:                 Uptime: 1 hour, 8 mins
            `/:-:++oooo+:                Packages: 1408 (pacman), 7 (snap)
           `/++++/+++++++:               Shell: zsh 5.9
          `/++++++++++++++:              Display (27G1S): 2560x1440 @ 240 Hz in 27″ [External]
         `/+++ooooooooooooo/`            DE: KDE Plasma 6.1.5
        ./ooosssso++osssssso+`           WM: KWin (Wayland)
       .oossssso-````/ossssss+`          WM Theme: Breeze
      -osssssso.      :ssssssso.         Theme: Breeze (Dark) [Qt], Breeze-Dark [GTK2], Breeze [GTK3]
     :osssssss/        osssso+++.        Icons: breeze-dark [Qt], breeze-dark [GTK2/3/4]
    /ossssssss/        +ssssooo/-        Font: Noto Sans (10pt) [Qt], Noto Sans (10pt) [GTK2/3/4]
  `/ossssso+/:-        -:/+osssso+-      Cursor: breeze (24px)
 `+sso+:-`                 `.-/+oso:     Terminal: konsole 24.8.1
`++:.                           `-/+/    Terminal Font: FiraCode Nerd Font (10pt)
.`                                 `/    CPU: 13th Gen Intel(R) Core(TM) i9-13900K (32) @ 5.80 GHz
                                         GPU 1: NVIDIA GeForce RTX 4090 [Discrete]
                                         GPU 2: Intel UHD Graphics 770 @ 1.65 GHz [Integrated]
                                         Memory: 5.68 GiB / 31.11 GiB (18%)
                                         Swap: 54.00 MiB / 32.00 GiB (0%)
                                         Disk (/): 92.47 GiB / 1.79 TiB (5%) - xfs
                                         Disk (/media/extra): 168.49 GiB / 1.82 TiB (9%) - xfs
                                         Local IP (enp7s0): 192.168.0.211/24
                                         Locale: en_US.UTF-8

I also have an Eaton 5E USB UPS which I configured with NUT and it doesn't show up in my fastfetch output. Also not listed here is that the root filesystem & boot partition are on a SAMSUNG 990 Pro SSD.

I assume I messed up something during the installation process or that there's some hardware compatibility problem, as I have a severely more underpowered system at home (AMD Ryzen 7840HS, slower RAM, slower SSD) which I installed Arch on quickly with archinstall and it doesn't have this issue, while this time I went through a manual install.

I have benchmarked my boot drive because someone in another community suggested "it might be a lot of I/O when Plasma saves and loads its states", and my SSD performance seems to not be the issue:

Some notes:
- I believe the issue happened immediately from the first time I used Plasma on the system.
- I had the issue before installing linux-zen afterwards. linux does not solve it either.
- Another attempt to fix it was changing video display drivers, so I went from nvidia-open (on linux) to nvidia-dkms on linux-zen.

Last edited by patchouli (2024-10-24 15:24:14)

yxcv · 2024-09-19 08:00:02

I use KDE only because of colours and its windowsmanaging.
Switching of most times is OK, but too often from my point of view it never stops. But there is the fantastic world of NO-AND-NEVER-KDE. Or pure X.
So I do: [Strg][Alt][F3, F5], log in and switch to root and "systemctl poweroff"
and finnish within some 1/100 Sek no power can be noted HTH You may train "systemctl reboot". Power is noted again.

patchouli · 2024-09-19 09:07:35

yxcv wrote:

I use KDE only because of colours and its windowsmanaging.
Switching of most times is OK, but too often from my point of view it never stops. But there is the fantastic world of NO-AND-NEVER-KDE. Or pure X.
So I do: [Strg][Alt][F3, F5], log in and switch to root and "systemctl poweroff"
and finnish within some 1/100 Sek no power can be noted HTH You may train "systemctl reboot". Power is noted again.

Thanks for replying, but I have no idea what you’re talking about. I’m just interested in using the DE’s features properly, including logout. I posted this because I believe I either messed up during the installation or configuration somewhere, and figured someone might be able to help. I’m not interested in switching to a different TTY to write a command for that. In fact even switching from KDE Plasma to a TTY takes nearly 15 seconds on my system right now.. while it’s almost instant on my other computer.

Last edited by patchouli (2024-09-19 09:08:00)

Lone_Wolf · 2024-09-19 09:22:12

In fact even switching from KDE Plasma to a TTY takes nearly 15 seconds on my system right now

Delay when switicihng from gui to TTY is rather common for nvidia cards, although 15 seconds seems a bit too long.

Please post from an X session the full outputs of

$ lspci -k
$ glxinfo -B #comes with mesa-utils package
$ DRI_PRIME=1 glxinfo -B

Also run (with root tights)

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

and post the link it outputs.

patchouli · 2024-09-19 09:52:17

Lone_Wolf wrote:

In fact even switching from KDE Plasma to a TTY takes nearly 15 seconds on my system right now
Delay when switicihng from gui to TTY is rather common for nvidia cards, although 15 seconds seems a bit too long.
Please post from an X session the full outputs of
$ lspci -k
$ glxinfo -B #comes with mesa-utils package
$ DRI_PRIME=1 glxinfo -B
Also run (with root tights)
journalctl -b | curl -F 'file=@-' 0x0.st
and post the link it outputs.

Launched KDE Plasma via an X11 session, here's the output for all commands:

❯  ~ lspci -k
00:00.0 Host bridge: Intel Corporation Device a700 (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
00:01.0 PCI bridge: Intel Corporation Raptor Lake PCI Express 5.0 Graphics Port (PEG010) (rev 01)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: pcieport
00:02.0 Display controller: Intel Corporation Raptor Lake-S GT1 [UHD Graphics 770] (rev 04)
        DeviceName: Onboard - Video
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: i915
        Kernel modules: i915, xe
00:06.0 PCI bridge: Intel Corporation Raptor Lake PCIe 4.0 Graphics Port (rev 01)
        Kernel driver in use: pcieport
00:08.0 System peripheral: Intel Corporation GNA Scoring Accelerator module (rev 01)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
00:0a.0 Signal processing controller: Intel Corporation Raptor Lake Crashlog and Telemetry (rev 01)
        DeviceName: Onboard - Other
        Kernel driver in use: intel_vsec
        Kernel modules: intel_vsec
00:14.0 USB controller: Intel Corporation Raptor Lake USB 3.2 Gen 2x2 (20 Gb/s) XHCI Host Controller (rev 11)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: xhci_hcd
        Kernel modules: mei_me, xhci_pci
00:14.2 RAM memory: Intel Corporation Raptor Lake-S PCH Shared SRAM (rev 11)
        DeviceName: Onboard - Other
00:14.3 Network controller: Intel Corporation Raptor Lake-S PCH CNVi WiFi (rev 11)
        DeviceName: Onboard - Ethernet
        Subsystem: Intel Corporation Device 0094
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi
00:16.0 Communication controller: Intel Corporation Raptor Lake CSME HECI #1 (rev 11)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: mei_me
        Kernel modules: mei_me
00:17.0 SATA controller: Intel Corporation Raptor Lake SATA AHCI Controller (rev 11)
        DeviceName: Onboard - SATA
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: ahci
00:1a.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #25 (rev 11)
        Subsystem: nCipher Security Device 001a
        Kernel driver in use: pcieport
00:1b.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #17 (rev 11)
        Kernel driver in use: pcieport
00:1b.4 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #21 (rev 11)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: pcieport
00:1c.0 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #1 (rev 11)
        Kernel driver in use: pcieport
00:1c.1 PCI bridge: Intel Corporation Device 7a39 (rev 11)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: pcieport
00:1c.3 PCI bridge: Intel Corporation Raptor Lake PCI Express Root Port #4 (rev 11)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: pcieport
00:1f.0 ISA bridge: Intel Corporation Raptor Lake LPC/eSPI Controller (rev 11)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
00:1f.3 Audio device: Intel Corporation Raptor Lake High Definition Audio Controller (rev 11)
        DeviceName: Onboard - Sound
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel, snd_soc_avs, snd_sof_pci_intel_tgl
00:1f.4 SMBus: Intel Corporation Raptor Lake-S PCH SMBus Controller (rev 11)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: i801_smbus
        Kernel modules: i2c_i801
00:1f.5 Serial bus controller: Intel Corporation Raptor Lake SPI (flash) Controller (rev 11)
        DeviceName: Onboard - Other
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: intel-spi
        Kernel modules: spi_intel_pci
01:00.0 VGA compatible controller: NVIDIA Corporation AD102 [GeForce RTX 4090] (rev a1)
        Subsystem: PNY Device 13da
        Kernel driver in use: nvidia
        Kernel modules: nouveau, nvidia_drm, nvidia
01:00.1 Audio device: NVIDIA Corporation AD102 High Definition Audio Controller (rev a1)
        Subsystem: PNY Device 13da
        Kernel driver in use: snd_hda_intel
        Kernel modules: snd_hda_intel
02:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD Controller S4LV008[Pascal]
        Subsystem: Samsung Electronics Co Ltd Device a801
        Kernel driver in use: nvme
        Kernel modules: nvme
03:00.0 USB controller: ASMedia Technology Inc. ASM3242 USB 3.2 Host Controller
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: xhci_hcd
        Kernel modules: xhci_pci
05:00.0 Non-Volatile memory controller: Silicon Motion, Inc. SM2262/SM2262EN SSD Controller (rev 03)
        Subsystem: Silicon Motion, Inc. SM2262/SM2262EN SSD Controller
        Kernel driver in use: nvme
        Kernel modules: nvme
07:00.0 Ethernet controller: Intel Corporation Ethernet Controller I226-V (rev 04)
        Subsystem: Micro-Star International Co., Ltd. [MSI] Device 7d89
        Kernel driver in use: igc
        Kernel modules: igc
08:00.0 SATA controller: ASMedia Technology Inc. ASM1061/ASM1062 Serial ATA Controller (rev 02)
        Subsystem: ASMedia Technology Inc. Device 1060
        Kernel driver in use: ahci
❯  ~ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24564 MB
    Total available memory: 24564 MB
    Currently available dedicated video memory: 23394 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 560.35.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 560.35.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 560.35.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

❯  ~ DRI_PRIME=1 glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 24564 MB
    Total available memory: 24564 MB
    Currently available dedicated video memory: 23394 MB
OpenGL vendor string: NVIDIA Corporation
OpenGL renderer string: NVIDIA GeForce RTX 4090/PCIe/SSE2
OpenGL core profile version string: 4.6.0 NVIDIA 560.35.03
OpenGL core profile shading language version string: 4.60 NVIDIA
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile

OpenGL version string: 4.6.0 NVIDIA 560.35.03
OpenGL shading language version string: 4.60 NVIDIA
OpenGL context flags: (none)
OpenGL profile mask: (none)

OpenGL ES profile version string: OpenGL ES 3.2 NVIDIA 560.35.03
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20

journalctl (via root): http://0x0.st/X3J0.txt

Lone_Wolf · 2024-09-21 12:20:45

Sep 19 12:29:26 patchouli kernel: Command line: initrd=\initramfs-linux-zen.img root=UUID=b4b53932-d0bc-41d8-a278-b7f3fa6fbf3c usbhid.quirks=0x0463:0xffff:0x08 rw

Sep 19 12:29:26 patchouli kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device

Nvidia driver is known to have trouble cooperating with the simpledrm device.

Add nvidia_drm.modeset=1 as kernel parameter, then reboot .
see https://wiki.archlinux.org/title/NVIDIA … de_setting for more info .

patchouli · 2024-09-21 13:24:51

Lone_Wolf wrote:

Sep 19 12:29:26 patchouli kernel: Command line: initrd=\initramfs-linux-zen.img root=UUID=b4b53932-d0bc-41d8-a278-b7f3fa6fbf3c usbhid.quirks=0x0463:0xffff:0x08 rw

Sep 19 12:29:26 patchouli kernel: simple-framebuffer simple-framebuffer.0: [drm] fb0: simpledrmdrmfb frame buffer device
Nvidia driver is known to have trouble cooperating with the simpledrm device.
Add nvidia_drm.modeset=1 as kernel parameter, then reboot .
see https://wiki.archlinux.org/title/NVIDIA … de_setting for more info .

I already did that via modprobe.d during my initial installation, and the following command prints “Y”:

cat /sys/module/nvidia_drm/parameters/modeset

The same applies for fbdev, and the wiki page for NVIDIA says it’s required as efifb/vesafb don’t work under simpledrm.

Edit: I think I see what's the issue
https://wiki.archlinux.org/title/Kernel … le_options

If the module is built into the kernel, the kernel command line must be used and other methods will not work.

I assumed this wouldn't apply to nvidia-dkms as it's an out-of-tree module. The NVIDIA page also says:

To enable it, set the modeset=1 kernel module parameter for the nvidia_drm module.
To verify nvidia_drm.modeset=1 was correctly applied after a reboot, execute the following:
cat /sys/module/nvidia_drm/parameters/modeset

And that printed Y. Setting modeset via probemod.d allowed me to start Wayland sessions, so I assumed it worked fine considering it worked, as well as the 'verify it works' text from the wiki.

I got rid of my probemod.d and added modeset=1 to my kernel command line. I also see that there was an update to nvidia-dkms yesterday. A new look at my journalctl shows this now rather than simple-framebuffer:

Sep 21 16:39:43 patchouli kernel: efifb: probing for efifb
Sep 21 16:39:43 patchouli kernel: efifb: framebuffer at 0x6000000000, using 23040k, total 23040k
Sep 21 16:39:43 patchouli kernel: efifb: mode is 2560x1440x32, linelength=16384, pages=1
Sep 21 16:39:43 patchouli kernel: efifb: scrolling: redraw
Sep 21 16:39:43 patchouli kernel: efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0

From a quick look, setting nvidia-drm.fbdev=1 still makes the journal show efifb being used.. not sure what's up with that..

I'll do some testing, then update back here if the issue is resolved. Hopefully I'll also add [SOLVED] to the post title if everything seems good.

Last edited by patchouli (2024-09-21 13:48:05)

Lone_Wolf · 2024-09-21 14:14:40

The verification statement in the wiki only tells whether modeset is enabled, not when.

Until nvidia manages to cooperate with simpledrm like other kernel modules do, things work best if nvidia_drm.modeset=1 is set before simpledrm is activated .

patchouli · 2024-09-21 14:19:54

Unfortunately that didn't resolve the issue. I'm able to sometimes get quick log-outs, more than before, but sometimes it still hangs for somewhere between 10 to 15 seconds.
I also removed kms from the mkinitpcio hooks, then rebuilt initramfs.

Here's an up to date journal, if it's useful at all: http://0x0.st/X3FB.txt

Last edited by patchouli (2024-09-21 14:20:19)

Lone_Wolf · 2024-09-21 14:53:47

Sep 21 17:10:06 patchouli sddm-helper[1179]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                             Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                             If this causes problems, reconfigure your locale. See the locale(1) manual
                                             for more information.

You may have locale issues, please post the outputs of

$ locale
$ localedef --list-archive
$ localectl list-locales

KDE tries to restore your session (and the state of all open programs).

Sep 21 17:10:16 patchouli systemd[1228]: Finished KDE Session Restoration.

The saving may be partially responsible for the delays, try disabling session restore.

seth · 2024-09-21 15:12:36

Sep 21 17:16:45 patchouli systemd[1228]: Stopped KDE Plasma Workspace.
Sep 21 17:16:45 patchouli systemd[1228]: plasma-plasmashell.service: Consumed 2.111s CPU time, 208M memory peak.
Sep 21 17:16:45 patchouli systemd[1228]: Stopping KDE Session Management Server...
Sep 21 17:16:45 patchouli systemd[1228]: Stopped KDE Session Management Server.
Sep 21 17:16:45 patchouli systemd[1228]: Stopping KDE Window Manager...
Sep 21 17:16:45 patchouli kwalletd6[4841]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 17:16:45 patchouli kwalletd6[4841]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 17:16:45 patchouli kwalletd6[4841]: Failed to write to the pipe: Bad file descriptor.
Sep 21 17:16:45 patchouli kwalletd6[4841]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 17:17:03 patchouli systemd[1228]: Stopped KDE Window Manager.
Sep 21 17:17:03 patchouli systemd[1228]: plasma-kwin_wayland.service: Consumed 19.776s CPU time, 116.5M memory peak.
Sep 21 17:17:03 patchouli sddm-helper[4833]: [PAM] Closing session

Looks like kwallet causes this?

patchouli · 2024-09-21 18:06:30

Lone_Wolf wrote:

Sep 21 17:10:06 patchouli sddm-helper[1179]: Detected locale "C" with character encoding "ANSI_X3.4-1968", which is not UTF-8.
                                             Qt depends on a UTF-8 locale, and has switched to "C.UTF-8" instead.
                                             If this causes problems, reconfigure your locale. See the locale(1) manual
                                             for more information.

You may have locale issues, please post the outputs of

$ locale
$ localedef --list-archive
$ localectl list-locales

KDE tries to restore your session (and the state of all open programs).

Sep 21 17:10:16 patchouli systemd[1228]: Finished KDE Session Restoration.

The saving may be partially responsible for the delays, try disabling session restore.

Seems unrelated, but good catch.

❯  ~ locale
LANG=en_US.UTF-8
LC_CTYPE=en_US.UTF-8
LC_NUMERIC=en_US.UTF-8
LC_TIME=en_IL.UTF-8
LC_COLLATE=en_US.UTF-8
LC_MONETARY=en_US.UTF-8
LC_MESSAGES=en_US.UTF-8
LC_PAPER=en_US.UTF-8
LC_NAME=en_US.UTF-8
LC_ADDRESS=en_US.UTF-8
LC_TELEPHONE=en_US.UTF-8
LC_MEASUREMENT=en_IL.UTF-8
LC_IDENTIFICATION=en_US.UTF-8
LC_ALL=
❯  ~ localedef --list-archive 
en_IL
en_IL.utf8
en_US.utf8
❯  ~ localectl list-locales 
C.UTF-8
en_IL.UTF-8
en_US.UTF-8

I only uncommented en_US.UTF-8 UTF-8 and the same line for en_IL in locale.gen. My /etc/locale.conf is just like the output of the locale command, but without the LC_ALL= line in the end.

I actually have Session Restore disabled in Plasma since I installed it:

seth wrote:

Sep 21 17:16:45 patchouli systemd[1228]: Stopped KDE Plasma Workspace.
Sep 21 17:16:45 patchouli systemd[1228]: plasma-plasmashell.service: Consumed 2.111s CPU time, 208M memory peak.
Sep 21 17:16:45 patchouli systemd[1228]: Stopping KDE Session Management Server...
Sep 21 17:16:45 patchouli systemd[1228]: Stopped KDE Session Management Server.
Sep 21 17:16:45 patchouli systemd[1228]: Stopping KDE Window Manager...
Sep 21 17:16:45 patchouli kwalletd6[4841]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 17:16:45 patchouli kwalletd6[4841]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 17:16:45 patchouli kwalletd6[4841]: Failed to write to the pipe: Bad file descriptor.
Sep 21 17:16:45 patchouli kwalletd6[4841]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 17:17:03 patchouli systemd[1228]: Stopped KDE Window Manager.
Sep 21 17:17:03 patchouli systemd[1228]: plasma-kwin_wayland.service: Consumed 19.776s CPU time, 116.5M memory peak.
Sep 21 17:17:03 patchouli sddm-helper[4833]: [PAM] Closing session

Looks like kwallet causes this?

Honestly, I don't know if I need KDE Wallet at all. I got rid of KDE Wallet Manager, and disabled it via:

cat ~/.config/kwalletrc    
[Wallet]
Enabled=false

Seems good so far! But I will report back in a bit and mark as solved if it fixed my issue.
Spoke too quick, it's like that again. Here's another updated journal with KDE Wallet gone: http://0x0.st/XYrN.txt
Now I get the same error with kiod6 which doesn't seem nearly as trivial to get rid of, it's a dependency by at least 30 packages I have.

I actually checked again after a reboot, and after about 2 minutes of the computer being on, logging out becomes extremely slow.
It looks like this in the journal:

Sep 21 21:54:41 patchouli systemd[1301]: Stopped KDE Plasma Workspace.
Sep 21 21:54:41 patchouli systemd[1301]: plasma-plasmashell.service: Consumed 3.759s CPU time, 196.5M memory peak.
Sep 21 21:54:41 patchouli systemd[1301]: Stopping KDE Session Management Server...
Sep 21 21:54:42 patchouli systemd[1301]: Stopped KDE Session Management Server.
Sep 21 21:54:42 patchouli systemd[1301]: Stopping KDE Window Manager...
Sep 21 21:54:59 patchouli systemd[1301]: Stopped KDE Window Manager.
Sep 21 21:54:59 patchouli systemd[1301]: plasma-kwin_wayland.service: Consumed 20.666s CPU time, 92.2M memory peak.
Sep 21 21:54:59 patchouli sddm-helper[2409]: [PAM] Closing session
Sep 21 21:54:59 patchouli sddm-helper[2409]: pam_unix(sddm:session): session closed for user patchouli
Sep 21 21:54:59 patchouli sddm-helper[2409]: pam_systemd(sddm:session): New sd-bus connection (system-bus-pam-systemd-2409) opened.
Sep 21 21:55:00 patchouli sddm-helper[2409]: [PAM] Ended.

Note the 17 seconds delay between "Stopping KDE Window Manager" and "Stopped KDE Window Manager". No errors inbetween.
As a side note, I also tried the unstable Plasma repositories with no luck with regards to this issue. So I removed them and synced back to the stable Plasma packages.

Last edited by patchouli (2024-09-21 19:11:44)

seth · 2024-09-21 20:46:50

Because of the locale situation

localectl

The message is from SDDM, so the global config will be more imporant than the locale in your shell.

Sep 21 21:14:37 patchouli systemd[1242]: Stopping KDE Window Manager...
Sep 21 21:14:37 patchouli flameshot[4106]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli flameshot[4106]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 21:14:37 patchouli kiod6[2314]: Failed to write to the pipe: Bad file descriptor.
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 21:14:39 patchouli systemd[1]: Starting Cleanup of Temporary Directories...
Sep 21 21:14:39 patchouli systemd-tmpfiles[5010]: /usr/lib/tmpfiles.d/nut.conf:1: Duplicate line for path "/run/nut", ignoring.
Sep 21 21:14:39 patchouli systemd-tmpfiles[5010]: /usr/lib/tmpfiles.d/nut.conf:2: Duplicate line for path "/var/lib/nut", ignoring.
Sep 21 21:14:39 patchouli systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Sep 21 21:14:39 patchouli systemd[1]: Finished Cleanup of Temporary Directories.
Sep 21 21:14:39 patchouli systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Failed with result 'exit-code'.
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Consumed 2.233s CPU time, 87.9M memory peak.
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.
Sep 21 21:14:55 patchouli systemd[1242]: Stopped KDE Window Manager.

You just installed flameshot and your other journal also has

Sep 21 17:14:38 patchouli kiod6[2407]: Failed to write to the pipe: Bad file descriptor.
Sep 21 17:14:38 patchouli kiod6[2407]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
…
Sep 21 17:14:56 patchouli systemd[1228]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 17:14:56 patchouli systemd[1228]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.

Sep 21 21:00:50 patchouli systemd[1242]: Starting Fuse interface for KIO...
Sep 21 21:00:50 patchouli systemd[1242]: Started Fuse interface for KIO.
Sep 21 21:00:50 patchouli kioworker[2290]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 21 21:00:50 patchouli kioworker[2290]: kf.kio.core: An error occurred during write. The worker terminates now.
Sep 21 21:00:50 patchouli kioexec[2300]: kf.kio.core: Protocol Class of url QUrl("http://0x0.st/XYrr.txt") , isn't ':local', cancelling job.
Sep 21 21:00:51 patchouli systemd[1242]: Created slice Slice /app/dbus-:1.4-org.kde.kioexecd6.
Sep 21 21:00:51 patchouli systemd[1242]: Started dbus-:1.4-org.kde.kioexecd6@0.service.
Sep 21 21:00:51 patchouli kiod6[2314]: kf.kio.kiod: loadModule "kioexecd"
Sep 21 21:00:51 patchouli kioexec[2319]: Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Sep 21 21:09:46 patchouli systemsettings[3450]: kf.kio.filewidgets.kfilefiltercombo: Could not find file filter
Sep 21 21:10:54 patchouli systemsettings[3450]: kf.kio.filewidgets.kfilefiltercombo: Could not find file filter
Sep 21 21:14:37 patchouli systemd[1242]: Stopping Fuse interface for KIO...
Sep 21 21:14:37 patchouli systemd[1]: run-user-1000-kio\x2dfuse\x2dfeTiFU.mount: Deactivated successfully.
Sep 21 21:14:37 patchouli systemd[1242]: Stopped Fuse interface for KIO.
Sep 21 21:14:37 patchouli kiod6[2314]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 21:14:37 patchouli kiod6[2314]: Failed to write to the pipe: Bad file descriptor.
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.

The service gets autogenerated by dbus-broker and probably not properly taken down.
You'll have to look up the exact name in the next session, then try too stop it - see whether that generates any error.
Then try to log out.

patchouli · 2024-09-21 21:19:08

seth wrote:

Because of the locale situation

localectl

The message is from SDDM, so the global config will be more imporant than the locale in your shell.

Sep 21 21:14:37 patchouli systemd[1242]: Stopping KDE Window Manager...
Sep 21 21:14:37 patchouli flameshot[4106]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli flameshot[4106]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 21:14:37 patchouli kiod6[2314]: Failed to write to the pipe: Bad file descriptor.
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 21:14:39 patchouli systemd[1]: Starting Cleanup of Temporary Directories...
Sep 21 21:14:39 patchouli systemd-tmpfiles[5010]: /usr/lib/tmpfiles.d/nut.conf:1: Duplicate line for path "/run/nut", ignoring.
Sep 21 21:14:39 patchouli systemd-tmpfiles[5010]: /usr/lib/tmpfiles.d/nut.conf:2: Duplicate line for path "/var/lib/nut", ignoring.
Sep 21 21:14:39 patchouli systemd[1]: systemd-tmpfiles-clean.service: Deactivated successfully.
Sep 21 21:14:39 patchouli systemd[1]: Finished Cleanup of Temporary Directories.
Sep 21 21:14:39 patchouli systemd[1]: run-credentials-systemd\x2dtmpfiles\x2dclean.service.mount: Deactivated successfully.
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Failed with result 'exit-code'.
Sep 21 21:14:55 patchouli systemd[1242]: app-org.flameshot.Flameshot@0348d24f28394655a4152384d9a4c2e2.service: Consumed 2.233s CPU time, 87.9M memory peak.
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.
Sep 21 21:14:55 patchouli systemd[1242]: Stopped KDE Window Manager.

You just installed flameshot and your other journal also has

Sep 21 17:14:38 patchouli kiod6[2407]: Failed to write to the pipe: Bad file descriptor.
Sep 21 17:14:38 patchouli kiod6[2407]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
…
Sep 21 17:14:56 patchouli systemd[1228]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 17:14:56 patchouli systemd[1228]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.

Sep 21 21:00:50 patchouli systemd[1242]: Starting Fuse interface for KIO...
Sep 21 21:00:50 patchouli systemd[1242]: Started Fuse interface for KIO.
Sep 21 21:00:50 patchouli kioworker[2290]: kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
Sep 21 21:00:50 patchouli kioworker[2290]: kf.kio.core: An error occurred during write. The worker terminates now.
Sep 21 21:00:50 patchouli kioexec[2300]: kf.kio.core: Protocol Class of url QUrl("http://0x0.st/XYrr.txt") , isn't ':local', cancelling job.
Sep 21 21:00:51 patchouli systemd[1242]: Created slice Slice /app/dbus-:1.4-org.kde.kioexecd6.
Sep 21 21:00:51 patchouli systemd[1242]: Started dbus-:1.4-org.kde.kioexecd6@0.service.
Sep 21 21:00:51 patchouli kiod6[2314]: kf.kio.kiod: loadModule "kioexecd"
Sep 21 21:00:51 patchouli kioexec[2319]: Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Sep 21 21:09:46 patchouli systemsettings[3450]: kf.kio.filewidgets.kfilefiltercombo: Could not find file filter
Sep 21 21:10:54 patchouli systemsettings[3450]: kf.kio.filewidgets.kfilefiltercombo: Could not find file filter
Sep 21 21:14:37 patchouli systemd[1242]: Stopping Fuse interface for KIO...
Sep 21 21:14:37 patchouli systemd[1]: run-user-1000-kio\x2dfuse\x2dfeTiFU.mount: Deactivated successfully.
Sep 21 21:14:37 patchouli systemd[1242]: Stopped Fuse interface for KIO.
Sep 21 21:14:37 patchouli kiod6[2314]: The Wayland connection broke. Did the Wayland compositor die?
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Attempting wayland reconnect
Sep 21 21:14:37 patchouli kiod6[2314]: Failed to write to the pipe: Bad file descriptor.
Sep 21 21:14:37 patchouli kiod6[2314]: qt.qpa.wayland: Creating a fake screen in order for Qt not to crash
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 21 21:14:55 patchouli systemd[1242]: dbus-:1.4-org.kde.kioexecd6@0.service: Failed with result 'exit-code'.

The service gets autogenerated by dbus-broker and probably not properly taken down.
You'll have to look up the exact name in the next session, then try too stop it - see whether that generates any error.
Then try to log out.

The global config is just..

❯  ~ cat /etc/locale.conf 
LANG=en_US.UTF-8
LC_CTYPE="en_US.UTF-8"
LC_NUMERIC="en_US.UTF-8"
LC_TIME=en_IL.UTF-8
LC_COLLATE="en_US.UTF-8"
LC_MONETARY="en_US.UTF-8"
LC_MESSAGES="en_US.UTF-8"
LC_PAPER="en_US.UTF-8"
LC_NAME="en_US.UTF-8"
LC_ADDRESS="en_US.UTF-8"
LC_TELEPHONE="en_US.UTF-8"
LC_MEASUREMENT=en_IL.UTF-8
LC_IDENTIFICATION="en_US.UTF-8"

I don't know where C.UTF-8 is even coming from. I don't remember setting it up at all, just the US and IL locales for English.

And about the service.. I'm confused. Are you referring to the Flameshot service? Because I just installed it today in place of Spectacle and I've had the slow log-out issue regardless of either apps. It seems to throw that message in the journal as long as I take a screenshot using a Flameshot keybind while the Flameshot configurator app is open in background. I don't think it's related and I should probably report as a bug to Flameshot instead.
If you're talking about the kioexecd6 service, I cannot find it running on another boot.

seth · 2024-09-21 21:41:57

Are you referring to the Flameshot service?

Nope, you only just installed flameshot, so it's not the casue.
But there's a constant pattern around "dbus-:1.4-org.kde.kioexecd6@0.service" (but the name is generic and can change between boots)

I cannot find it running on another boot.

It's going to be a user service and if it's not there (doesn't yet show up in the journal at all) you might be able to log out w/o delay as consequence.
It was triggered last time when you tried to access http://0x0.st/XYrr.txt using some KDE program.

patchouli · 2024-09-22 11:26:25

seth wrote:

Are you referring to the Flameshot service?
Nope, you only just installed flameshot, so it's not the casue.
But there's a constant pattern around "dbus-:1.4-org.kde.kioexecd6@0.service" (but the name is generic and can change between boots)
I cannot find it running on another boot.
It's going to be a user service and if it's not there (doesn't yet show up in the journal at all) you might be able to log out w/o delay as consequence.
It was triggered last time when you tried to access http://0x0.st/XYrr.txt using some KDE program.

No, doesn't seem to be the case.
For testing purposes I booted up my PC, left it idle on the SDDM login window for about an hour, came back, logged in and it hung for about 12 seconds before KDE Plasma started loading. Then, I immediately logged out without running any app or any shortcut, and it hung again.
Here's another cleaner journal which I captured from a TTY so it is less bloated: https://0x0.st/XYH8.txt
I also tried GDM rather than SDDM and it didn't solve it, so I'm back on SDDM.

Last edited by patchouli (2024-09-22 13:50:47)

seth · 2024-09-22 14:57:31

Sep 22 14:13:00 patchouli plasmashell[1569]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot read property 'screenGeometry' of null
…
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KActivityManager Activity manager Service.
Sep 22 14:13:00 patchouli systemd[1362]: dbus-:1.4-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 22 14:13:00 patchouli systemd[1362]: dbus-:1.4-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
…
Sep 22 14:13:00 patchouli plasmashell[1569]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot read property 'plasmoid' of undefined
…
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KDE Plasma Workspace.
Sep 22 14:13:00 patchouli systemd[1362]: plasma-plasmashell.service: Consumed 1.386s CPU time, 222.3M memory peak.
Sep 22 14:13:00 patchouli systemd[1362]: Stopping KDE Session Management Server...
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KDE Session Management Server.
Sep 22 14:13:00 patchouli systemd[1362]: Stopping KDE Window Manager...
Sep 22 14:13:18 patchouli systemd[1362]: Stopped KDE Window Manager.
Sep 22 14:13:18 patchouli systemd[1362]: plasma-kwin_wayland.service: Consumed 5.194s CPU time, 104.1M memory peak.

There's this weird 18s gap after the logout prompt (don't you get one?) failed and something™ seems to try to send a notification (what fails because plasma-shell is/has died)

What happens if you install and pre-start dunst (on X11) to hopefully catch that notification?
nb. https://bbs.archlinux.org/viewtopic.php … 9#p2197169

patchouli · 2024-09-22 16:06:10

seth wrote:

Sep 22 14:13:00 patchouli plasmashell[1569]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:136: TypeError: Cannot read property 'screenGeometry' of null
…
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KActivityManager Activity manager Service.
Sep 22 14:13:00 patchouli systemd[1362]: dbus-:1.4-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE
Sep 22 14:13:00 patchouli systemd[1362]: dbus-:1.4-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'.
…
Sep 22 14:13:00 patchouli plasmashell[1569]: file:///usr/share/plasma/plasmoids/org.kde.plasma.notifications/contents/ui/global/Globals.qml:250: TypeError: Cannot read property 'plasmoid' of undefined
…
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KDE Plasma Workspace.
Sep 22 14:13:00 patchouli systemd[1362]: plasma-plasmashell.service: Consumed 1.386s CPU time, 222.3M memory peak.
Sep 22 14:13:00 patchouli systemd[1362]: Stopping KDE Session Management Server...
Sep 22 14:13:00 patchouli systemd[1362]: Stopped KDE Session Management Server.
Sep 22 14:13:00 patchouli systemd[1362]: Stopping KDE Window Manager...
Sep 22 14:13:18 patchouli systemd[1362]: Stopped KDE Window Manager.
Sep 22 14:13:18 patchouli systemd[1362]: plasma-kwin_wayland.service: Consumed 5.194s CPU time, 104.1M memory peak.

There's this weird 18s gap after the logout prompt (don't you get one?) failed and something™ seems to try to send a notification (what fails because plasma-shell is/has died)

What happens if you install and pre-start dunst (on X11) to hopefully catch that notification?
nb. https://bbs.archlinux.org/viewtopic.php … 9#p2197169

I do get a logout prompt, it looks like this:

After I click on "logout", it either hangs on the same screen for the 15~ ish seconds, or a few frames afterwards where the Plasma UI starts disappearing. I'll try dunst hopefully tomorrow and reply back

seth · 2024-09-22 19:11:12

Assuming this still works w/ plasma 6, can you logout immediately when skipping that dialog?
https://discuss.kde.org/t/logout-reboot … rminal/743

patchouli · 2024-10-01 10:03:19

seth wrote:

Assuming this still works w/ plasma 6, can you logout immediately when skipping that dialog?
https://discuss.kde.org/t/logout-reboot … rminal/743

Doesn't work, but this does:

qdbus org.kde.Shutdown /Shutdown org.kde.Shutdown.logout

Does not cause an immediate logout either unfortunately

seth · 2024-10-01 11:46:29

Does it still show the dialog (first)?
The idea was to bypass that thing and see whether the direct invocation still stalls.
If the dbus call bypasses the dialog, we should take a look at the jorunal for the remaining stall.

patchouli · 2024-10-11 10:04:16

It doesn't show the dialog first no, just an immediate logout (well, it hangs for at least 10 seconds before that; but there's no dialogue).

I went out of my way and did some extra testing with other compositors as well (GNOME, COSMIC Alpha, Hyprland) and they all have the same problem. I'm thinking maybe it's related to using an NVIDIA GPU & the proprietary NVIDIA drivers, as I cannot reproduce this on my other system with an AMD APU no matter what. It's definitely unrelated to SDDM because I get the same problem if I launch a TTY and start the compositor directly from there without using a login manager.
I also noticed that the time it takes to log out from a DE/WM session is about the same time it takes to go from a graphic session to TTY or vice-versa.

Maybe there's some possible workaround? Or I might've configured something wrong because I can't really see many complaints about this issue when I Google it.

Last edited by patchouli (2024-10-11 10:07:02)

patchouli · 2024-10-24 15:23:44

I solved this.

I had an xorg server running. And apparently switching between TTYs while an Xorg server is running is horrendously slow on my system.
My xorg server was running on the SDDM TTY. Frankly I also had the issue when logging out of X11 DEs. SDDM runs in its own TTY all the time.

Followed this part of the wiki to make use of the experimental Wayland support of SDDM, and now my logouts are immediate: https://wiki.archlinux.org/title/SDDM#Wayland

seth · 2024-10-24 15:27:30

And apparently switching between TTYs while an Xorg server is running is horrendously slow on my system.

That's somewhat par for the course on nvidia systems (takes about a second), but 10s and when shutting down the X11 server is kinda new

Arch Linux

#1 2024-09-18 16:19:43

[SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#2 2024-09-19 08:00:02

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#3 2024-09-19 09:07:35

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#4 2024-09-19 09:22:12

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#5 2024-09-19 09:52:17

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#6 2024-09-21 12:20:45

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#7 2024-09-21 13:24:51

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#8 2024-09-21 14:14:40

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#9 2024-09-21 14:19:54

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#10 2024-09-21 14:53:47

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#11 2024-09-21 15:12:36

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#12 2024-09-21 18:06:30

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#13 2024-09-21 20:46:50

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#14 2024-09-21 21:19:08

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#15 2024-09-21 21:41:57

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#16 2024-09-22 11:26:25

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#17 2024-09-22 14:57:31

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#18 2024-09-22 16:06:10

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#19 2024-09-22 19:11:12

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#20 2024-10-01 10:03:19

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#21 2024-10-01 11:46:29

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#22 2024-10-11 10:04:16

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#23 2024-10-24 15:23:44

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

#24 2024-10-24 15:27:30

Re: [SOLVED] Slow log-out from DE to display manager on both X11/Wayland

Board footer