NetworkManager/knetworkmanager stopped working

Hi,

I’ve run into a situation where knetworkmanager tells me networking is disabled. If I switch to the ifup method in Yast then I can get online but when I switch back to user controlled knetworkmanager tells me that networking is disabled.

I’ve actually had this happen twice. The first time I somehow managed to get it working again (I thought it was by right clicking on the icon in the system tray). This time I don’t see the same option.

Has anybody got any suggestions on how to get knetworkmanager working again.

Thanks

openSUSE 11.3 (i586) - kde 4.4.4

Is the knetworkmanager applet in the tray?
If not, is it actually running? (type: knetworkmanager) in a terminal to start it.
Did you have to do anything special to get wireless working when you installed - what wireless device do you have?
Have you performed updates recently?
Have you tested a new user account?

Should have done more googling first. But just in case someone else is has the same issue.

The solution is (based on this archlinux thread). As root:


rcnetwork stop
rm /var/lib/NetworkManager/NetworkManager.state
rcnetwork start

To answer caf’s questions for the sake of completeness

Yes.
Nothing special, Atheros AR928X - ath9k.
No it actually stopped working when I unplugged my laptop, shut the lid (i.e. suspended) and opened it again after a while.
Yes, same thing with a new user account.

Do you think it’s a suspend issue then that caused it?

Suspending is the only common thing between the 2 times it happened. The first time (a week ago) I was just web browsing and put my laptop aside for a while. The second time I was actually at work so I had more programs running; external monitor, keyboard, mouse; I had to move from my office to the lab so I shut a few (not all) programs and disconnected everything.

I just quickly tried shutting the lid and suspending to disk. Both times everything came back normally. I’ll keep an eye out for the same issue and see if I can find a reliable reproduction method.

OK
Thanks for all the detail - It may help others.

I had exactly the same issue, and this post has helped me to resolve it. Thanks a lot, cpackham (and caf4926).
I don’t know the cause, but I’m sure that it was not a suspend issue in my case.

Yeah I’m beginning to think the issue I’ve seen isn’t a suspend thing. It doesn’t look the same as this thread: knetworkmanager 11.3? which states that after creating a new user, that new user can use knetworkmanager.

Still haven’t reproduced it yet but I wonder if its actually related to another problem I was seeing when I was switching back and forth between ifup and networkmanager. I’ve got a few network services running (tftpd, sshd) and everytime I changed something in Yast I’d get an error message saying “No network running” after the “Starting network services…” line. I wonder if that meant that even though Yast had switched itself from using ifup it never got to the part that updates NetworkManager.state to say that its enabled.

Bug fixed => https://bugzilla.novell.com/show_bug.cgi?id=585433

I did create a new user but none could use knetworkmanager until yesterday, when I did what you suggested in your post. So I thing that this case is different from that one, as you say.
Anyway, as framp says, the bug should be fixed already.

Still haven’t reproduced it yet but I wonder if its actually related to another problem I was seeing when I was switching back and forth between ifup and networkmanager. I’ve got a few network services running (tftpd, sshd) and everytime I changed something in Yast I’d get an error message saying “No network running” after the “Starting network services…” line. I wonder if that meant that even though Yast had switched itself from using ifup it never got to the part that updates NetworkManager.state to say that its enabled.

I don’t have this problem. Just that Yast takes a lot of time in resetting the network after switching between ifup and networkmanager. But it’s not a great issue.
So, I’m quite happy with this solution. Thanks again.

This fixed my problem too - thanks. Will fix my “suspend” settings to avoid a recurrence. But…WHY???