On Fri, Aug 5, 2022 at 10:13 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:

On 8/5/22 02:24, Roger Oberholtzer wrote:

...

I have been using NetworkManager in KDE for a long time. It has been working great. Until now.

I was helping a friend so I disabled NetworkManager in yast. All went fine. I could do what I needed to do in the network to sort out his thing.

I then selected NetworkManager in yast again. I get nothing. I cannot even get the plasma widget back. Nada.

I know about KDE's rather fragile state when it comes to plasmoid widgets. I just cannot see what is confusing things. I don't even see NetworkManager as a widget I can add. Shouldn't I be able to do so if it is no longer showing up automatically?

I've googled this and see lots from a while back when this was all less stable- I don't see much recently.

Wicked works. But I don't want to use yast to control wireless. I'm rather mobile with this computer.

Pointers and suggestions welcome. It's a Tumbleweed system that is rather up-to-date.

Roger,

Have you verified networkmanager service was started? (I'm sure you have, but just a thought), e.g.

$ systemctl status NetworkManager

If service is disabled, start it. If the preset is disabled, enable it to start on boot, e.g.

# systemctl start NetworkManager # systemctl enable NetworkManager

My only guess is turning it off in Yast may have disabled the systemd service and turning it back on may not have re-enabled/started it. It's not like Yast is bug-proof :)

It was a classic KDE configuration gets confused thing. I replaced .kde4 and .config in $HOME, and all is okay again. I'm amazed that this is still so volatile. So much of KDE works so very well. But the configuration storage leaves lots to be desired. Happily my work VPN is working again. It's tied to me wireless interface only. Our IT folk are, lets say, inflexible... -- Roger Oberholtzer