Re: Request for ergonomy feature

2007-10-13 Thread Eric . Brunet
On Thu, Oct 11, 2007 at 01:09:54PM -0400, Dan Williams wrote:
> On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> please check and make sure your distro is correctly telling NM to go to
> sleep and waking up.  The behavior you describe is consistent with NM
> _not_ going to sleep, which is should be doing.
> 
Hi,

On my fedora 7, it is a script of the pm-utils package doing this job of
disconnecting/reconnecting NM before/after suspend. I don't have
gnome-power-manager.

And it is enabled by default, but I decided to disable it.

Why ? Because most of the time, I wake up at the same place that I
suspended, and I enjoy having the instant connectivity on wake up rather
than wait for NM to reconnect, which is quite slow. And it is true that
when I change place, it is a little bit of an hassle to reconnect to the
new network, for the reason that have been described, but that's a rare
occurence compared to the convenience I have when I wake up in the same
place.

(The problem is exacerbated by the fact that, for some reason, NM has
some difficulty connecting to a known network. It won't do it alone, I
have to click on the icon, and it usually works only the second or third
time. F7 fully updated with iwl3945. One day, I need to send some logs to
this list to make a proper bug report.)

So, is it possible to have the best of both worlds ? A NM who keeps a
connexion fully configured if one wakes up at the same place, and changes
promptly the network when one wakes up at another place ? For instance,
would it make sense to have the ".sleep" method be a NOP, and that on a
".wake" method, NM rescans immediately the networks and tries to decide
if the computer moved or not ?

Éric
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-12 Thread Joel Goguen

On Fri, 2007-10-12 at 19:37 +0200, Jürg Billeter wrote:
> On Fri, 2007-10-12 at 08:38 -0400, Dan Williams wrote:
> > On Thu, 2007-10-11 at 20:46 -0300, Joel Goguen wrote:
> > > I think the problem may actually be in the system configuration, and
> > > both gnome-power-manager and NM are doing exactly what they're told to
> > > do.  After some poking around in the gnome-power-manager source, I found
> > > that it does send the sleep/wake commands to NM if the key
> > > '/apps/gnome-power-manager/general/network_sleep' is set to true.  If
> > > this is false, the sleep/wake signals won't be sent.  When I opened up
> > > the GConf config tool, this value was false for me.  I'm not able to
> > > test it yet, but in about 2 hours I'll be able to check and post back if
> > > this works.  In the meantime, if someone else is able to verify that the
> > > value is false and NM properly rescans after waking up with the value
> > > set to true that would be great :)
> > 
> > This is a distro problem.  I think g-p-m turned that key off by default
> > (I have _no_ idea why) a while ago, and distro maintainers need to be on
> > top of these sorts of things to make sure stuff works for their users.
> 
> The reason is probably that pm-utils already sends the sleep/wake
> signals to NetworkManager and that's what many distros use now.
> 
> Jürg
> 
The pm-utils package is not installed on my laptop.  It's Ubuntu Feisty
-> Gutsy upgrade.  It's also not installed on my desktop, which is
Ubuntu Edgy -> Feisty -> Gutsy upgrade.  So either Ubuntu needs to
enable the /apps/gnome-power-manager/general/network_sleep key by
default if NM is installed or install the pm-utils package by default.
I don't know if it gives some benefit to install pm-utils, but I think
it would be simpler to enable this key that AFAIK is specifically for
NM.

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Medawar


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-12 Thread Jürg Billeter

On Fri, 2007-10-12 at 08:38 -0400, Dan Williams wrote:
> On Thu, 2007-10-11 at 20:46 -0300, Joel Goguen wrote:
> > I think the problem may actually be in the system configuration, and
> > both gnome-power-manager and NM are doing exactly what they're told to
> > do.  After some poking around in the gnome-power-manager source, I found
> > that it does send the sleep/wake commands to NM if the key
> > '/apps/gnome-power-manager/general/network_sleep' is set to true.  If
> > this is false, the sleep/wake signals won't be sent.  When I opened up
> > the GConf config tool, this value was false for me.  I'm not able to
> > test it yet, but in about 2 hours I'll be able to check and post back if
> > this works.  In the meantime, if someone else is able to verify that the
> > value is false and NM properly rescans after waking up with the value
> > set to true that would be great :)
> 
> This is a distro problem.  I think g-p-m turned that key off by default
> (I have _no_ idea why) a while ago, and distro maintainers need to be on
> top of these sorts of things to make sure stuff works for their users.

The reason is probably that pm-utils already sends the sleep/wake
signals to NetworkManager and that's what many distros use now.

Jürg

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-12 Thread Dan Williams
On Thu, 2007-10-11 at 20:46 -0300, Joel Goguen wrote:
> On Thu, 2007-10-11 at 15:14 -0400, Dan Williams wrote:
> > On Thu, 2007-10-11 at 14:14 -0300, Joel Goguen wrote:
> > > On Thu, 2007-10-11 at 13:09 -0400, Dan Williams wrote:
> > > > On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> > > > > On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > > > > > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > > > > > 
> > > > > > >
> > > > > > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > > > > > >> I have a similar problem with sleeping my laptop at work and then
> > > > > > >> going home to connect to my wireless network.  I usually resort 
> > > > > > >> to
> > > > > > >> opening a terminal and restarting the Network Manager service on 
> > > > > > >> the
> > > > > > >> occasions that the applet refuses to scan for wireless networks 
> > > > > > >> in
> > > > > > >> timely fashion.
> > > > > > >
> > > > > > > Rescan on wake from suspend or hibernate might be the way to 
> > > > > > > solve this?
> > > > > > 
> > > > > > Did you have a look in /etc/hibernate/common.conf?
> > > > > > At least on Debian there is an option "EnableNMReconnect yes".
> > > > > > 
> > > > > > BR,
> > > > > > Markus Becker
> > > > > > 
> > > > > > >
> > > > > > > -- 
> > > > > > > Peter Clifton
> > > > > > >
> > > > > > > Electrical Engineering Division,
> > > > > > > Engineering Department,
> > > > > > > University of Cambridge,
> > > > > > > 9, JJ Thomson Avenue,
> > > > > > > Cambridge
> > > > > > > CB3 0FA
> > > > > > >
> > > > > > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > > > > > >
> > > > > > > ___
> > > > > > > NetworkManager-list mailing list
> > > > > > > NetworkManager-list@gnome.org
> > > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > > > >
> > > > > > ___
> > > > > > NetworkManager-list mailing list
> > > > > > NetworkManager-list@gnome.org
> > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > > On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> > > > > Also, I'm not able to hibernate the laptop at all, only Suspend.  
> > > > > Maybe
> > > > > that file normally handles both, but this is the first I've heard of 
> > > > > it.
> > > > 
> > > > On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> > > > wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> > > > please check and make sure your distro is correctly telling NM to go to
> > > > sleep and waking up.  The behavior you describe is consistent with NM
> > > > _not_ going to sleep, which is should be doing.
> > > > 
> > > > Dan
> > > > 
> > > > 
> > > > > ___
> > > > > NetworkManager-list mailing list
> > > > > NetworkManager-list@gnome.org
> > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > 
> > > Primarily for my own curiosity and so I can put some details in a bug
> > > report if needed, what would be the proper way to tell NM to go to sleep
> > > and wake up?  Is there a way to broadcast a message over dbus and
> > > anything listening that receives the message goes to sleep or wakes up
> > > as appropriate?  Or would a message need to be sent specifically to NM
> > > for each?
> > 
> > Historically, there has not been a system service that sends out dbus
> > signals on sleep/wake.  That should probably be HAL if anything.  But
> > since power policy is managed int he _session_, and not system wide,
> > it's unclear exactly how that would work.  In any case, you must call
> > the 'sleep' and 'wake' methods like so:
> > 
> > dbus-send --system
> > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> > org.freedesktop.NetworkManager.sleep
> > 
> > and 'wake'.
> > 
> > Dan
> > 
> > 
> I think the problem may actually be in the system configuration, and
> both gnome-power-manager and NM are doing exactly what they're told to
> do.  After some poking around in the gnome-power-manager source, I found
> that it does send the sleep/wake commands to NM if the key
> '/apps/gnome-power-manager/general/network_sleep' is set to true.  If
> this is false, the sleep/wake signals won't be sent.  When I opened up
> the GConf config tool, this value was false for me.  I'm not able to
> test it yet, but in about 2 hours I'll be able to check and post back if
> this works.  In the meantime, if someone else is able to verify that the
> value is false and NM properly rescans after waking up with the value
> set to true that would be great :)

