[resolu] Network-manager plante si ipw3945 chargé

Support Debian
#1

[resolu en utilisant wicd]

Hello,

Tout d’abord bonjour… c’est mon 1er message. Je viens de migrer de Ubuntu à Debian testing sur T60p sans trop de problèmes.

Mais lors de depuis les derniers updates network-manager ne fonctionne plus vraiment. L’icone est là, mais rien ne se passe:
-lors d’un démarage -> reste en état déconnecté (même si le net fonctionne si j’ai mis un câble avant le démrage)
-si je relance network-manager -> reste en recherche (même avec un câble)

Par contre si je désactive ma carte wifi (en déchargeant le module) tout fonctionne (sauf lw wifi évidement…).

log SANS ipw3945 donc connection réussi

Mar 25 11:46:51 area42 hcid[3239]: HCI dev 0 down
Mar 25 11:46:51 area42 hcid[3239]: Stopping security manager 0
Mar 25 11:46:51 area42 hcid[3239]: Device hci0 has been disabled
Mar 25 11:46:52 area42 hcid[3239]: HCI dev 0 unregistered
Mar 25 11:46:52 area42 hcid[3239]: Unregister path: /org/bluez/hci0
Mar 25 11:46:52 area42 hcid[3239]: Device hci0 has been removed
Mar 25 11:47:07 area42 NetworkManager: <info>  starting... 
Mar 25 11:47:07 area42 NetworkManager: <info>  New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn). 
Mar 25 11:47:07 area42 NetworkManager: <info>  New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc). 
Mar 25 11:47:07 area42 NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch 
Mar 25 11:47:07 area42 NetworkManager: <info>  eth1: Device is fully-supported using driver 'ipw3945'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Mar 25 11:47:07 area42 NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Now managing wireless (802.11) device 'eth1'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Deactivating device eth1. 
Mar 25 11:47:07 area42 NetworkManager: <info>  eth0: Device is fully-supported using driver 'e1000'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Mar 25 11:47:07 area42 NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Deactivating device eth0. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Updating allowed wireless network lists. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
Mar 25 11:47:07 area42 NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Will activate connection 'eth0'. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Device eth0 activation scheduled... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) started... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Old device 'eth0' activating, won't change. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
Mar 25 11:47:07 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Mar 25 11:47:07 area42 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 3240
Mar 25 11:47:07 area42 dhclient: killed old client process, removed PID file
Mar 25 11:47:07 area42 NetworkManager: <info>  Error getting killswitch power arguments:  - ^E 
Mar 25 11:47:07 area42 NetworkManager: <info>  Wireless now enabled by radio killswitch 
Mar 25 11:47:07 area42 dhclient: DHCPRELEASE on eth0 to 10.248.80.1 port 67
Mar 25 11:47:07 area42 dhclient: send_packet: Network is unreachable
Mar 25 11:47:07 area42 dhclient: send_packet: please consult README file regarding broadcast address.
Mar 25 11:47:38 area42 NetworkManager: <info>  starting... 
Mar 25 11:47:38 area42 NetworkManager: <info>  New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn). 
Mar 25 11:47:38 area42 NetworkManager: <info>  New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc). 
Mar 25 11:47:38 area42 NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch 
Mar 25 11:47:38 area42 NetworkManager: <info>  eth0: Device is fully-supported using driver 'e1000'. 
Mar 25 11:47:38 area42 NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Mar 25 11:47:38 area42 NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Deactivating device eth0. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Updating allowed wireless network lists. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
Mar 25 11:47:38 area42 NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Will activate connection 'eth0'. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Device eth0 activation scheduled... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) started... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Old device 'eth0' activating, won't change. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
Mar 25 11:47:38 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Mar 25 11:47:38 area42 NetworkManager: <info>  Error getting killswitch power: org.freedesktop.Hal.Device.KillSwitch.NotSupported - hal-ipw-killswitch-linux returned 255 
Mar 25 11:47:38 area42 NetworkManager: <info>  Wireless now enabled by radio killswitch 
Mar 25 11:47:39 area42 NetworkManager: <info>  Activation (eth0) Beginning DHCP transaction. 
Mar 25 11:47:39 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) complete. 
Mar 25 11:47:39 area42 NetworkManager: <info>  DHCP daemon state is now 12 (successfully started) for interface eth0 
Mar 25 11:47:40 area42 NetworkManager: <info>  DHCP daemon state is now 1 (starting) for interface eth0 
Mar 25 11:47:40 area42 dhclient: DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 3
Mar 25 11:47:40 area42 dhclient: DHCPOFFER from 10.248.80.1
Mar 25 11:47:40 area42 dhclient: DHCPREQUEST on eth0 to 255.255.255.255 port 67
Mar 25 11:47:40 area42 dhclient: DHCPACK from 10.248.80.1
Mar 25 11:47:41 area42 NetworkManager: <info>  DHCP daemon state is now 2 (bound) for interface eth0 
Mar 25 11:47:41 area42 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) scheduled... 
Mar 25 11:47:41 area42 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) started... 
Mar 25 11:47:41 area42 dhclient: bound to 84.73.190.22 -- renewal in 1536 seconds.
Mar 25 11:47:41 area42 NetworkManager: <info>  Retrieved the following IP4 configuration from the DHCP daemon: 
Mar 25 11:47:41 area42 NetworkManager: <info>    address 84.73.190.22 
Mar 25 11:47:41 area42 NetworkManager: <info>    netmask 255.255.252.0 
Mar 25 11:47:41 area42 NetworkManager: <info>    broadcast 255.255.255.255 
Mar 25 11:47:41 area42 NetworkManager: <info>    gateway 84.73.188.1 
Mar 25 11:47:41 area42 NetworkManager: <info>    nameserver 62.2.17.60 
Mar 25 11:47:41 area42 NetworkManager: <info>    nameserver 62.2.24.162 
Mar 25 11:47:41 area42 NetworkManager: <info>    nameserver 62.2.17.61 
Mar 25 11:47:41 area42 NetworkManager: <info>    nameserver 62.2.24.158 
Mar 25 11:47:41 area42 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) scheduled... 
Mar 25 11:47:41 area42 NetworkManager: <info>  Activation (eth0) Stage 4 of 5 (IP Configure Get) complete. 
Mar 25 11:47:41 area42 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) started... 
Mar 25 11:47:42 area42 NetworkManager: <info>  DHCP returned name servers but system has disabled dynamic modification! 
Mar 25 11:47:42 area42 NetworkManager: <info>  Activation (eth0) Finish handler scheduled. 
Mar 25 11:47:42 area42 NetworkManager: <info>  Activation (eth0) Stage 5 of 5 (IP Configure Commit) complete. 
Mar 25 11:47:42 area42 NetworkManager: <info>  Activation (eth0) successful, device activated.

