Given it is the same time each day, I am guessing "feature" rather than bug. It may also be that the power plug resets/reboots itself once a day and that the reboot does a quick power blip that is quick enough to not matter for non-computer devices. Device makers love to find and implement half-assed "solutions" to problems. I would guess they had some sort of memory leak (most software does) and will stop working after a week or 2, and instead of finding and fixing the leak chose to reboot it daily so that the leak is not an issue. And on a reboot they don't have a way to maintain power during the reboot and decide a quick blip is ok. On Thu, Nov 16, 2023 at 4:00 AM Patrick O'Callaghan <pocallaghan@xxxxxxxxx> wrote: > > On Wed, 2023-11-15 at 15:10 -0800, Samuel Sieb wrote: > > On 11/15/23 15:02, Patrick O'Callaghan wrote: > > > On Wed, 2023-11-15 at 14:20 -0800, Samuel Sieb wrote: > > > > On 11/14/23 05:52, Patrick O'Callaghan wrote: > > > > > My system (both F38 and now F39) reboots itself every morning > > > > > at > > > > > 8am, > > > > > yet nothing in the cron configuration is telling it to do that > > > > > and > > > > > I > > > > > don't see anything obvious in the journal to cause it. > > > > > > > > > > How can I figure out what is triggering this? I know the > > > > > description is > > > > > vague, but there it is. > > > > > > > > As mentioned, that isn't a reboot. It's a hard power-off. Have > > > > you > > > > tried being at your computer at that time to see what it's doing? > > > > > > Once I've tried Barry's suggestion of turning off the programmed > > > hibernation, that'll be the next thing. It's usually a bad idea to > > > change more that one variable at a time. > > > > I don't see how watching your computer is changing a variable. :-) > > Heisenberg? > > Seriously though, in the end I did watch it with hibernation disabled, > and sure enough the "smart" power plug turned itself off and on again > at 08:00. > > I've checked and rechecked the settings on the thing, and it > positively, definitely, absolutely does *not* have a scheduled power > cycle at that time. In fact I'd completely disabled it during the > experiment (but of course left it connected), yet it still decided to > do this entirely of its own volition. > > In other words, it's a bug in the plug. > > Given that I actually do want to reboot (i.e. resume) at 08:00, I could > just hibernate as normal and let it do its thing, but I don't like > magic solutions. I may decide to replace it if I can get a refund (or > even if not - it was cheap). > > I appreciate everyone's efforts to help with this, even if in the end > it had nothing to do with Fedora, or hibernation, or my computer. > > Thanks guys. > > poc > _______________________________________________ > users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx > Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
