Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

System shutdown on its own (related to timedated?) #395

Open
canadaduane opened this issue Apr 13, 2022 · 0 comments
Open

System shutdown on its own (related to timedated?) #395

canadaduane opened this issue Apr 13, 2022 · 0 comments

Comments

@canadaduane
Copy link

canadaduane commented Apr 13, 2022

How did you upgrade to 22.04? (Fresh install / Upgrade)
Upgraded from 21.10

Related Application and/or Package Version (run apt policy $PACKAGE NAME):

I'm not sure.

Issue/Bug Description:
My system shut itself off suddenly. I'm looking at journalctl logs to see what may have caused it:

I'm seeing hundreds or thousands of messages in journalctl like this (more than appear to fit in the log? or perhaps I just don't know how to see what's before "line 1" of journalctl output?):

pop-os gsd-datetime[2440]: gweather_location_unref: assertion 'loc != NULL' failed

I also have a message that says:

Apr 13 10:40:35 pop-os systemd[1]: systemd-timedated.service: Deactivated successfully.
░░ Subject: Unit succeeded
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░ 
░░ The unit systemd-timedated.service has successfully entered the 'dead' state.

Steps to reproduce (if you know):

I'm not sure what caused this, but I'm betting the != NULL assertion shouldn't be happening.

Expected behavior:

The system should not shutdown on its own.

Other Details:
I was running libinput debug-events at the time in a background terminal, which is a monitoring tool for the trackpad. I wonder if it's somehow related...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant