So, as the title says, I seem to have problems with my network, or with NetworkManager, or with both. There is a NetworkManager process running, and systemctl output tells me that network.service is “active (exited)” and “status=0/SUCCESS”, and that NetworkManager.service is “active (running)” and “status=0/SUCCESS”, and that it spawned a ‘/usr/sbin/NetworkManager --no-daemon’ process. After killing that process, the plasmoid no longer says that “NetworkManager is not running. Please start it.”, but it still does not work. It lets me configure only VPN connections, and I can’t access the internet using my wired connection (which is the only one I have, hence I cannot access the internet at all) with that machine. Any ideas about how to solve this? Thanks in advance.
Basic information is missing. What version of openSUSE?? What desktop (KDE, Gnome, …)?
BTW, why are you using NetworkManager at all when you are apparently using a system that is allways on the same place and uses a cabled NIC?
OpenSuse 12.2, KDE 4.10. And I use NetworkManager because I want to, but I don’t see how that is relevant. The point is helping me to make it work, not telling me to use something else. 
Network Manager should support wired connections just fine.
Is this a brand new install?
Have you done a system update anytime recently?
# zypper up
Have you tried doing a force update for just Network Manager (that forces re-installation, perhaps fixing anomalies and/or replacing missing or faulty configurations).
And, of course you have to have perfectly working hardware. If your NIC is unplugged or otherwise not connecting, then NM will behave as you’ve described.
HTH,
TSU
It’s not brand new, but yes, I did a system update the day before it broke (zypper dup, though, but I’m not sure it installed any updates for NM, and everything was fine after the update until I booted again today). I’m not sure if reinstalling NM would work, since I can’t access the internet from that machine, so unless I have the rpm cached somewhere… But I’ll try, just in case.
The hardware is fine, however. The problem lies with network.service and NetworkManager.service, as explained above. For some reason those services fail to start properly at boot, according to boot.log, but systemctl reports they’re fine, the NetworkManager process is properly spawned, yet none of it seems to work and it doesn’t get detected by the plasmoid.
I don’t remember if “zypper dup” will pull down the latest updates or not. It’s primarily used as a recovery or full system upgrade, not simply an update.
Recommend run “zypper up” and see if anything happens.
TSU
On 02/23/2013 12:06 AM, potatomash wrote:
> I did a system update the day before it
> broke (zypper dup, though, but I’m not sure it installed any updates for
> NM,
first: why did you use ‘zypper dup’? that is, are you running
Tumbleweed? if running Tumbleweed this thread should be in the
Tumbleweed forum–please ask a moderator to move the thread
and everytime posting please mention that you are running Tumbleweed.
however, if not using Tumbleweed one should use only ‘zypper patch’
or ‘zypper up’ to install security updates and/or bug fixes.
‘zypper dup’ used wrongly is a very dangerous (system destructive)
command which should only be used when all the conditions are set for
its proper use.
> and everything was fine after the update until I booted again
> today).
updates sometimes include kernel and other changes which cannot be
switched to in a running system, and their use is therefore delayed
until the next boot…
you can learn what packages were changed in your last update by
executing this command in a user terminal:
sudo tail -n 100 /var/log/zypp/history | less
individual package update lines begin with a date/time stamp (like:
2013-02-13 17:16:32) which can be used to determine which packages
were in your last ‘dup’
while TSU’s recommended ‘zypper up’ might be helpful, it is possible
that the only way to return to a fully fuctional system is to enable
only those repos know to provide clash free software and then do
another ‘dup’ to remove the conflicts…
if you wish to try that, so advise and someone might help you with
the details…
–
dd
openSUSE®, the “German Engineered Automobile” of operating systems!
http://tinyurl.com/DD-Caveat
I’m not using Tumbleweed (if the “stable” release breaks like this, I shudder to think what Tumbleweed might be like), and I don’t know how helpful a “zypper up” or “zypper dup” will be in a machine that has no access to the internet (therefore being unable to pull any updates; whatever might be in any package cache would be what is already installed, and therefore it won’t be pulled in an update). I’ll see what packages were affected by the update later when I have access to the system. Thanks for your advice.