You are not logged in.
Operating system : Arch linux
Installed via : Archinstall
Desktop environment : Gnome
HW :
- (Asus zenbook 14 OLED UX3405CA)
- intel core ultra 7 255H
- 1 TB NVMe SSD
- 32 GB RAM
Behaviour :
Whenever I start up my system and start and run an app (noticed with firefox, gnome-console, nautilus, gnome-control-center) they tend to freeze and become totally unresponsive and takes 5-10 seconds to be responsive or sometimes they just dont and after closing and starting again they start like normal
I have looked into the gnome logs app and saw this log in the applications tab ... I have rebooted since so can't seem to find any other entries
`app-gnome-firefox-8482.scope: Consumed 2min 59.135s CPU time, 2G memory peak.`
I am not sure where to start looking since I am new so please help me out ><
Offline
Whenever I start up my system and start and run an app … after closing and starting again they start like normal
So this is only a problem during some interval right after the boot?
Or do those processes also randomly misbehave on starting somewhen later the day (but restarting them always "fixes" it)?
Offline
I have had the apps freeze even well after the boot. Usually happens right after launching the apps ... once it has been used they behave mostly normally. Firefox has been a heavy resource drainer for sure tho
Offline
Whenever I start up my system and start and run an app … after closing and starting again they start like normal
So this is only a problem during some interval right after the boot?
Or do those processes also randomly misbehave on starting somewhen later the day (but restarting them always "fixes" it)?
I am able to find these instances by doing
journalctl | grep "memory peak"they even show some instances where I didn't notice maybe because it got fixed sooner
also check the above reply ... sorry I am new to the forum so kinda flimsy
Last edited by RusticBard (2025-06-21 14:53:47)
Offline
Was able to fix the issue by switching to `linux-lts` kernel !!
Offline
If this is a kernel bug you want to figure what it actually is - there'll probably show up some errors/warnings in the journal.
sudo journalctl -b -3 will get to the third to last boots journal
If you want to post that, please use sth. like
sudo journalctl -b -3 | curl -F 'file=@-' 0x0.stand do not copypaste it out of the pager.
Offline