Do you want it in normal running (which is what the above instructions would achieve) or when there is an error?
I don't know how to provoke the error other than it occurs a few days after my last reboot and some number of cycles of suspend/hibernate although that may be a red herring. My main point in filing this bug was so that if anyone else sees the same issues they know they are not alone. Do you still want many days worth of logs, or have a way of collecting useful state information once it is in the borked state? (Feel free to just give a list of tools like lsof/strace etc - I've been a developer since long before either Linux or Python existed.) -- Connected and not connected, requires reboot to unwedge https://bugs.launchpad.net/bugs/527580 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
