Description of problem: cjdns-resume is supposed to restart cjdns on resume from suspend. But, After=sleep.target often results in restarting before suspend - it is timing dependent. Version-Release number of selected component (if applicable): cjdns-21.1-3.fc34.x86_64 How reproducible: Usually Steps to Reproduce: 1. Suspend 2. Resume 3. Check journalctl to see when cjdns was actually restarted Actual results: Often, cjdns is restarted before suspend Expected results: Cjdns is restarted after resume Additional info: It may be necessary to use a hook in /usr/lib/systemd/system-sleep instead.
This is having the effect of often disabling cjdroute until it is restarted. Upping the priority. End user work around: reboot (shades of Windoze)
Put this in /usr/lib/systemd/system-sleep/cjdns.sleep. Will test on a number of laptops. #!/bin/sh if [ "${1}" == "pre" ]; then # Do the thing you want before sleep here elif [ "${1}" == "post" ]; then # Do the thing you want after resume here, e.g.: systemctl restart cjdns fi
That fix does not work - because it restarts cjdns before the wireless reconnects on a typical laptop. Back to the drawing board.
Best workaround seems to be to disable cjdns-resume and just wait for cjdroute to smell the coffee ...
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
This message is a reminder that Fedora Linux 35 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '35'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 35 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13. Fedora Linux 35 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.