Hans Deragon

I have the latest version of FAH and I confirmed that it is still coded for Python 2. @jwesterdale-rh, solution to replace the first line of the scripts with `#!/usr/bin/env...

Fixed with commit #https://github.com/deragon/autopoweroff/commit/125a7f8de009b7236b65e1690fd57cac23c67cf4.

Yes, me too since I moved to Ubuntu 22.04 LTS... Ugh... dependencies change with distributions. I need to start creating more distribution dependent packages. Need time to do this...

Fixed (hoperfully) in [release 4.1.2](https://github.com/deragon/autopoweroff/releases/tag/4.1.2). Please provide feedback.

@creativecoder , the command tell you what the problem is. :) _Package autopoweroff-daemon is not installed._ You have to install the daemon too. The GUI does not include the daemon....

When you power up the computer, is it in the [StartHour, EndHour] range defined in `/etc/autopoweroff/autopoweroff.conf`? Because that is what you want. The computer must wake up in the range...

Ah yes, there are also these two parameters you should consider: ``` # StartupDelay parameter (expressed in minutes): # # When the computer is booting up, if all the conditions...

Yes, I confirmed I fixed it in commit [ff57c44d1ccda7ab1770b668529fdb776f976150](https://github.com/deragon/autopoweroff/commit/ff57c44d1ccda7ab1770b668529fdb776f976150), which made it into 4.2.0 as @it-jonas stated (thanks Jonas). I fixed it because myself, during testing, suffered of the same...

More than a year later, I still have this problem. After many other more important fixes, I will tackle this one next. Sorry for the soo long delay... My life...

I did not find direct evidence, but from what I read, Sys-V init.d script are not handled properly by systemd and thus this bug. :( I am in the process...