log AVEC ipw3945 donc connection impossible ni en wifi ni via câble

Mar 25 11:48:55 area42 NetworkManager: <info>  starting... 
Mar 25 11:48:55 area42 NetworkManager: <info>  New VPN service 'openvpn' (org.freedesktop.NetworkManager.openvpn). 
Mar 25 11:48:55 area42 NetworkManager: <info>  New VPN service 'vpnc' (org.freedesktop.NetworkManager.vpnc). 
Mar 25 11:48:55 area42 NetworkManager: <info>  Found radio killswitch /org/freedesktop/Hal/devices/ipw_wlan_switch 
Mar 25 11:48:55 area42 NetworkManager: <info>  eth1: Device is fully-supported using driver 'ipw3945'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Mar 25 11:48:55 area42 NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Now managing wireless (802.11) device 'eth1'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Deactivating device eth1. 
Mar 25 11:48:55 area42 NetworkManager: <info>  eth0: Device is fully-supported using driver 'e1000'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  nm_device_init(): waiting for device's worker thread to start 
Mar 25 11:48:55 area42 NetworkManager: <info>  nm_device_init(): device's worker thread started, continuing. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Now managing wired Ethernet (802.3) device 'eth0'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Deactivating device eth0. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Updating allowed wireless network lists. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Will activate wired connection 'eth0' because it now has a link. 
Mar 25 11:48:55 area42 NetworkManager: <info>  SWITCH: no current connection, found better connection 'eth0'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Will activate connection 'eth0'. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Device eth0 activation scheduled... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) started... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) scheduled... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Old device 'eth0' activating, won't change. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) started... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) scheduled... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 1 of 5 (Device Prepare) complete. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) starting... 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) successful. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) scheduled. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 2 of 5 (Device Configure) complete. 
Mar 25 11:48:55 area42 NetworkManager: <info>  Activation (eth0) Stage 3 of 5 (IP Configure Start) started... 
Mar 25 11:48:55 area42 dhclient: There is already a pid file /var/run/dhclient.eth0.pid with pid 3970
Mar 25 11:48:55 area42 dhclient: killed old client process, removed PID file
Mar 25 11:48:55 area42 NetworkManager: <info>  Error getting killswitch power arguments:  - ^E 
Mar 25 11:48:55 area42 NetworkManager: <info>  Wireless now enabled by radio killswitch 
Mar 25 11:48:55 area42 dhclient: DHCPRELEASE on eth0 to 10.248.80.1 port 67
Mar 25 11:48:55 area42 dhclient: send_packet: Network is unreachable
Mar 25 11:48:55 area42 dhclient: send_packet: please consult README file regarding broadcast address.

