Re: dbus-send sleep/wake does not always trigger the action
There is a bug about it. please add your information! http://bugzilla.gnome.org/show_bug.cgi?id=423885 - Messaggio originale - Da: Dawid Wróbel [EMAIL PROTECTED] A: networkmanager-list@gnome.org Inviato: Venerdì 30 marzo 2007, 2:30:48 Oggetto: dbus-send sleep/wake does not always trigger the action Hi, I was investigating something weird today. It seemed that NM doesn't switch offline everytime it's supposed to. I noticed that when it was done through the scripts (e.g. pm-utils). After trying 'manually' I was really confused to see that it was either NM or dbus fault. I had real evidence when I saw that after 5 tries of executing dbus-send --system --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager org.freedesktop.NetworkManager.sleep NM would still be online. What I noticed is that I have to stay away from dbus/NM for some time for this problem to appear. Moreover, I noticed that sometimes NM-Dispatcher doesn't execute the scripts, despite NM changing it's online state into offline and back. Dbus-monitor unfortunately seems to not inform about anything at all. dbus 1.0.2 networkmanager 0.6.4 -- Regards, Dawid Wróbel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list ___ L'email della prossima generazione? Puoi averla con la nuova Yahoo! Mail: http://it.docs.yahoo.com/nowyoucan.html ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dbus-send sleep/wake does not always trigger the action
Dnia Fri, 30 Mar 2007 08:43:39 + (GMT) yelo_3 [EMAIL PROTECTED] napisał: There is a bug about it. please add your information! http://bugzilla.gnome.org/show_bug.cgi?id=423885 This is something different. It's not that it's just applet that doesn't show correct connection state, it's the whole NM that doesn't suspend/wake - I can see that in the system logs that nothing happens at all. Also, please note that frequent Dispatcher problem. For example now I can clearly see it doesn't work. NM manages to change it's connection status the dispatcher scripts are not executed. Dispatcher is obviously demonized in the background. It will be like this until I restart it. -- Regards, Dawid Wróbel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dbus-send sleep/wake does not always trigger the action
On 3/30/07, Dawid Wróbel [EMAIL PROTECTED] wrote: Dnia Fri, 30 Mar 2007 08:43:39 + (GMT) yelo_3 [EMAIL PROTECTED] napisał: There is a bug about it. please add your information! http://bugzilla.gnome.org/show_bug.cgi?id=423885 This is something different. It's not that it's just applet that doesn't show correct connection state, it's the whole NM that doesn't suspend/wake - I can see that in the system logs that nothing happens at all. Also, please note that frequent Dispatcher problem. For example now I can clearly see it doesn't work. NM manages to change it's connection status the dispatcher scripts are not executed. Dispatcher is obviously demonized in the background. It will be like this until I restart it. It sounds a lot like some sort of DBUS issue that prevents the messages to reach NM. Is the system bus really busy when it happens? There are some limits in dbus for maximum number of pending calls. Messages that do not fit in that limit are just dropped (AFAIK). Tambet ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: dbus-send sleep/wake does not always trigger the action
On Fri, 30 Mar 2007 17:47:04 +0300 Tambet Ingo [EMAIL PROTECTED] wrote: It sounds a lot like some sort of DBUS issue that prevents the messages to reach NM. Is the system bus really busy when it happens? There are some limits in dbus for maximum number of pending calls. Messages that do not fit in that limit are just dropped (AFAIK). I managed to run dbus-monitor and dbus doesn't seem busy at all. Couple of messages every couple of tens of seconds. What I noticed is that in case I send a dbus sleep/wake command and NM does nothing with it, dbus-monitor reports only: signal sender=org.freedesktop.DBus - dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.185 string string :1.185 signal sender=org.freedesktop.DBus - dest=(null destination) path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameOwnerChanged string :1.185 string :1.185 string And nothing else happens. In case it works as supposed (usually after a couple of tries with the wake/sleep command), I additionally get: signal sender=:1.2 - dest=(null destination) path=/org/freedesktop/NetworkManager; interface=org.freedesktop.NetworkManager; member=StateChange uint32 4 and the rest of the stuff you probably know very well. Also, when I manage to wake it up, it takes quite a lot of time for it to begin dhcp negotiations. Please note that 20s gap and sorry for formatting: Mar 30 17:06:26 kromka NetworkManager: informationWaking up from sleep. Mar 30 17:06:26 kromka NetworkManager: informationDeactivating device ath0. Mar 30 17:06:26 kromka NetworkManager: informationDeactivating device eth0. Mar 30 17:06:26 kromka NetworkManager: informationath0: Device is fully-supported using driver 'ath_pci'. Mar 30 17:06:26 kromka NetworkManager: informationnm_device_init(): waiting for device's worker thread to start Mar 30 17:06:26 kromka NetworkManager: informationnm_device_init(): device's worker thread started, continuing. Mar 30 17:06:26 kromka NetworkManager: informationNow managing wireless (802.11) device 'ath0'. Mar 30 17:06:26 kromka NetworkManager: informationDeactivating device ath0. Mar 30 17:06:26 kromka NetworkManager: informationeth0: Device is fully-supported using driver 'tg3'. Mar 30 17:06:26 kromka NetworkManager: informationnm_device_init(): waiting for device's worker thread to start Mar 30 17:06:26 kromka NetworkManager: informationnm_device_init(): device's worker thread started, continuing. Mar 30 17:06:26 kromka NetworkManager: informationNow managing wired Ethernet (802.3) device 'eth0'. Mar 30 17:06:26 kromka NetworkManager: informationDeactivating device eth0. Mar 30 17:06:47 kromka NetworkManager: informationSWITCH: no current connection, found better connection 'ath0'. Mar 30 17:06:47 kromka NetworkManager: informationWill activate connection 'ath0/some_essid'. Mar 30 17:06:47 kromka NetworkManager: informationDevice ath0 activation scheduled... Mar 30 17:06:47 kromka NetworkManager: informationActivation (ath0) started... Mar 30 17:06:47 kromka NetworkManager: informationActivation (ath0) Stage 1 of 5 (Device Prepare) scheduled. (...) -- Regards, Dawid Wróbel ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