This is a distro problem.  I think g-p-m turned that key off by default
(I have _no_ idea why) a while ago, and distro maintainers need to be on
top of these sorts of things to make sure stuff works for their users.

Dan

___
NetworkManager-list mailing list
NetworkManager-list@gnome

Re: Request for ergonomy feature

2007-10-12 Thread Jeroen van de Nieuwenhof
Op donderdag 11-10-2007 om 11:19 uur [tijdzone -0400], schreef Dan Williams:
> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> > Ok, but it is just a pain in the *ss this bug, and everybody
complains.
> >
> > Please, rather than saying "I disagree", maybe propose an alternative,

> > because it is really annoying bug.
>
> We already discussed alternatives on this list.  First, NM should scan
quite quickly after dropping the menu down, as long as NM has not
scanned within the last 20 seconds.  Currently that may not be the case,
it might push off the scan for 20 seconds.  This is a case of a bug that
should be fixed (if it exists).
>
> Furthermore, I don't believe that it's that much of a burden to check
the menu twice.  Can you refresh my memory as to what situations
explicitly scanning for networks is necessary?  The applet should be
kept simple, additional functionality that doesn't fit in the applet can
certainly be farmed out to other tools that are not the applet or NM.
The applet should cover 90% of all users needs 90% of the time.  It
should _not_ cover 100% of all users needs 100% of the time.  There are
some features that just won't be implemented.  I believe explicitly scan
requests fit in that last 10%.  I may be able to be convinced otherwise.
>
> Dan
>

I think the main problem is that new users of NM don't KNOW that NM scans
for new networks after a click or some time. So if a new user runs NM and
sees no networks while he knows there are networks in the area he gets
annoyed that they aren't available in the applet.

Jeroen







Op donderdag 11-10-2007 om 11:19 uur [tijdzone -0400], schreef Dan Williams:


On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> Ok, but it is just a pain in the *ss this bug, and everybody complains.
> 
> Please, rather than saying "I disagree", maybe propose an alternative, 
> because it is really annoying bug.

We already discussed alternatives on this list.  First, NM should scan
quite quickly after dropping the menu down, as long as NM has not
scanned within the last 20 seconds.  Currently that may not be the case,
it might push off the scan for 20 seconds.  This is a case of a bug that
should be fixed (if it exists).

Furthermore, I don't believe that it's that much of a burden to check
the menu twice.  Can you refresh my memory as to what situations
explicitly scanning for networks is necessary?  The applet should be
kept simple, additional functionality that doesn't fit in the applet can
certainly be farmed out to other tools that are not the applet or NM.
The applet should cover 90% of all users needs 90% of the time.  It
should _not_ cover 100% of all users needs 100% of the time.  There are
some features that just won't be implemented.  I believe explicitly scan
requests fit in that last 10%.  I may be able to be convinced otherwise.

Dan




I think the main problem is that new users of NM don't KNOW that NM scans for new networks after a click or some time. So if a new user runs NM and sees no networks while he knows there are networks in the area he gets annoyed that they aren't available in the applet.

Jeroen

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen

On Thu, 2007-10-11 at 20:46 -0300, Joel Goguen wrote:
> On Thu, 2007-10-11 at 15:14 -0400, Dan Williams wrote:
> > On Thu, 2007-10-11 at 14:14 -0300, Joel Goguen wrote:
> > > On Thu, 2007-10-11 at 13:09 -0400, Dan Williams wrote:
> > > > On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> > > > > On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > > > > > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > > > > > 
> > > > > > >
> > > > > > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > > > > > >> I have a similar problem with sleeping my laptop at work and then
> > > > > > >> going home to connect to my wireless network.  I usually resort 
> > > > > > >> to
> > > > > > >> opening a terminal and restarting the Network Manager service on 
> > > > > > >> the
> > > > > > >> occasions that the applet refuses to scan for wireless networks 
> > > > > > >> in
> > > > > > >> timely fashion.
> > > > > > >
> > > > > > > Rescan on wake from suspend or hibernate might be the way to 
> > > > > > > solve this?
> > > > > > 
> > > > > > Did you have a look in /etc/hibernate/common.conf?
> > > > > > At least on Debian there is an option "EnableNMReconnect yes".
> > > > > > 
> > > > > > BR,
> > > > > > Markus Becker
> > > > > > 
> > > > > > >
> > > > > > > -- 
> > > > > > > Peter Clifton
> > > > > > >
> > > > > > > Electrical Engineering Division,
> > > > > > > Engineering Department,
> > > > > > > University of Cambridge,
> > > > > > > 9, JJ Thomson Avenue,
> > > > > > > Cambridge
> > > > > > > CB3 0FA
> > > > > > >
> > > > > > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > > > > > >
> > > > > > > ___
> > > > > > > NetworkManager-list mailing list
> > > > > > > NetworkManager-list@gnome.org
> > > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > > > >
> > > > > > ___
> > > > > > NetworkManager-list mailing list
> > > > > > NetworkManager-list@gnome.org
> > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > > On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> > > > > Also, I'm not able to hibernate the laptop at all, only Suspend.  
> > > > > Maybe
> > > > > that file normally handles both, but this is the first I've heard of 
> > > > > it.
> > > > 
> > > > On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> > > > wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> > > > please check and make sure your distro is correctly telling NM to go to
> > > > sleep and waking up.  The behavior you describe is consistent with NM
> > > > _not_ going to sleep, which is should be doing.
> > > > 
> > > > Dan
> > > > 
> > > > 
> > > > > ___
> > > > > NetworkManager-list mailing list
> > > > > NetworkManager-list@gnome.org
> > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > 
> > > Primarily for my own curiosity and so I can put some details in a bug
> > > report if needed, what would be the proper way to tell NM to go to sleep
> > > and wake up?  Is there a way to broadcast a message over dbus and
> > > anything listening that receives the message goes to sleep or wakes up
> > > as appropriate?  Or would a message need to be sent specifically to NM
> > > for each?
> > 
> > Historically, there has not been a system service that sends out dbus
> > signals on sleep/wake.  That should probably be HAL if anything.  But
> > since power policy is managed int he _session_, and not system wide,
> > it's unclear exactly how that would work.  In any case, you must call
> > the 'sleep' and 'wake' methods like so:
> > 
> > dbus-send --system
> > --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> > org.freedesktop.NetworkManager.sleep
> > 
> > and 'wake'.
> > 
> > Dan
> > 
> > 
> I think the problem may actually be in the system configuration, and
> both gnome-power-manager and NM are doing exactly what they're told to
> do.  After some poking around in the gnome-power-manager source, I found
> that it does send the sleep/wake commands to NM if the key
> '/apps/gnome-power-manager/general/network_sleep' is set to true.  If
> this is false, the sleep/wake signals won't be sent.  When I opened up
> the GConf config tool, this value was false for me.  I'm not able to
> test it yet, but in about 2 hours I'll be able to check and post back if
> this works.  In the meantime, if someone else is able to verify that the
> value is false and NM properly rescans after waking up with the value
> set to true that would be great :)
> 
This seemed to work nicely when transitioning from campus to a friend's
place to home.

I feel like kicking myself if this was all I needed to do to solve this
problem the whole time :)

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Me

Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen

