System suddenly lags one boot then gets worse every boot

Support
1

I’ve been running Manjaro KDE on quite a few systems for quite some years now, all without issue. Now I got a new worklaptop last year, and I keep running into the same thing.

Everything is fine. Until one day when I boot my PC. This could be days, weeks or months after instalment, but sooner or later it happens. From there on, it lags like hell. And from there on, every time I boot the system it seems to get worse. I don’t see anything unusual in my CPU use, memory usage, hard disk activity or whatever. There is a action before this happens, like after updates or so. It’s seemingly random, beside that it always happens one day as I boot my system and from there on it breaks. But the system becomes unusable as soon as it does.

More specifically: there is a huge delay in things you do (moving the mouse, typing, etc) and it actually showing as well as software opening slower (although it could be possible that it just looks slower because of a delay in rendering). I normally have a setup of a 4K screen (21:9) on 100Hz and the built in laptop screen on full-HD (16:10) on 60Hz. The 4K screen is a bit more smooth, but still lags extremely. The full-HD
one is unusable. If I unplug the screen (with built in dock to mouse, keyboard, audio, and charging) the laptop screen becomes similar to the 4K screen otherwise.

At first it took a month after a fresh install. I thought the integrated graphics drivers (i915) where acting up. I reinstalled everything ensuring I used the open-source drivers (I normally use them unless I have an Nvidia card, but just in case). Went well for months. 2 weeks ago I had the issue again. I noticed that the encrypted swap partition didn’t seem to get decrypted anymore, nor did it appear in any swap on output. Fresh install with a swapfile instead followed. Everything seemed ok again. Now 2 week later it’s back.

I currently have over 400GB of free disk space, system is up to date, swapfile is listed properly if I check swapon -s, and I don’t use snap of flatpacks. Changing kernels doesn’t change anything regarding this issue either.

I’m at a loss…

Output of inxi -zv8:

System:
  Kernel: 6.12.39-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 15.1.1
    clocksource: tsc avail: acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-6.12-x86_64
    root=UUID=14b49009-20fb-4b9f-ba95-a08a9f568816 rw quiet
    cryptdevice=UUID=2459ee1b-00bc-4eec-a422-257b7d7d7967:luks-2459ee1b-00bc-4eec-a422-257b7d7d7967
    root=/dev/mapper/luks-2459ee1b-00bc-4eec-a422-257b7d7d7967 splash
    udev.log_priority=3
  Desktop: KDE Plasma v: 6.3.6 tk: Qt v: N/A info: frameworks v: 6.16.0
    wm: kwin_x11 vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: HP product: HP EliteBook 840 14 inch G11 Notebook PC
    v: SBKPF serial: <superuser required> Chassis: type: 10
    serial: <superuser required>
  Mobo: HP model: 8C26 v: KBC Version 02.4B.00 serial: <superuser required>
    part-nu: 9G0H5ET#ABH uuid: <superuser required> UEFI: HP
    v: W70 Ver. 01.03.05 date: 09/12/2024
Battery:
  ID-1: BAT0 charge: 50.4 Wh (94.6%) condition: 53.3/56.0 Wh (95.2%)
    volts: 12.9 min: 11.6 model: Hewlett-Packard Primary type: Li-ion
    serial: <filter> status: not charging cycles: 24
Memory:
  System RAM: total: 16 GiB available: 15.09 GiB used: 6.36 GiB (42.2%)
  Message: For most reliable report, use superuser + dmidecode.
  Array-1: capacity: 64 GiB slots: 2 modules: 2 EC: None
    max-module-size: 32 GiB note: est.
  Device-1: Bottom-Slot 1(left) type: DDR5 detail: synchronous size: 8 GiB
    speed: 5600 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M425R1GB4PB0-CWMOL serial: <filter>
  Device-2: Bottom-Slot 2(right) type: DDR5 detail: synchronous size: 8 GiB
    speed: 5600 MT/s volts: curr: 1 width (bits): data: 64 total: 64
    manufacturer: Samsung part-no: M425R1GB4PB0-CWMOL serial: <filter>
PCI Slots:
  Permissions: Unable to run dmidecode. Root privileges required.
