System is sluggish after system upgrade

Aqm · 26 May 2024 15:51

First of all, I did search the forum. There are a lot of topics about slow starting apps, this is not the issue for me. So I could not find anything specific which seems an issue like mine recently.

Yesterday I did a system upgrade. The last time before was a maybe couple of weeks (maybe months? before). Since the upgrade, the whole system feels sluggish.

But I think it is just the window manager which is sluggish. I am not 100% sure, though, this is just my analysis. Switching between apps, resizing and moving windows, opening context menu’s with right mouse click etc. are very slow which makes a frustrating user experience. Before the upgrade, everything worked very smooth and snappy. System monitor (htop) does not show 100% CPU or all ram being used or other weird signals. So that part seems ok.

Oh, in the meantime when making this post I realised that playing video (in the browser) is also a bit choppy, this is best noticeable when the there is a panning shot. Just to clarify, I didn’t have that before the upgrade.

I am on Manjaro for 5+ years now, so I know my way around, but I not an expert who can debug this. How can I solve this? Or at least take steps towards finding the issue. Any help is much appreciated.

Dell XPS (9560) 15 inch laptop
7e gen Intel® Core™ i7-7700HQ Quad Core processor (6 MB cache, tot 3,8 GHz)
32 GB DDR4 -2400MH ram
NVIDIA® GeForce® GTX 1050 met 4 GB GDDR5
512 GB PCIE Solid State-hard drive

I upgraded with

sudo pacman -Syu

Some info system info I gathered which might be usefull with the help of ChatGPT:

xps@xps ~> uname -r
5.10.216-1-MANJARO

xps@xps ~> uname -a
Linux xps-xps 5.10.216-1-MANJARO #1 SMP PREEMPT Fri May 3 03:59:28 UTC 2024 x86_64 GNU/Linux

xps@xps ~> cat /etc/lsb-release
DISTRIB_ID="ManjaroLinux"
DISTRIB_RELEASE="24.0.0"
DISTRIB_CODENAME="Wynsdey"
DISTRIB_DESCRIPTION="Manjaro Linux"

xps@xps ~> lspci | grep VGA
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 630 (rev 04)

I upgraded with `pacman -Syu`

htop doesn't show strange data

xsp@xps ~ [1|1]> sudo dmesg | grep error
[sudo] password for xps: 
[33333.501521] pcieport 0000:00:1d.6: AER: Corrected error message received from 0000:00:1d.6
[33333.501544] pcieport 0000:00:1d.6:   device [8086:a11e] error status/mask=00000001/00002000
[33938.544374] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[33947.871844] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)
[33947.871858] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)
[33947.871877] ACPI Error: Aborting method \_GPE._E42 due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)
[44343.187505] pcieport 0000:00:1d.6: AER: Corrected error message received from 0000:00:1d.6
[44343.187513] pcieport 0000:00:1d.6:   device [8086:a11e] error status/mask=00000001/00002000
[44953.240575] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[48780.736427] pcieport 0000:00:1d.6: AER: Corrected error message received from 0000:00:1d.6
[48780.736445] pcieport 0000:00:1d.6:   device [8086:a11e] error status/mask=00000001/00002000
[48787.703487] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV.ECR1 due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48787.704638] Aborting method \_SB.PCI0.LPCB.ECDV.ECR2 due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48787.704645] ACPI Error: Aborting method \ECRW due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48787.704653] ACPI Error: Aborting method \ECGD due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48787.704661] ACPI Error: Aborting method \NEVT due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48787.704682] ACPI Error: Aborting method \_SB.PCI0.LPCB.ECDV._Q66 due to previous error (AE_BAD_PARAMETER) (20200925/psparse-529)
[48789.428517] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[48803.018912] pcieport 0000:00:1c.0: AER: Corrected error message received from 0000:00:1c.0
[48803.018938] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00003000/00002000
[48803.020537] pcieport 0000:00:1c.0: AER: Corrected error message received from 0000:00:1c.0
[48803.020556] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00003000/00002000
[48805.691676] pcieport 0000:00:1c.0: AER: Corrected error message received from 0000:00:1c.0
[48805.691720] pcieport 0000:00:1c.0:   device [8086:a110] error status/mask=00003000/00002000
[50197.460921] xhci_hcd 0000:00:14.0: xHC error in resume, USBSTS 0x411, Reinit
[50207.168038] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)
[50207.168049] ACPI Error: Aborting method \_GPE.XTBT due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)
[50207.168066] ACPI Error: Aborting method \_GPE._E42 due to previous error (AE_ALREADY_EXISTS) (20200925/psparse-529)