On Thu, 2007-10-11 at 15:14 -0400, Dan Williams wrote:
> On Thu, 2007-10-11 at 14:14 -0300, Joel Goguen wrote:
> > On Thu, 2007-10-11 at 13:09 -0400, Dan Williams wrote:
> > > On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> > > > On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > > > > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > > > > 
> > > > > >
> > > > > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > > > > >> I have a similar problem with sleeping my laptop at work and then
> > > > > >> going home to connect to my wireless network.  I usually resort to
> > > > > >> opening a terminal and restarting the Network Manager service on 
> > > > > >> the
> > > > > >> occasions that the applet refuses to scan for wireless networks in
> > > > > >> timely fashion.
> > > > > >
> > > > > > Rescan on wake from suspend or hibernate might be the way to solve 
> > > > > > this?
> > > > > 
> > > > > Did you have a look in /etc/hibernate/common.conf?
> > > > > At least on Debian there is an option "EnableNMReconnect yes".
> > > > > 
> > > > > BR,
> > > > > Markus Becker
> > > > > 
> > > > > >
> > > > > > -- 
> > > > > > Peter Clifton
> > > > > >
> > > > > > Electrical Engineering Division,
> > > > > > Engineering Department,
> > > > > > University of Cambridge,
> > > > > > 9, JJ Thomson Avenue,
> > > > > > Cambridge
> > > > > > CB3 0FA
> > > > > >
> > > > > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > > > > >
> > > > > > ___
> > > > > > NetworkManager-list mailing list
> > > > > > NetworkManager-list@gnome.org
> > > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > > >
> > > > > ___
> > > > > NetworkManager-list mailing list
> > > > > NetworkManager-list@gnome.org
> > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> > > > Also, I'm not able to hibernate the laptop at all, only Suspend.  Maybe
> > > > that file normally handles both, but this is the first I've heard of it.
> > > 
> > > On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> > > wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> > > please check and make sure your distro is correctly telling NM to go to
> > > sleep and waking up.  The behavior you describe is consistent with NM
> > > _not_ going to sleep, which is should be doing.
> > > 
> > > Dan
> > > 
> > > 
> > > > ___
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list@gnome.org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > 
> > Primarily for my own curiosity and so I can put some details in a bug
> > report if needed, what would be the proper way to tell NM to go to sleep
> > and wake up?  Is there a way to broadcast a message over dbus and
> > anything listening that receives the message goes to sleep or wakes up
> > as appropriate?  Or would a message need to be sent specifically to NM
> > for each?
> 
> Historically, there has not been a system service that sends out dbus
> signals on sleep/wake.  That should probably be HAL if anything.  But
> since power policy is managed int he _session_, and not system wide,
> it's unclear exactly how that would work.  In any case, you must call
> the 'sleep' and 'wake' methods like so:
> 
> dbus-send --system
> --dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
> org.freedesktop.NetworkManager.sleep
> 
> and 'wake'.
> 
> Dan
> 
> 
I think the problem may actually be in the system configuration, and
both gnome-power-manager and NM are doing exactly what they're told to
do.  After some poking around in the gnome-power-manager source, I found
that it does send the sleep/wake commands to NM if the key
'/apps/gnome-power-manager/general/network_sleep' is set to true.  If
this is false, the sleep/wake signals won't be sent.  When I opened up
the GConf config tool, this value was false for me.  I'm not able to
test it yet, but in about 2 hours I'll be able to check and post back if
this works.  In the meantime, if someone else is able to verify that the
value is false and NM properly rescans after waking up with the value
set to true that would be great :)

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Medawar


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Dan Williams
On Thu, 2007-10-11 at 14:14 -0300, Joel Goguen wrote:
> On Thu, 2007-10-11 at 13:09 -0400, Dan Williams wrote:
> > On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> > > On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > > > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > > > 
> > > > >
> > > > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > > > >> I have a similar problem with sleeping my laptop at work and then
> > > > >> going home to connect to my wireless network.  I usually resort to
> > > > >> opening a terminal and restarting the Network Manager service on the
> > > > >> occasions that the applet refuses to scan for wireless networks in
> > > > >> timely fashion.
> > > > >
> > > > > Rescan on wake from suspend or hibernate might be the way to solve 
> > > > > this?
> > > > 
> > > > Did you have a look in /etc/hibernate/common.conf?
> > > > At least on Debian there is an option "EnableNMReconnect yes".
> > > > 
> > > > BR,
> > > > Markus Becker
> > > > 
> > > > >
> > > > > -- 
> > > > > Peter Clifton
> > > > >
> > > > > Electrical Engineering Division,
> > > > > Engineering Department,
> > > > > University of Cambridge,
> > > > > 9, JJ Thomson Avenue,
> > > > > Cambridge
> > > > > CB3 0FA
> > > > >
> > > > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > > > >
> > > > > ___
> > > > > NetworkManager-list mailing list
> > > > > NetworkManager-list@gnome.org
> > > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > > >
> > > > ___
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list@gnome.org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> > > Also, I'm not able to hibernate the laptop at all, only Suspend.  Maybe
> > > that file normally handles both, but this is the first I've heard of it.
> > 
> > On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> > wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> > please check and make sure your distro is correctly telling NM to go to
> > sleep and waking up.  The behavior you describe is consistent with NM
> > _not_ going to sleep, which is should be doing.
> > 
> > Dan
> > 
> > 
> > > ___
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > 
> Primarily for my own curiosity and so I can put some details in a bug
> report if needed, what would be the proper way to tell NM to go to sleep
> and wake up?  Is there a way to broadcast a message over dbus and
> anything listening that receives the message goes to sleep or wakes up
> as appropriate?  Or would a message need to be sent specifically to NM
> for each?

Historically, there has not been a system service that sends out dbus
signals on sleep/wake.  That should probably be HAL if anything.  But
since power policy is managed int he _session_, and not system wide,
it's unclear exactly how that would work.  In any case, you must call
the 'sleep' and 'wake' methods like so:

dbus-send --system
--dest=org.freedesktop.NetworkManager /org/freedesktop/NetworkManager
org.freedesktop.NetworkManager.sleep

and 'wake'.

Dan


___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen

On Thu, 2007-10-11 at 13:09 -0400, Dan Williams wrote:
> On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> > On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > > 
> > > >
> > > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > > >> I have a similar problem with sleeping my laptop at work and then
> > > >> going home to connect to my wireless network.  I usually resort to
> > > >> opening a terminal and restarting the Network Manager service on the
> > > >> occasions that the applet refuses to scan for wireless networks in
> > > >> timely fashion.
> > > >
> > > > Rescan on wake from suspend or hibernate might be the way to solve this?
> > > 
> > > Did you have a look in /etc/hibernate/common.conf?
> > > At least on Debian there is an option "EnableNMReconnect yes".
> > > 
> > > BR,
> > > Markus Becker
> > > 
> > > >
> > > > -- 
> > > > Peter Clifton
> > > >
> > > > Electrical Engineering Division,
> > > > Engineering Department,
> > > > University of Cambridge,
> > > > 9, JJ Thomson Avenue,
> > > > Cambridge
> > > > CB3 0FA
> > > >
> > > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > > >
> > > > ___
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list@gnome.org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >
> > > ___
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> > Also, I'm not able to hibernate the laptop at all, only Suspend.  Maybe
> > that file normally handles both, but this is the first I've heard of it.
> 
> On Fedora, gnome-power-manager is the thing that tells NM to sleep and
> wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
> please check and make sure your distro is correctly telling NM to go to
> sleep and waking up.  The behavior you describe is consistent with NM
> _not_ going to sleep, which is should be doing.
> 
> Dan
> 
> 
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
Primarily for my own curiosity and so I can put some details in a bug
report if needed, what would be the proper way to tell NM to go to sleep
and wake up?  Is there a way to broadcast a message over dbus and
anything listening that receives the message goes to sleep or wakes up
as appropriate?  Or would a message need to be sent specifically to NM
for each?

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Medawar


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Derek Atkins
Quoting Dan Williams <[EMAIL PROTECTED]>:

> This is likely a distro or driver problem.  When NM is told to go to
> sleep (whcih your setup may not be doing), it will blow away _all_
> network state.  That means, when NM wakes up (if told to wake up
> correctly), it won't know about _any_ networks.  It will rescan
> immediately.  If it's getting stale networks when you turn it back on,
> that's clearly a sleep/wake bug, or a driver bug.

Just for the record, nm-applet does not always properly clear it's state.
When I suspend/move/resume the applet still "remembers" the networks
it saw before the suspend.  I've certainly seen this with a relatively
up-to-date Fedora 7 system (which means NM-0.6.5).  So maybe the applet
is caching the state and not clearing out the list properly on suspend
or resume?

> dan

-derek

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   [EMAIL PROTECTED]PGP key available

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Dan Williams
On Thu, 2007-10-11 at 13:56 -0300, Joel Goguen wrote:
> On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> > On Thu, 11 Oct 2007, Peter Clifton wrote:
> > 
> > >
> > > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> > >> I have a similar problem with sleeping my laptop at work and then
> > >> going home to connect to my wireless network.  I usually resort to
> > >> opening a terminal and restarting the Network Manager service on the
> > >> occasions that the applet refuses to scan for wireless networks in
> > >> timely fashion.
> > >
> > > Rescan on wake from suspend or hibernate might be the way to solve this?
> > 
> > Did you have a look in /etc/hibernate/common.conf?
> > At least on Debian there is an option "EnableNMReconnect yes".
> > 
> > BR,
> > Markus Becker
> > 
> > >
> > > -- 
> > > Peter Clifton
> > >
> > > Electrical Engineering Division,
> > > Engineering Department,
> > > University of Cambridge,
> > > 9, JJ Thomson Avenue,
> > > Cambridge
> > > CB3 0FA
> > >
> > > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> > >
> > > ___
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> Also, I'm not able to hibernate the laptop at all, only Suspend.  Maybe
> that file normally handles both, but this is the first I've heard of it.

