On Mon, 2007-08-20 at 17:41 -0400, Yaakov Nemoy wrote:
> Here's the patch.
>
> It's really Robert Frank's patch. He told me where to put the code.
> It's untested, and doesn't work in as a distro agnostic method as it
> should.
>
> On 8/20/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> > Does HAL
method as it
> > should.
> >
>
> Why do you need it at all? dhclient (from the dhcp3-client package)
> reads /etc/dhcp3/dhclient.conf by default.
>
> I'm running latest 0.7 svn on Debian sid without such a patch, and dhcp
> works just fine.
0.64 doesn't, so i ass
the dhcp3-client package)
reads /etc/dhcp3/dhclient.conf by default.
I'm running latest 0.7 svn on Debian sid without such a patch, and dhcp
works just fine.
Cheers,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
sign
Here's the patch.
It's really Robert Frank's patch. He told me where to put the code.
It's untested, and doesn't work in as a distro agnostic method as it
should.
On 8/20/07, Dan Williams <[EMAIL PROTECTED]> wrote:
> Does HAL show the devices in 'lshal'? Feel free to post the patch for
> dhclie
On Sat, 2007-08-18 at 02:33 -0400, Yaakov Nemoy wrote:
> Hi List,
>
> I just tried compiling the latest SVN on debian lenny. I made a 3 line
> change to have it honour /etc/dhcp3/dhclient.conf (the location may
> vary per distro). It compiles and installs cleanly. I'm u
Hi List,
I just tried compiling the latest SVN on debian lenny. I made a 3 line
change to have it honour /etc/dhcp3/dhclient.conf (the location may
vary per distro). It compiles and installs cleanly. I'm using the
following hardware (from lspci):
02:00.0 Ethernet controller: Marvell Techn
On Monday 04 June 2007 16:36:30 Dan Williams wrote:
> If you'd like something to start on in the mean time, it would be great
> to get the rfkill support in HAL 0.5.9 and later hooked in NM 0.6.x.
>
> ...
>
> Sound like something you'd like to work on?
Sure, I'll get on it.
-- Ben
pgpxGk3KQOf
On Mon, 2007-06-04 at 14:23 -0400, Benjamin Kreuter wrote:
> Hi everyone --
>
> I have been having some trouble getting the latest development snapshot of NM
> to work. It looks like there have been some changes to the DBUS interface,
> so that only the newest GNOME applet will work, but this a
Hi everyone --
I have been having some trouble getting the latest development snapshot of NM
to work. It looks like there have been some changes to the DBUS interface,
so that only the newest GNOME applet will work, but this applet is broken.
Are there any other applets or methods of using NM
On 3/28/07, Simon Geard <[EMAIL PROTECTED]> wrote:
Ok, I don't think this is the problem I saw last time, but the current
failure is that in real_write_supplicant_config(), the call to
nm_ap_security_get_key() is returning NULL, causing a segmentation fault
on the call to strlen() on line 162.
On Wed, 2007-03-28 at 19:54 +1200, Simon Geard wrote:
> On Tue, 2007-03-27 at 14:49 +0300, Tambet Ingo wrote:
> > Can you debug it and see why and where it aborts? It's been working
> > fine for me and Dan for the whole time so it's not going to get
> > magically fixed unless we know what's going o
't test it and stay online at the same time).
> The current SVN trunk should mostly work, except manual activation of
> wireless devices from nm-applet. If there's info about preferred
> networks in GConf NM will activate it successfully. VPN also works
> now. It's stil
On 3/27/07, Simon Geard <[EMAIL PROTECTED]> wrote:
Ok, is there any prospect that SVN head might be functional any time
soon? Every now and then I try building it, but at best it aborts after
start,
Can you debug it and see why and where it aborts? It's been working fine for
me
On Tue, 2007-02-20 at 06:29 -0500, Dan Williams wrote:
> On Tue, 2007-02-20 at 20:45 +1300, Simon Geard wrote:
> > On Mon, 2007-02-19 at 14:54 +0200, Tambet Ingo wrote:
> > > Don't use the SVN head. We know it's completely unstable. We'll
> let you
> >
The problem was that the newest version of automake in Debian
(automake 1.10) somehow gets interpreted as automake 1.7, so the
gnome-autogen.sh script tries to find the 'dirlist' file, which
doesn't exist. Installing automake1.9 did the trick.
--
- Patrick Bogen
__
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
Hello Aaron,
Aaron Konstam wrote:
> Lets try again. CVI => CVS
> And the question is how does one download a src version of NM in order
> to compile it from a SVN database?
From:
http://developer.gnome.org/tools/svn.html
Just type:
svn co http://svn.gnome.org/svn/Ne
On Thu, 2007-03-15 at 08:38 -0500, Aaron Konstam wrote:
> Am I to conclude that the NetwoprkManager source is now stored in a
> Subversion database rather than CVI. How does one download a binary
> version of NetworkManager from the SVN database?
Lets try again. CVI => CVS
And the que
On Thu, 2007-03-15 at 08:38 -0500, Aaron Konstam wrote:
> Am I to conclude that the NetwoprkManager source is now stored in a
> Subversion database rather than CVI. How does one download a binary
> version of NetworkManager from the SVN database?
SVN is source control, there are no binar
Am I to conclude that the NetwoprkManager source is now stored in a
Subversion database rather than CVI. How does one download a binary
version of NetworkManager from the SVN database?
Clearly the CVI should be CVS
--
--
Aaron Konstam <[EMAIL PROTEC
Am I to conclude that the NetwoprkManager source is now stored in a
Subversion database rather than CVI. How does one download a binary
version of NetworkManager from the SVN database?
--
===
Yow! Are we laid back yet
On 3/14/07, Steev Klimaszewski <[EMAIL PROTECTED]> wrote:
> Matthew Shannon wrote:
> > I don't understand how wireless tools could not be installed since I use
> > wireless already. I am trying to get LEAP functionality from
> > NetworkManager SVN. I noticed that
Matthew Shannon wrote:
> I don't understand how wireless tools could not be installed since I use
> wireless already. I am trying to get LEAP functionality from
> NetworkManager SVN. I noticed that there was a configure file so I tried
> it as well, but got basically the
cking for /etc/SuSE-release... no
checking for /etc/fedora-release... no
checking for /etc/gentoo-release... no
checking for /etc/debian_version... yes
checking for /etc/arch-release... no
checking for /etc/slackware-version... no
checking for wireless-tools >= 28pre9... no
configure: error: wire
On Tue, 2007-02-20 at 06:29 -0500, Dan Williams wrote:
> Hopefully days... though I was able to get it to associate with
> unencrypted yesterday OK. It should at least start up, find your
> devices, and if you have an instance of the applet (or another
> info-daemon) running, it should connect if
ding trunk (rev 2337) completely unstable. It takes about 10
> > > seconds to start up, going through the business of reconnecting to the
> > > system bus before aborting with the stacktrace.
> >
> > Don't use the SVN head. We know it's completely unstable. We&#
to start up, going through the business of reconnecting to the
> > system bus before aborting with the stacktrace.
>
> Don't use the SVN head. We know it's completely unstable. We'll let you
> know when it's usable again.
Ok, I'll do that. Do you have
system bus before aborting with the stacktrace.
Don't use the SVN head. We know it's completely unstable. We'll let you
know when it's usable again.
Tambet
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnom
On Tue, 2007-02-06 at 17:03 +1300, Simon Geard wrote:
> I've just grabbed the latest NM code from SVN (revision 2287), finding
> it badly broken for me. It builds fine, but crashes shortly after
> startup, apparently just after retrieving scan results from
> wpa_supplicant.
On Mon, 2007-02-05 at 23:59 -0500, Darren Albers wrote:
> I just looked and rev 2287 is definitely trunk, I would stick with the
> Release branch until Dan mentions that Trunk is ready for testing.
I know it's trunk - I'm trying to make some changes in it (see my
previous emails about non-string S
On Tue, 2007-02-06 at 07:43 -0500, Dan Williams wrote:
> On Tue, 2007-02-06 at 13:46 +0200, Tambet Ingo wrote:
> > Why not use HAL UDI for device names to get at least some sort of
> > human-readable names?
>
> We could provide mapping functions, but this is mostly for the D-Bus
> object paths for
On Tue, 2007-02-06 at 07:43 -0500, Dan Williams wrote:
> We could provide mapping functions, but this is mostly for the D-Bus
> object paths for objects. HAL UDIs have / in them, which are object
> paths. I'm not sure using HAL UDIs as our device object paths instead
> would be clearer, or more c
On Tue, 2007-02-06 at 13:46 +0200, Tambet Ingo wrote:
> On Wed, 2007-01-31 at 10:07 -0500, Dan Williams wrote:
> > Note also that devices themselves are assigned a UID, because if you
> > change 'eth0' to something else on the fly (interface renaming is
> > obviously allowed) then NM shouldn't brea
On Wed, 2007-01-31 at 10:07 -0500, Dan Williams wrote:
> Note also that devices themselves are assigned a UID, because if you
> change 'eth0' to something else on the fly (interface renaming is
> obviously allowed) then NM shouldn't break here either. Having human
> readable names was somewhat mor
On 2/5/07, Darren Albers <[EMAIL PROTECTED]> wrote:
> On 2/5/07, Simon Geard <[EMAIL PROTECTED]> wrote:
> > I've just grabbed the latest NM code from SVN (revision 2287), finding
> > it badly broken for me. It builds fine, but crashes shortly after
> > sta
On 2/5/07, Simon Geard <[EMAIL PROTECTED]> wrote:
> I've just grabbed the latest NM code from SVN (revision 2287), finding
> it badly broken for me. It builds fine, but crashes shortly after
> startup, apparently just after retrieving scan results from
> wpa_supplicant.
I've just grabbed the latest NM code from SVN (revision 2287), finding
it badly broken for me. It builds fine, but crashes shortly after
startup, apparently just after retrieving scan results from
wpa_supplicant.
Anyone else having problems with this? It's a clean snapshot from SVN,
wi
On Mon, 2007-02-05 at 08:16 -0500, Dan Williams wrote:
> nminfotest.c will be talking to the info-daemon, which happens to be
> implemented by applets.
Ok, so in order for nminfotest to run, an up to date copy of the applet
needs to be running?
Simon.
signature.asc
Description: This is a digita
e pairs, one of which will happen to be a bytes array with a key
of 'ssid'.
> Incidentally, what's happening with nm-applet at the moment? I went to
> try fixing the interfaces, but found everything had disappeared,
> apparently into a separate project? Is the network-manag
plet at the moment? I went to
try fixing the interfaces, but found everything had disappeared,
apparently into a separate project? Is the network-manager-applet
project in SVN basically everything that was in gnome/applet previously?
One other question too - what exactly is the program nminfotest
On Thu, 2007-02-01 at 07:51 -0500, Dan Williams wrote:
> On Thu, 2007-02-01 at 21:49 +1300, Simon Geard wrote:
> > And as I think about it, is that a meaningful distinction if we're not
> > going to pretend SSID is a string?
>
> That's exactly the reason. Since we no longer care, orig_essid can g
On Thu, 2007-02-01 at 21:49 +1300, Simon Geard wrote:
> On Thu, 2007-02-01 at 21:44 +1300, Simon Geard wrote:
> > Incidentally, what's the difference between essid and orig_essid in that
> > struct? Is it simply that essid is guaranteed to be in UTF8 and
> > orig_essid might not be?
>
> And as I t
On Thu, 2007-02-01 at 21:44 +1300, Simon Geard wrote:
> Incidentally, what's the difference between essid and orig_essid in that
> struct? Is it simply that essid is guaranteed to be in UTF8 and
> orig_essid might not be?
And as I think about it, is that a meaningful distinction if we're not
going
On Wed, 2007-01-31 at 10:07 -0500, Dan Williams wrote:
> We can change the internal stuff in 0.6, but we cannot change the DBus
> interface.
No problem there - 0.6 works fine for me, since I don't care about it
ignoring the odd access point, as long as it can connect to my own
without crashing.
On Wed, 2007-01-31 at 18:12 +, Andrew Duggan wrote:
> Hi,
>
> I am looking for the 0.6.5 branch in svn that
> Dan Williams mentioned the other day...
>
> "Yeah; 0.6.5 from SVN branch. Could you provide some logs so we can try
> to track it down? Once I get don
Hi,
I am looking for the 0.6.5 branch in svn that
Dan Williams mentioned the other day...
"Yeah; 0.6.5 from SVN branch. Could you provide some logs so we can try
to track it down? Once I get done splitting the applet out, I'll do a
bunch more functional testing against a few APs I
On Wed, 2007-01-31 at 21:23 +1300, Simon Geard wrote:
> On Tue, 2007-01-30 at 12:13 -0500, Dan Williams wrote:
> > Yeah; there are bits of NM that assume a string SSID, and those are
> > going to get removed with 0.7 and the SSID will be a plain byte array.
>
> More than just 'bits' of NM, so far
On Tue, 2007-01-30 at 12:13 -0500, Dan Williams wrote:
> Yeah; there are bits of NM that assume a string SSID, and those are
> going to get removed with 0.7 and the SSID will be a plain byte array.
More than just 'bits' of NM, so far as I can tell - pretty much every
piece of code I've encountered
On Tue, 30 Jan 2007 12:13:09 -0500, Dan Williams wrote:
> A blank SSID of all 0s is perfectly legal; we do need to figure out how
> to deal with this in UI.
My 5 cents:
In the applet drop-down list: substitute dot='.' for non-printable
characters.
When you enter ssid ("Network Name"), allow the
On Tue, 2007-01-30 at 14:37 +, Volker Braun wrote:
> On Tue, 30 Jan 2007 20:14:29 +1300, delgarde wrote:
> > +if (entry.bytearray_value[0] == 0 && ssid_len>0) {
> > + nm_warning("Error: got an access point with an invalid SSID");
>
> The ssid is not a string but a char[ssid_le
On Tue, 2007-01-30 at 20:14 +1300, [EMAIL PROTECTED] wrote:
> Dan Williams wrote:
> > If you can build your own copy of wpa_supplicant, put some
> > debugging prints in driver_wext.c in
> > wpa_driver_wext_get_scan_results() in the 'case
> > SIOCGIWESSID:' block to print out the code flow there.
>
On Tue, 30 Jan 2007 20:14:29 +1300, delgarde wrote:
> +if (entry.bytearray_value[0] == 0 && ssid_len>0) {
> + nm_warning("Error: got an access point with an invalid SSID");
The ssid is not a string but a char[ssid_len]. Control characters and \0
are allowed (although many programs
On Tue, 2007-01-30 at 16:46 +1300, [EMAIL PROTECTED] wrote:
> Dan Williams wrote:
> > If you can build your own copy of wpa_supplicant, put some
> > debugging prints in driver_wext.c in
> > wpa_driver_wext_get_scan_results() in the 'case
> > SIOCGIWESSID:' block to print out the code flow there.
>
Dan Williams wrote:
> If you can build your own copy of wpa_supplicant, put some
> debugging prints in driver_wext.c in
> wpa_driver_wext_get_scan_results() in the 'case
> SIOCGIWESSID:' block to print out the code flow there.
> What's 'ssid_len'? Does the 'if (custom + ssid_len >
> end)' trigger?
Dan Williams wrote:
> If you can build your own copy of wpa_supplicant, put some
> debugging prints in driver_wext.c in
> wpa_driver_wext_get_scan_results() in the 'case
> SIOCGIWESSID:' block to print out the code flow there.
> What's 'ssid_len'? Does the 'if (custom + ssid_len >
> end)' trigger?
On Mon, 2007-01-29 at 17:45 +1300, Simon Geard wrote:
> On Sat, 2007-01-27 at 07:14 -0500, Dan Williams wrote:
> > dbus-send --system --dest=org.freedesktop.NetworkManager \
> > --print-reply /org/freedesktop/NetworkManager/Devices/ath0 \
> > org.freedesktop.NetworkManager.Devices.getProp
On Sat, 2007-01-27 at 07:14 -0500, Dan Williams wrote:
> dbus-send --system --dest=org.freedesktop.NetworkManager \
> --print-reply /org/freedesktop/NetworkManager/Devices/ath0 \
> org.freedesktop.NetworkManager.Devices.getProperties
>
> See if any of the network object paths look funny.
On Tue, 2007-01-23 at 20:55 +1300, Simon Geard wrote:
> Trying to get the current NM code to work on my LFS system, with some
> custom code to support LFS. I've hit a couple of bugs which I've logged
> in Bugzilla.
>
> http://bugzilla.gnome.org/show_bug.cgi?id=394956
>
> http://bugzilla.gnome.org
Trying to get the current NM code to work on my LFS system, with some
custom code to support LFS. I've hit a couple of bugs which I've logged
in Bugzilla.
http://bugzilla.gnome.org/show_bug.cgi?id=394956
http://bugzilla.gnome.org/show_bug.cgi?id=399292
The first, 393956, I've included a patch fo
101 - 160 of 160 matches
Mail list logo
