System freezes when switching users

Hi,

I have a recent laptop with an equally recent Manjaro KDE install (everything stock.) I have an account set up on my laptop for every family member as well as a “gaming” account.

When I switch users the system frequently hangs and I need to hard reset. Sometimes by mashing the ctrl-alt-f1-f2-f3 b buttons I can get a terminal and reboot the computer with a command.

I saw a similar post: KDE plasma issues logging in, shutting down and restarting - #3 by michaldybczak but the proposed fix (using a foreign SDDM package) did not help.

Perhaps this will;

Please see the items listed under Known issues and solutions of Stable Update 2024-10-10.

Specifically, look for the following heading:

  • KDE Plasma hangs on Shutdown, Restart and Logout

To save you having to search too much, the workaround is to change your session settings:

System SettingsSessionDesktop SessionSession Restore:

Change “On login, launch apps that were open” to:

  • Start with an empty session

Edit:- You may need to do this for every User of the system.

Regards.


As an infrequent forum user, please take some time to familiarise yourself with Forum requirements; in particular, the many ways to use the forum to your benefit:

Last, but not least, the Update Announcements, which you should check frequently for important update related information.

An issue may be directly related to a particular update; these announcements should generally be checked before posting a request for support.

I hope this is helpful. Cheers.


2 Likes

Hi thanks fot the quick reply and the tips! I implemented the situation you proposed for all users but it did not work. I am able to reproduce the problem however.

Reproducing the problem

  1. Log in as user A.
  2. As user A, switch user → Brought to the login screen → Select and log in as user B.
  3. As user B, switch user → Brought to the login screen → Select and log in as user A.
  4. At this point I have persistent black screen.
  5. Press ctrl-alt-F1. I’m brought to a screen for user B prompting for a password. I’m able to log back in as user B.
  6. As user B, log out. This brings me back to login screen.
  7. Select user A, log in, everything works.

I don’t believe this is the expected behaviour and to my best knowledge this hasn’t been reported yet. I do not have any ideas how to troubleshoot this.

Note This problem started when I was using X11. Switching to Wayland didn’t fix the problem, however after the switch ctrl-alt-F1 became more useful.

Post full system info:
inxi -zav7

and how do you switch users? you select the ‘log out’ or ‘switch user’ in the application menu?

Hi Brahma,

and how do you switch users? you select the ‘log out’ or ‘switch user’ in the application menu?

I always use the application menu. If I select log out there are no problems. If I use switch user twice to move to a new user and then back, then I have issues.

Post full system info:
inxi -zav7

Here it is:

System:
  Kernel: 6.6.54-2-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.6-x86_64
    root=UUID=f2a53fbe-7c5a-4c59-b7bb-0283c09c923b rw quiet splash
    resume=UUID=564efdca-2a1f-4f06-9952-ce8e92d9caed udev.log_priority=3
  Desktop: KDE Plasma v: 6.1.5 tk: Qt v: N/A info: frameworks v: 6.6.0
    wm: kwin_wayland vt: 1 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: Dell product: Precision 3480 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 0PPNXG v: A01 serial: <superuser required> part-nu: 0C02
    uuid: <superuser required> UEFI: Dell v: 1.9.1 date: 11/07/2023
Battery:
  ID-1: BAT0 charge: 47.2 Wh (87.4%) condition: 54.0/54.0 Wh (100.1%)
    volts: 12.2 min: 11.4 model: BYD DELL KDM9P3B type: Li-poly serial: <filter>
    status: discharging cycles: 142
