Help with getting Network Manager Plasmoid working again (openSUSE 13.1)

English Network/Internet
#1

Hi,

I could do with some help getting my Network Manager Plasmoid (0.9.0.10 nm09 20131128) back working again.

For various reasons I’ve been playing around with using wicd rather than Network Manager. I’ve swapped them a few times. Now I’m back to using NM (0.9.8.8). I’ve swapped the plasma sys tray app a few times as well (between plasmoid-networkmanagement and nm-plasma).

Now, the plasmoid doesn’t load at KDE startup and when I add it manually to the system tray it says that “Network Manager is not running. Please start it.”

NM is running and I have network connection both cable and wireless.

I’ve read a few forums/bug report to do with pam.d, dbus1 and system.d and tried a few commands to reset things, but got nowhere so far. So I could do with some help to troubleshoot the problem.

I’ve also reinstalled all of the NetworkManager software.

I don’t know what info you need me to supply to fix this, so just let me know.

Thanks in advance.

#2

I just posted the default packages for NM in another thread
http://forums.opensuse.org/showthread.php/494279-problem-with-NetworkManager?p=2616282#post2616282

Same recommendation as there but perhaps do a force re-installation which should hopefully re-apply default configurations

zypper in -f <package names separated by a space>

TSU

#3

Thanks tsu2.

I didn’t have all those packages installed.

However, in reinstalling them, I noticed that a stray KDE411 repository had provided some of the packages rather than the openSUSE main repo (I must have added it for other reasons). So having corrected that and reinstalled all the packages, we’re now back up and running again.

#4

On 01/15/2014 09:36 AM, cmt29 pecked at the keyboard and wrote:
> Hi,
>
> I could do with some help getting my Network Manager Plasmoid (0.9.0.10
> nm09 20131128) back working again.
>
> For various reasons I’ve been playing around with using wicd rather than
> Network Manager. I’ve swapped them a few times. Now I’m back to using NM
> (0.9.8.8). I’ve swapped the plasma sys tray app a few times as well
> (between plasmoid-networkmanagement and nm-plasma).
>
> Now, the plasmoid doesn’t load at KDE startup and when I add it manually
> to the system tray it says that “Network Manager is not running. Please
> start it.”
>
> NM is running and I have network connection both cable and wireless.
>
> I’ve read a few forums/bug report to do with pam.d, dbus1 and system.d
> and tried a few commands to reset things, but got nowhere so far. So I
> could do with some help to troubleshoot the problem.
>
> I’ve also reinstalled all of the NetworkManager software.
>
> I don’t know what info you need me to supply to fix this, so just let me
> know.
>
> Thanks in advance.
>
>
I too am having the same problem and will monitor this thread as well
and if I find a solution I will post it.

Ken

#5

Note the OP in this thread. There might be a bug in the packages provided in the KDE4 repo. Try installing all the packages in my list from the OSS repo.

TSU

#6

On 01/15/2014 09:46 PM, tsu2 wrote:
>
> kensch;2616419 Wrote:
>> On 01/15/2014 09:36 AM, cmt29 pecked at the keyboard and wrote:
>>> Hi,
>>>
>>> I could do with some help getting my Network Manager Plasmoid
>> (0.9.0.10
>>> nm09 20131128) back working again.
>>>
>>> For various reasons I’ve been playing around with using wicd rather
>> than
>>> Network Manager. I’ve swapped them a few times. Now I’m back to using
>> NM
>>> (0.9.8.8). I’ve swapped the plasma sys tray app a few times as well
>>> (between plasmoid-networkmanagement and nm-plasma).
>>>
>>> Now, the plasmoid doesn’t load at KDE startup and when I add it
>> manually
>>> to the system tray it says that “Network Manager is not running.
>> Please
>>> start it.”
>>>
>>> NM is running and I have network connection both cable and wireless.
>>>
>>> I’ve read a few forums/bug report to do with pam.d, dbus1 and system.d
>>> and tried a few commands to reset things, but got nowhere so far. So I
>>> could do with some help to troubleshoot the problem.
>>>
>>> I’ve also reinstalled all of the NetworkManager software.
>>>
>>> I don’t know what info you need me to supply to fix this, so just let
>> me
>>> know.
>>>
>>> Thanks in advance.
>>>
>>>
>> I too am having the same problem and will monitor this thread as well
>> and if I find a solution I will post it.
>>
>> Ken
>
> Note the OP in this thread. There might be a bug in the packages
> provided in the KDE4 repo. Try installing all the packages in my list
> from the OSS repo.

