That's because what I instructed in #15 makes laptop-mode-tools
ineffective to USB hotplug events. Not something that a user would want.
As I see from the reports, this is what I think is happening.
1) Users have some combination of usb devices, getting hotplugged upon
discovery.
2) Step 1
Okay. Thanks for the reports. It could very well be the flakiness in usb
devices that are causing this problem. Anyways, the best fix for this is to
contain usb execution to the runtime module only.
Note to self: per module activation was reported to not activating general
power savings. Check
Thanks for confirming @reckenrode. I'd appreciate if more users
confirmed the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1726930
Title:
System fails to start
This would still be a flaky device or a kernel bug. Because the
mentioned laptop-mode-tools version (1.71) brought in forced execution
mode, so that it could apply proper power saving values. That's pretty
much it. That does not result in read only rootfs because if it
logically did, it'd be seen
Folks...
Does changing to following in /lib/udev/rules.d/99-laptop-mode.rules
help ?
ACTION=="add", SUBSYSTEM=="usb", RUN+="lmt-udev auto"
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
This must be an Ubuntu specific problem. I haven't encountered the problem
upstream.
https://GitHub.com/rickysarraf/laptop-mode-tools
s3nt fr0m a $martph0ne, excuse typ0s
On 07-Dec-2017 02:36, "timor" <1726...@bugs.launchpad.net> wrote:
> Uninstalling laptop-mode-tools helped me, but it's
This was fixed in the upload of apport 2.17.3-1 to Debian Experimental
** Changed in: apport (Debian)
Status: New = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
7 matches
Mail list logo