On Fedora, gnome-power-manager is the thing that tells NM to sleep and
wake up.  Maybe that's the case for Ubuntu as well, I don't know.  But
please check and make sure your distro is correctly telling NM to go to
sleep and waking up.  The behavior you describe is consistent with NM
_not_ going to sleep, which is should be doing.

Dan


> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Dan Williams
On Thu, 2007-10-11 at 12:31 -0300, Joel Goguen wrote:
> I have a need for it, and I imagine it's a common one.  I have a
> wireless network at home, and I put the laptop to sleep and head to my
> university.  When I get there, I have to wait sometimes minutes for
> the list to refresh and my campus network to appear so NM can attempt
> to connect to it.  Or I can open a terminal and manually restart NM,
> but that's not something a common user should be expected to do IMO.
> When I first get to campus I still see all the networks I can see from
> my house, even though none of them are anywhere near the campus.
> After a few minutes of waiting, during which I'm checking the applet
> list at least once every 30 seconds, the list finally refreshes and NM
> connects to my campus network.  This doesn't seem very user-friendly
> to me.

This is likely a distro or driver problem.  When NM is told to go to
sleep (whcih your setup may not be doing), it will blow away _all_
network state.  That means, when NM wakes up (if told to wake up
correctly), it won't know about _any_ networks.  It will rescan
immediately.  If it's getting stale networks when you turn it back on,
that's clearly a sleep/wake bug, or a driver bug.

dan

> 
> On 10/11/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> > On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> > > Ok, but it is just a pain in the *ss this bug, and everybody complains.
> > >
> > > Please, rather than saying "I disagree", maybe propose an alternative,
> > > because it is really annoying bug.
> >
> > We already discussed alternatives on this list.  First, NM should scan
> > quite quickly after dropping the menu down, as long as NM has not
> > scanned within the last 20 seconds.  Currently that may not be the case,
> > it might push off the scan for 20 seconds.  This is a case of a bug that
> > should be fixed (if it exists).
> >
> > Furthermore, I don't believe that it's that much of a burden to check
> > the menu twice.  Can you refresh my memory as to what situations
> > explicitly scanning for networks is necessary?  The applet should be
> > kept simple, additional functionality that doesn't fit in the applet can
> > certainly be farmed out to other tools that are not the applet or NM.
> > The applet should cover 90% of all users needs 90% of the time.  It
> > should _not_ cover 100% of all users needs 100% of the time.  There are
> > some features that just won't be implemented.  I believe explicitly scan
> > requests fit in that last 10%.  I may be able to be convinced otherwise.
> >
> > Dan
> >
> > > Thanks in advance
> > >
> > > Dan Williams wrote:
> > > > On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:
> > > >
> > > >> I know this has been posted and discussed already, but this bug is *so*
> > > >> annoying, that I guess I am not the only "simple user" having troubles
> > > >> with that.
> > > >>
> > > >> Would it be possible to fix it ?
> > > >>
> > > >
> > > > I still don't agree that this is the right way to solve the issue.
> > > >
> > > > Dan
> > > >
> > > >
> > > >> Thanks a lot
> > > >>
> > > >> JM
> > > >>
> > > >> Joan B. Moreau wrote:
> > > >>
> > > >>> Hi all,
> > > >>>
> > > >>> I like the applet but here my request in terms of ergonomy:
> > > >>>
> > > >>> Would it be possible to stop triggering a scan when clicking on the
> > > >>> applet (which people do quite frequently to see the available 
> > > >>> networks)
> > > >>> but rather put a menu item "scan for available networks" that we can
> > > >>> click when one decide so  ?
> > > >>>
> > > >>> Thanks
> > > >>>
> > > >>> Joan
> > > >>>
> > > >> ___
> > > >> NetworkManager-list mailing list
> > > >> NetworkManager-list@gnome.org
> > > >> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >>
> > > >
> > > >
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> 
> 

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Scott Rossillo
I suspend to RAM on FC6 and it does not always scan wireless networks  
when it wakes from sleep after going home.

On Oct 11, 2007, at 12:56 PM, Joel Goguen wrote:

>
> On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
>> On Thu, 11 Oct 2007, Peter Clifton wrote:
>>
>>>
>>> On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
 I have a similar problem with sleeping my laptop at work and then
 going home to connect to my wireless network.  I usually resort to
 opening a terminal and restarting the Network Manager service on  
 the
 occasions that the applet refuses to scan for wireless networks in
 timely fashion.
>>>
>>> Rescan on wake from suspend or hibernate might be the way to  
>>> solve this?
>>
>> Did you have a look in /etc/hibernate/common.conf?
>> At least on Debian there is an option "EnableNMReconnect yes".
>>
>> BR,
>> Markus Becker
>>
>>>
>>> -- 
>>> Peter Clifton
>>>
>>> Electrical Engineering Division,
>>> Engineering Department,
>>> University of Cambridge,
>>> 9, JJ Thomson Avenue,
>>> Cambridge
>>> CB3 0FA
>>>
>>> Tel: +44 (0)7729 980173 - (No signal in the lab!)
>>>
>>> ___
>>> NetworkManager-list mailing list
>>> NetworkManager-list@gnome.org
>>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>>
>> ___
>> NetworkManager-list mailing list
>> NetworkManager-list@gnome.org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
> Also, I'm not able to hibernate the laptop at all, only Suspend.   
> Maybe
> that file normally handles both, but this is the first I've heard  
> of it.
>
> -- 
> Joel Goguen
> http://jgoguen.net/
> The human mind treats a new idea the way the body treats a strange
> protein -- it rejects it.  -- P. Medawar
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen

On Thu, 2007-10-11 at 18:31 +0200, Markus Becker wrote:
> On Thu, 11 Oct 2007, Peter Clifton wrote:
> 
> >
> > On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> >> I have a similar problem with sleeping my laptop at work and then
> >> going home to connect to my wireless network.  I usually resort to
> >> opening a terminal and restarting the Network Manager service on the
> >> occasions that the applet refuses to scan for wireless networks in
> >> timely fashion.
> >
> > Rescan on wake from suspend or hibernate might be the way to solve this?
> 
> Did you have a look in /etc/hibernate/common.conf?
> At least on Debian there is an option "EnableNMReconnect yes".
> 
> BR,
> Markus Becker
> 
> >
> > -- 
> > Peter Clifton
> >
> > Electrical Engineering Division,
> > Engineering Department,
> > University of Cambridge,
> > 9, JJ Thomson Avenue,
> > Cambridge
> > CB3 0FA
> >
> > Tel: +44 (0)7729 980173 - (No signal in the lab!)
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
On Ubuntu Gutsy beta, there is no such directory '/etc/hibernate/'.
Also, I'm not able to hibernate the laptop at all, only Suspend.  Maybe
that file normally handles both, but this is the first I've heard of it.

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Medawar


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen
On Thu, 2007-10-11 at 12:47 -0400, Bill Peck wrote:
> Joel Goguen wrote:
> > I have a need for it, and I imagine it's a common one.  I have a
> > wireless network at home, and I put the laptop to sleep and head to my
> > university.  When I get there, I have to wait sometimes minutes for
> > the list to refresh and my campus network to appear so NM can attempt
> > to connect to it.  Or I can open a terminal and manually restart NM,
> > but that's not something a common user should be expected to do IMO.
> > When I first get to campus I still see all the networks I can see from
> > my house, even though none of them are anywhere near the campus.
> > After a few minutes of waiting, during which I'm checking the applet
> > list at least once every 30 seconds, the list finally refreshes and NM
> > connects to my campus network.  This doesn't seem very user-friendly
> > to me.
> >   
> 
> What distro are you using?  I put my laptop to sleep between work and 
> home and it connects to each network right away when it wakes up.
> 
> I've never had a problem, both with Fedora 6 and 7.
Ubuntu.  This occurred both with Feisty and with the latest Gutsy beta.
A few times, daemon.log shows that NM crashed with signal 11 (SIGSEGV,
segmentation fault) and then the crash manager tries to say it crashed
with signal 5.

