Comment 29 for bug 1450396
Revision history for this message
| Jan Rathmann (kaiserclaudius) wrote | #29 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Christopher, yes, my workaround seems to work in both cases 1) and 2) ( =PC stays suspended properly and doesn't power itself on unwantedly). Btw. it seems that which graphics driver is in use is completely unrelated to this bug.
Regarding 3):
- It doesn't seem to matter if I suspend by pressing power button, session menu in Unity or executing 'systemctl suspend'. As noted before, the bug never appears when suspending with 'pm-suspend', because that implicitly does the same thing as my workaround (=explicitly setting wol flag to 'g' on my network card).
- Is it really necessary to provide a resume trace? As far as I understand, this is for cases when resume fails/doesn't work properly, but this bug is _not_ about that resume fails, but that it works correctly, but is triggered automatically (and undesired) by wake-on-lan.
Kind regards,
Jan