Cannot "close" network manager

English Applications
1

Pretty sure this falls under software, not networking. OS -> OpenSuSE version 13.2, KDE 4 running on my desktop, wicked installed by default to manage my network card (no problems whatsoever).

Issue I am having: in the taskbar is the icon for network manager with an red X through it, complaining that it is not connected (yet I am on the internet all the time, so I am connected). I read breifly before somewhere that network manager is not compatible with wicked (does not bother me in any way), what I would like to do would be to turn off the network manager program yet nothing I try exits the program. Right clicking, no options to do this; settings, no options…

This is not crucial, just an annoyance. If anyone can tell me how to turn off the program “network manager” so I don’t have to look at that icon anymore, it would be greatly appreciated.

If this should belong to the networking forum, I apologize now for the mistake.

Thanks!

2

This is no “program”, it is a system tray applet.

You can disable or hide it in the “System Tray Settings”. To reach them, right-click on an empty space in the system tray, the easiest spot is the small up-arrow just left of the digital clock.

OTOH, you can switch between Wicked and NetworkManager in YaST->Network Devices->Network Settings->Global Options.

3

Did the trick, had a feeling it was simple to the point that I was overlooking it, thanks for the info!

4

And when you are not interested in running NM at all, you can of course de-install it. That will certainly remove the applet :wink:

BTW, this is not a joke, I do not install NM at all (saving me the de-install) on "fixed place systems (like computer room or desktop ones).

5

Yes, with KDE this is an option as well.

But it will not be possible if you want to have GNOME installed as well.
gnome-shell itself requires NetworkManager.

6

:question::question:
In any case a reason for me not to consider using Gnome. Thanks for the info, can save me some time.

7

Just to be clear: gnome-shell requires NetworkManager on a package level, i.e. you need to have NetworkManager installed when installing/using GNOME.
GNOME should work fine with NetworkManager being disabled.

And a quick search revealed that mate-panel requires NetworkManager as well. Not really surprising though, as MATE is a fork of GNOME(2).

8

Strange way of handling IMHO. But I of course do not know the logic of the idea behind this. I am not sure, but some might call this bloatware, or do I misunderstand the meaning of this term?

9

AIUI, GNOME’s networking applet is directly integrated in the shell/panel and cannot be removed/uninstalled. (there is the stand-alone nm-applet too, but that is not used by GNOME itself, although it is in the package NetworkManager-gnome, for historical reasons I suppose)

You’d have to ask the GNOME developers though, why they did it this way.

One reason might be that NetworkManager is actually a GNOME project…

10

On 04/04/2015 07:06 AM, wolfi323 wrote:
>
> hcvv;2703105 Wrote:
>> Strange way of handling IMHO. But I of course do not know the logic of
>> the idea behind this.
> AIUI, GNOME’s networking applet is directly integrated in the
> shell/panel and cannot be removed/uninstalled. (there is the stand-alone
> nm-applet too, but that is not used by GNOME itself, although it is in
> the package NetworkManager-gnome, for historical reasons I suppose)
>
> You’d have to ask the GNOME developers though, why they did it this way.
>
> One reason might be that NetworkManager is actually a GNOME project…
>
>

When in Gnome, do as the Gnomens do. :slight_smile:

11

As said, I will avoid it.

12

On Sat 04 Apr 2015 03:16:01 PM CDT, hcvv wrote:

kensch;2703114 Wrote:
>
> When in Gnome, do as the Gnomens do. :slight_smile:
As said, I will avoid it.

Hi
It’s probably in one of the patterns, my SLES 12 system doesn’t use it
and it’s not installed… just uses wicked.

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.38-44-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

13

Thank. Good to know that it is not so strongly bonded with it.

14

Well, maybe that’s the case in SLES, but it’s definitely required by gnome-shell in openSUSE 13.2:

wolfi@linux-lf90:/> zypper info --requires gnome-shell | grep Network
  NetworkManager-gnome
  typelib(NetworkManager)
  typelib(NetworkManager) == 1.0
wolfi@linux-lf90:/>
15

On Sat 04 Apr 2015 04:46:01 PM CDT, wolfi323 wrote:

malcolmlewis;2703127 Wrote:
> It’s probably in one of the patterns, my SLES 12 system doesn’t use it
> and it’s not installed… just uses wicked.
>
Well, maybe that’s the case in SLES, but it’s definitely required by
gnome-shell in openSUSE 13.2:

Code:

wolfi@linux-lf90:/> zypper info --requires gnome-shell | grep
Network NetworkManager-gnome typelib(NetworkManager)
typelib(NetworkManager) == 1.0

wolfi@linux-lf90:/>

Hi
Those are just the introspection bindings and are present (as
installed) in SLES 12 as well, but not the actual packages indicated.
Probably worth a bug report…?

–
Cheers Malcolm °¿° LFCS, SUSE Knowledge Partner (Linux Counter #276890)
SUSE Linux Enterprise Desktop 12 GNOME 3.10.1 Kernel 3.12.39-47-default
If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below… Thanks!

16

No, NetworkManager-gnome “contains GNOME utilities and applications for use with
NetworkManager, including a panel applet for wireless networks”, and it requires NetworkManager in turn.

The typelib-* packages are the “introspection bindings”, but they are not the reason for requiring NetworkManager.

Probably worth a bug report…?

I don’t think it is a bug per se.
Maybe in SLES the parts that require NetworkManager got split out into an optional subpackage?

At least they made such a change with evolution-data-server, which is required in openSUSE as well:
http://lists.opensuse.org/opensuse-gnome/2015-03/msg00005.html