-- 
Joel Goguen
http://jgoguen.net/
The human mind treats a new idea the way the body treats a strange
protein -- it rejects it.  -- P. Medawar


signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Bill Peck
Joel Goguen wrote:
> I have a need for it, and I imagine it's a common one.  I have a
> wireless network at home, and I put the laptop to sleep and head to my
> university.  When I get there, I have to wait sometimes minutes for
> the list to refresh and my campus network to appear so NM can attempt
> to connect to it.  Or I can open a terminal and manually restart NM,
> but that's not something a common user should be expected to do IMO.
> When I first get to campus I still see all the networks I can see from
> my house, even though none of them are anywhere near the campus.
> After a few minutes of waiting, during which I'm checking the applet
> list at least once every 30 seconds, the list finally refreshes and NM
> connects to my campus network.  This doesn't seem very user-friendly
> to me.
>   

What distro are you using?  I put my laptop to sleep between work and 
home and it connects to each network right away when it wakes up.

I've never had a problem, both with Fedora 6 and 7.
>
> On 10/11/07, Dan Williams <[EMAIL PROTECTED]> wrote:
>   
>> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
>> 
>>> Ok, but it is just a pain in the *ss this bug, and everybody complains.
>>>
>>> Please, rather than saying "I disagree", maybe propose an alternative,
>>> because it is really annoying bug.
>>>   
>> We already discussed alternatives on this list.  First, NM should scan
>> quite quickly after dropping the menu down, as long as NM has not
>> scanned within the last 20 seconds.  Currently that may not be the case,
>> it might push off the scan for 20 seconds.  This is a case of a bug that
>> should be fixed (if it exists).
>>
>> Furthermore, I don't believe that it's that much of a burden to check
>> the menu twice.  Can you refresh my memory as to what situations
>> explicitly scanning for networks is necessary?  The applet should be
>> kept simple, additional functionality that doesn't fit in the applet can
>> certainly be farmed out to other tools that are not the applet or NM.
>> The applet should cover 90% of all users needs 90% of the time.  It
>> should _not_ cover 100% of all users needs 100% of the time.  There are
>> some features that just won't be implemented.  I believe explicitly scan
>> requests fit in that last 10%.  I may be able to be convinced otherwise.
>>
>> Dan
>>
>> 
>>> Thanks in advance
>>>
>>> Dan Williams wrote:
>>>   
 On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:

 
> I know this has been posted and discussed already, but this bug is *so*
> annoying, that I guess I am not the only "simple user" having troubles
> with that.
>
> Would it be possible to fix it ?
>
>   
 I still don't agree that this is the right way to solve the issue.

 Dan


 
> Thanks a lot
>
> JM
>
> Joan B. Moreau wrote:
>
>   
>> Hi all,
>>
>> I like the applet but here my request in terms of ergonomy:
>>
>> Would it be possible to stop triggering a scan when clicking on the
>> applet (which people do quite frequently to see the available networks)
>> but rather put a menu item "scan for available networks" that we can
>> click when one decide so  ?
>>
>> Thanks
>>
>> Joan
>>
>> 
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
>   
 
>> ___
>> NetworkManager-list mailing list
>> NetworkManager-list@gnome.org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>
>> 
>
>
>   

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Markus Becker

On Thu, 11 Oct 2007, Peter Clifton wrote:

>
> On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
>> I have a similar problem with sleeping my laptop at work and then
>> going home to connect to my wireless network.  I usually resort to
>> opening a terminal and restarting the Network Manager service on the
>> occasions that the applet refuses to scan for wireless networks in
>> timely fashion.
>
> Rescan on wake from suspend or hibernate might be the way to solve this?

Did you have a look in /etc/hibernate/common.conf?
At least on Debian there is an option "EnableNMReconnect yes".

BR,
Markus Becker

>
> -- 
> Peter Clifton
>
> Electrical Engineering Division,
> Engineering Department,
> University of Cambridge,
> 9, JJ Thomson Avenue,
> Cambridge
> CB3 0FA
>
> Tel: +44 (0)7729 980173 - (No signal in the lab!)
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Peter Clifton

On Thu, 2007-10-11 at 11:45 -0400, Scott Rossillo wrote:
> I have a similar problem with sleeping my laptop at work and then  
> going home to connect to my wireless network.  I usually resort to  
> opening a terminal and restarting the Network Manager service on the  
> occasions that the applet refuses to scan for wireless networks in  
> timely fashion.

Rescan on wake from suspend or hibernate might be the way to solve this?

-- 
Peter Clifton

Electrical Engineering Division,
Engineering Department,
University of Cambridge,
9, JJ Thomson Avenue,
Cambridge
CB3 0FA

Tel: +44 (0)7729 980173 - (No signal in the lab!)

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Scott Rossillo

I have a similar problem with sleeping my laptop at work and then  
going home to connect to my wireless network.  I usually resort to  
opening a terminal and restarting the Network Manager service on the  
occasions that the applet refuses to scan for wireless networks in  
timely fashion.

I understand the point that adding a button the "scan for networks"  
may not be ideal.  However, something should be done to address this  
because the average user should not have to open a terminal a restart  
the service just to see new wireless networks.

How about scanning on every single click, regardless of time since  
last scan, if the wireless card is not currently associated with an  
in-range wireless network?

Also, thank you guys for Network Manager ... it's a great application.

Thanks,
Scott


On Oct 11, 2007, at 11:31 AM, Joel Goguen wrote:

> I have a need for it, and I imagine it's a common one.  I have a
> wireless network at home, and I put the laptop to sleep and head to my
> university.  When I get there, I have to wait sometimes minutes for
> the list to refresh and my campus network to appear so NM can attempt
> to connect to it.  Or I can open a terminal and manually restart NM,
> but that's not something a common user should be expected to do IMO.
> When I first get to campus I still see all the networks I can see from
> my house, even though none of them are anywhere near the campus.
> After a few minutes of waiting, during which I'm checking the applet
> list at least once every 30 seconds, the list finally refreshes and NM
> connects to my campus network.  This doesn't seem very user-friendly
> to me.
>
>
> On 10/11/07, Dan Williams <[EMAIL PROTECTED]> wrote:
>> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
>>> Ok, but it is just a pain in the *ss this bug, and everybody  
>>> complains.
>>>
>>> Please, rather than saying "I disagree", maybe propose an  
>>> alternative,
>>> because it is really annoying bug.
>>
>> We already discussed alternatives on this list.  First, NM should  
>> scan
>> quite quickly after dropping the menu down, as long as NM has not
>> scanned within the last 20 seconds.  Currently that may not be the  
>> case,
>> it might push off the scan for 20 seconds.  This is a case of a  
>> bug that
>> should be fixed (if it exists).
>>
>> Furthermore, I don't believe that it's that much of a burden to check
>> the menu twice.  Can you refresh my memory as to what situations
>> explicitly scanning for networks is necessary?  The applet should be
>> kept simple, additional functionality that doesn't fit in the  
>> applet can
>> certainly be farmed out to other tools that are not the applet or NM.
>> The applet should cover 90% of all users needs 90% of the time.  It
>> should _not_ cover 100% of all users needs 100% of the time.   
>> There are
>> some features that just won't be implemented.  I believe  
>> explicitly scan
>> requests fit in that last 10%.  I may be able to be convinced  
>> otherwise.
>>
>> Dan
>>
>>> Thanks in advance
>>>
>>> Dan Williams wrote:
 On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:

> I know this has been posted and discussed already, but this bug  
> is *so*
> annoying, that I guess I am not the only "simple user" having  
> troubles
> with that.
>
> Would it be possible to fix it ?
>

 I still don't agree that this is the right way to solve the issue.

 Dan


> Thanks a lot
>
> JM
>
> Joan B. Moreau wrote:
>
>> Hi all,
>>
>> I like the applet but here my request in terms of ergonomy:
>>
>> Would it be possible to stop triggering a scan when clicking  
>> on the
>> applet (which people do quite frequently to see the available  
>> networks)
>> but rather put a menu item "scan for available networks" that  
>> we can
>> click when one decide so  ?
>>
>> Thanks
>>
>> Joan
>>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>


