Red Hat Bugzilla – Bug 1264685
Applet not visible in MATE after login when no connection is established
Last modified: 2016-07-19 15:18:47 EDT
Description of problem:
Applet is not visible in notification area until some connection is established.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Log in using MATE session
2. Ensure that no active connection is established and ethernet cable is unplugged
3. Try to connect to any wireless/mobile network ;-)
There's no nm-applet icon visible even though nm-applet and notificaiton-area-applet are running
Visible icon of nm-applet in notification area
Workaround is to use nmcli. I think that the icon was visible in Fedora 21...
I don't know whether nm-applet is supposed to run in MATE, or the DE uses its own networking applet.
Anyway, can you check, in terminal, whether nm-applet is running
$ ps aux | grep nm-applet
Does the icon appear when you start nm-applet manually?
What do you get with
$ tail -n 10 /usr/share/applications/nm-applet.desktop
Check any MATE related autostart script/file.
Ofcourse the nm-applet is running. Plugging the ethernet cable correctly "wakes up" the applet and it becomes visible. Restarting NetworkManager service does the trick too (and it works even when there's no active connection).
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Hm, this is weird. Can't reproduce in Xfce and GNOME; mate-panel seems to want to drag in 150 M of dependencies :(
I'm wondering if you can try running the applet in some other DE to check if the issue is specific to the mate-panel?
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.