Description of problem:
The network notification for connection to either Network, wireless or VPN connections are not shown in Gnome 3.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. disconnect from wired network
2. connect to wired network
No notification that you are connected to a network
Notification that you are connected to a network
We were looking to use the Cisco VPN option to present a message after the user logged in. This was working on RHEL 6, and works while using vpnc on the command line.
The settings in Dconf are not disabled (and I did reset them with the following commands:
gsettings reset org.gnome.nm-applet disable-connected-notifications
gsettings reset org.gnome.nm-applet disable-disconnected-notifications
gsettings reset org.gnome.nm-applet disable-wifi-create
gsettings reset org.gnome.nm-applet suppress-wireless-networks-available
gsettings reset org.gnome.nm-applet disable-vpn-notifications
(In reply to Oliver Haessler from comment #0)
> Description of problem:
> The network notification for connection to either Network, wireless or VPN
> connections are not shown in Gnome 3.
That's because GNOME 3 has built-in network indicator support instead of relying on nm-applet. That is this:
> The settings in Dconf are not disabled (and I did reset them with the
> following commands:
> gsettings reset org.gnome.nm-applet disable-connected-notifications
> gsettings reset org.gnome.nm-applet disable-disconnected-notifications
> gsettings reset org.gnome.nm-applet disable-wifi-create
> gsettings reset org.gnome.nm-applet suppress-wireless-networks-available
> gsettings reset org.gnome.nm-applet disable-vpn-notifications
configures a component that isn't used, and the one that *is* used doesn't follow those settings.
IMHO this is not a regression (if we changed the default browser from Firefox to Chromium, I would not expect the latter to follow the settings of the previous default browser either), but a feature request.
Also I would rather avoid copying nm-applet's settings one-by-one if possible, so can we pin down what feature exactly is missing? We do show notifications when a connection has been lost, what you want is another one when a connection has been established?
This behavior is unchanged since 7.0, I don't think it qualifies as a blocker.
The best option for the CSB is a small shell extension, maybe ?
We can probably help with writing one. Setting devack- to get this off the blocker list.
Development Management has reviewed and declined this request. You may appeal this decision by reopening this request.