>>
>> ___
>> NetworkManager-list mailing list
>> NetworkManager-list@gnome.org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>>
>
>
> -- 
> Joel Goguen
> http://jgoguen.net/
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joel Goguen
I have a need for it, and I imagine it's a common one.  I have a
wireless network at home, and I put the laptop to sleep and head to my
university.  When I get there, I have to wait sometimes minutes for
the list to refresh and my campus network to appear so NM can attempt
to connect to it.  Or I can open a terminal and manually restart NM,
but that's not something a common user should be expected to do IMO.
When I first get to campus I still see all the networks I can see from
my house, even though none of them are anywhere near the campus.
After a few minutes of waiting, during which I'm checking the applet
list at least once every 30 seconds, the list finally refreshes and NM
connects to my campus network.  This doesn't seem very user-friendly
to me.


On 10/11/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> > Ok, but it is just a pain in the *ss this bug, and everybody complains.
> >
> > Please, rather than saying "I disagree", maybe propose an alternative,
> > because it is really annoying bug.
>
> We already discussed alternatives on this list.  First, NM should scan
> quite quickly after dropping the menu down, as long as NM has not
> scanned within the last 20 seconds.  Currently that may not be the case,
> it might push off the scan for 20 seconds.  This is a case of a bug that
> should be fixed (if it exists).
>
> Furthermore, I don't believe that it's that much of a burden to check
> the menu twice.  Can you refresh my memory as to what situations
> explicitly scanning for networks is necessary?  The applet should be
> kept simple, additional functionality that doesn't fit in the applet can
> certainly be farmed out to other tools that are not the applet or NM.
> The applet should cover 90% of all users needs 90% of the time.  It
> should _not_ cover 100% of all users needs 100% of the time.  There are
> some features that just won't be implemented.  I believe explicitly scan
> requests fit in that last 10%.  I may be able to be convinced otherwise.
>
> Dan
>
> > Thanks in advance
> >
> > Dan Williams wrote:
> > > On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:
> > >
> > >> I know this has been posted and discussed already, but this bug is *so*
> > >> annoying, that I guess I am not the only "simple user" having troubles
> > >> with that.
> > >>
> > >> Would it be possible to fix it ?
> > >>
> > >
> > > I still don't agree that this is the right way to solve the issue.
> > >
> > > Dan
> > >
> > >
> > >> Thanks a lot
> > >>
> > >> JM
> > >>
> > >> Joan B. Moreau wrote:
> > >>
> > >>> Hi all,
> > >>>
> > >>> I like the applet but here my request in terms of ergonomy:
> > >>>
> > >>> Would it be possible to stop triggering a scan when clicking on the
> > >>> applet (which people do quite frequently to see the available networks)
> > >>> but rather put a menu item "scan for available networks" that we can
> > >>> click when one decide so  ?
> > >>>
> > >>> Thanks
> > >>>
> > >>> Joan
> > >>>
> > >> ___
> > >> NetworkManager-list mailing list
> > >> NetworkManager-list@gnome.org
> > >> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > >>
> > >
> > >
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>


-- 
Joel Goguen
http://jgoguen.net/
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Dan Williams
On Thu, 2007-10-11 at 18:08 +0300, Joan B. Moreau wrote:
> Ok, but it is just a pain in the *ss this bug, and everybody complains.
> 
> Please, rather than saying "I disagree", maybe propose an alternative, 
> because it is really annoying bug.

We already discussed alternatives on this list.  First, NM should scan
quite quickly after dropping the menu down, as long as NM has not
scanned within the last 20 seconds.  Currently that may not be the case,
it might push off the scan for 20 seconds.  This is a case of a bug that
should be fixed (if it exists).

Furthermore, I don't believe that it's that much of a burden to check
the menu twice.  Can you refresh my memory as to what situations
explicitly scanning for networks is necessary?  The applet should be
kept simple, additional functionality that doesn't fit in the applet can
certainly be farmed out to other tools that are not the applet or NM.
The applet should cover 90% of all users needs 90% of the time.  It
should _not_ cover 100% of all users needs 100% of the time.  There are
some features that just won't be implemented.  I believe explicitly scan
requests fit in that last 10%.  I may be able to be convinced otherwise.

Dan

> Thanks in advance
> 
> Dan Williams wrote:
> > On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:
> >   
> >> I know this has been posted and discussed already, but this bug is *so* 
> >> annoying, that I guess I am not the only "simple user" having troubles 
> >> with that.
> >>
> >> Would it be possible to fix it ?
> >> 
> >
> > I still don't agree that this is the right way to solve the issue.
> >
> > Dan
> >
> >   
> >> Thanks a lot
> >>
> >> JM
> >>
> >> Joan B. Moreau wrote:
> >> 
> >>> Hi all,
> >>>
> >>> I like the applet but here my request in terms of ergonomy:
> >>>
> >>> Would it be possible to stop triggering a scan when clicking on the
> >>> applet (which people do quite frequently to see the available networks)
> >>> but rather put a menu item "scan for available networks" that we can
> >>> click when one decide so  ?
> >>>
> >>> Thanks
> >>>
> >>> Joan
> >>>   
> >> ___
> >> NetworkManager-list mailing list
> >> NetworkManager-list@gnome.org
> >> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >> 
> >
> >   

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joan B. Moreau

Ok, but it is just a pain in the *ss this bug, and everybody complains.

Please, rather than saying "I disagree", maybe propose an alternative, 
because it is really annoying bug.

Thanks in advance

Dan Williams wrote:
> On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:
>   
>> I know this has been posted and discussed already, but this bug is *so* 
>> annoying, that I guess I am not the only "simple user" having troubles 
>> with that.
>>
>> Would it be possible to fix it ?
>> 
>
> I still don't agree that this is the right way to solve the issue.
>
> Dan
>
>   
>> Thanks a lot
>>
>> JM
>>
>> Joan B. Moreau wrote:
>> 
>>> Hi all,
>>>
>>> I like the applet but here my request in terms of ergonomy:
>>>
>>> Would it be possible to stop triggering a scan when clicking on the
>>> applet (which people do quite frequently to see the available networks)
>>> but rather put a menu item "scan for available networks" that we can
>>> click when one decide so  ?
>>>
>>> Thanks
>>>
>>> Joan
>>>   
>> ___
>> NetworkManager-list mailing list
>> NetworkManager-list@gnome.org
>> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>> 
>
>   
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Dan Williams
On Thu, 2007-10-11 at 17:20 +0300, Joan B. Moreau wrote:
> I know this has been posted and discussed already, but this bug is *so* 
> annoying, that I guess I am not the only "simple user" having troubles 
> with that.
> 
> Would it be possible to fix it ?

I still don't agree that this is the right way to solve the issue.

Dan

> Thanks a lot
> 
> JM
> 
> Joan B. Moreau wrote:
> > Hi all,
> >
> > I like the applet but here my request in terms of ergonomy:
> >
> > Would it be possible to stop triggering a scan when clicking on the
> > applet (which people do quite frequently to see the available networks)
> > but rather put a menu item "scan for available networks" that we can
> > click when one decide so  ?
> >
> > Thanks
> >
> > Joan
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-10-11 Thread Joan B. Moreau

I know this has been posted and discussed already, but this bug is *so* 
annoying, that I guess I am not the only "simple user" having troubles 
with that.

Would it be possible to fix it ?

Thanks a lot

JM

Joan B. Moreau wrote:
> Hi all,
>
> I like the applet but here my request in terms of ergonomy:
>
> Would it be possible to stop triggering a scan when clicking on the
> applet (which people do quite frequently to see the available networks)
> but rather put a menu item "scan for available networks" that we can
> click when one decide so  ?
>
> Thanks
>
> Joan
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-20 Thread Joan B. Moreau

Thanks but the long discussion did not get any conclusion.

When  would it be possible to stop the weird behavior of launching a
scan on the clic on the applet, and implement just a simple menu item to
launch a scan ?

Thanks

joan

Darren Albers wrote:
>
> Joan, this thread has a long discussion that subject that may answer
> your question:
> http://thread.gmane.org/gmane.linux.network.networkmanager.devel/6270/focus=6274
>
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-20 Thread Darren Albers
On 5/19/07, Joan B. Moreau <[EMAIL PROTECTED]> wrote:
> hello,
>
> If we have to go into the console to delete some configuration file, the
> whole point of the applet is over (confort for the users, otherwise,
> iwconfig works always ;-)
>
> What is the decision about the "menu item"  to scan for new networks
> rather than triggering the scan when the user click on the applet ?
>
> THanks
>
> Joan

Joan, this thread has a long discussion that subject that may answer
your question:
http://thread.gmane.org/gmane.linux.network.networkmanager.devel/6270/focus=6274
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-19 Thread Joan B. Moreau
hello,

