Comment 21 for bug 1169614

Revision history for this message
Steve Dodd (anarchetic) wrote :

OK, if you can change /etc/init/network-manager.conf so the exec line reads:

exec NetworkManager --log-level=DEBUG

And apply the attached patch to the n-m sources, rebuild & install, what happens? (As you need syslogd to stay up to log the results, just 'sudo stop network-manager' and have a in /var/log/syslog.)

I see (slightly edited):

Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> caught signal 15, shutting down normally.
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38]
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): deactivating device (reason 'connection-removed') [38]
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <debug> [nm-dhcp-client.c:148] nm_dhcp_client_stop_pid(): Sending SIGTERM to 27161.
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): canceled DHCP transaction, DHCP client pid 27161

?field.comment=OK, if you can change /etc/init/network-manager.conf so the exec line reads:

exec NetworkManager --log-level=DEBUG

And apply the attached patch to the n-m sources, rebuild & install, what happens? (As you need syslogd to stay up to log the results, just 'sudo stop network-manager' and have a in /var/log/syslog.)

I see (slightly edited):

Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> caught signal 15, shutting down normally.
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): device state change: activated -> disconnected (reason 'connection-removed') [100 30 38]
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): deactivating device (reason 'connection-removed') [38]
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <debug> [nm-dhcp-client.c:148] nm_dhcp_client_stop_pid(): Sending SIGTERM to 27161.
Mar 4 22:07:44 xubuntu NetworkManager[27154]: <info> (eth0): canceled DHCP transaction, DHCP client pid 27161