Re: After laptop resume NM doesn't come active

[binro <robin binro org>]

binro wrote:
> 
> 
> Dan Williams wrote:
>> 
>> On Tue, 2012-04-24 at 08:03 -0700, binro wrote:
>>> 
>>> binro wrote:
>>> > 
>>> > After I wakeup my laptop NM re-activates the WiFi connection. That
>>> works
>>> > but NM never seems to see the signal that tells it a connection is up
>>> and
>>> > to change its status to started (this is a Gentoo system). Hence
>>> network
>>> > dependent services never start. Is there some dbus invocation I can
>>> use to
>>> > make NM change state?
>>> > 
>>> > TIA
>>> > 
>>> > 
>>> I "solved" the problem by plugging in an ether net cable which generated
>>> an
>>> event and NM became started. But I don't regard this as a permanent
>>> solution... ;)
>> 
>> When this happens, can you run "nmcli nm" and post the output?
>> 
>> 
> 
> topaz robin # serv NetworkManager status
>  * status: inactive
> topaz robin # nmcli nm
> RUNNING         STATE           WIFI-HARDWARE   WIFI       WWAN-HARDWARE  
> WWAN      
> running         connected       enabled         enabled    enabled        
> disabled  
> 
> The network is up and running as I post this, just NM'a status is wrong.
> 
Hmm, not too much interest in this problem. Here is the syslog after the
DHCP expires:

Apr 28 19:15:13 topaz dhcpcd[7562]: wlan0: leased 192.168.1.40 for 43200
seconds
Apr 28 19:15:13 topaz NetworkManager[7023]: <info> (wlan0): DHCPv4 state
changed preinit -> bound
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   address 192.168.1.40
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   prefix 24
(255.255.255.0)
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   gateway 192.168.1.1
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   hostname 'topaz'
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   nameserver
'192.168.1.2'
Apr 28 19:15:13 topaz NetworkManager[7023]: <info>   domain name 'binro.org'
Apr 28 19:15:13 topaz NetworkManager[7023]: <info> Activation (wlan0) Stage
5 of 5 (IPv4 Configure Commit) scheduled...
Apr 28 19:15:13 topaz NetworkManager[7023]: <info> Activation (wlan0) Stage
5 of 5 (IPv4 Commit) started...
Apr 28 19:15:14 topaz NetworkManager[7023]: <info> Clearing nscd hosts
cache.
Apr 28 19:15:14 topaz NetworkManager[7023]: <info> (wlan0): device state
change: ip-config -> activated (reason 'none') [70 100 0]
Apr 28 19:15:14 topaz NetworkManager[7023]: <info> Policy set 'Binro.Org'
(wlan0) as default for IPv4 routing and DNS.
Apr 28 19:15:14 topaz NetworkManager[7023]: <info> Activation (wlan0)
successful, device activated.
Apr 28 19:15:14 topaz NetworkManager[7023]: <info> Activation (wlan0) Stage
5 of 5 (IPv4 Commit) complete.
Apr 28 19:15:14 topaz dbus[6961]: [system] Activating service
name='org.freedesktop.nm_dispatcher' (using servicehelper)
Apr 28 19:15:14 topaz dbus[6961]: [system] Successfully activated service
'org.freedesktop.nm_dispatcher'
Apr 28 19:15:14 topaz /etc/init.d/NetworkManager[7602]: status: inactive


Dbus sends the activate signal but NM remains inactive. That looks like a
bug too me.

-- 
View this message in context: http://old.nabble.com/After-laptop-resume-NM-doesn%27t-come-active-tp33728260p33763301.html
Sent from the Gnome - NetworkManager mailing list archive at Nabble.com.