Bug 625393 - Networkmanager is disabled
Summary: Networkmanager is disabled
Status: RESOLVED DUPLICATE of bug 552862
Alias: None
Product: openSUSE 11.3
Classification: openSUSE
Component: Network (show other bugs)
Version: Final
Hardware: x86-64 openSUSE 11.3
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-25 15:26 UTC by Peter Stolz
Modified: 2010-07-26 11:09 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Stolz 2010-07-25 15:26:32 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.6) Gecko/20100626 SUSE/3.6.6-1.2 Firefox/3.6.6

I updated from 11.2 to 11.3. I use KDE 4 (11.2 and 11.3). Now the networkmanager is disabled. I can not activate it and I have no network connection.
So I have to use the traditional method with ifup. But I use a laptop and networkmanager would be better and it worked with 11.2.


Reproducible: Always

Steps to Reproduce:
1. It definitely not work
2.
3.
Comment 1 Peter Stolz 2010-07-25 19:31:42 UTC
I found in the internet the following command:
solid-network set networking enabled.

After this command the networkmanager works.
Comment 2 Tim Mohlmann 2010-07-25 20:49:43 UTC
Did you happen to have a failed suspent? Forcing you to reboot or do a fresh boot on power on?
Comment 3 Peter Stolz 2010-07-26 10:54:01 UTC
I can not remember if there was a failed suspent. It worked after the update to 11.3 and I recognized the problem the next day. So I can not answer your question.
Comment 4 Tim Mohlmann 2010-07-26 11:09:02 UTC
Well, since the command

solid-network set networking enabled

wakes you knetwork manager up again, I'm quite sure this bug is similar to #552862, so I will mark it as a duplicate. The problem also excist for the GNOME network manager. It misses the command to "wake up" the network again after suspend. Solutions seem to be underway.

*** This bug has been marked as a duplicate of bug 552862 ***