Happens on Ubuntu 16.10 (fresh install, Compiz fallback session) after a few hours of uptime. htop reports 100% usage of one CPU for the command
/sbin/initctl emit indicator-services-start
which goes on indefinitely. Tracing (with only this initctl process around) yields similar to #5
$ sudo strace -p `pidof initctl` poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}]) [endless repeat]
/var/log/upstart is empty and dmesg/kern.log/syslog don't help.
The random battery drain is annoying (especially during presentations), and apt purging upstart depends on a little too much for comfort.
Suggestions?
Happens on Ubuntu 16.10 (fresh install, Compiz fallback session) after a few hours of uptime.
htop reports 100% usage of one CPU for the command
/sbin/initctl emit indicator- services- start
which goes on indefinitely. Tracing (with only this initctl process around) yields similar to #5
$ sudo strace -p `pidof initctl`
poll([{fd=3, events=POLLIN}], 1, -1) = 1 ([{fd=3, revents=POLLIN}])
[endless repeat]
/var/log/upstart is empty and dmesg/kern. log/syslog don't help.
The random battery drain is annoying (especially during presentations), and apt purging upstart depends on a little too much for comfort.
Suggestions?