Knetworkmanager ... disabled without any reason!!

English Network/Internet
#1

Hi,

I m running the 11.3.

Today I put the machine to suspend to RAM, then the OS was frozen (did not completed the suspend to RAM). After this, my only choice was to power off the machine via the power switch.

When I booted again, the Network management is disabled, there is no way to enable it. Even via the yast2 I tried to switch from ifup then back to Network manager, but in vain.

When i am trying to run the knetworkmanager from the terminal
i got this:

Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)

running it as root i got this:

knetworkmanager(5490): KUniqueApplication: Cannot find the D-Bus session server: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”

knetworkmanager(5489): KUniqueApplication: Pipe closed unexpectedly.

So, that means that the network manager is corrupted ? Any tips

thx

Chris

knetworkmanager(5490): KUniqueApplication: Cannot find the D-Bus session server: “Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.”

knetworkmanager(5489): KUniqueApplication: Pipe closed unexpectedly.

Connecting to deprecated signal

#2

I even uninstalled then installed again the knetworkmanager , without any result.

#3

I think that something is wrong with opensuse 11.3 , as today i have no sound and cannot see any USB device! I mean WTF the system auto-corrupts itself??
Nevermind, I will try another distro.

#4

NetworkManager quit working on one of my laptops after suspend to ram.

Spent a couple days trying to get it working again and finally gave up.

Read MANY threads with this NetworkManager issue but found no solutiion.

Using ifup and WICD now.

:frowning:

#5

You are right… big problem, I tried to use the WICD , but I had no success , coiuld not install it. so I gave up and installed
the LXDE desktop of opensuse 11.3 (KDE seems to be a bit slow on my laptop) … so far so good…

#6

Solution: “Networking disabled” / “Netwerkverwaltung deaktiviert”

#7

This is definitely a bug…

Nice tip mate!

cheers

#8

Great find Mario :slight_smile:

Now to figure out how to get WICD from prompting for password when KDE starts :slight_smile:

#9

Mine just did this. I am sort of angry, so far this has been the cleanest, smoothest transition to Linux on my computer, ever, and now this… Kind of disappointing. Hopefully with 11.4 it’ll be fixed.

#10

Well actually it’s a feature (not a bug) of NetworkManager to remember the state of the network between reboots. Usually the bug is in the suspend to ram and resume scripts as they sometimes tell NetworkManager to turn the network off and don’t tell it to turn it on again when the resume script fires itself up.

Best regards,
Greg

#11

Write the installation process here.

#12

Guys,
I’ve seen this, for the most part it’s transitory and the auto start usually fixes itself after a few hard boots (full power down and up)

In the meantime…
I’ve determined that Network Manager is always running but for some reason the icon isn’t visible in the tray.
To re-enable in the tray simply restart using kdestart, not the command line (you’ll find a relatively recent thread in these forums where I was corrected trying to start a KDE app from root in a CLI… You’ll get the dbus error because you’re not launching to a running xserver).

KDE start > Run command > networkmanager
or
KDE start > Run command > knetworkmanager

Your NetworkManager tray icon will re-appear and you’ll note your network connection will already be active (which wouldn’t be the case if it wasn’t already running).

I’ve verified the problem is not that the property for displaying in the tray isn’t checked, the problem is elsewhere.

I’ve found that the best way to avoid this problem is if your laptop has a physical way of disabling the wireless NIC(I have a slider switch on my HP dv9500). Do that when you’re not connecting to wireless and you’ll never see this problem.

Note that even when Network Manager is running, you can certainly ifup/ifdown an interface, but don’t attempt to ifup/ifdown without specifying the interface…

HTH,
Tony

#13

I was actually thinking of writing a shell script that pretty much does all the things necessary in the case that this happens on a more constant basis. It’s gotten to the point where I keep handwritten instructions (which, by now I’ve memorized) with me at all times in case this happens, which it has at least 4 times since my last post. I’d disable STD completely, but I don’t want to. And only 4 days until 11.4 Stable, so here’s to hoping I won’t be doing this for long.