Vous avez une idée?

Merci :slightly_smiling:

#2

Jamais réussi à le configurer correctement avec ma 3945.
Utilises wicd:
wicd.sourceforge.net/download.php

#3

wouha! réponse rapide merci.
J’avais déjà testé wicd sans succès mais il y a un moment déjà… Je (re)testerai si je trouve pas d’autre solution.

#4

Bonjour,

Je ne sais pas si c’est toujours le cas, mais chez moi si ma carte ethernet est en IP fixe elle n’est pas prise en compte par NetworkManager.

et que dis nm-applet (applet gnome de configuration de networkManager -fonctionnant aussi sous xfce au passage :slightly_smiling: ).

Et ensuite quand le module est chargé que donne les commandes :

  • ifconfig
  • iwconfig

Et quand le modules n’est pas chargé?

Chez moi le chargement du module ipw3945 créer une nouvelle interface eth2 (un eth0 renommé en eth2 je crois)

Le probleme vient peut être du fait que la migration (renommage) du nouveau périphérique ne se fait pas et du coup ton /dev/ethx ne pointe plus vers le point periphérique, ou même encore il y a des conflits pour l’accès au périphérique.

–
Jackall

#5

Je n’ai pas l’impression d’avoir une ip fixe, dans le configuration réseau de gnome j’ai de mode “itinérant” activé.

Sinon mon fichier interfaces est vide:

area42:/etc/network# cat interfaces 
# The loopback network interface
auto lo
iface lo inet loopback

Module dechargé

area42:/# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:58:7f:96:c7  
          inet adr:84.73.190.22  Bcast:255.255.255.255  Masque:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:97078 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3587 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:100 
          RX bytes:10110261 (9.6 MiB)  TX bytes:541730 (529.0 KiB)
          Adresse de base:0x3000 Mémoire:ee000000-ee020000 

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:2216 (2.1 KiB)  TX bytes:2216 (2.1 KiB)

area42:/# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

irda0     no wireless extensions.

Module chargé

area42:/# modprobe ipw3945
Starting ipw3945 regulatory daemon: ipw3945d.
area42:/# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:15:58:7f:96:c7  
          inet adr:84.73.190.22  Bcast:255.255.255.255  Masque:255.255.252.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:98004 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3589 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:100 
          RX bytes:10175402 (9.7 MiB)  TX bytes:541939 (529.2 KiB)
          Adresse de base:0x3000 Mémoire:ee000000-ee020000 

eth1      Link encap:Ethernet  HWaddr 00:19:d2:07:a1:67  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interruption:17 Adresse de base:0xc000 Mémoire:edf00000-edf00fff 

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:2216 (2.1 KiB)  TX bytes:2216 (2.1 KiB)

area42:/# iwconfig
lo        no wireless extensions.

eth0      no wireless extensions.

irda0     no wireless extensions.

eth1      unassociated  ESSID:off/any  
          Mode:Managed  Frequency=nan kHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:16 dBm   
          Retry limit:15   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

Module chargé + redémarage network-manager
A partir de ce moment, je perd la connexion par câble. Et je n’ai plus de connexion active dans network-manager (passe en mode “recherche”)

area42:/# etc/init.d/network-manager restart
Restarting network connection manager: NetworkManager.
area42:/# iwconfig 
lo        no wireless extensions.

eth0      no wireless extensions.