If we have to go into the console to delete some configuration file, the
whole point of the applet is over (confort for the users, otherwise,
iwconfig works always ;-)

What is the decision about the "menu item"  to scan for new networks
rather than triggering the scan when the user click on the applet ?

THanks

Joan

Michael Trunner wrote:
> Am Mittwoch, den 02.05.2007, 17:39 -0400 schrieb Dan Williams:
>   
>> On Wed, 2007-05-02 at 23:00 +0200, Michael Trunner wrote:
>> 
>>> Hi,
>>>
>>> I had a very similar idea. If I have choose a network it shouldn't
>>> switch to another when the my goes off. Because everyday when my own
>>> network is to faraway nm switch to the network of my neighbour. In this
>>> case nm shouldn't  search for other networks. I think a checkbox "search
>>> for networks" would be nice.
>>>   
>> If you don't want to associate with your neighbors network, remove it
>> from GConf.  You connected to it once upon a time, which is why NM is
>> trying now.  Granted, there should be a nice way to remove cached
>> networks, but having a checkbox for scanning is not the solution.
>>
>> 
>
> Hmm okay, but I have a similar problem on my University. There is one
> for the complete campus (VPN) and one for special buildings with eap
> which I prefer. But sometimes it switch like at home. Deleting the gconf
> entry is okay for the problem with my neighbours. But not for my problem
> one the university, because when I leave the building (so there is no
> eap conncetion) then I'm using the campus WLAN and the gconf entry is
> back.
> Maybe some one have a good idea for this problem.
>
> Michael
>
>
>
>   
>> Dan
>>
>> 
>>> Bye
>>>
>>> Michael
>>>
>>> Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau:
>>>   
 The point is not to do it by oneself or by the pc, but one may click 
 several time on the icon to see the status of the discovery which 
 trigger a new search and that does not end , while having to click once 
 on a button let people be able to see the current list of network 
 without "risking" to trigger a new search.


 Christopher Aillon wrote:
 
> Greg Oliver wrote:
>   
>   
>> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
>> 
>> 
>>> Could one of you perhaps explain to me why you want to do something
>>> manually that network-manager does for you automatically? I don't quite
>>> get it.
>>>   
>>>   
>> Honestly, so my LED does not blink repeatedly
>> 
>> 
> You'll have others blinking anyway.  Hard disk, etc.
>
>   
>   
>> - as well as go back to a
>> previous request to have wired/wireless active simultaneously (I know
>> thats coming).  In that situation, that would be most pleasant.  My
>> radio would not be scanning constantly when I do not need it and I could
>> scan when I want them both on.
>> 
>> 
> And if your wired ever dies out?  Or if you need to move for some reason 
> and need to unplug?  Do you want NetworkManager to just sit there for 
> you to realize what happened, then click the applet, then click perform 
> scan, wait for a few seconds, figure out which Network, and then connect 
> you to wireless?
>
> Personally, I'd rather my music stream keep on playing.  The whole point 
> of NetworkManager is to do the work for you.  People that don't want it 
> to do the work still have iwconfig/iwlist.
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>   
>   
 ___
 NetworkManager-list mailing list
 NetworkManager-list@gnome.org
 http://mail.gnome.org/mailman/listinfo/networkmanager-list

 
>> 
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-03 Thread Michael Trunner
Am Mittwoch, den 02.05.2007, 17:39 -0400 schrieb Dan Williams:
> On Wed, 2007-05-02 at 23:00 +0200, Michael Trunner wrote:
> > Hi,
> > 
> > I had a very similar idea. If I have choose a network it shouldn't
> > switch to another when the my goes off. Because everyday when my own
> > network is to faraway nm switch to the network of my neighbour. In this
> > case nm shouldn't  search for other networks. I think a checkbox "search
> > for networks" would be nice.
> 
> If you don't want to associate with your neighbors network, remove it
> from GConf.  You connected to it once upon a time, which is why NM is
> trying now.  Granted, there should be a nice way to remove cached
> networks, but having a checkbox for scanning is not the solution.
> 

Hmm okay, but I have a similar problem on my University. There is one
for the complete campus (VPN) and one for special buildings with eap
which I prefer. But sometimes it switch like at home. Deleting the gconf
entry is okay for the problem with my neighbours. But not for my problem
one the university, because when I leave the building (so there is no
eap conncetion) then I'm using the campus WLAN and the gconf entry is
back.
Maybe some one have a good idea for this problem.

Michael



> Dan
> 
> > Bye
> > 
> > Michael
> > 
> > Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau:
> > > The point is not to do it by oneself or by the pc, but one may click 
> > > several time on the icon to see the status of the discovery which 
> > > trigger a new search and that does not end , while having to click once 
> > > on a button let people be able to see the current list of network 
> > > without "risking" to trigger a new search.
> > > 
> > > 
> > > Christopher Aillon wrote:
> > > > Greg Oliver wrote:
> > > >   
> > > >> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
> > > >> 
> > > >>> Could one of you perhaps explain to me why you want to do something
> > > >>> manually that network-manager does for you automatically? I don't 
> > > >>> quite
> > > >>> get it.
> > > >>>   
> > > >> Honestly, so my LED does not blink repeatedly
> > > >> 
> > > >
> > > > You'll have others blinking anyway.  Hard disk, etc.
> > > >
> > > >   
> > > >> - as well as go back to a
> > > >> previous request to have wired/wireless active simultaneously (I know
> > > >> thats coming).  In that situation, that would be most pleasant.  My
> > > >> radio would not be scanning constantly when I do not need it and I 
> > > >> could
> > > >> scan when I want them both on.
> > > >> 
> > > >
> > > > And if your wired ever dies out?  Or if you need to move for some 
> > > > reason 
> > > > and need to unplug?  Do you want NetworkManager to just sit there for 
> > > > you to realize what happened, then click the applet, then click perform 
> > > > scan, wait for a few seconds, figure out which Network, and then 
> > > > connect 
> > > > you to wireless?
> > > >
> > > > Personally, I'd rather my music stream keep on playing.  The whole 
> > > > point 
> > > > of NetworkManager is to do the work for you.  People that don't want it 
> > > > to do the work still have iwconfig/iwlist.
> > > >
> > > > ___
> > > > NetworkManager-list mailing list
> > > > NetworkManager-list@gnome.org
> > > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > >   
> > > ___
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > > 
> 
> 
-- 
Wenn das eigene Wohlbefinden von der vereinigten Dummheit fast aller
Anderer geprägt ist, lebt man meistens in einer Demokratie.

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Dan Williams
On Wed, 2007-05-02 at 23:00 +0200, Michael Trunner wrote:
> Hi,
> 
> I had a very similar idea. If I have choose a network it shouldn't
> switch to another when the my goes off. Because everyday when my own
> network is to faraway nm switch to the network of my neighbour. In this
> case nm shouldn't  search for other networks. I think a checkbox "search
> for networks" would be nice.

If you don't want to associate with your neighbors network, remove it
from GConf.  You connected to it once upon a time, which is why NM is
trying now.  Granted, there should be a nice way to remove cached
networks, but having a checkbox for scanning is not the solution.

Dan

> Bye
> 
> Michael
> 
> Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau:
> > The point is not to do it by oneself or by the pc, but one may click 
> > several time on the icon to see the status of the discovery which 
> > trigger a new search and that does not end , while having to click once 
> > on a button let people be able to see the current list of network 
> > without "risking" to trigger a new search.
> > 
> > 
> > Christopher Aillon wrote:
> > > Greg Oliver wrote:
> > >   
> > >> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
> > >> 
> > >>> Could one of you perhaps explain to me why you want to do something
> > >>> manually that network-manager does for you automatically? I don't quite
> > >>> get it.
> > >>>   
> > >> Honestly, so my LED does not blink repeatedly
> > >> 
> > >
> > > You'll have others blinking anyway.  Hard disk, etc.
> > >
> > >   
> > >> - as well as go back to a
> > >> previous request to have wired/wireless active simultaneously (I know
> > >> thats coming).  In that situation, that would be most pleasant.  My
> > >> radio would not be scanning constantly when I do not need it and I could
> > >> scan when I want them both on.
> > >> 
> > >
> > > And if your wired ever dies out?  Or if you need to move for some reason 
> > > and need to unplug?  Do you want NetworkManager to just sit there for 
> > > you to realize what happened, then click the applet, then click perform 
> > > scan, wait for a few seconds, figure out which Network, and then connect 
> > > you to wireless?
> > >
> > > Personally, I'd rather my music stream keep on playing.  The whole point 
> > > of NetworkManager is to do the work for you.  People that don't want it 
> > > to do the work still have iwconfig/iwlist.
> > >
> > > ___
> > > NetworkManager-list mailing list
> > > NetworkManager-list@gnome.org
> > > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > >   
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> > 

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Michael Trunner
Hi,