xps@xps ~ [127]> vmstat
procs -----------memory---------- ---swap-- -----io---- -system-- -------cpu-------
 r  b   swpd   free   buff  cache   si   so    bi    bo   in   cs us sy id wa st gu
 1  0      0 3340196 3794948 16055048    0    0    56   181 1750   17 13  5 81  0  0  0

xps@xps ~ [127]> echo $XDG_CURRENT_DESKTOP
KDE

xps@xps ~> wmctrl -m
Name: KWin
Class: N/A
PID: N/A
Window manager's "showing the desktop" mode: OFF

Keruskerfuerst · 26 May 2024 16:22

Are you using X11 or Wayland ?
Can you post inxi -Fza ?

ydar · 26 May 2024 17:18

Nobody should be relying on ChatGPT for correct answers. Everything it says needs to be checked for accuracy.

Anyway, I see nvidia and it’s entirely possible that you’ve logged into a Wayland session. Please logout, or maybe even reboot, then make sure you change or verify that you’re using X11. I suspect your issues may be resolved for now, and then wait until Plasma 6.1 to try nvidia/wayland because it may work better together.

Takakage · 26 May 2024 17:44

While I have no reason to suspect that this is an issue, it may be useful to try a more recent LTS kernel like 6.1 or 6.6 and see if it makes any difference.

Aqm · 26 May 2024 20:24

xps@xps ~> inxi -Fza 
System:
  Kernel: 5.10.216-1-MANJARO arch: x86_64 bits: 64 compiler: gcc v: 13.2.1
    clocksource: tsc avail: hpet,acpi_pm
    parameters: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64
    root=UUID=896ed284-4bf0-4d32-becc-4b6d4ec239c8 rw quiet
    resume=UUID=2bb3c290-7b46-49ae-866f-2f7dc5eccfc1
  Desktop: KDE Plasma v: 6.0.4 tk: Qt v: N/A info: frameworks v: 6.1.0
    wm: kwin_x11 with: krunner vt: 2 dm: SDDM Distro: Manjaro base: Arch Linux
Machine:
  Type: Laptop System: Dell product: XPS 15 9560 v: N/A
    serial: <superuser required> Chassis: type: 10 serial: <superuser required>
  Mobo: Dell model: 05FFDN v: A00 serial: <superuser required> part-nu: 07BE
    uuid: <superuser required> UEFI: Dell v: 1.7.1 date: 01/25/2018
Battery:
  ID-1: BAT0 charge: 29.7 Wh (43.1%) condition: 68.9/97.0 Wh (71.0%)
    volts: 10.9 min: 11.4 model: SMP DELL GPM0365 type: Li-ion serial: <filter>
    status: discharging
