Window freezes when user switches to garuda

Issues & Assistance KDE
1

I don’t know how to write about a glitch in the kde bug report, but when you click switch user (and I have only one) in the running garuda and on another distribution, Arch also checked, you don’t change the login, but you change the Wayland interface to X11 or vice versa, then no Having managed to log into the system, the login window freezes and only resetting the PC helps.

garuda-inxi
System:
Kernel: 6.8.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=8d024738-0c86-44cf-8e50-cf9b720d6939 rw rootflags=subvol=@
quiet resume=UUID=4cad94ff-4c56-4c19-8602-e2f6b377d041 loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
wm: kwin_wayland vt: 1 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop System: Micro-Star product: MS-7B89 v: 1.0
serial: <superuser required>
Mobo: Micro-Star model: B450M MORTAR MAX (MS-7B89) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 2.H0 date: 07/27/2022
CPU:
Info: model: AMD Ryzen 5 3600 bits: 64 type: MT MCP arch: Zen 2 gen: 3
level: v3 note: check built: 2020-22 process: TSMC n7 (7nm)
family: 0x17 (23) model-id: 0x71 (113) stepping: 0 microcode: 0x8701021
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache:
L1: 384 KiB desc: d-6x32 KiB; i-6x32 KiB L2: 3 MiB desc: 6x512 KiB
L3: 32 MiB desc: 2x16 MiB
Speed (MHz): avg: 2550 high: 3600 min/max: 2200/4208 boost: enabled
scaling: driver: acpi-cpufreq governor: schedutil cores: 1: 2200 2: 3600
3: 2200 4: 2200 5: 2200 6: 2200 7: 2200 8: 3600 9: 2200 10: 2200 11: 3600
12: 2200 bogomips: 86400
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities: <filter>
Graphics:
Device-1: NVIDIA TU106 [GeForce RTX 2060 SUPER] vendor: ASUSTeK
driver: nvidia v: 550.76 alternate: nouveau,nvidia_drm non-free: 550.xx+
status: current (as of 2024-04; EOL~2026-12-xx) arch: Turing code: TUxxx
process: TSMC 12nm FF built: 2018-2022 pcie: gen: 3 speed: 8 GT/s
lanes: 16 ports: active: none off: HDMI-A-2 empty: DP-1, DP-2, HDMI-A-1,
Unknown-2 bus-ID: 26:00.0 chip-ID: 10de:1f47 class-ID: 0300
Display: wayland server: X.org v: 1.21.1.13 with: Xwayland v: 23.2.6
compositor: kwin_wayland driver: X: loaded: nvidia unloaded: modesetting
alternate: fbdev,nouveau,nv,vesa gpu: nvidia display-ID: 0
Monitor-1: HDMI-A-2 res: 1920x1080 size: N/A modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2
drv: swrast gbm: drv: nvidia surfaceless: drv: nvidia wayland: drv: nvidia
x11: drv: zink inactive: device-1
API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: nvidia mesa v: 550.76
glx-v: 1.4 direct-render: yes renderer: NVIDIA GeForce RTX 2060
SUPER/PCIe/SSE2 memory: 7.81 GiB display-ID: :1.0
API: Vulkan v: 1.3.279 layers: 6 device: 0 type: discrete-gpu name: NVIDIA
GeForce RTX 2060 SUPER driver: nvidia v: 550.76 device-ID: 10de:1f47
surfaces: xcb,xlib,wayland device: 1 type: cpu name: llvmpipe (LLVM
17.0.6 256 bits) driver: mesa llvmpipe v: 24.0.6-arch1.2 (LLVM 17.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib,wayland
Audio:
Device-1: NVIDIA TU106 High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel pcie: gen: 3 speed: 8 GT/s lanes: 16
bus-ID: 26:00.1 chip-ID: 10de:10f9 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel pcie: gen: 4 speed: 16 GT/s lanes: 16
bus-ID: 28:00.4 chip-ID: 1022:1487 class-ID: 0403
Device-3: Kingston HyperX 7.1 Audio
driver: hid-generic,snd-usb-audio,usbhid type: USB rev: 2.0 speed: 12 Mb/s
lanes: 1 mode: 1.1 bus-ID: 1-1:2 chip-ID: 0951:16a4 class-ID: 0300
serial: <filter>
API: ALSA v: k6.8.8-zen1-1-zen status: kernel-api with: aoss
type: oss-emulator tools: alsactl,alsamixer,amixer
Server-1: PipeWire v: 1.0.5 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
4: pw-jack type: plugin tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet
vendor: Micro-Star MSI driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s
lanes: 1 port: f000 bus-ID: 22:00.0 chip-ID: 10ec:8168 class-ID: 0200
IF: enp34s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Info: services: NetworkManager,systemd-timesyncd
Drives:
Local Storage: total: 1.47 TiB used: 518.95 GiB (34.4%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: AMD Radeon model: R5MP120G8
size: 111.79 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
lanes: 4 tech: SSD serial: <filter> fw-rev: T1103F0L temp: 42.9 C
scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:5 vendor: Western Digital
model: WD BLACK SN750 SE 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 63.2 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 711250WD temp: 38.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: Western Digital
model: WD10EZEX-75WN4A0 size: 931.51 GiB block-size: physical: 4096 B
logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: 1A01 scheme: GPT
Partition:
ID-1: / raw-size: 48.83 GiB size: 48.83 GiB (100.00%)
used: 37.37 GiB (76.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
ID-2: /boot/efi raw-size: 1.47 GiB size: 1.46 GiB (99.80%)
used: 584 KiB (0.0%) fs: vfat dev: /dev/nvme1n1p1 maj-min: 259:6
ID-3: /home raw-size: 399.84 GiB size: 399.84 GiB (100.00%)
used: 340.19 GiB (85.1%) fs: btrfs dev: /dev/nvme1n1p4 maj-min: 259:9
ID-4: /var/log raw-size: 48.83 GiB size: 48.83 GiB (100.00%)
used: 37.37 GiB (76.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
ID-5: /var/tmp raw-size: 48.83 GiB size: 48.83 GiB (100.00%)
used: 37.37 GiB (76.5%) fs: btrfs dev: /dev/nvme1n1p2 maj-min: 259:7
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.54 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo,lzo-rle,lz4,lz4hc,842 max-streams: 12 dev: /dev/zram0
ID-2: swap-2 type: partition size: 15.62 GiB used: 0 KiB (0.0%)
priority: -2 dev: /dev/nvme1n1p3 maj-min: 259:8
Sensors:
System Temperatures: cpu: 44.4 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB available: 15.54 GiB used: 3.94 GiB (25.4%)
Processes: 375 Power: uptime: 12m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.16 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 255 default: graphical
tool: systemctl
Packages: 2026 pm: pacman pkgs: 2010 libs: 523
tools: octopi,pamac,paru,yay pm: flatpak pkgs: 16 Compilers: clang: 17.0.6
gcc: 13.2.1 Shell: garuda-inxi default: fish v: 3.7.1 running-in: konsole
inxi: 3.3.34
Garuda (2.6.26-1):
System install date:     2024-02-21
Last full system update: 2024-05-01
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut nvidia-dkms
Windows dual boot:       Probably (Run as root to verify)
Failed units:
2
  • After rebooting, post the FULL output of garuda-inxi in the body of the post (not linked externally, or collapsed with the “hide details” feature)
3

Looks like I did as asked. But that’s a lot of letters. I just wanted to hide it under a spoiler.
But this is a problem not only for garuda, I think, but for the entire arch. I installed a fresh cachy os system, did the same operation and it also froze.

4

Looks much better if you use preformatted text as requested in the template (fixed that for you)

1 Like
5

Thank you.
I’m just not good at English and have to translate every text into Russian. And I don’t know how to format the text either. It could be formatted automatically and inserted ready for the post.
But I hope the bug will be fixed.

6

Please write a program for the forum software that reads the user’s thoughts and thus knows that the entries should be formatted or unformatted.

But wait, there is a Garuda App, Assistant, that do that for you.
But in forum you have to do all by yourself

Copy that for your next help request

-Недостаточная информация, указанная в шаблоне, может привести к отказу в получении помощи

Перед отправкой сообщения убедитесь, что вы сделали следующее:

Проблема все еще не решена? Тогда

  • ОДИН вопрос в каждой теме.
    -Подробно опишите свою проблему.
    Чем больше мы знаем, тем лучше сможем помочь.

  • Покажите нам результаты ваших поисков и то, что вы пробовали.

  • После перезагрузки опубликуйте ПОЛНЫЙ результат работы garuda-inxi в теле сообщения (без внешних ссылок или свернутых с помощью функции “скрыть детали”)

  • Оформите вывод терминала (включая ваш garuda-inxi) как блок кода, нажав на кнопку форматированного текста (</>), или поставьте три тильды (~) над и под текстом

Без garuda-inxi этот запрос будет перемещен в 412 Precondition Failed

Переведено с помощью DeepL.com (бесплатная версия)

1 Like
7

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.