irda0     no wireless extensions.

eth1      unassociated  ESSID:off/any  
          Mode:Managed  Frequency=nan kHz  Access Point: Not-Associated   
          Bit Rate:0 kb/s   Tx-Power:16 dBm   
          Retry limit:15   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality:0  Signal level:0  Noise level:0
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:0   Missed beacon:0

area42:/# ifconfig 
eth0      Link encap:Ethernet  HWaddr 00:15:58:7f:96:c7  
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:99595 errors:0 dropped:0 overruns:0 frame:0
          TX packets:3599 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:100 
          RX bytes:10283266 (9.8 MiB)  TX bytes:542782 (530.0 KiB)
          Adresse de base:0x3000 Mémoire:ee000000-ee020000 

eth1      Link encap:Ethernet  HWaddr 00:19:d2:07:a1:67  
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:2 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interruption:17 Adresse de base:0xc000 Mémoire:edf00000-edf00fff 

lo        Link encap:Boucle locale  
          inet adr:127.0.0.1  Masque:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:0 
          RX bytes:2216 (2.1 KiB)  TX bytes:2216 (2.1 KiB)
#6

Hello,

J’ai testé wicd et ça marche plus ou moins. Bon mon access point à quelques problèmes (déjà commandé un nouveau :smiley: ) donc difficile de savoir d’où viennent le bugs. Je vais aller tester dans un café.

Mais sans protection aucune je peux me connecter quelque minutes… ensuite ça plante. C’est déjà pas mal :wink:.

J’ai perdu un peu de temps a cause d’une erreur bizarre qui l’empêchait de démarrer (un fichier de conf mal formé apparemment):

area42:/opt/wicd$ ./gui.py 
attempting to connect daemon...
success
starting gui.py...
refreshing...
using global dns: 0
disabling ip
disabling dns
dns checkbox toggled False
global dns checkbox toggled False
Traceback (most recent call last):
  File "./gui.py", line 1319, in ?
    app = appGui()
  File "./gui.py", line 910, in __init__
    self.refresh_networks(fresh=False)
  File "./gui.py", line 1190, in refresh_networks
    wiredNetwork = PrettyWiredNetworkEntry()
  File "./gui.py", line 306, in __init__
    PrettyNetworkEntry.__init__(self,WiredNetworkEntry())
  File "./gui.py", line 540, in __init__
    self.profileList = config.GetWiredProfileList()
  File "/var/lib/python-support/python2.4/dbus/proxies.py", line 139, in __call__
    args,
  File "/var/lib/python-support/python2.4/dbus/connection.py", line 606, in call_blocking
    reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Python.ConfigParser.MissingSectionHeaderError: Traceback (most recent call last):
  File "/var/lib/python-support/python2.4/dbus/service.py", line 696, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/opt/wicd/daemon.py", line 904, in GetWiredProfileList
    config.read(self.wired_conf)
  File "/usr/lib/python2.4/ConfigParser.py", line 267, in read
    self._read(fp, filename)
  File "/usr/lib/python2.4/ConfigParser.py", line 462, in _read
    raise MissingSectionHeaderError(fpname, lineno, line)
MissingSectionHeaderError: File contains no section headers.
file: data/wired-settings.conf, line: 1
'[]\n'

J’ai dût enlever à la mains le dossier /opt/wicd car purge ne finissait pas sont travail :/. Mais après ce nettoyage et une réinstallation -> miracle ça fonctionne.

Je vais tester un peu wicd qui me convient pour l’instant assez bien. Je trouve quand même dommage que les préférences soit toutes stocker dans le dossier /opt/wicd/data et pas dans /home/user/.wicd .

Merci pour votre aide :slightly_smiling:

#7

quote="gagarine"
Je vais tester un peu wicd qui me convient pour l’instant assez bien. Je trouve quand même dommage que les préférences soit toutes stocker dans le dossier /opt/wicd/data et pas dans /home/user/.wicd .
(…)[/quote]C’est normal, ce ne sont pas des préfèrences individuelles, mais celles du démon (qui fonctionne même quand X n’est pas lancé).
/opt/wicd/gui.py n’est là que pour causer avec le demon, mais ce n’est pas parcequ’il s’arrète que la liaison tombe.

#8

Ouais c’est vrais que ça se tiens…