Wayland Glitch/Lag/Freeze post flashing Mokka/Dragonized KDE

Valiant_AJ · 28 March 2025 19:07

Let’s start from beginning, had been constantly using dragonised, no issues so far, just 5 days back, to play valorant for a while you know what i did (flashed windows 11). Yesterday flashed Mokka OS with open drivers. Today Wayland Becomes unstable-unusable, i did post videos on telegram group as well.
p.s. All components, etc. work perfectly fine in X11, even i’m in X11 environment while making this forum post.

inxi:-

System:
Kernel: 6.13.8-zen1-1-zen arch: x86_64 bits: 64 compiler: gcc v: 14.2.1
clocksource: tsc avail: hpet,acpi_pm
parameters: BOOT_IMAGE=/@/boot/vmlinuz-linux-zen
root=UUID=aa2a672a-43bc-49b9-be53-78c1111b1bc8 rw rootflags=subvol=@
vt.default_red=30,243,166,249,137,245,148,186,88,243,166,249,137,245,148,166
vt.default_grn=30,139,227,226,180,194,226,194,91,139,227,226,180,194,226,173
vt.default_blu=46,168,161,175,250,231,213,222,112,168,161,175,250,231,213,200
quiet loglevel=3 ibt=off
Desktop: KDE Plasma v: 6.3.3 tk: Qt v: N/A info: frameworks v: 6.12.0
wm: kwin_x11 vt: 2 dm: SDDM Distro: Garuda base: Arch Linux
Machine:
Type: Desktop Mobo: Micro-Star model: PRO H610M-G DDR4 (MS-7D46) v: 1.0
serial: <superuser required> uuid: <superuser required> UEFI: American
Megatrends LLC. v: 1.B0 date: 03/23/2023
CPU:
Info: model: 12th Gen Intel Core i3-12100 bits: 64 type: MT MCP
arch: Alder Lake gen: core 12 level: v3 note: check built: 2021+
process: Intel 7 (10nm ESF) family: 6 model-id: 0x97 (151) stepping: 5
microcode: 0x38
Topology: cpus: 1x dies: 1 clusters: 4 cores: 4 threads: 8 tpc: 2
smt: enabled cache: L1: 320 KiB desc: d-4x48 KiB; i-4x32 KiB L2: 5 MiB
desc: 4x1.2 MiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 800 min/max: 800/4300 scaling: driver: intel_pstate
governor: powersave cores: 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800
8: 800 bogomips: 52838
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities: <filter>
Graphics:
Device-1: Intel Alder Lake-S GT1 [UHD Graphics 730] vendor: Micro-Star MSI
driver: i915 v: kernel alternate: xe arch: Xe process: Intel 10nm
built: 2020-21 ports: active: DP-2 empty: DP-1, DP-3, HDMI-A-1, HDMI-A-2,
HDMI-A-3, HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0 chip-ID: 8086:4692
class-ID: 0300
Display: x11 server: X.Org v: 21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_x11 driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: :0 screens: 1
Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 508x285mm (20.00x11.22")
s-diag: 582mm (22.93")
Monitor-1: DP-2 model: Lenovo G24-20 serial: <filter> built: 2021 res: N/A
dpi: 93 gamma: 1.2 size: 527x296mm (20.75x11.65") diag: 604mm (23.8")
ratio: 16:9 modes: max: 1920x1080 min: 720x400
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.0.2-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 730 (ADL-S
GT1) device-ID: 8086:4692 memory: 7.47 GiB unified: yes
API: Vulkan v: 1.4.309 layers: 5 device: 0 type: integrated-gpu name: Intel
UHD Graphics 730 (ADL-S GT1) driver: N/A device-ID: 8086:4692
surfaces: xcb,xlib device: 1 type: cpu name: llvmpipe (LLVM 19.1.7 256
bits) driver: N/A device-ID: 10005:0000 surfaces: xcb,xlib
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr
Audio:
Device-1: Intel Alder Lake-S HD Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel alternate: snd_soc_avs,snd_sof_pci_intel_tgl
bus-ID: 00:1f.3 chip-ID: 8086:7ad0 class-ID: 0403
API: ALSA v: k6.13.8-zen1-1-zen status: kernel-api tools: N/A
Server-1: PipeWire v: 1.4.1 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: Intel Ethernet I219-V vendor: Micro-Star MSI driver: e1000e
v: kernel port: N/A bus-ID: 00:1f.6 chip-ID: 8086:1a1d class-ID: 0200
IF: eno1 state: up speed: 1000 Mbps duplex: full mac: <filter>
Device-2: Lite-On Dell Wireless Device driver: hid-generic,usbhid
type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-3:2
chip-ID: 04ca:00bd class-ID: 0301
Info: services: NetworkManager,systemd-timesyncd
Bluetooth:
Device-1: Cambridge Silicon Radio Bluetooth Dongle (HCI mode) driver: btusb
v: 0.8 type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-9.2:5
chip-ID: 0a12:0001 class-ID: e001
Report: btmgmt ID: hci0 rfk-id: 0 state: up address: <filter> bt-v: 4.0
lmp-v: 6 status: discoverable: no pairing: no class-ID: 6c0104
Drives:
Local Storage: total: 465.76 GiB used: 20.78 GiB (4.5%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Western Digital
model: WD Blue SN570 500GB size: 465.76 GiB block-size: physical: 512 B
logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 234100WD temp: 42.9 C scheme: GPT
Partition:
ID-1: / raw-size: 465.47 GiB size: 465.47 GiB (100.00%)
used: 20.78 GiB (4.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
used: 608 KiB (0.2%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
ID-3: /home raw-size: 465.47 GiB size: 465.47 GiB (100.00%)
used: 20.78 GiB (4.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-4: /var/log raw-size: 465.47 GiB size: 465.47 GiB (100.00%)
used: 20.78 GiB (4.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
ID-5: /var/tmp raw-size: 465.47 GiB size: 465.47 GiB (100.00%)
used: 20.78 GiB (4.5%) fs: btrfs dev: /dev/nvme0n1p2 maj-min: 259:2
Swap:
Kernel: swappiness: 133 (default 60) cache-pressure: 100 (default) zswap: no
ID-1: swap-1 type: zram size: 15.31 GiB used: 0 KiB (0.0%) priority: 100
comp: zstd avail: lzo-rle,lzo,lz4,lz4hc,deflate,842 max-streams: 8
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 64.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 16 GiB note: est. available: 15.31 GiB used: 3.66 GiB (23.9%)
Processes: 281 Power: uptime: 5m states: freeze,mem,disk suspend: deep
avail: s2idle wakeups: 0 hibernate: platform avail: shutdown, reboot,
suspend, test_resume image: 6.11 GiB services: org_kde_powerdevil,
power-profiles-daemon, upowerd Init: systemd v: 257 default: graphical
tool: systemctl
Packages: pm: pacman pkgs: 1328 libs: 375 tools: octopi,pacseek,paru
Compilers: gcc: 14.2.1 Shell: garuda-inxi default: fish v: 4.0.1
running-in: konsole inxi: 3.3.37
Garuda (2.7.2-1):
System install date:     2025-03-28
Last full system update: 2025-03-28
Is partially upgraded:   No
Relevant software:       snapper NetworkManager dracut
Windows dual boot:       No/Undetected
Failed units:

nepti · 29 March 2025 14:33

After the reboot after the installation, the plasma wayland session is loaded by default - did you already have these issues or only after the first system update?

Your garuda-inxi looks good. Post from a wayland session the output of:

inxi -Gxx

Open htop in a wayland session and check if anything is massively using CPU or MEM.
As a test, you can try disabling the desktop effects, for example “active blur” wallpaper, rounded corners, etc.

It would be helpful to link the videos here too, not every potential helper creates a Telegram account for this reason.

Valiant_AJ · 29 March 2025 18:03

Thanks @nepti for the reply, i’ll try to answer all questions in the manner they’ve been asked,

issues began right after 1st update, particularly after rebooting once. Since this was unusual glitch and i had not yet installed any major software, i flashed my system with dragonised kde, but to no avail, right after updating and rebooting, same wayland issues persisted. ultimately i resorted to gnome version.

Unfortunately as of now i have booted into gnome version which works completely fine, no issues so far in wayland session. I’m attaching output from gnome version’s terminal.

Graphics:
  Device-1: Intel Alder Lake-S GT1 [UHD Graphics 730] vendor: Micro-Star MSI
    driver: i915 v: kernel arch: Xe ports: active: DP-2 empty: DP-1, DP-3,
    HDMI-A-1, HDMI-A-2, HDMI-A-3, HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0
    chip-ID: 8086:4692
  Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
    compositor: gnome-shell v: 48.0 driver: gpu: i915 display-ID: 0
  Monitor-1: DP-2 model: Lenovo G24-20 res: 1920x1080 dpi: 93
    diag: 604mm (23.8")
  API: Vulkan v: 1.4.309 surfaces: xcb,xlib,wayland device: 0
    type: integrated-gpu driver: N/A device-ID: 8086:4692 device: 1 type: cpu
    driver: N/A device-ID: 10005:0000
  API: EGL Message: EGL data requires eglinfo. Check --recommends.
  Info: Tools: api: vulkaninfo x11: xdpyinfo, xprop, xrandr

yes in the video i have shown that cpu and ram usage is well under control with ram consumed being 6gbs at max(i’m having 16gigs of ram installed), when hang occured, cpu usage also fluctuated but stayed under 30% load. yes, had disabled active blur, several animations and other settings, yet issue persisted.

definitely, i tried to add it but there wasn’t any direct method. Sharing Gdrive link

One thing I’d like to mention while I was switching Secure-Boot - ON/OFF. I had increased shared graphics memory from 64M → 160M. I thought since i have 16 gigs of ram this won’t affect much, moreover in windows or in Garuda Gnome there is no issue so far, yet i have switched back to 64M just in case its causing an issue. because that’s the only hardware level tweak i did.

nepti · 29 March 2025 18:52

In the videos you can see that the WM theme is “Scratchy” and the system icons are “Fluent-teal-dark”, both of which are not standard - this may be the cause. Did you also have the issues with the default Mokka theme?

Another possibility would be that KDE + wayland has a problem with the 144 hz of the monitor. Did you have the 144 hz set on the old garuda installation (before you installed windows)?

Valiant_AJ · 29 March 2025 19:41

I have 4 reasons why WM theme(Scratchy), icons(fluent..), 144 hz, are not part of the issue:

ever since i’m on Garuda, though my monitor supports upto 165hz, i have constantly stayed on 144 hz, no issues so far.
today as i had tested with installing dragonised kde(since before mokka release i had this flavour), without any customizations, i just made multiple profiles in firedragon and similar lag as in the video can be seen.
here have a look at this,
Screenshots | Garuda Linux preferred :master: - #1874 by Valiant_AJ
this was taken 19 days ago, same settings but no problem. same WM, Icons, Refresh Rate, even sddm’s refresh rate was also set to 144hz for smooth login experience
Currently i’m on gnome 144 hz on wayland no issues.

                   .%;888:8898898:                vone@vantage
                 x;XxXB%89b8:b8%b88:              ------------
              .8Xxd                8X:.           OS: Garuda Linux x86_64
            .8Xx;                    8x:.         Host: MS-7D46 (1.0)
          .tt8x          .d            x88;       Kernel: 6.13.8-zen1-1-zen
       .@8x8;          .db:              xx@;     Uptime: 1 hour, 6 mins
     ,tSXX°          .bbbbbbbbbbbbbbbbbbbB8x@;    Packages: 1259 (pacman)[stable]
   .SXxx            bBBBBBBBBBBBBBBBBBBBbSBX8;    Shell: fish 4.0.1
 ,888S                                     pd!    Resolution: 1920x1080
8X88/                                       q     DE: GNOME 48.0
8X88/                                             WM: Mutter (Wayland)
GBB.                                              WM Theme: Adwaita-dark
 x%88        d888@8@X@X@X88X@@XX@@X@8@X.          Theme: Adwaita-dark [GTK2/3/4]
   dxXd    dB8b8b8B8B08bB88b998888b88x.           Icons: Adwaita [GTK2/3/4]
    dxx8o                      .@@;.              Terminal: GNOME Terminal 3.56.0
      dx88                   .t@x.                Terminal Font: FiraCode Nerd Font Mono 12
        d:SS@8ba89aa67a853Sxxad.                  CPU: 12th Gen Intel(R) Core(TM) i3-12100 (8) @ 4.30 GHz
          .d988999889889899dd.                    GPU: Intel UHD Graphics 730 @ 1.40 GHz [Integrated]
                                                  Memory: 2726 MiB / 15768 MiB

                                                                          
                                                                          

 ╭─vone@vantage in ~ 
 ╰─λ

nepti · 29 March 2025 20:18

Then the cause is probably the system update after the fresh install, some (KDE ) package seems to be spreading a bad mood.

But we can only find out the cause if the OS in question is also installed and it is possible to trace when, where and how the issue occurs (htop and logs would also be very helpful).

Valiant_AJ · 29 March 2025 20:22

Indirectly you want to say i nuke my system again for testing purposes ok! just for the sake to prevent future mishaps, i thought no one replied because its a minor issue.. just few minutes… flashing mokka again!

Valiant_AJ · 29 March 2025 20:44

Issue still perists !!
here htop ss:
(5 windows of firedragon launched whole system lags…)

Graphics:
Device-1: Intel Alder Lake-S GT1 [UHD Graphics 730] vendor: Micro-Star MSI
driver: i915 v: kernel arch: Xe ports: active: DP-2 empty: DP-1, DP-3,
HDMI-A-1, HDMI-A-2, HDMI-A-3, HDMI-A-4, HDMI-A-5 bus-ID: 00:02.0
chip-ID: 8086:4692
Display: wayland server: X.org v: 1.21.1.16 with: Xwayland v: 24.1.6
compositor: kwin_wayland driver: X: loaded: modesetting
alternate: fbdev,intel,vesa dri: iris gpu: i915 display-ID: 0
Monitor-1: DP-2 model: Lenovo G24-20 res: 1920x1080 hz: 144 dpi: 93
diag: 604mm (23.8")
API: EGL v: 1.5 platforms: device: 0 drv: iris device: 1 drv: swrast gbm:
drv: iris surfaceless: drv: iris wayland: drv: iris x11: drv: iris
API: OpenGL v: 4.6 compat-v: 4.5 vendor: intel mesa v: 25.0.2-arch1.2
glx-v: 1.4 direct-render: yes renderer: Mesa Intel UHD Graphics 730 (ADL-S
GT1) device-ID: 8086:4692 display-ID: :1.0
API: Vulkan v: 1.4.309 surfaces: xcb,xlib,wayland device: 0
type: integrated-gpu driver: N/A device-ID: 8086:4692 device: 1 type: cpu
driver: N/A device-ID: 10005:0000
Info: Tools: api: clinfo, eglinfo, glxinfo, vulkaninfo
de: kscreen-console,kscreen-doctor wl: wayland-info
x11: xdpyinfo, xprop, xrandr

Here, have a look at how just opening 6 tabs in firedragon causes whole system lag/ hang.

nepti · 29 March 2025 21:18

This is after the system update? And before the system update it works without issues?

CPU usage and memory usage look normal when 5 firedragon windows are open + obs. And inxi -Gxx is also ok.

Valiant_AJ · 30 March 2025 07:20

After the system update, before that there’s no such issue.

Moreover i’d like to add that in X11 too, after opening some firedragon windows ..system stutters, there’s that choppy experience which makes you uncomfortable. Though it’s less than in wayland.

Valiant_AJ · 30 March 2025 07:41

All the readers, if you have any spare PC maybe you can try replicating the issue, then maybe it can be known, it’s Only me or others are affected too …
I’d like to add i’m using ventoy for installation (latest version 1.1.05), and latest ISOs(for mokka/dragonised/gnome), for me both methods- booting into Normal mode or Grub2 mode work fine

Thank you all for support, i’ll try kde maybe after sometime, it seems more like issue of KDE instead of wayland since gnome is perfectly holding up. Maybe a mismatch between packages or other diagnosis as suggested in this thread in Manjaro Forum is causing issues

since i have brevity of time and exams are near ..i shall switch to gnome for smoother and better experience. Thank You

nepti · 30 March 2025 15:59

Now a is dawning on me. Possibly plasma falls back to “software rendering mode” (that would fit your error picture).

If you ever switch back to KDE and the issue occurs again, open ~/.config/kdeglobals and check if this entry is there:

[QtQuickRendererSettings]
SceneGraphBackend=software

If yes, simply delete both lines.

alok-debnath · 3 April 2025 17:58

I am facing the same issue on my system (lag + heating), everything on htop looks normal. Nothing running heavy just vscode and on x11 there is no such issues. btw i checked if I have SceneGraphBackend but I dont in kdeglobals

system · 17 April 2025 17:59

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