network-manager-kde say 'no active devices'

[Andrew Belitsky]

Binary package hint: network-manager-kde

kde-network manager writing 'no active device', but network is configured and works fine.
andrew@andrew-desktop:~$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:F1:0B:12:C5
          inet addr:10.1.128.109 Bcast:10.1.143.255 Mask:255.255.240.0
          inet6 addr: fe80::230:f1ff:fe0b:12c5/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
          RX packets:26041 errors:0 dropped:0 overruns:0 frame:0
          TX packets:9134 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1577 txqueuelen:1000
          RX bytes:11098477 (10.5 MB) TX bytes:876639 (856.0 KB)
          Interrupt:10 Base address:0x6000

lo Link encap:Local Loopback
          inet addr:127.0.0.1 Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING MTU:16436 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 txqueuelen:0
          RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

[Marco Cimmino (cimmo)]

can you give more details? Can you say if this bug is the same that you are describing? If yes mark this duplicate of that one, thanx.
http://launchpad.net/bugs/125767

[Andrew Belitsky (belitsky-a)]

No, it's not the same. I have configured wired connection that not represent in status window (screenshot - http://img86.imageshack.us/my.php?image=snapshot2ls6.jpg). Where can i get additional information?

[Sarah Kowalik (hobbsee-deactivatedaccount)]

no, this isn't the same - but it is a dupe, of something in network-manager. Network manager will show that it's not connected if it itself is not running the connection. The same thing happens with any type of manual configuration (like iwconfig and dhclient via command line)

[opm8 (glorx-launchpad-forum)]

I'm running Debian but this fix helped me with this exact problem: http://technowizah.com/2007/02/debian-how-to-managing-networks-with.html

1) Comment out all but the following from your /etc/network/interfaces:
auto lo
iface lo inet loopback

2) Add the user to the netdev group:
sudo adduser your_username netdev

[Andrew Belitsky (belitsky-a)]

Its not work, adduser says that "user andrew already in netdev".

[Elias Grinias (grinias)]

The same problem here. And since I use network-manager to connect via my vpn connection,
the problem is huge. Yes I know that I can manually connect via pptp, but the problem appeared
before 2 days, and I do not have time to manually configure my vpn connection.

[Elias Grinias (grinias)]

Problem solved using the 1st instruction of opm8. Thank you...

[Luka Renko (lure)]

Can you still reproduce this with up-to-date Hardy?

[Milan Masek (milan-m-masek)]

Hi, with up to date Hardy still the same problem. It's necessary to comment /etc/network/interfaces. Otherwise goes well.
M.

[melondrift (shauber)]

This just happened to us with Kubuntu Hardy. An update last weekend knocked out KNetworkManager. Was working with system files on mine when it happened and thought I'd killed my box and re-installed from the cd. When it showed up on my dads box, knew there had to be something hanky.

Ifconfig wouldn't auto initiate. Ifconfig could be forced to turn on networking, but the network manager refused to go online. And of course, with that happening, nothing went online.

I did this which was posted by "opm8":

1) Comment out all but the following from your /etc/network/interfaces:
auto lo
iface lo inet loopback

2) Add the user to the netdev group:
sudo adduser your_username netdev

; and now it's working again.

I didn't catch which updates were done, but remember them having to do with networking.

Many Many thanks to "opm8" 8-)

[Jonathan Thomas (echidnaman)]

Thank you for taking the time to report this bug and helping to make Kubuntu better. The KDE3 version of KNetworkManager has been discontinued by its original authors. This unfortunately means that there will be no more bugfix releases, and updates in general will be limited to those fixing security flaws.

While we cannot fix your bug, the good news is that the applet has been totally rewritten for KDE4 in the upcoming Kubuntu 9.10 release. There is a good chance that this bug is no longer an issue with the new applet. If you find any similar or new issues with the applet included in Kubuntu 9.10, we would politely ask you to file them as new bugs against the "plasma-widget-networkmanagement" package.

Thanks in advance for your cooperation and understanding.