Michael Biebl a écrit :
> If the nm-applet does not show up, it often means that the hal daemon is
> not running.
> Could you please check next time you resume from suspend, that the dbus
> and hal daemon are running correctly (what does nm-tool say after resume)

So :
- the applet is still in my toolbar but it does not show any interface anymore.
- nm-tool show me :
[EMAIL PROTECTED]:~$ nm-tool

NetworkManager Tool

State: disconnected

print_devices(): didn't get a reply from NetworkManager.
There are no available network devices.
[EMAIL PROTECTED]:~$
- ifup/ifconfig/... (ie low level tools) still works correctly
- dbus and hal deamon seems to be still here :
[EMAIL PROTECTED]:~$ ps axf | egrep '(dbus|hal)'
 4341 ?        Ss     0:02 /usr/bin/dbus-daemon --system
 4349 ?        Ss     0:39 /usr/sbin/hald
 4350 ?        S      0:00  \_ hald-runner
 4356 ?        S      0:00      \_ hald-addon-acpi: listening on acpid socket 
/var/run/acpid.socket
 4374 ?        S      0:00      \_ hald-addon-keyboard: listening on 
/dev/input/event0
 4391 ?        S      0:12      \_ hald-addon-storage: polling /dev/scd0
 5598 ?        Ss     0:06          \_ /usr/bin/ssh-agent /usr/bin/dbus-launch 
--exit-with-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session
 5601 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session 
/usr/bin/seahorse-agent --execute /usr/bin/gnome-session
 5602 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 4 
--print-address 6 --session
 3510 pts/6    S+     0:00      \_ grep -E (dbus|hal)
[EMAIL PROTECTED]:~$

  What do you want else ? What can I try for you ?

  Best regards,
    Vincent

PS:
  As usual, executing /etc/init.d/dbus restart makes all ok:
[EMAIL PROTECTED]:~$ sudo /etc/init.d/dbus restart
Stopping network events dispatcher: NetworkManagerDispatcher.
Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Stopping network connection manager: NetworkManager.
Stopping DHCP D-Bus daemon: dhcdbd.
Stopping Hardware abstraction layer: hald.
Stopping system message bus: dbus.
Starting system message bus: dbus.
Starting Hardware abstraction layer: hald.
Starting DHCP D-Bus daemon: dhcdbd.
Starting network connection manager: NetworkManager.
Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
Starting network events dispatcher: NetworkManagerDispatcher.
[EMAIL PROTECTED]:~$ nm-tool

NetworkManager Tool

State: connected

- Device: eth5 ----------------------------------------------------------------
  NM Path:           /org/freedesktop/NetworkManager/Devices/eth5
  Type:              Wired
  Driver:            tg3
  Active:            no
  HW Address:        00:14:22:C1:0F:5A

  Capabilities:
    Supported:       yes
    Carrier Detect:  yes
    Speed:           100 Mb/s

  Wired Settings
    Hardware Link:   no


- Device: eth6 ----------------------------------------------------------------
  NM Path:           /org/freedesktop/NetworkManager/Devices/eth6
  Type:              802.11 Wireless
  Driver:            ipw2200
  Active:            yes
  HW Address:        00:13:CE:C5:F6:6F

  Capabilities:
    Supported:       yes
    Speed:           54 Mb/s

  Wireless Settings
    Scanning:        yes
    WEP Encryption:  yes
    WPA Encryption:  yes
    WPA2 Encryption: yes

  Wireless Networks (* = Current Network)
    *U1-IMA-UJF:     Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, 
Strength 52%
    DRAKKAR1:        Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, 
Strength 39%
    IMAG-ENS:        Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, 
Strength 31%
    PLAYBOT_WIFI:    Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, 
Strength 29%, Encrypted (WEP)
    IMAG-VPN:        Infrastructure Mode, Freq 0.000 MHz, Rate 62 Mb/s, 
Strength 25%

  IP Settings:
    IP Address:      10.1.18.162
    Subnet Mask:     255.255.255.0
    Broadcast:       10.1.18.255
    Gateway:         10.1.18.254
    Primary DNS:     152.77.2.5
    Secondary DNS:   193.54.238.51


[EMAIL PROTECTED]:~$ ps axf | egrep '(dbus|hal)'
 5598 ?        Ss     0:06          \_ /usr/bin/ssh-agent /usr/bin/dbus-launch 
--exit-with-session /usr/bin/seahorse-agent --execute /usr/bin/gnome-session
 5601 ?        S      0:00 /usr/bin/dbus-launch --exit-with-session 
/usr/bin/seahorse-agent --execute /usr/bin/gnome-session
 5602 ?        Ss     0:00 /usr/bin/dbus-daemon --fork --print-pid 4 
--print-address 6 --session
 4436 pts/6    S+     0:00      \_ grep -E (dbus|hal)
 3709 ?        Ss     0:00 /usr/bin/dbus-daemon --system
 3717 ?        Ss     0:01 /usr/sbin/hald
 3718 ?        S      0:00  \_ hald-runner
 3725 ?        S      0:00      \_ hald-addon-acpi: listening on acpid socket 
/var/run/acpid.socket
 3735 ?        S      0:00      \_ hald-addon-keyboard: listening on 
/dev/input/event0
 3752 ?        S      0:00      \_ hald-addon-storage: polling /dev/scd0
 4118 ?        S      0:00  \_ /sbin/dhclient -1 -lf 
/var/lib/dhcp3/dhclient.eth6.leases -pf /var/run/dhclient.eth6.pid -q -e 
dhc_dbus=31 -d eth6
[EMAIL PROTECTED]:~$



> I doubt it's a bug in network-manager, but rather in your driver or
> hal-backend. What do you use as hal-backend, powersave, hibernate,
> acpi-support?
> 
> Cheers,
> Michael
> 
> 


Reply via email to