Hi!
Am 27.04.2007 13:32, schrieb Steinar H. Gunderson:
Package: network-manager
Version: 0.6.4-8+b1
Severity: important
Whenever I suspend my D420 (by closing the lid) and resume,
network-manager dies completely; it just shows the standard icon of a
computer with an X, with the menu only
On Thu, May 03, 2007 at 09:17:20AM +0200, Michael Biebl wrote:
Hm. I understand that it might be difficult to fix then. Perhaps we should
send it upstream?
Could be related to
http://bugzilla.gnome.org/show_bug.cgi?id=372840
Doesn't seem to be; three of the four threads wait in poll(), which
Steinar H. Gunderson wrote:
On Wed, May 02, 2007 at 12:02:02PM +0200, Michael Biebl wrote:
You don't have to restart nm for that. Simply left click on the
nm-applet notification are icon. This triggers a rescan after 30 secs.
So your network should show up quickly. Don't click multiple time on
severity 421251 important
thanks
On Fri, Apr 27, 2007 at 05:42:42PM +0200, Michael Biebl wrote:
As a workaround, you can tell g-p-m to not notify NetworkManager.
Edit the gconf key (via gconf-editor)
/apps/gnome-power-manager/networkmanager_sleep and set it to false.
As there is a working
tags 421251 unreproducible
thanks
Steinar H. Gunderson wrote:
severity 421251 important
thanks
On Fri, Apr 27, 2007 at 05:42:42PM +0200, Michael Biebl wrote:
As a workaround, you can tell g-p-m to not notify NetworkManager.
Edit the gconf key (via gconf-editor)
On Wed, May 02, 2007 at 12:02:02PM +0200, Michael Biebl wrote:
You don't have to restart nm for that. Simply left click on the
nm-applet notification are icon. This triggers a rescan after 30 secs.
So your network should show up quickly. Don't click multiple time on the
icon, because this will
Steinar H. Gunderson wrote:
Package: network-manager
Version: 0.6.4-8+b1
Severity: important
Whenever I suspend my D420 (by closing the lid) and resume,
network-manager dies completely; it just shows the standard icon of a
computer with an X, with the menu only showing a greyed-out cable
On Fri, Apr 27, 2007 at 02:33:20PM +0200, Michael Biebl wrote:
IIRC, the ipw3945 uses a separate regulatory daemon. Have you checked if
this daemon is still running after hibernate/resume? Maybe the suspend
scripts you are using are stopping this daemon.
Yes, it is. Note that this works fine
Steinar H. Gunderson wrote:
On Fri, Apr 27, 2007 at 02:33:20PM +0200, Michael Biebl wrote:
I doubt it's a bug in NM, rather in the driver.
I'm not sure how you can think that when it works if NM doesn't know about
the wakeup...
Because NM works perfectly with other drivers and it does
On Fri, Apr 27, 2007 at 03:06:37PM +0200, Michael Biebl wrote:
I'm not sure how you can think that when it works if NM doesn't know about
the wakeup...
Because NM works perfectly with other drivers and it does not anything
special for ipw3945. Googling for ipw3945 reveils many hits with people
Steinar H. Gunderson wrote:
On Fri, Apr 27, 2007 at 02:33:20PM +0200, Michael Biebl wrote:
IIRC, the ipw3945 uses a separate regulatory daemon. Have you checked if
this daemon is still running after hibernate/resume? Maybe the suspend
scripts you are using are stopping this daemon.
Yes, it
On Fri, Apr 27, 2007 at 03:47:54PM +0200, Michael Biebl wrote:
Does it still work if you run:
dbus-send --system \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager\
org.freedesktop.NetworkManager.sleep
sleep 1
severity 421251 minor
thanks
Steinar H. Gunderson wrote:
On Fri, Apr 27, 2007 at 03:47:54PM +0200, Michael Biebl wrote:
Does it still work if you run:
dbus-send --system \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager
On Fri, Apr 27, 2007 at 05:42:42PM +0200, Michael Biebl wrote:
What happens if you leave out the hal-system-power-sleep-linux call and
simply put NM into sleep and wake it up again?
Then it works.
What happens if you unload/load the ipw3945 module in between?
Still works.
I don't own a
14 matches
Mail list logo
