knetworkmanager fails to find network devices

I have what is probably the same issue on an Edgy install on a x86 system. I have networkmanager version 0.6.3-2ubuntu6 and knetworkmanager version 0.1-0ubuntu1 installed. This is the behavior I am seeing:

Looking at the knetworkmanager applet it is showing as disconnected. Left clicking on the applet brings up the menu where I see the message "No network device found." NetworkManager is running though and I am connected to my wireless network and have an IP address.

I have removed the knetworkmanager applet and added it again and this did not change it's behavior. I have rebooted and that did not change the behavior. I have logged in as a different user and that did not change the behavior.

Are you also connected to your network?

Come to find out I had used the network-admin application that is part of gnome-system-tools to configure my network. This prevented knetworkmanager from seeing the device.

After using knetworkconf, which is part of kde control panel, I had the same issue: my wireless device is not detected any more

After some investigations I found that any program which alters the /etc/network/interfaces file deleting the "auto" command from a wireless interface messes up knetworkmanager. To workaround the problem just put back the "auto" command before the wireless interface name.

Example:

auto eth0
iface eth0 inet dhcp

wifi0
iface wifi0 inet dhcp

Change it in

auto eth0
iface eth0 inet dhcp

auto wifi0
iface wifi0 inet dhcp

Brian, can you confirm that you have same problem in /etc/network/interfaces as sk0rp10?
In that case, this is bug in knetworkconf and should be addressed there.

sk0rp10: can you tell us exact steps that you need to to do in knetworkconf to reproduce missing "auto" in /etc/network/interfaces? Are you running edgy or feisty?

I am running Feisty development branch, updated with latest packages. I just changed the wireless interface configuration from knetworkconf and found that the line "auto wifi0" was missing.

Morever I found that on Feisty knetworkconf autodetects the system as " Slackware 9.1" , and if I force version popup by altering knetworkconfrc as this:

[General]
askAgainPlatform=true
detectedPlatform=Ubuntu_7.04

I can then select Feisty as platform, but then no network interfaces are found, so I think there should be some mess in knetworkconf which thinks that feisty is slackware 9.1 and does wrong configurations

Correction :

setting up this as knetworkrc makes interface detection work ok:

[General]
askAgainPlatform=false
detectedPlatform=ubuntu-7.04

and changing settings does not alter anymore the /etc/network/interfaces file

I am doing some more tests however

The "auto" entry in /etc/network/interfaces is deleted when disabling the "enable at startup" voice in Knetworkconf .

Verified on Edgy and Feisty

OK, but this is correct - this means that you will enable this interface manually.
Does knetworkmanager work if you do:

  sudo ifup <interface>

I'm running Feisty with recent updates 6/2/2007 and the KNetworkManager says "disconnected" and by right clicking the tray icon I get a menu which says "no network device found". I checked the /etc/network/interfaces, there were "auto"s correctly placed. This has been the behavior since the manager appeared the tray on some updates (Herd #2 installation originally).

I have a wired Ethernet with no DHCP. The connection is working fine. The adapter is Intel DG965WH motherboard's integrated adapter connected to a 100Mbit LAN.

As with updates downloaded 14/3/2007 KNetworkManager works as expected! Says wired ethernet eth0 connected!

Yesterday's update (2007-04-11) borked the whole thing again. KNetworkManager says that it couldn't find any network devices (even when they are present and working - I am just connected through wireless). Please see screenshot (in spanish, sorry).

I don't know whether it is related or not, but when I start KNetworkManager from the command line, I get the following message:
** Message: another gnome-keyring-daemon is running

If I check processes, I get this:
luis@ordenata:~$ ps aux|grep -i gnome-keyring
luis 8753 0.0 0.0 2752 988 ? S 09:00 0:00 gnome-keyring-daemon
luis 24549 0.0 0.0 2756 1016 pts/1 S 13:12 0:00 gnome-keyring-daemon

If I kill one of the processes, it doesn't complain anymore, but it still won't show any network devices. It will create a new gnome-keyring process so we have two processes again. If I kill both processes and start KNetworkManager, it won't complain either, create a new gnome-keyring process and again no network devices.

Can you try with latest distro (feisty final or gutsy) and verify?
thanks

Seems to work fine in Feisty :)

My error was this:

** Message: another gnome-keyring-daemon is running
Error requesting name, org.freedesktop.DBus.Error.AccessDenied: Connection ":1.9" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file

Now i got a solution...it is not related to the keyring-manager. This old page gave me the hint http://ubuntuforums.org/showthread.php?t=125150
This page shows setting policies for single users...

I started playing with the rights in /etc/dbus-1/system.d/NetworkManager.conf
According to an other page I changed the settings for the "default" policy from "deny" to "allow".
After that the Error had to be corrected with the line
                <allow own="org.freedesktop.NetworkManagerInfo"/>
below.

Cable and wireless-net working perfectly!

So one more Question: should I "allow" by "default" (security??) or for single users?

PS: I am running Debian testing (pre - lenny)

[Expired for knetworkmanager (Ubuntu) because there has been no activity for 60 days.]

Please see my recent comment in bug #50770.
Should I really have to add my username in
 /etc/dbus-1/system.d/knetworkmanager.conf
 /etc/dbus-1/system.d/NetworkManager.conf
to be able to run knetworkmanager?

To answer my own question (again!): no. The directory permissions on /var/run/console were incorrect. I corrected them (755) and that resolved the isuse.

Working from sk0rp10s tips above I have found the following:

First of all: Problem description, as it is a little different. At some point I did something stupid, probably turning off the transmitter (easily done on a Dell D600 by hitting Fn-F2 instead of Alt-F2 :-( ). This got knetworkmanager confused and me in a state of panic. I reconfigured the wireless settings through systemsettings, and poof! the wireless network device was gone from knetworkmanager.
The system as such worked, but I was now unable to switch networks easily when going from one location to another, and knetworkmanager gave the familiar "no active device found" message.

My solution:
Not only do you need to set wlan0 back to auto, but you also need to give it _empty_ authentication details, like so:

auto wifi0
iface wifi0 inet dhcp
wireless-essid
wireless-key

This makes the available network list magically reappear and I am yet again able to switch WLANs via knetworkmanager. Peace of mind finally restored; this has been bugging me for a while :-)

This issue is present in Hardy, the output from knetworkmanager is such:

Error requesting name, org.freedesktop.DBus.Error.AccessDenied: Connection ":1.2 2" is not allowed to own the service "org.freedesktop.NetworkManagerInfo" due to security policies in the configuration file

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.