In Natty, the network-management widget is much noiser than it was in
Maverick. It now raises a notification when a connection attempt starts, when
it succeeds, when it fails, and if wifi strength gets too low (the last one
may not me new, I'm not sure). These are all things that are visible in the
systray. In my opinion, I think they are redundant and a distraction (having
the connecting and connected notifications right on top of each other is
particularly so).

I'd like to disable these by default by adding a networkmanagement.notifyrc to
kubuntu-default-settings (see below). Any objections?

Scott K

[Event/connected]
Action=
Execute=
KTTS=
Logfile=
Sound=

[Event/connecting]
Action=
Execute=
KTTS=
Logfile=
Sound=

[Event/connfailed]
Action=
Execute=
KTTS=
Logfile=
Sound=

[Event/lowsignal]
Action=
Execute=
KTTS=
Logfile=
Sound=

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On 01.04.2011 21:07, Scott Kitterman wrote:
> I'd like to disable these by default by adding a networkmanagement.notifyrc to
> kubuntu-default-settings (see below). Any objections?
+1 from me.
This would also work around the bug that it displays unthemed
notifications before plasma is started.

Felix

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Am Freitag 01 April 2011, 21:07:44 schrieb Scott Kitterman:
> In Natty, the network-management widget is much noiser than it was in
> Maverick. It now raises a notification when a connection attempt starts,
> when it succeeds, when it fails, and if wifi strength gets too low (the
> last one may not me new, I'm not sure).

Are those configurable via GUI now? The last git checkout I tried (one or so month ago)
had the notifications but no way to configure them in System Settings.

Btw: If Connection Failed also covers lost VPN connections (due bad signal or whatever can
interrupt them), I'm in favor of keeping that notification enabled for security reasons
(only unencrypted WLANs available -- eg. in some universities).

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On Friday, April 01, 2011 11:10:19 PM Markus Slopianka wrote:
> Am Freitag 01 April 2011, 21:07:44 schrieb Scott Kitterman:
> > In Natty, the network-management widget is much noiser than it was in
> > Maverick. It now raises a notification when a connection attempt starts,
> > when it succeeds, when it fails, and if wifi strength gets too low (the
> > last one may not me new, I'm not sure).
>
> Are those configurable via GUI now? The last git checkout I tried (one or
> so month ago) had the notifications but no way to configure them in System
> Settings.
>
> Btw: If Connection Failed also covers lost VPN connections (due bad signal
> or whatever can interrupt them), I'm in favor of keeping that notification
> enabled for security reasons (only unencrypted WLANs available -- eg. in
> some universities).

You can configure them, but you do it via the notification settings, not via
the networkmanagement setting (I had trouble finding this). I suspect it's
been there, just not very disoverable.

I think the indication in the systray is generally sufficient and if people
are particularly concerned, then have a way to re-enable them. Does the
ability to enable them via GUI resolve your concern?

Scott K

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

2011/4/2 Markus Slopianka <markus.s@kdemail.net>:
> Btw: If Connection Failed also covers lost VPN connections (due bad signal or whatever can
> interrupt them), I'm in favor of keeping that notification enabled for security reasons
> (only unencrypted WLANs available -- eg. in some universities).
>
I agree.
+1

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

Am Samstag 02 April 2011, 05:45:04 schrieb Scott Kitterman:

> You can configure them, but you do it via the notification settings, not
> via the networkmanagement setting (I had trouble finding this). I suspect
> it's been there, just not very disoverable.

I looked in System Settings. Wasn't there at that time. But good to hear it's now.


> I think the indication in the systray is generally sufficient and if people
> are particularly concerned, then have a way to re-enable them. Does the
> ability to enable them via GUI resolve your concern?

No. Thanks to tools like Firesheep, taking over unencrypted connections is a really big
security risk because it's so easy to do for anybody. If [Event/connfailed] also covers
that already established VPN connections are lost, it should be active. Or do you
constantly look at the systray? I guess you're not.
If [Event/connfailed] does not cover lost VPN connections, then I agree it makes little
sense to have it.

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On Saturday, April 02, 2011 08:39:18 AM Markus Slopianka wrote:
> Am Samstag 02 April 2011, 05:45:04 schrieb Scott Kitterman:
> > You can configure them, but you do it via the notification settings, not
> > via the networkmanagement setting (I had trouble finding this). I
> > suspect it's been there, just not very disoverable.
>
> I looked in System Settings. Wasn't there at that time. But good to hear
> it's now.
>
> > I think the indication in the systray is generally sufficient and if
> > people are particularly concerned, then have a way to re-enable them.
> > Does the ability to enable them via GUI resolve your concern?
>
> No. Thanks to tools like Firesheep, taking over unencrypted connections is
> a really big security risk because it's so easy to do for anybody. If
> [Event/connfailed] also covers that already established VPN connections
> are lost, it should be active. Or do you constantly look at the systray? I
> guess you're not.
> If [Event/connfailed] does not cover lost VPN connections, then I agree it
> makes little sense to have it.

I don't have a VPN to test with. Can someone check and see if these
notications are used for VPN connections?

Scott K

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On Fri, Apr 01, 2011 at 03:07:44PM -0400, Scott Kitterman wrote:
> In Natty, the network-management widget is much noiser than it was in
> Maverick. It now raises a notification when a connection attempt starts, when
> it succeeds, when it fails, and if wifi strength gets too low (the last one
> may not me new, I'm not sure). These are all things that are visible in the
> systray. In my opinion, I think they are redundant and a distraction (having
> the connecting and connected notifications right on top of each other is
> particularly so).
>
> I'd like to disable these by default by adding a networkmanagement.notifyrc to
> kubuntu-default-settings (see below). Any objections?

Go ahead.

Jonathan

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel

On Friday, April 01, 2011 21:07:44 Scott Kitterman wrote:
> In Natty, the network-management widget is much noiser than it was in
> Maverick. It now raises a notification when a connection attempt starts,
> when it succeeds, when it fails, and if wifi strength gets too low (the
> last one may not me new, I'm not sure). These are all things that are
> visible in the systray. In my opinion, I think they are redundant and a
> distraction (having the connecting and connected notifications right on
> top of each other is particularly so).
>
> I'd like to disable these by default by adding a networkmanagement.notifyrc
> to kubuntu-default-settings (see below). Any objections?
>
> Scott K
>
> [Event/connected]
> Action=
> Execute=
> KTTS=
> Logfile=
> Sound=
>
> [Event/connecting]
> Action=
> Execute=
> KTTS=
> Logfile=
> Sound=
>
> [Event/connfailed]
> Action=
> Execute=
> KTTS=
> Logfile=
> Sound=
>
> [Event/lowsignal]
> Action=
> Execute=
> KTTS=
> Logfile=
> Sound=

I'd be happy to receive a patch against master

The reason why we didn't kill those earlier is that they were broken. Lamarque
fixed that, and now it's too noisy.

There's also the "network management system disabled" thing, should probably
go away as well.

Cheers,
--
sebas

http://www.kde.org | http://vizZzion.org | GPG Key ID: 9119 0EF9

--
kubuntu-devel mailing list
kubuntu-devel@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel