On Sun, 2010-01-31 at 21:27 +0100, Rolf Schumacher wrote: > upgraded to debian sid 2.6.32-7 > kde 4.3.4 > network-manager 0.7.999 > > What I did: > I installed the package network-manager-kde, that is based on > network-manager. > I installed it on 2.6.32-6 and was happy: > I could choose from wlan ssid's surrounding me. > I could enter my 3G details and connected to two different umts networks > via two different chips: Huawei E160 and Ericsson F3507g. > > Than, I upgraded to the newer kernel (and maybe some other newer libs).
Did you upgrade NetworkManager at the same time? Did network-manager-kde (or whatever the plasma network control applet is) get updated at the same time? Note that there have been a few UI incarnations for KDE; last I knew network-manager-kde was the KDE 3 applet, while there was some new stuff integrating with the KDE hardware abstraction layer and a shiny new applet for KDE 4... Dan > What I got: > > Now, I'm no longer able to connect to a ssid. If I click on an ssid the > KNetworkManager dialog closes without any message, but no connetion is > done (in the past there was a rotating gear till connection). > > Also the ttyasp interface is not shown any longer in favor of usb0. And > it constantly displays "no carrier" below it where my umts supplier used > to get displayed. > > Question: > > What can I do to identify the mistake behind this and bring > network-manager up again as it was? > > > Rolf > _______________________________________________ > NetworkManager-list mailing list > [email protected] > http://mail.gnome.org/mailman/listinfo/networkmanager-list _______________________________________________ NetworkManager-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/networkmanager-list
