Whole system is slow after update

[UPDATE]

Video demonstrating the problem: https://drive.proton.me/urls/Z1QDNJBGNW#Q9HfHDp6LBXV

Hardware infos: https://0x0.st/PXjp.txt inxi -Fxxc0z | eos-sendlog

Boot infos: https://0x0.st/PXjO.txt journalctl -k -b -0 | eos-sendlog

Partition infos: lsblk -o name,type,size,PTTYPE,FSTYPE

NAME TYPE SIZE PTTYPE FSTYPE
nvme0n1 disk 931,5G gpt
├─nvme0n1p1 part 4G gpt vfat
├─nvme0n1p2 part 742G gpt ext4
└─nvme0n1p3 part 185,5G gpt ext4


I’m brand new to EndeavourOS and Linux ricing, and I just updated my system with the command sudo pacman -Syu

I’m using Hyprland, which is also up to date.

After rebooting, I observed my systel is slower at the statup in some cases

  • Long loading after entering the password into the sddm screen
  • Long loading of all exec-once software on Hyprland (waybar, swaync)
  • Hyprland commands seems to be slow. For eg: hitting my keyboard shortcut to start a terminal instance, it take 5 whole second to start
  • btop is crashing with 8558 IOT instruction (core dumped) btop

All of it happens after booting the system up, and it seems that my system is in general slower.

If you need more informations, let me know, since I don’t really know what do you need to help me!

https://discovery.endeavouros.com/forum-log-tool-options/how-to-include-systemlogs-in-your-post/2021/03/

1 Like

done, thanks!

I don’t see anything wrong with the boot logs. Can you update the system once again and reboot. Yesterday there were updates to lots of packages, you might have missed some.

I just did, and the slowness are still there

There is a video demonstrating my problem

https://drive.proton.me/urls/Z1QDNJBGNW#Q9HfHDp6LBXV

Your video is 771mb in size to demonstrate your issue. Which isn’t really practical.

I’m not familiar with Hyprland and be aware that the majority of users are prefering KDE Plasma.

I’ld switch into a different tty via Ctrl + Alt + F3 and launch hyprland manually via start-hyprland which should at least give some context ? Alternatively, hyprland writes its log per session id to /tmp/hypr/<session_id>/hyprland.log. That session id could be retrieve via the /tmp/hypr/ directory.

I can’t tell if you’re using a custom hyprland configuration or if you’ve adopted foreign dotfiles such as ML4W.