CPU:
  Info: model: Intel Core i7-7700HQ bits: 64 type: MT MCP arch: Kaby Lake
    gen: core 7 level: v3 note: check built: 2018 process: Intel 14nm family: 6
    model-id: 0x9E (158) stepping: 9 microcode: 0xF8
  Topology: cpus: 1x cores: 4 tpc: 2 threads: 8 smt: enabled cache:
    L1: 256 KiB desc: d-4x32 KiB; i-4x32 KiB L2: 1024 KiB desc: 4x256 KiB
    L3: 6 MiB desc: 1x6 MiB
  Speed (MHz): avg: 1827 high: 2291 min/max: 800/3800 scaling:
    driver: intel_pstate governor: powersave cores: 1: 1764 2: 1589 3: 2102
    4: 2016 5: 1617 6: 1622 7: 2291 8: 1618 bogomips: 44817
  Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
  Vulnerabilities:
  Type: gather_data_sampling mitigation: Microcode
  Type: itlb_multihit status: KVM: VMX disabled
  Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT
    vulnerable
  Type: mds mitigation: Clear CPU buffers; SMT vulnerable
  Type: meltdown mitigation: PTI
  Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
  Type: reg_file_data_sampling status: Not affected
  Type: retbleed mitigation: IBRS
  Type: spec_rstack_overflow status: Not affected
  Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via
    prctl and seccomp
  Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer
    sanitization
  Type: spectre_v2 mitigation: IBRS, IBPB: conditional, STIBP: conditional,
    RSB filling, PBRSB-eIBRS: Not affected
  Type: srbds mitigation: Microcode
  Type: tsx_async_abort status: Not affected