CPU:
  Info: model: Intel Core Ultra 7 155U bits: 64 type: MST AMCP
    arch: Meteor Lake level: v3 note: check built: 2023+ process: Intel 4 (7nm)
    family: 6 model-id: 0xAA (170) stepping: 4 microcode: 0x24
  Topology: cpus: 1x dies: 1 clusters: 5 cores: 12 threads: 14 mt: 2 tpc: 2
    st: 10 smt: enabled cache: L1: 1.2 MiB desc: d-10x32 KiB, 2x48 KiB; i-12x64
    KiB L2: 10 MiB desc: 5x2 MiB L3: 12 MiB desc: 1x12 MiB
  Speed (MHz): avg: 1364 min/max: 400/4800:3800:2100 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1364 2: 1364 3: 1364
    4: 1364 5: 1364 6: 1364 7: 1364 8: 1364 9: 1364 10: 1364 11: 1364 12: 1364
    13: 1364 14: 1364 bogomips: 75292
  Flags: 3dnowprefetch abm acpi adx aes aperfmperf apic arat
    arch_capabilities arch_lbr arch_perfmon art avx avx2 avx_vnni bmi1 bmi2
    bts bus_lock_detect 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 pcid
    pclmulqdq 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 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: indirect_target_selection 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 status: Not affected
  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; PBRSB-eIBRS: Not affected; BHI: BHI_DIS_S
  Type: srbds status: Not affected
  Type: tsa status: Not affected
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel Meteor Lake-P [Intel Graphics] vendor: Hewlett-Packard
    driver: i915 v: kernel alternate: xe arch: Xe-LPG process: Intel 4 (7nm+)
    built: 2023+ ports: active: DP-1,eDP-1 empty: DP-2, DP-3, DP-4, HDMI-A-1
    bus-ID: 00:02.0 chip-ID: 8086:7d45 class-ID: 0300
  Device-2: Chicony HP 5MP Camera driver: uvcvideo type: USB rev: 2.0
    speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-5:7 chip-ID: 04f2:b7e9
    class-ID: fe01 serial: <filter>
  Device-3: Logitech Logitech Webcam C925e driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:8
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  Display: x11 server: X.Org v: 21.1.18 with: Xwayland v: 24.1.8
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 5360x2054 s-dpi: 96 s-size: 1418x543mm (55.83x21.38")
    s-diag: 1518mm (59.78") monitors: <missing: xrandr>
  Monitor-1: DP-1 model: LG (GoldStar) HDR WQHD serial: <filter> built: 2023
    res: 3440x1440 dpi: 107 gamma: 1.2 chroma: red: x: 0.663 y: 0.337 green:
    x: 0.294 y: 0.643 blue: x: 0.145 y: 0.059 white: x: 0.314 y: 0.329
    size: 820x346mm (32.28x13.62") diag: 888mm (34.9") modes: 3440x1440,
    1920x1080, 1280x720, 1024x768, 800x600, 720x480, 640x480
  Monitor-2: eDP-1 model: BOE Display 0x0bfc built: 2023 res: 1920x1200
    dpi: 161 gamma: 1.2 chroma: red: x: 0.635 y: 0.333 green: x: 0.298 y: 0.624
    blue: x: 0.153 y: 0.051 white: x: 0.314 y: 0.329
    size: 302x188mm (11.89x7.4") diag: 356mm (14") ratio: 16:10
    modes: 1920x1200
  EDID-Warnings: 1: parse_edid: unknown flag 2 2: parse_edid: unknown tag
    112
  API: EGL v: 1.5 hw: drv: intel iris platforms: device: 0 drv: iris
    device: 1 drv: swrast gbm: drv: iris surfaceless: drv: iris x11: drv: iris
    inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.1.6-arch1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel Graphics (MTL)
    device-ID: 8086:7d45 memory: 14.73 GiB unified: yes
  API: Vulkan v: 1.4.321 layers: N/A device: 0 type: integrated-gpu
    name: Intel Graphics (MTL) driver: mesa intel v: 25.1.6-arch1.1
    device-ID: 8086:7d45 surfaces: N/A
  Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
    de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo,xprop
Audio:
  Device-1: Intel Meteor Lake-P HD Audio vendor: Hewlett-Packard
    driver: sof-audio-pci-intel-mtl
    alternate: snd_hda_intel,snd_sof_pci_intel_mtl bus-ID: 00:1f.3
    chip-ID: 8086:7e28 class-ID: 0401
  Device-2: Logitech Logitech Webcam C925e driver: snd-usb-audio,uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 3-9:8
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  API: ALSA v: k6.12.39-1-MANJARO status: kernel-api with: aoss
    type: oss-emulator tools: alsactl,alsamixer,amixer
  Server-1: JACK v: 1.9.22 status: off tools: N/A
  Server-2: PipeWire v: 1.4.6 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 Meteor Lake PCH CNVi WiFi driver: iwlwifi v: kernel
    bus-ID: 00:14.3 chip-ID: 8086:7e40 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
  Info: services: NetworkManager, 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:9 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.
  Device-1: luks-2459ee1b-00bc-4eec-a422-257b7d7d7967 maj-min: 254:0
    type: LUKS dm: dm-0 size: 476.64 GiB
  Components:
  p-1: nvme0n1p2 maj-min: 259:2 size: 476.64 GiB
RAID:
  Message: No RAID data found.
Drives:
  Local Storage: total: 476.94 GiB used: 38.26 GiB (8.0%)
  SMART Message: Required tool smartctl not installed. Check --recommends
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: KIOXIA model: N/A
    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: HP01AP40 temp: 31.9 C
    scheme: GPT
  Message: No optical or floppy data found.
Partition:
  ID-1: / raw-size: 476.64 GiB size: 468.09 GiB (98.21%)
    used: 38.26 GiB (8.2%) fs: ext4 dev: /dev/dm-0 maj-min: 254:0
    mapped: luks-2459ee1b-00bc-4eec-a422-257b7d7d7967 label: N/A
    uuid: 14b49009-20fb-4b9f-ba95-a08a9f568816
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 488 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1 label: N/A
    uuid: F9DF-2952
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: no
  ID-1: swap-1 type: file size: 512 MiB used: 0 KiB (0.0%) priority: -2
    file: /swapfile
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: 4 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
  Hub-4: 3-1:10 info: Realtek RTS5411 Hub ports: 5 rev: 2.1
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 chip-ID: 0bda:5411
    class-ID: 0900
  Device-1: 3-1.1:11 info: Mad Catz Catz RAT6 type: mouse,HID,keyboard
    driver: hid-generic,usbhid interfaces: 4 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 100mA chip-ID: 0738:1732 class-ID: 0300
    serial: <filter>
  Device-2: 3-1.2:12 info: Corsair K95 RGB Platinum Keyboard [RGP0056]
    type: keyboard,HID driver: usbfs interfaces: 2 rev: 2.0
    speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1 power: 500mA
    chip-ID: 1b1c:1b2d class-ID: 0300 serial: <filter>
  Device-3: 3-3:3 info: Yubicom Yubikey 4/5 U2F type: HID
    driver: hid-generic,usbhid interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s)
    lanes: 1 mode: 1.1 power: 30mA chip-ID: 1050:0402 class-ID: 0300
  Device-4: 3-4:5 info: Synaptics type: <vendor specific> driver: N/A
    interfaces: 1 rev: 2.0 speed: 12 Mb/s (1.4 MiB/s) lanes: 1 mode: 1.1
    power: 100mA chip-ID: 06cb:00f0 class-ID: ff00 serial: <filter>
  Device-5: 3-5:7 info: Chicony HP 5MP Camera type: video driver: uvcvideo
    interfaces: 5 rev: 2.0 speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0
    power: 500mA chip-ID: 04f2:b7e9 class-ID: fe01 serial: <filter>
  Device-6: 3-9:8 info: Logitech Logitech Webcam C925e type: video,audio
    driver: snd-usb-audio,uvcvideo interfaces: 4 rev: 2.0
    speed: 480 Mb/s (57.2 MiB/s) lanes: 1 mode: 2.0 power: 500mA
    chip-ID: 046d:085b class-ID: 0102 serial: <filter>
  Device-7: 3-10:9 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-5: 4-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
Sensors:
  System Temperatures: cpu: 36.2 C mobo: N/A
  Fan Speeds (rpm): N/A
Repos:
  Packages: pm: pacman pkgs: 1338 libs: 358 tools: octopi,yay
  Active pacman repo servers in: /etc/pacman.d/mirrorlist
    1: https://mirrors2.manjaro.org/stable/$repo/$arch
    2: https://mirror.bouwhuis.network/manjaro/stable/$repo/$arch
    3: https://manjaro.mirror.wearetriple.com/stable/$repo/$arch
    4: https://mirror.koddos.net/manjaro/stable/$repo/$arch
    5: https://manjaro.mirrors.lavatech.top/stable/$repo/$arch
    6: https://manjaro.kurdy.org/stable/$repo/$arch
    7: https://mirror.futureweb.be/manjaro/stable/$repo/$arch
    8: https://mirrors.cicku.me/manjaro/stable/$repo/$arch
    9: https://www.mirrorservice.org/sites/repo.manjaro.org/repos/stable/$repo/$arch
    10: https://mirrors.manjaro.org/repo/stable/$repo/$arch
    11: http://ftp.rz.tu-bs.de/pub/mirror/manjaro.org/repos/stable/$repo/$arch
    12: https://mirror.alpix.eu/manjaro/stable/$repo/$arch
    13: https://ipng.mm.fcix.net/manjaro/stable/$repo/$arch
    14: https://ftp.gwdg.de/pub/linux/manjaro/stable/$repo/$arch
    15: https://manjaro.ynh.ovh/stable/$repo/$arch
    16: http://manjaro.mirrors.uk2.net/stable/$repo/$arch
    17: https://ftp.lysator.liu.se/pub/manjaro/stable/$repo/$arch
    18: https://mirror.vinehost.net/manjaro/stable/$repo/$arch
    19: https://mirror.raiolanetworks.com/manjaro/stable/$repo/$arch
    20: https://mirror.init7.net/manjaro/stable/$repo/$arch
Processes:
  CPU top: 5 of 363
  1: cpu: 10.6% command: librewolf pid: 4359 mem: 651.9 MiB (4.2%)
  2: cpu: 5.5% command: librewolf pid: 4888 mem: 375.2 MiB (2.4%)
  3: cpu: 3.4% command: slack pid: 4030 mem: 472.1 MiB (3.0%)
  4: cpu: 3.2% command: s1-agent pid: 817 mem: 220.6 MiB (1.4%)
  5: cpu: 2.7% command: konsole pid: 7870 mem: 229.4 MiB (1.4%)
  Memory top: 5 of 363
  1: mem: 675.8 MiB (4.3%) command: plasmashell pid: 3058 cpu: 2.4%
  2: mem: 651.9 MiB (4.2%) command: librewolf pid: 4359 cpu: 10.6%
  3: mem: 492.9 MiB (3.1%) command: thunderbird pid: 3466 cpu: 1.3%
  4: mem: 472.1 MiB (3.0%) command: slack pid: 4030 cpu: 3.4%
  5: mem: 375.2 MiB (2.4%) command: librewolf pid: 4888 cpu: 5.5%
Info:
  Processes: 363 Power: uptime: 33m states: freeze,mem,disk suspend: s2idle
    wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume
    image: 6.02 GiB services: org_kde_powerdevil, power-profiles-daemon,
    upowerd Init: systemd v: 257 default: graphical tool: systemctl
  Compilers: clang: 20.1.8 gcc: 15.1.1 Shell: Zsh v: 5.9 running-in: konsole
    inxi: 3.3.38
2

That is very strange…

Have you tried a Plasma Wayland session?

Wayland is better when you use multiple displays.

Do you have i915 and xe in your mkinitcpio MODULES line?

2 Likes
3

I have no personal experience with ssd/nvme drives but I read that some form of maintenance is needed in the form of trim or discard.
That is normally taken care of automatically - but an encrypted drive like yours is a bit different and apparently some configuration is needed to make this work.

From here:
https://wiki.archlinux.org/title/Solid_state_drive

I got to here, where that is explained:
https://wiki.archlinux.org/title/Dm-crypt/Specialties#Discard/TRIM_support_for_solid_state_drives_(SSD)

Solid state drive users should be aware that, by default, TRIM commands are not enabled by the device-mapper, i.e. block-devices are mounted without the discard option unless you override the default.

It could be the reason for the system relatively suddenly behave like what you describe.

It could also be initiated manually but as I said:
I have zero experience with ssd/nvme drives

2 Likes
4

I haven’t. But although it doesn’t explain why it happens suddenly, I can try so tho. How can I change this?

I haven’t touched this myself, but I just checked and the default conf says: MODULES=() . I don’t see any additional config files in /etc/mkinitcpio.conf.d/

In the mean time I tried to reinstall the GPU drivers using
sudo mhwd -r pci video-linux
sudo mhwd -a pci free 0300
systemctl reboot
But that didn’t help either.

5

Before login - choose the Plasma Wayland session in lower right corner.

As lagging can have many origins - I suggest you look at @Nachlese suggestions with the Arch Wiki.

A logical conclusion to your issue is very difficult.

Please look for specific point in time where it start.

Check your pacman log.

As it is Intel - drivers are provided to the kernel by Intel developers.

Since the system is an Iris Xe it is worth a try to add i915 xe to the modules on mkinitcpio.conf.

MODULES=(i915 xe)

The save the changes and rebuild init

sudo mkinitcpio -p
1 Like
6

I’ve done this. Sadly, it doesn’t seem to make any change either.

This is exactly the part I struggled with. I haven’t been able to pin point any cause so far looking at logs and other things happening/changing making it very hard to figure out what goes wrong, let alone why.

As it started almost a year ago with intervals after reinstalls, I don’t have a list of everything I checked ready hence being a bit vague. But:

Wayland is blazing fast! It may be the contrast of the previous lagging, but it feels faster than X. Any changes I could make to make this default? I normally auto-login on boot, so it’ll be nice if it auto-logins into Wayland.

The oddest thing is, my issue only seems to apply to rendering. Non-visual functionality works fine. So I feel it’s somewhere in that layer where it goes wrong.

Either way, the issue seems fixed with Wayland, at least for now. Hopefully it stays so. Gotta look into the Wayland compatibility of some things, it seems at least Birdtray doesn’t like it very much. Ah well, as long as the essentials works I can take time to figure out the rest.

In the meantime I will also read into Nachlese’s remarks. It doesn’t hurt to look into that, no matter if it’s the cause or not.

7

That is where the display driver is in play.

Certainly it won’t hurt to have the i915 xe driver load as early as possible - which the modules array make sure of.

I have no experience with autologin - but I am fairly confident that when you have once selected Wayland it will load again.

You could remove the package plasma-x11-session to ensure the option does not exist.

8

I got that :wink: . More thinking such causes seem more likely than the SSD, altrough maybe not impossible.

I had tested it before I posted, but sadly it doesn’t. After reboot I have to logout to log back in with Wayland :confused: .

I don’t have a plasma-x11-session package. Nor do I have a plasma-wayland-session package when it comes to that. I’m not sure how they are provided nowadays, but I guess in a different way. This instalment is 2 weeks old, made a new bootable USB for it.

9

You can change your Plasma session from X11 to Wayland by selecting the session type at the login screen (Wayland is the default for Plasma).

If you have set up autologin to skip the password screen, you can change to a Wayland session by opening System Settings → Colors & Themes → Login Screen (SDDM) → Behavior.

The separation of Plasma X11 from Plasma Wayland occurs in Plasma 6.4, which hasn’t reached Stable or Testing branch.

4 Likes
10

Edit your /etc/sddm.conf.d/kde_settings.conf

[Autologin]
Session=plasmawayland

Another config you may have or maybe not

 $ cat 10-wayland.conf 
[General]
DisplayServer=wayland
GreeterEnvironment=QT_WAYLAND_SHELL_INTEGRATION=layer-shell

[Wayland]
CompositorCommand=kwin_wayland --drm --no-lockscreen --no-global-shortcuts --locale1
11

That setting is there! Great, thanks! That works :slight_smile: .

1 Like
12

Something to potentially save you time and effort in future;

Regards.

13

I’m familiar with Ventoy, but it doesn’t change much as I don’t need multiple ISOs. I have a dedicated bootable Manjaro KDE minimal USB as that’s my only daily driver, as sometimes it’s useful for other things than simply installing too.

Whenever I do a fresh install, just write the new version over it (unless I would have no device to do so with, then I use the old version still on it). Since I don’t need other ISOs ready, it doesn’t really matter if I update Ventoy or the just the Manjaro USB.

14

I find it invaluable. Plus, being able to reserve a portion of the USB has allowed me to also install NomadBSD to an additional partition; convenient as repair media, or simply a portable OS.

Cheers.

15

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