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
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 tosecurity
policies
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
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?
** Changed in: knetworkmanager (Ubuntu)
Status: Invalid = Confirmed
--
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.
--
knetworkmanager fails to find network devices
https://bugs.launchpad.net/bugs/77557
You received this bug notification because you are a
[Expired for knetworkmanager (Ubuntu) because there has been no activity
for 60 days.]
--
knetworkmanager fails to find network devices
https://bugs.launchpad.net/bugs/77557
You received this bug notification because you are a member of Kubuntu
Team, which is a bug contact for knetworkmanager in
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
Seems to work fine in Feisty :)
--
knetworkmanager fails to find network devices
https://bugs.launchpad.net/bugs/77557
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Can you try with latest distro (feisty final or gutsy) and verify?
thanks
** Changed in: knetworkmanager (Ubuntu)
Status: New = Incomplete
--
knetworkmanager fails to find network devices
https://bugs.launchpad.net/bugs/77557
You received this bug notification because you are a member of
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
As with updates downloaded 14/3/2007 KNetworkManager works as expected!
Says wired ethernet eth0 connected!
--
knetworkmanager fails to find network devices
https://launchpad.net/bugs/77557
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
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 autos correctly placed. This has
been the behavior since the manager
The auto entry in /etc/network/interfaces is deleted when disabling
the enable at startup voice in Knetworkconf .
Verified on Edgy and Feisty
--
knetworkmanager fails to find network devices
https://launchpad.net/bugs/77557
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
OK, but this is correct - this means that you will enable this interface
manually.
Does knetworkmanager work if you do:
sudo ifup interface
--
knetworkmanager fails to find network devices
https://launchpad.net/bugs/77557
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
After using knetworkconf, which is part of kde control panel, I had the
same issue: my wireless device is not detected any more
--
knetworkmanager fails to find network devices
https://launchpad.net/bugs/77557
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
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
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
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
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
--
knetworkmanager fails to find
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
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.
--
knetworkmanager fails to find network devices
https://launchpad.net/bugs/77557
--
kubuntu-bugs mailing list
21 matches
Mail list logo
