Sorry if I break a forum’s rule.
This is a problem that has been touched in another thread.

I use Tumbleweed+KDE.
I did not use NetworkManager.
If I want to remove NetworkManager it is necessary to remove KDE Plasma.
With wicked everything is fine.
In Gnome I could remove NetworkManager without any dependencies.

Thank you.

Just leave NetworkManager there, but don’t use it.


This is what I do.
But I would like to remove it.
For me Networkmanager is a package that I associate with Gnome.
And in Gnome I can remove it but in KDE I cannot.

All desktops use it, to some extent. Well, okay, the Icewm desktop doesn’t use it in an essential way. Most other desktops have a network applet for configuring connections.

And in Gnome I can remove it but in KDE I cannot.

I’ve never tried removing it, so I’m only guessing here.

Both Gnome and KDE (and several other desktops) make use of a NetworkManager applet. But I guess it depends on packaging. The desktop can make the network applet a dependency, in which case it must be there. Or I guess it can make the network applet a recommend, so that it will be brought in as a recommended applet. The network applet itself presumably makes NetworkManager a dependency.

NetworkManager-applet is not installed.
I think I will begin to search the dependecy that does not allow to uninstall it.

PS.Networkmanager-openconnect depends on plasma-nm5-openconnect,Networkmanager-openvpn depend on plasma-nm5-openvpn, Networkmanager-pptp depends on plasma-nm5-pptp and libKF5networkManagerQt6 depends on …all.

Networkmanager is not a specific Gnome thing.

It is in fact a server/client application (both in the same system).
The server is a daemon running with root as owner (only root can configure networking in the kernel).

The clients are run by the end-user in his/her desktop. Thus they can be different for different desktops. I assume that the NM clients in KDE and Gnome are different, but I guess that both interface through an applet with the end-user.

As you do not tell us what you removed “in Gnome” I can not comment on that, but I guess you
removed the Gnome NM client.

Removing the package NetworkManager indeed wants to remove several plasma packages. I assume at least some of them belong to the KDE NM client. Thus it could be that it is only removing plasma packages you do not need.

But as I found out that removing the Samba server (which is system software that has nothing to do with a desktop IMHO) brakes KDE/plasma (it even removed applications ?!?!?), I am not sure that this is going to be harmless in a KDE/plasma environment.

That is what it want to remove:

zypper rm NetworkManager
Loading repository data...
Reading installed packages...
Resolving package dependencies...

The following application is going to be REMOVED:

The following 19 packages are going to be REMOVED:
  NetworkManager NetworkManager-branding-openSUSE NetworkManager-lang NetworkManager-openconnect
  NetworkManager-openconnect-lang NetworkManager-openvpn NetworkManager-openvpn-lang NetworkManager-pptp
  NetworkManager-pptp-lang patterns-kde-kde patterns-kde-kde_imaging patterns-kde-kde_plasma plasma-nm5
  plasma-nm5-lang plasma-nm5-openconnect plasma-nm5-openvpn plasma-nm5-pptp plasma5-session

The following 3 patterns are going to be REMOVED:
  kde kde_imaging kde_plasma

19 packages to remove.
After the operation, 20.0 MiB will be freed.
**Continue? [y/n/...? shows all options] (y): **n

Why? It really makes no sense to remove.

I am a former ArchLinux user. Maybe that’s why I am used to keep the system as lean as I can. After I install it I remove all the things I don’t need (games, packagekit, k3b etc.). For me there is no reason to keep a package if I did not use it.
But that is not a reason not to use anymore openSUSE. :slight_smile:

I agree with the others about just leaving it, but that aside it is possible to remove a given package with ‘rpm -e --nodeps’, and you’d also want to taboo the package with the package manager as well. Note that this can introduce unintended issues, so you need a good understanding of what you’re doing before removing such packages.

I will not remove it.
I do not want to break my system.
For me was strange such a dependecy for KDE.

Same here. And also for the Samba server.

In earlier days I just did not install things like NM and Samba already at installation. Never was a problem.

BTW for the NM client applet on the desktop I can understand why a system manager wants to remove it. When not using NM, it is an annoyance to the user. He gets an icon, which at best does not do anything when clicking on it, or worse (or is it the other way around) give an error he probably will not understand. >:(

I am somewhat like that, myself. Actually, on install, I now go through and Taboo each game, packagekit, Plymouth, and a few other things.

However, in a case like this, rather than untangle the mess, I just shrug my shoulders, since space is no longer a!

I will do the same. lol!

Network Manager is a Gnome project, but that only means it’s sponsored by and managed by Gnome.
Does not mean that the code has any Gnome library or Desktop dependencies.
In fact, AFAIK the only real dependency is wpa_supplicant which is the fundamental utility all Linux uses to connect to WPA Access points.

I can believe (but not tested) that the KDE implementation has KDE dependencies, but that is because so many KDE apps are interoperable (There are many KDE apps that depend on network connections). So, removing KDE Network Manager would probably break all those KDE apps that require network connections.

Not necessarily specific to Network Manager, I’ve also tried to remove certain KDE apps in the past which started me on a seemingly never-ending path of removing dependency upon dependency ad infinitum to where I finally cancelled the whole attempt.