[Pkg-utopia-maintainers] Bug#859147: Bug#859147: network-manager: restart failure on upgrade

[ydirson at free.fr]

Will test this soon.

Oh, just noticed that the fan was indeed noisy... and top reports this:

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND                                                                                                                   
 6019 root      20   0  237608  96996   2368 R 100.0  1.2   0:30.49 (kManager)                                                                                                                

I can't seem to find what a "kManager" process could be around here.  There
is but a common suffix with NetworkManager, but I admit I don't see why it
would be truncated.  Looking at /proc it just looks like a systemd thread, and
it gets started and restarted again and again.

----- Mail original -----
> De: "Michael Biebl" <biebl at debian.org>
> À: ydirson at free.fr
> Cc: 859147 at bugs.debian.org
> Envoyé: Vendredi 31 Mars 2017 11:12:38
> Objet: Re: [Pkg-utopia-maintainers] Bug#859147: network-manager: restart failure on upgrade
> 
> Am 31.03.2017 um 11:08 schrieb ydirson at free.fr:
> > Here is the relevant journalctl -alb excerpt, sending more details
> > in private mail
> > 
> > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager Wait
> > Online...
> > Mar 30 20:22:06 yantop systemd[1]: Stopping Network Manager...
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.5839] caught SIGTERM, shutting down normally.
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.6660] device (wlan0): state change: unavailable ->
> > unmanaged (reason 'unmanaged') [20 10 3]
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.6663] device (wlan0): set-hw-addr: reset MAC address
> > to B4:6D:83:58:53:31 (unmanage)
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.6676] device (E0:98:61:62:F4:53): state change:
> > disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.6761] device (44:00:10:24:8F:70): state change:
> > disconnected -> unmanaged (reason 'unmanaged') [30 10 3]
> > Mar 30 20:22:06 yantop NetworkManager[4948]: <info>
> >  [1490898126.8186] exiting (success)
> > Mar 30 20:22:07 yantop systemd[1]: Stopped Network Manager.
> > Mar 30 20:22:07 yantop systemd[1]: Starting Network Manager...
> > Mar 30 20:23:06 yantop systemd[1]: Starting Laptop Mode Tools -
> > Battery Polling Service...
> > Mar 30 20:23:06 yantop systemd[1]: Reloading Laptop Mode Tools.
> > Mar 30 20:23:06 yantop systemd[1]: Started Laptop Mode Tools -
> > Battery Polling Service.
> > Mar 30 20:23:06 yantop laptop_mode[5372]: Laptop mode
> > Mar 30 20:23:06 yantop laptop_mode[5372]: enabled, not active
> > [unchanged]
> > Mar 30 20:23:06 yantop systemd[1]: Reloaded Laptop Mode Tools.
> > Mar 30 20:23:37 yantop systemd-journald[398]: Suppressed 1050
> > messages from /init.scope
> > Mar 30 20:23:37 yantop systemd[1]: NetworkManager.service: Start
> > operation timed out. Terminating.
> 
> Your systemd instance seems to be in a confused state. I wonder if
> that's related to laptop-mode-tools.
> Try purging that package and reboot to reset the state.
> 
> 
> --
> Why is it that all of the instruments seeking intelligent life in the
> universe are pointed away from Earth?
> 
>