On 3/19/07, Steev Klimaszewski <[EMAIL PROTECTED]> wrote:
> Patrick Bogen wrote:
> >
> > What am I missing?
> >
> The gnome-common package
>
norsethite:~# dpkg-query -s gnome-common | grep Status
Status: install ok installed
--
- Patrick Bogen
___
Net
I'm trying to build from svn on Debian. I've installed the
gnome-common package, but I still get the error:
Checking for required M4 macros...
gnome-common.m4 not found
gnome-compiler-flags.m4 not found
libtool.m4 not found
glib-gettext.m4 not found
intltool.m4 not found
pkg.m4 not fo
While we're on warts in Network Manager, here's mine. It would be nice if
one could mark certain access points as "preferred" and others as "avoid".
For example, I would rather connect to my secured access point rather than
someone else's unsecured one.
--
David Griffith
[EMAIL PROTECTED]
A: B
>> 1) why can't nm do the scan in the time between the user clicks and the menu
>> is popped?
>
>Because scans take a non-trival amount of time on many cards. You
>simply cannot block the menu being popped down for 3 or 5 seconds while
>a scan is taking place.
If you can't update the list whil
On Mon, 2007-03-19 at 15:58 +, yelo_3 wrote:
> > There are essentially none, except that the 'iwlist scan' obviously
> > starts a scan right away, and blocks waiting on the scan results, while
> > NetworkManager schedules scans at various points in time because it's
> > not a command-line tool
> There are essentially none, except that the 'iwlist scan' obviously
> starts a scan right away, and blocks waiting on the scan results, while
> NetworkManager schedules scans at various points in time because it's
> not a command-line tool that you explicitly invoke from a terminal. But
> the in
On Mon, 2007-03-19 at 14:59 +, yelo_3 wrote:
> > Right, that's a bug. The scan shouldn't get rescheduled a further 20
> > seconds every time the menu is dropped down, it should let the 20s
> > timeout run down first.
> > Dan
>
> In my case the scan is not done, even If I wait for the 20 secon
> Right, that's a bug. The scan shouldn't get rescheduled a further 20
> seconds every time the menu is dropped down, it should let the 20s
> timeout run down first.
> Dan
In my case the scan is not done, even If I wait for the 20 seconds timeout.
Can someone tell me the differences between how
On Mon, 2007-03-19 at 10:27 -0400, Matthew Saltzman wrote:
> On Mon, 19 Mar 2007, Tambet Ingo wrote:
> > [...]
> > There are multiple problems when trying to "fix" this behavior:
> >
> > * Scanning disables all other operations on card so network doesn't work at
> > that time. That's the reason the
On Mon, 2007-03-19 at 14:30 +, [EMAIL PROTECTED] wrote:
> I have found that I can only authenticate with my wireless router if I
> enable SSID broadcast on the router. I would prefer not to. Is there
> something I can tweak in NM instead?
While I would note that SSID hiding is no security at a
On Mon, 2007-03-19 at 14:48 +0200, Tambet Ingo wrote:
> Here's how scanning is scheduled:
>
> When the nm-applet's devices menu is expanded, NetworkManager
> schedules a scan to start in 20 seconds. If the menu is deactivated
> and activated again within that 20 seconds, NM re-schedules the scan
>
On Mon, 2007-03-19 at 00:12 +, yelo_3 wrote:
> It is simpler: Sorry I was not clear. I was not connected, and I was moving
> around to search for the correct AP (there is only one for students)
>
> In this case and in the case that wireless was off, scanning is not fast
> enough
Ok, good.
> Here's how scanning is scheduled:
> When the nm-applet's devices menu is expanded, NetworkManager schedules a
> scan to start in 20 seconds. If the menu is deactivated and activated again
> within that 20 seconds, NM re-schedules the scan after another 20 seconds.
I've tried to do so: boot
I have found that I can only authenticate with my wireless router if I enable
SSID broadcast on the router. I would prefer not to. Is there something I can
tweak in NM instead?
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://ma
On Mon, 19 Mar 2007, Tambet Ingo wrote:
> [...]
> There are multiple problems when trying to "fix" this behavior:
>
> * Scanning disables all other operations on card so network doesn't work at
> that time. That's the reason there is a timeout, that's the reason there
> can't be a "scan now" button
On Sun, 2007-03-18 at 16:14 +0200, Sertaç Ö. Yıldız wrote:
> * [13.Mar.07 10:39 -0400] Dan Williams:
> > Well, if the driver is sending a disassociation event, then clearly the
> > driver cannot proceed with the options it's been given. In the plain
> > wpa_supplicant case that was noted above, ev
Here's how scanning is scheduled:
When the nm-applet's devices menu is expanded, NetworkManager schedules a
scan to start in 20 seconds. If the menu is deactivated and activated again
within that 20 seconds, NM re-schedules the scan after another 20 seconds.
So if you keep clicking on applet with
> Does it cost much just to set a menu (as in all Windows) that reset the
> list of network available and launch a scan immediately ?
The problem is different: Dan was saying that the scan is performed every time
you click on the applet, although I don't really know if it is done! (at least
i
18 matches
Mail list logo