Graphics:
  Device-1: Intel HD Graphics 630 vendor: Dell driver: i915 v: kernel
    arch: Gen-9.5 process: Intel 14nm built: 2016-20 ports: active: eDP-1
    empty: DP-1, DP-2, HDMI-A-1, HDMI-A-2 bus-ID: 00:02.0 chip-ID: 8086:591b
    class-ID: 0300
  Device-2: NVIDIA GP107M [GeForce GTX 1050 Mobile] vendor: Dell driver: N/A
    alternate: nouveau non-free: 545.xx+ status: current (as of 2024-04;
    EOL~2026-12-xx) arch: Pascal code: GP10x process: TSMC 16nm
    built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
    chip-ID: 10de:1c8d class-ID: 0302
  Device-3: Sunplus Innovation Integrated_Webcam_HD driver: uvcvideo
    type: USB rev: 2.0 speed: 480 Mb/s lanes: 1 mode: 2.0 bus-ID: 1-12:3
    chip-ID: 1bcf:2b95 class-ID: 0e02
  Display: x11 server: X.Org v: 21.1.13 with: Xwayland v: 23.2.6
    compositor: kwin_x11 driver: X: loaded: modesetting alternate: fbdev,vesa
    dri: iris gpu: i915 display-ID: :0 screens: 1
  Screen-1: 0 s-res: 1920x1080 s-dpi: 96 s-size: 507x285mm (19.96x11.22")
    s-diag: 582mm (22.9")
  Monitor-1: eDP-1 model: Sharp 0x1453 built: 2015 res: 1920x1080 hz: 60
    dpi: 141 gamma: 1.2 size: 346x194mm (13.62x7.64") diag: 397mm (15.6")
    ratio: 16:9 modes: 1920x1080
  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: 24.0.6-manjaro1.1
    glx-v: 1.4 direct-render: yes renderer: Mesa Intel HD Graphics 630 (KBL GT2)
    device-ID: 8086:591b memory: 30.48 GiB unified: yes
  API: Vulkan Message: No Vulkan data available.
Audio:
  Device-1: Intel CM238 HD Audio vendor: Dell driver: snd_hda_intel v: kernel
    bus-ID: 00:1f.3 chip-ID: 8086:a171 class-ID: 0403
  API: ALSA v: k5.10.216-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.0.5 status: off with: pipewire-media-session
    status: active tools: pw-cli
  Server-3: PulseAudio v: 17.0 status: active with: 1: pulseaudio-alsa
    type: plugin 2: pulseaudio-jack type: module tools: pacat,pactl,pavucontrol
Network:
  Device-1: Qualcomm Atheros QCA6174 802.11ac Wireless Network Adapter
    vendor: Rivet Networks Killer Wireless-n/a/ac 1535 driver: ath10k_pci
    v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 bus-ID: 02:00.0
    chip-ID: 168c:003e class-ID: 0280 temp: 42.0 C
  IF: wlp2s0 state: up mac: <filter>
  IF-ID-1: br-1f83cad548ff state: down mac: <filter>
  IF-ID-2: br-28f2c4630d7b state: down mac: <filter>
  IF-ID-3: br-4917c04780b2 state: down mac: <filter>
  IF-ID-4: br-6d532a4a8de5 state: down mac: <filter>
  IF-ID-5: br-6d5be2fcadf5 state: down mac: <filter>
  IF-ID-6: br-832925d69f03 state: down mac: <filter>
  IF-ID-7: br-8bff0fb4fbd5 state: down mac: <filter>
  IF-ID-8: br-8d2146888dac state: down mac: <filter>
  IF-ID-9: br-95729fb97189 state: down mac: <filter>
  IF-ID-10: br-b5be513c2015 state: down mac: <filter>
  IF-ID-11: br-bda8990f0cc2 state: down mac: <filter>
  IF-ID-12: br-c41a72f7f357 state: down mac: <filter>
  IF-ID-13: br-fdfa7995e7bb state: down mac: <filter>
  IF-ID-14: docker0 state: up speed: 10000 Mbps duplex: unknown
    mac: <filter>
  IF-ID-15: lxcbr0 state: down mac: <filter>
  IF-ID-16: veth23a3c02 state: up speed: 10000 Mbps duplex: full
    mac: <filter>
  Info: services: NetworkManager, nginx, sshd, wpa_supplicant
Bluetooth:
  Device-1: Qualcomm Atheros QCA61x4 Bluetooth 4.0 driver: btusb v: 0.8
    type: USB rev: 2.0 speed: 12 Mb/s lanes: 1 mode: 1.1 bus-ID: 1-4:2
    chip-ID: 0cf3:e300 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 9 state: up address: see --recommends
Drives:
  Local Storage: total: 476.94 GiB used: 401.61 GiB (84.2%)
  SMART Message: Unable to run smartctl. Root privileges required.
  ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: SK Hynix model: PC401 NVMe 512GB
    size: 476.94 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s
    lanes: 4 tech: SSD serial: <filter> fw-rev: 80003E00 temp: 24.9 C
    scheme: GPT
Partition:
  ID-1: / raw-size: 459.57 GiB size: 451.28 GiB (98.20%)
    used: 401.61 GiB (89.0%) fs: ext4 dev: /dev/nvme0n1p2 maj-min: 259:2
  ID-2: /boot/efi raw-size: 300 MiB size: 299.4 MiB (99.80%)
    used: 288 KiB (0.1%) fs: vfat dev: /dev/nvme0n1p1 maj-min: 259:1
Swap:
  Kernel: swappiness: 60 (default) cache-pressure: 100 (default) zswap: yes
    compressor: zstd max-pool: 20%
  ID-1: swap-1 type: partition size: 17.08 GiB used: 0 KiB (0.0%)
    priority: -2 dev: /dev/nvme0n1p3 maj-min: 259:3
Sensors:
  System Temperatures: cpu: 39.0 C pch: 30.5 C mobo: 25.0 C sodimm: SODIMM C
  Fan Speeds (rpm): cpu: 0
Info:
  Memory: total: 32 GiB available: 31.21 GiB used: 16.98 GiB (54.4%)
  Processes: 451 Power: uptime: 2d 9h 23m states: freeze,mem,disk
    suspend: deep avail: s2idle wakeups: 9 hibernate: platform avail: shutdown,
    reboot, suspend, test_resume image: 12.48 GiB
    services: org_kde_powerdevil,upowerd Init: systemd v: 255
    default: graphical tool: systemctl
  Packages: pm: pacman pkgs: 1819 libs: 463 tools: octopi,pamac,yaourt,yay
    Compilers: clang: 17.0.6 gcc: 13.2.1 Shell: fish v: 3.7.1 default: Bash
    v: 5.2.26 running-in: konsole inxi: 3.3.34

soundofthunder · 26 May 2024 21:13

Are you aware at all that the last was a major update, in the sense that the entire display environment was changed to KDE Plasma 6? Are you also aware that this update likely needed additional preparation from you?

The respective information was noted in the usual Update Announcement. It does seem many simply ignore those (generally), however, the importance cannot be understated. Many people have claimed ignorance and the focus suddenly switched to ‘how do I recover from this’.

If you search the forum now you should find related posts. Some people have had success by removing foreign (and no longer supported) widgets and other software, logging out and deleting the ~/.cache from a TTY; manually cleaning any remnants of old widgets etc that may exist under ~/.config, and finally rebooting. Most of this should actually have been done prior to updating; especially for those with heavily modified environments. This post of mine, and several others in the 2024-05-13 Stable Update announcement might be helpful.

This may well be the main contributor (and possibly the cure) to your apparent sluggishness.

I hope this helps. Cheers.

Aqm · 27 May 2024 14:27

Thanks for your reply. No, I was not aware of that. I didn’t even know there was such thing as a major release. Should I have known this? Also didn’t know there were releases which require preperation.

Deleting ~/.cache and rebooting did not have the desired effect. The ~/.config folder has allot of subdirs in it. So I did not delete it yet. Can I just make a backup and delete it and test after a reboot to check if it fixes the issue? If it does I

andreas85 · 27 May 2024 14:34

You can just rename the folder to .config_old

Yes

There is a thread for every update. Please ask yourself: Why would anyone write something like that if it’s not necessary?

cscs · 27 May 2024 20:22

The suggestion for .config is not really to remove the whole thing.
But to delete, or rather mv-backup, plasma related files and directories in ~/.config
https://wiki.archlinux.org/title/KDE#Configuration_related

Aqm · 27 May 2024 20:57

Ok

Did that, thanks for the suggestions. I rebooted I do see verry different thing which is what I expect after resetting all conifg. But the issue still remains. The system is still sluggish. It gets even worse when I have PHPStorm running. It ran smooth before.

What steps can I take more to debug the issue?

Aqm · 28 May 2024 09:56

Not sure what to do now. Would it be possible to revert the upgrade? Not sure if that is a straigtforward solution? I don’t have specific backups or something.

andreas85 · 28 May 2024 10:19

Only if you use timeshift or snapper

Aqm · 28 May 2024 11:56

No unfortunatly I don’t use those. So the only way forward is debugging. How would I proceed on the debugging journey?

andreas85 · 28 May 2024 12:02

One step could be to create a new user, login and test if this user works better.

Aqm · 10 June 2024 14:54

Thanks, ok I tried this. At first it looked like it was solved. But after a while I get the same problem of a slow/laggy system.

I got back to my original user and did some tests. When I reboot everything works very very fast. Then I start working day to day and the system gets slower. I cannot pinpoint any patterns when it gets slow. Just when I use programms like Thunderbird, Brave browser, PHPStorm, Spotify, Kate, Terminal etc. Closing one or more apps does not fix the issue. The system keeps being slow.

Any further guidance on how to proceed?

soundofthunder · 10 June 2024 15:37

Possibly related: I’ve seen issues in the past with baloo apparently slowing file and directory browsing. Perhaps search the forum for any issues containing baloo slow for example, and see if you find anything that seems similar.

ydar · 10 June 2024 16:42

It’s possible but I doubt it’s baloo, one of the last updates to Plasma 5 they changed some settings and it’s now a very low priority and really didn’t interfere at all with my normal use when I tested (re-indexed).

soundofthunder · 10 June 2024 16:46

I’m dubious too, but nothing much else is jumping out screaming “Pick me!”.

The OP might check the partitions for consistency, I suppose, to see if that reveals any issues (fsck), but even that wouldn’t seem to match the symptoms they describe.

Aqm · 11 June 2024 07:52

I disabled Baloo just for the sake of testing. I will report back if this solves the issue.

Aqm · 11 June 2024 11:42

Disabling Baloo does not have the desired effect unfortunately.