Just to let you know, I installed wicd on 13.1 to help a user in the
linux-wireless ML. Remember that “no good deed goes unpunished”! When I later
attempted to uninstall it and restore NetworkManager, I was unable to get NM to
work. I ended up reinstalling 13.1. YMMV, but that was the fastest solution for
me, and I like to think I understand NM.

That is my second absolute failure with wicd. I will never install it again
until I have to. According to the factory ML, wicked (aka wicd) will replace
ifup in 13.2.

#7

On 01/16/2014 11:54 AM, Larry Finger pecked at the keyboard and wrote:
> On 01/15/2014 09:46 PM, tsu2 wrote:
>>
>> kensch;2616419 Wrote:
>>> On 01/15/2014 09:36 AM, cmt29 pecked at the keyboard and wrote:
>>>> Hi,
>>>>
>>>> I could do with some help getting my Network Manager Plasmoid
>>> (0.9.0.10
>>>> nm09 20131128) back working again.
>>>>
>>>> For various reasons I’ve been playing around with using wicd rather
>>> than
>>>> Network Manager. I’ve swapped them a few times. Now I’m back to using
>>> NM
>>>> (0.9.8.8). I’ve swapped the plasma sys tray app a few times as well
>>>> (between plasmoid-networkmanagement and nm-plasma).
>>>>
>>>> Now, the plasmoid doesn’t load at KDE startup and when I add it
>>> manually
>>>> to the system tray it says that “Network Manager is not running.
>>> Please
>>>> start it.”
>>>>
>>>> NM is running and I have network connection both cable and wireless.
>>>>
>>>> I’ve read a few forums/bug report to do with pam.d, dbus1 and system.d
>>>> and tried a few commands to reset things, but got nowhere so far. So I
>>>> could do with some help to troubleshoot the problem.
>>>>
>>>> I’ve also reinstalled all of the NetworkManager software.
>>>>
>>>> I don’t know what info you need me to supply to fix this, so just let
>>> me
>>>> know.
>>>>
>>>> Thanks in advance.
>>>>
>>>>
>>> I too am having the same problem and will monitor this thread as well
>>> and if I find a solution I will post it.
>>>
>>> Ken
>>
>> Note the OP in this thread. There might be a bug in the packages
>> provided in the KDE4 repo. Try installing all the packages in my list
>> from the OSS repo.
>
> Just to let you know, I installed wicd on 13.1 to help a user in the
> linux-wireless ML. Remember that “no good deed goes unpunished”! When
> I later attempted to uninstall it and restore NetworkManager, I was
> unable to get NM to work. I ended up reinstalling 13.1. YMMV, but that
> was the fastest solution for me, and I like to think I understand NM.
>
> That is my second absolute failure with wicd. I will never install it
> again until I have to. According to the factory ML, wicked (aka wicd)
> will replace ifup in 13.2.
>
>
>

Thanks for the info. I find having to “re-install” the OS to be a rather
poor way to have to fix an errant package problem. Next step is to look
at all of the config files.

Ken

#8

On 01/16/2014 02:06 PM, Ken Schneider wrote:
>
> Thanks for the info. I find having to “re-install” the OS to be a rather poor
> way to have to fix an errant package problem. Next step is to look at all of the
> config files.

I did not like it either, but after about 4 hours of little headway, and little
belief that I would find the real problem, I decided that my best approach was
to reinstall so that I could actually use the computer.