Memory:
  System RAM: total: 16 GiB available: 15.28 GiB used: 5.31 GiB (34.7%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 1 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: DIMM A type: no module installed
  Device-2: DIMM B type: DDR5 detail: synchronous size: 16 GiB speed:
    spec: 5600 MT/s actual: 5200 MT/s volts: curr: 1 width (bits): data: 64
    total: 64 manufacturer: 80AD000080AD part-no: HMCG78AGBSA092N
    serial: <filter>
CPU:
  Info: model: 13th Gen Intel Core i7-1370P bits: 64 type: MST AMCP
    arch: Raptor Lake level: v3 note: check built: 2022+ process: Intel 7 (10nm)
    family: 6 model-id: 0xBA (186) stepping: 2 microcode: 0x4122
  Topology: cpus: 1x dies: 1 clusters: 8 cores: 14 threads: 20 mt: 6 tpc: 2
    st: 8 smt: enabled cache: L1: 1.2 MiB desc: d-8x32 KiB, 6x48 KiB; i-6x32
    KiB, 8x64 KiB L2: 11.5 MiB desc: 6x1.2 MiB, 2x2 MiB L3: 24 MiB
    desc: 1x24 MiB
  Speed (MHz): avg: 400 min/max: 400/5000:5200:3900 scaling:
    driver: intel_pstate governor: powersave cores: 1: 400 2: 400 3: 400 4: 400
    5: 400 6: 400 7: 400 8: 400 9: 400 10: 400 11: 400 12: 400 13: 400 14: 400
    15: 400 16: 400 17: 400 18: 400 19: 400 20: 400 bogomips: 87580
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts clflush clflushopt clwb cmov constant_tsc cpuid cpuid_fault cx16 cx8
    de ds_cpl dtes64 dtherm dts epb ept ept_ad erms est f16c flexpriority
    flush_l1d fma fpu fsgsbase fsrm fxsr gfni hfi ht hwp hwp_act_window
    hwp_epp hwp_notify hwp_pkg_req ibpb ibrs ibrs_enhanced ibt ida intel_pt
    invpcid lahf_lm lm mca mce md_clear mmx monitor movbe movdir64b movdiri
    msr mtrr nonstop_tsc nopl nx ospke pae pat pbe pclmulqdq pconfig pdcm
    pdpe1gb pebs pge pku pln pni popcnt pse pse36 pts rdpid rdrand rdseed
    rdtscp rep_good sdbg sep serialize sha_ni smap smep smx split_lock_detect
    ss ssbd sse sse2 sse4_1 sse4_2 ssse3 stibp syscall tm tm2 tme tpr_shadow
    tsc tsc_adjust tsc_deadline_timer tsc_known_freq umip user_shstk vaes vme
    vmx vnmi vpclmulqdq vpid waitpkg x2apic xgetbv1 xsave xsavec xsaveopt
    xsaves xtopology xtpr
  Vulnerabilities:
  Type: gather_data_sampling status: Not affected
  Type: itlb_multihit status: Not affected
  Type: l1tf status: Not affected
  Type: mds status: Not affected
  Type: meltdown status: Not affected
  Type: mmio_stale_data status: Not affected
  Type: reg_file_data_sampling mitigation: Clear Register File
  Type: retbleed status: Not affected
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: Enhanced / Automatic IBRS; IBPB:
    conditional; RSB filling; PBRSB-eIBRS: SW sequence; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Raptor Lake-P [UHD Graphics] vendor: Dell driver: i915
    v: kernel arch: Gen-13 process: Intel 7 (10nm) built: 2022+ ports:
    active: eDP-1 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 0000:00:02.0
    chip-ID: 8086:a720 class-ID: 0300
  Device-2: NVIDIA GA107GLM [RTX A500 Laptop GPU] vendor: Dell
    driver: nvidia v: 550.120 alternate: nouveau,nvidia_drm non-free: 550.xx+
    status: current (as of 2024-09; EOL~2026-12-xx) arch: Ampere code: GAxxx
    process: TSMC n7 (7nm) built: 2020-2023 bus-ID: 0000:01:00.0
    chip-ID: 10de:25bb class-ID: 0302
  Device-3: Realtek Integrated_Webcam_FHD driver: uvcvideo type: USB
    rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-6:2 chip-ID: 0bda:5577
    class-ID: fe01 serial: <filter>
  Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
    compositor: kwin_wayland driver: X: loaded: modesetting,nvidia
    unloaded: nouveau alternate: fbdev,nv,vesa dri: iris gpu: i915,nvidia
    display-ID: 0
  Monitor-1: eDP-1 res: 1745x982 size: N/A modes: N/A
  API: EGL v: 1.5 hw: drv: intel iris drv: nvidia platforms: device: 0
    drv: nvidia device: 1 drv: iris device: 3 drv: swrast gbm: drv: iris
    surfaceless: drv: nvidia wayland: drv: iris x11: drv: iris
    inactive: device-2
  API: OpenGL v: 4.6.0 compat-v: 4.5 vendor: intel mesa v: 24.2.4-arch1.0.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (RPL-P)
    device-ID: 8086:a720 memory: 7.46 GiB unified: yes display-ID: :1.0
  API: Vulkan v: 1.3.295 layers: 1 device: 0 type: discrete-gpu name: NVIDIA
    RTX A500 Laptop GPU driver: nvidia v: 550.120 device-ID: 10de:25bb
    surfaces: xcb,xlib,wayland device: 1 type: integrated-gpu
    name: Intel Graphics (RPL-P) driver: mesa intel v: 24.2.4-arch1.0.1
    device-ID: 8086:a720 surfaces: xcb,xlib,wayland
Audio:
  Device-1: Intel Raptor Lake-P/U/H cAVS vendor: Dell driver: snd_hda_intel
    v: kernel alternate: snd_sof_pci_intel_tgl bus-ID: 0000:00:1f.3
    chip-ID: 8086:51ca class-ID: 0403
  API: ALSA v: k6.6.54-2-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: sndiod v: N/A status: off tools: aucat,midicat,sndioctl
  Server-2: JACK v: 1.9.22 status: off tools: N/A
  Server-3: PipeWire v: 1.2.5 status: active with: 1: pipewire-pulse
    status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
    tools: pactl,pw-cat,pw-cli,wpctl
Network:
  Device-1: Intel Raptor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 0000:00:14.3 chip-ID: 8086:51f1 class-ID: 0280
  IF: wlp0s20f3 state: up mac: <filter>
  IP v4: <filter> type: dynamic noprefixroute scope: global
    broadcast: <filter>
  IP v6: <filter> type: noprefixroute scope: link
  Device-2: Intel Ethernet I219-LM vendor: Dell driver: e1000e v: kernel
    port: N/A bus-ID: 0000:00:1f.6 chip-ID: 8086:0dc5 class-ID: 0200
  IF: enp0s31f6 state: down mac: <filter>
  Info: services: NetworkManager, sshd, systemd-timesyncd, wpa_supplicant
  WAN IP: <filter>
Bluetooth:
  Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
    speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 3-10:3 chip-ID: 8087:0033
    class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 0 state: up address: see --recommends
Logical:
  Message: No logical block device data found.
RAID:
  Hardware-1: Intel Volume Management Device NVMe RAID Controller Intel
    driver: vmd v: 0.6 port: N/A bus-ID: 0000:00:0e.0 chip-ID: 8086:a77f rev:
    class-ID: 0104
Drives:
  Local Storage: total: 476.94 GiB used: 384.16 GiB (80.5%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: BC901 NVMe 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 51006151 temp: 41.9 C
    scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 459.83 GiB size: 451.54 GiB (98.20%)
    used: 384.14 GiB (85.1%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
    label: N/A uuid: f2a53fbe-7c5a-4c59-b7bb-0283c09c923b
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 380 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: 81E3-94FC
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 16.81 GiB used: 27 MiB (0.2%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3 label: swap
    uuid: 564efdca-2a1f-4f06-9952-ce8e92d9caed
Unmounted:
  Message: No unmounted partitions found.
USB:
  Hub-1: 1-0:1 info: hi-speed hub with single TT ports: 1 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Hub-2: 2-0:1 info: super-speed hub ports: 2 rev: 3.1
    speed: 20 Gb/s (2.33 GiB/s) lanes: 2 mode: 3.2 gen-2x2 chip-ID: 1d6b:0003
    class-ID: 0900
  Hub-3: 3-0:1 info: hi-speed hub with single TT ports: 12 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 1d6b:0002
    class-ID: 0900
  Device-1: 3-6:2 info: Realtek Integrated_Webcam_FHD type: video
    driver: uvcvideo interfaces: 3 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s)
    lanes: 1 mode: 2.0 power: 500mA chip-ID: 0bda:5577 class-ID: fe01
    serial: <filter>
  Device-2: 3-10:3 info: Intel AX211 Bluetooth type: bluetooth driver: btusb
    interfaces: 2 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 8087:0033 class-ID: e001
  Hub-4: 4-0:1 info: super-speed hub ports: 4 rev: 3.1
    speed: 10 Gb/s (1.16 GiB/s) lanes: 1 mode: 3.2 gen-2x1 chip-ID: 1d6b:0003
    class-ID: 0900
Sensors:
  System Temperatures: cpu: 43.0 C mobo: 31.0 C sodimm: Mem C
  Fan Speeds (rpm): cpu: 2003
Info:
  Processes: 382 Power: uptime: 2h 35m states: freeze,mem,disk suspend: s2idle
    wakeups: 1 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 6.1 GiB services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 256 default: graphical tool: systemctl
  Packages: pm: dpkg pkgs: 0 pm: pacman pkgs: 2017 libs: 421 tools: pamac
    pm: rpm pkgs: 0 pm: flatpak pkgs: 0 Compilers: clang: 18.1.8 gcc: 14.2.1
    Shell: Zsh v: 5.9 default: Bash v: 5.2.37 running-in: konsole inxi: 3.3.36

so i and also another user on this forum i was helping have the same issue, if i select switch user from the application menu, i got stuck, if i use log out everything works… first time i noticed it was probably over a year ago, but since i dont use multiple users its not an issue for me…
it was an issue with kde and wayland, but i dont know if it was resolved…
try switching to x11 and see if it works there…

Please try this method generally:

  • Log in as user A.
  • As user A, switch user and log in as user B.
  • When finished using user B, logout from user B.

I do not use multiple accounts, however, if I understand correctly:

When you switch user to B, user A remains logged in; and if you attempt to then switch user (again) and login to A it will fail. Concurrent logged in users are possible, but the same user cannot be logged in twice.

If my understanding is in any way flawed I’m sure someone will correct me.

2 Likes

Maybe not in the most recent version of Plasma, but it used to be possible in earlier iterations, and it is still possible anywhere else on the system. You can easily log in multiple times at several virtual consoles, and if you use su, you can even nest multiple logins.

3 Likes

This is exactly how I understand it, but why does the login manager not detect the “target” user session is already running (effectively in a “lock-screen state” as I (probably mis-)interpret it?) and switch to that instead of attempting to open a second? :thinking:

Addendum: I have not encountered this issue so far but rarely switch users. Will post if this happens here.

I suggest you consider updating system BIOS
Dell Precision 3480 and Latitude 5440 System BIOS

Hi @soundofthunder,

Thanks for your reply.

Please try this method generally:

  • Log in as user A.
  • As user A, switch user and log in as user B.
  • When finished using user B, logout from user B.

Yes, this method indeed works. But it defeats the functionality I need. Here is my situation:

I have a laptop I bring home from work and my kids use it for homework. I’ve created separate accounts for my kids.

When my kid takes my laptop, it’s usually suspended and my screen is locked, but they can log in as themselves. Now maybe my kid takes a break and I want to log back into my account and write a quick email. I don’t want to log them out because they have a bunch of browser windows open for their schoolwork.

Is there a way to achieve this? I’m starting to see that switch user doesn’t seem to want to “switch back” to a previously opened (and currently running) session.

@brahma, thanks for your reply.

so i and also another user on this forum i was helping have the same issue, if i select switch user from the application menu, i got stuck, if i use log out everything works…

Yes this is exactly my issue.

try switching to x11 and see if it works there…

This issue was already present with x11. When I switched to Wayland it actually got better because when I hit ctrl-alt-F1, I actually get to a login window that can get me untangled. With x11, my only option was a hard reset.

@Aragorn, @BG405 Right, so maybe switch user doesn’t do what I think it does. It would be nice to be able to flip between concurrently open sessions.

If your prime concern is not to inconvenience other users, perhaps adopt a habit of logging out of your own account rather than leaving it to suspend and lock. In this way you only need to switch user, do your thing, logout, and switch back to the kid’s session.

I feel that might workaround the issue without much fuss. :eyes:


Musing:

There are frequent issues concerning black screens (mainly, they seem to be Nvidia related); Search: black screen.

It’s possible that the black screen you observe isn’t strictly a consequence of user switching, and may be related to one of many other issues.

If you happen to experience other black screens in different circumstances, even occasionally, it might be worth searching though those search results to see if any might be applicable to your environment.


Otherwise :man_shrugging:

Then, that certainly opens an avenue of research.

I haven’t used an Nvidia (anything) for at least a decade, and my graphics issues have been few and far between (using AMD graphics). Most graphic issues I see seem to be Nvidia; that said, there are always exceptions; some claim to be equally as troublefree.


I would suggest not dismissing the reminder given by @nikgnomic previously about the BIOS update. Updating a BIOS can often solve issues you might not even be aware of.

UEFI BIOS v1.18.1
was released on 2024-11-12 and is marked as critical.

@soundofthunder,

Wait! It’s not an nvidia thing!

I have an older laptop. Also a Dell laptop with KDE+Manjaro. Everything worked as it should… but the system was way out of date (okay a couple months) so I updated via pacman -Syu.

After the update the switch user is now broken on both my laptops. With the non-nvidia laptop instead of a black screen I get a “manjaro” screen with a spinning thing that stops spinning. Again ctrl-alt-F1 gets me to log back in.

After the update switch user no longer immediately brings me to the option to log in to a concurrently opened session.

If the built-in user switching is indeed broken in this iteration of Plasma — and mind you that Plasma 6.2 is just around the corner, probably arriving in the Stable branch in little over a week — then there is obviously no way to make it work now.

However, there is a workaround, i.e. have your children log into a tty, and have their login automatically start a new session on that tty. It’ll require some scripting trickery in their ~/.bashrc or ~/.zshrc, but it’s doable.

1 Like

i tested it yesterday and have still the issue … cant switch if i use the switch user option, instead of the log off…
just use the log off option in the mean time, until its fixed…
you can also provide logs, from when the issue happens, maybe something will be there:
journalctl -b0 -p5 --no-pager

I’ve found a workaround. It’s using different TTYs as you probably know, will update later when I get home if I think of anything else.

It appears that the primary user’s DE gets switched to TTY1 when a second user logs into a GUI environment (this doesn’t happen with regular TTY logins as far as I know). I’ve usually found it on one of the others (2 or 3?). Maybe this is a clue.

Basically, if I log in as another user, I can switch between them with CTRL + ALT + F… to switch between the logged in users and it doesn’t seem to matter if one has “timed-out” presenting the login screen, in the meantime, upon switching.

I enter the password, it opens. But, there is one TTY which shows a “non-responsive” login screen for the second user. Ignore that; it goes away when the second user is logged out.

I’m sure that’s not how it works in e,g. Xfce, Cinnamon etc.? seems to work as you’d expect it to there.

Edit:
I did have an issue with the log-in screen not functioning correctly when testing this, due to still having an old incompatible theme applied. Fixed by switching to Breath and Breath Dark accordingly, this fixed it.

I was suggesting only that an Nvidia issue might possibly be contributing (in some as yet undetermined way). Likewise the System freeze on suspend issue (apparently caused by a new systemd feature) might also have been contributing. These are guesses, at best.


As it seems apparent that others are now experiencing the same issue, the best that can be done is to wait for the condition to be officially acknowledged and fixed (possibly by KDE).

In the meantime, workarounds have been presented that should minimise the discomfort to some degree.


Updating your BIOS stands as a worthwhile suggestion, regardless.

Good luck.

1 Like

Thank you all for your input. I also ended up updating my BIOS, since that is indeed a good idea.

I think I’ll just have to wait until KDE Updates. As a matter of personal taste, I’m not a fan of the proposed workarounds as they seem too “hacky” to me.

I have the manjaro-downgrade package installed. Could anybody provide me guidance to revert to an earlier version of KDE with the working functionality? I attempted this once by downgrading plasma-desktop, but the result wasn’t very nice. I’m not sure which other packages need to be downgraded for it all to work again.

Personally, I feel that if an update breaks useful functionality, the right thing to do is to regress to an earlier version and then wait for a further update – unless there is a serious security vulnerability that was addressed.