Whenever I use Fedora without my Power Cable plugged in, it works fine on the first boot, but when I shut it down and restart it, it crashes after logging in. I wasn‘t able to find any logs about this though and it just immediately turns off, without showing me anything. Any idea what I could do to debug this?
1 Like
to isolate the issue:
temporarily disable all gnome extensions and see if the problem persists.
temporarily create a new user and see if you can log in the second time.
do logs show anything interesting?
1 Like
Hello @arbee ,
Welcome to 
,
Sorry to hear you’re having an issue.
As @augenauf mentioned, logs could help here. Also, can you trigger this behaviour in a repeatable fashion? If so please describe the steps you take to do this, maybe I can test it out here. For logs journalctl -b | grep "gnome-session" may give some relevant info at least to narrow things down some. Just out of curiosity, is there an NVidia GPU involved here?
It happens very often… I don’t know though if I’m doing something specific beforehand that causes this, also I just noticed, that it had to boot up completely even though I didn’t shut it down the last time and just put it to sleep… And yes I do have an nvidia gpu, but also another one… But the nvidia one is the main one right now (The other one is from intel but is quite bad compared to the nvidia one)(also I’m not new to , I just never encountered this issue before because I wasn’t using it remotely)
Hello, out of curiosity, do you have a Dell laptop? I’ve been experiencing weird performance and behavior issues from time to time (including occasional gnome session crashes) that all seems to be related to the power cable being plugged in or not. I noticed some issues appeared when the laptop was charged and I left the power alimentation for a while. Running on the battery from time to time solved all my issues.
It’s an hp spectre x360 5
Hey, I’ve been quite busy so I haven’t had the time to post here, and I just tried out creating a new user and logging into it. This fully worked and I now have a working user profile, so it’s something I have set up on my main User. I was thinking if it could be some app in my autostart causing this… Could this be the case? Also disabling the extensions did nothing.
So, I just tried logging in as that new user and then using the gnome-terminal to open up gnome-tweaks as my main user and removing all startup apps… After this I was able to log into my main user again without it crashing… Now I only have to figure out which app caused this
2 Likes
So, it seems to be Discord… But only after the second time I log in. So: 1. I boot it up, use new user to add Discord as a startup app 2. I log in as main user → works 3. I add more apps 4. I log out and back in → doesn’t work.
But when I remove Discord, everything works
1 Like
Nvm lmao… After adding all apps again except for Discord it did it again
An older battery may no longer deliver peak power requirements, and can also put more load on the power adapter. Some HP Systems have a UEFI battery test.
Well it isn’t an older battery since I had to switch it out due to the old one getting thicker and since it works when I remove autostart apps, I don’t think it’s anything battery related
Removing autostart apps would reduce the peak power demand and allow a weak battery to be used. There have been battery quality issues (blamed on COVID impacts on supply chains). If your system has the UEFI Battery Test you should use it.