I had a very similar idea. If I have choose a network it shouldn't
switch to another when the my goes off. Because everyday when my own
network is to faraway nm switch to the network of my neighbour. In this
case nm shouldn't  search for other networks. I think a checkbox "search
for networks" would be nice.

Bye

Michael

Am Mittwoch, den 02.05.2007, 19:12 +0300 schrieb Joan Moreau:
> The point is not to do it by oneself or by the pc, but one may click 
> several time on the icon to see the status of the discovery which 
> trigger a new search and that does not end , while having to click once 
> on a button let people be able to see the current list of network 
> without "risking" to trigger a new search.
> 
> 
> Christopher Aillon wrote:
> > Greg Oliver wrote:
> >   
> >> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
> >> 
> >>> Could one of you perhaps explain to me why you want to do something
> >>> manually that network-manager does for you automatically? I don't quite
> >>> get it.
> >>>   
> >> Honestly, so my LED does not blink repeatedly
> >> 
> >
> > You'll have others blinking anyway.  Hard disk, etc.
> >
> >   
> >> - as well as go back to a
> >> previous request to have wired/wireless active simultaneously (I know
> >> thats coming).  In that situation, that would be most pleasant.  My
> >> radio would not be scanning constantly when I do not need it and I could
> >> scan when I want them both on.
> >> 
> >
> > And if your wired ever dies out?  Or if you need to move for some reason 
> > and need to unplug?  Do you want NetworkManager to just sit there for 
> > you to realize what happened, then click the applet, then click perform 
> > scan, wait for a few seconds, figure out which Network, and then connect 
> > you to wireless?
> >
> > Personally, I'd rather my music stream keep on playing.  The whole point 
> > of NetworkManager is to do the work for you.  People that don't want it 
> > to do the work still have iwconfig/iwlist.
> >
> > ___
> > NetworkManager-list mailing list
> > NetworkManager-list@gnome.org
> > http://mail.gnome.org/mailman/listinfo/networkmanager-list
> >   
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
> 
-- 
Wenn das eigene Wohlbefinden von der vereinigten Dummheit fast aller
Anderer geprägt ist, lebt man meistens in einer Demokratie.

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Joan Moreau

The point is not to do it by oneself or by the pc, but one may click 
several time on the icon to see the status of the discovery which 
trigger a new search and that does not end , while having to click once 
on a button let people be able to see the current list of network 
without "risking" to trigger a new search.


Christopher Aillon wrote:
> Greg Oliver wrote:
>   
>> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
>> 
>>> Could one of you perhaps explain to me why you want to do something
>>> manually that network-manager does for you automatically? I don't quite
>>> get it.
>>>   
>> Honestly, so my LED does not blink repeatedly
>> 
>
> You'll have others blinking anyway.  Hard disk, etc.
>
>   
>> - as well as go back to a
>> previous request to have wired/wireless active simultaneously (I know
>> thats coming).  In that situation, that would be most pleasant.  My
>> radio would not be scanning constantly when I do not need it and I could
>> scan when I want them both on.
>> 
>
> And if your wired ever dies out?  Or if you need to move for some reason 
> and need to unplug?  Do you want NetworkManager to just sit there for 
> you to realize what happened, then click the applet, then click perform 
> scan, wait for a few seconds, figure out which Network, and then connect 
> you to wireless?
>
> Personally, I'd rather my music stream keep on playing.  The whole point 
> of NetworkManager is to do the work for you.  People that don't want it 
> to do the work still have iwconfig/iwlist.
>
> ___
> NetworkManager-list mailing list
> NetworkManager-list@gnome.org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list
>   
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Christopher Aillon
Greg Oliver wrote:
> On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
>> Could one of you perhaps explain to me why you want to do something
>> manually that network-manager does for you automatically? I don't quite
>> get it.
> 
> Honestly, so my LED does not blink repeatedly

You'll have others blinking anyway.  Hard disk, etc.

> - as well as go back to a
> previous request to have wired/wireless active simultaneously (I know
> thats coming).  In that situation, that would be most pleasant.  My
> radio would not be scanning constantly when I do not need it and I could
> scan when I want them both on.

And if your wired ever dies out?  Or if you need to move for some reason 
and need to unplug?  Do you want NetworkManager to just sit there for 
you to realize what happened, then click the applet, then click perform 
scan, wait for a few seconds, figure out which Network, and then connect 
you to wireless?

Personally, I'd rather my music stream keep on playing.  The whole point 
of NetworkManager is to do the work for you.  People that don't want it 
to do the work still have iwconfig/iwlist.

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Christopher Aillon
Joan B. Moreau wrote:
> Hi all,
> 
> I like the applet but here my request in terms of ergonomy:
> 
> Would it be possible to stop triggering a scan when clicking on the
> applet (which people do quite frequently to see the available networks)

How do we know what the available networks are if we don't perform 
automatic scans?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Greg Oliver
On Wed, 2007-05-02 at 09:08 +0200, Soren Hansen wrote:
> On Wed, May 02, 2007 at 02:02:12AM -0500, Greg Oliver wrote:
> > > I like the applet but here my request in terms of ergonomy:
> > > 
> > > Would it be possible to stop triggering a scan when clicking on the
> > > applet (which people do quite frequently to see the available networks)
> > > but rather put a menu item "scan for available networks" that we can
> > > click when one decide so  ?
> > I second this!  I also see that it is a very fast moving piece of
> > software, so I expect it will be there one day and can wait.  I am
> > usually wired for the speed, but would be nice on occasion when I must
> > go wireless.
> 
> Could one of you perhaps explain to me why you want to do something
> manually that network-manager does for you automatically? I don't quite
> get it.

Honestly, so my LED does not blink repeatedly - as well as go back to a
previous request to have wired/wireless active simultaneously (I know
thats coming).  In that situation, that would be most pleasant.  My
radio would not be scanning constantly when I do not need it and I could
scan when I want them both on.

-Greg

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Soren Hansen
On Wed, May 02, 2007 at 02:02:12AM -0500, Greg Oliver wrote:
> > I like the applet but here my request in terms of ergonomy:
> > 
> > Would it be possible to stop triggering a scan when clicking on the
> > applet (which people do quite frequently to see the available networks)
> > but rather put a menu item "scan for available networks" that we can
> > click when one decide so  ?
> I second this!  I also see that it is a very fast moving piece of
> software, so I expect it will be there one day and can wait.  I am
> usually wired for the speed, but would be nice on occasion when I must
> go wireless.

Could one of you perhaps explain to me why you want to do something
manually that network-manager does for you automatically? I don't quite
get it.

-- 
Mange hilsner, Søren Hansen.


signature.asc
Description: Digital signature
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Request for ergonomy feature

2007-05-02 Thread Greg Oliver
On Wed, 2007-05-02 at 08:58 +0300, Joan B. Moreau wrote:
> Hi all,
> 
> I like the applet but here my request in terms of ergonomy:
> 
> Would it be possible to stop triggering a scan when clicking on the
> applet (which people do quite frequently to see the available networks)
> but rather put a menu item "scan for available networks" that we can
> click when one decide so  ?
> 
> Thanks
> 
> Joan

I second this!  I also see that it is a very fast moving piece of
software, so I expect it will be there one day and can wait.  I am
usually wired for the speed, but would be nice on occasion when I must
go wireless.

-Greg

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Request for ergonomy feature

2007-05-01 Thread Joan B. Moreau

Hi all,

I like the applet but here my request in terms of ergonomy:

Would it be possible to stop triggering a scan when clicking on the
applet (which people do quite frequently to see the available networks)
but rather put a menu item "scan for available networks" that we can
click when one decide so  ?

Thanks

Joan
>   

___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list


Request for ergonomy feature

2007-04-07 Thread Joan Moreau

Hi all,

I like the appletbut here my request in terms of ergonomy:

Would it be possible to stop triggering a scan when clicking on the 
applet (which people do quite frequently to see the available networks)
but rather put a menu item "scan for available networks" that we can 
click when one decide so  ?

Thanks

Joan
>   
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list