http://bugzilla.suse.com/show_bug.cgi?id=965475
http://bugzilla.suse.com/show_bug.cgi?id=965475#c15
--- Comment #15 from Franck Bui
(In reply to Franck Bui from comment #13)
Doesn't help with my laptop issues, unfortunately :(
Are you laptop issues also involve "fix.service" unit ?
I don't know. At least it did not help to simply remove that fix.service. I tried that.
That sounds like another bug IMO.
Probably not - I don't think I saw the "Found ordering cycle" message there.
Did they appear after upgrading systemd from 208 to 210 ?
Yes.
I can try reverting to 208 on that laptop, tomorrow. (it's remote without anybody near at the moment, and after downgrade from 210 to 208 shutdown does not work, unfortunately....)
If there is anything that I could usefully run and save the output of, comparing the situation on the laptop before and after the 210->208 downgrade attempt?
Well if you cannot easily switch back to 208 that doesn't really matter, this info could have been useful but we can live without it. I would suggest to create a new bug (since removing fix.service is not enough) and attach the output of 'journalctl -b'. Before doing that, make sure to reboot and add to the kernel command line 'systemd.log_level=debug' and also remove 'quiet' from it. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.