Unintialized variable.
-Bryan
diff --git a/src/mm-plugin-base.c b/src/mm-plugin-base.c
index 198108c..3b21930 100644
--- a/src/mm-plugin-base.c
+++ b/src/mm-plugin-base.c
@@ -666,7 +666,7 @@ get_driver_name (GUdevDevice *device)
{
GUdevDevice *parent = NULL;
const char *driver;
-cha
$ ./configure && make
...
libtool: link: gcc -Wall -Werror -std=gnu89 -g -O2 -Wshadow
-Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement
-Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -fno-strict-aliasing
-o .libs/test-settings-defaults
test_settings_defaults-test-sett
ot; of GUI's which has brought
> > some people to actually enjoy dentist visits.(obscure analogy)
> >
> > If someone was to implement a *real* CLI, I believe it would have to use
> the
> > same guts as the GUI or else it would be a QA nightmare. Anyone who read
&
n 25, 2009 at 2:26 PM, Bryan Duff wrote:
> > Is there anyone going forward with this?
> >
> > It would be useful for non-X or non-KDE/GNOME setups. And if people do
> > think it's worth doing (I do) then what is the best path?
> >
> > 1) Split nm-applet
Is there anyone going forward with this?
It would be useful for non-X or non-KDE/GNOME setups. And if people do
think it's worth doing (I do) then what is the best path?
1) Split nm-applet into nm-client-lib (backend - with dbus calls) and gnome
based nm-applet, then create an nm-cli.
- I like
It still happened to me. I seleted my access point, then at some point it
re-polled and select the unencrypted one (that was first on the list of
available access points). This is after I deleted the unencrypted (and
unwanted) connection from "Edit Connections->Wireless".
-Bryan
On Wed, Apr 29,
My situation is that I have a number of accessible access points for me.
I'll connect to the AP I want, but at some interval NetworkManager re-scans
available AP's and picks an unencrypted AP (that I don't want). So I have
to then, via nm-applet, reselect the AP I want to use.
This is so irritat
