Re: How to use the keyfile plugin?
On Wed, 2008-12-17 at 22:02 +0100, Marcin 'Qrczak' Kowalczyk wrote: > 2008/12/17 Robert Piasek : > > > Did you add grant your user permission to manage system-wide settings? > > Yes. > and do you have the file /etc/NetworkManager/nm-system-settings.conf with the content > [main] > plugins=keyfile ? 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: New icons for nm-applet
On Tue, 2008-10-28 at 17:55 +, Karl Lattimer wrote: > On Tue, 2008-10-28 at 18:47 +0100, Björn Martensen wrote: > > On Tue, 2008-10-28 at 17:22 +, Karl Lattimer wrote: > > > On Tue, 2008-10-28 at 17:11 +, Karl Lattimer wrote: > > > > On Tue, 2008-10-28 at 12:50 -0400, Dan Williams wrote: > > > > > On Tue, 2008-10-28 at 16:11 +, Karl Lattimer wrote: > > > > > > On Tue, 2008-10-28 at 16:07 +, Karl Lattimer wrote: > > > > > > > > > > So match the size of the nm-vpn-connecting-* set to the > > > > > > > > > > same overall > > > > > > > > > > size as the applet icon area, but just offset the vpn lock > > > > > > > > > > itself so > > > > > > > > > > it's positioned in the lower-right corner. The progress > > > > > > > > > > twirlie can > > > > > > > > > > probably stay where it is. > > > > > > > > > > > > > > > > > > > > Existing connection with VPN active: > > > > > > > > > > http://bigw.org/~dan/Screenshot.png > > > > > > > > > > > > > > > > > > Now I get what you mean... Let me ponder this, I'll get back > > > > > > > > > to you as > > > > > > > > > soon as I can see a good solution. > > > > > > > > > > > > > > > > Great, hope it's soon :) I'd think just moving the padlock > > > > > > > > down and to > > > > > > > > the right in the existing images would be just fine. > > > > > > > > > > > > > > Probably, but I'd rather do some sketches of some other ideas, I > > > > > > > mean > > > > > > > it's only one image which is used as an overlay, so that one > > > > > > > could be > > > > > > > fixed easily, but I'm thinking now in terms of the progress meter > > > > > > > for > > > > > > > vpn. > > > > > > > > > > > > > > Maybe if we are moving the padlock down, then I could use icons > > > > > > > which > > > > > > > are similar to the standard connecting animation but instead of a > > > > > > > dot a > > > > > > > keyhole or something instead. > > > > > > > > > > > > > > I'm mulling it, there's some space for flexibility. > > > > > > > > > > > > > > Hopefully i can knock up some updated icons today, and while i'm > > > > > > > at it > > > > > > > classify them into sizes for 16,22 and 24 > > > > > > > > > > > > Actually as the padlock is composited we could probably benefit from > > > > > > compositing the icons for gsm/gprs, edge, umts, hsdpa and anything > > > > > > else > > > > > > that comes along, maybe the recently submitted patch should be > > > > > > updated > > > > > > to work in these terms? > > > > > > > > > > Yes, that's what I replied to it with. The code has "layers", and > > > > > there > > > > > are currently two layers: device and VPN. We can certainly add a > > > > > mobile > > > > > broadband layer in which the mobile broadband badge goes. Just need > > > > > to > > > > > figure out where in the icon area that should go so it doesn't > > > > > conflict > > > > > with the VPN lock. Because you certainly can have an active VPN over > > > > > cellular. > > > > > > > > Urgh, now we're starting to have problems... Colours are obviously going > > > > to be better as long as there is detailed explanation somewhere of what > > > > they mean. Mockups attached for discussion. > > > > > > > > vpn-umts.svg - My first impression of this is that it's starting to get > > > > crowded, and I can make the padlock smaller but loose detail which I > > > > feel is critical. > > > > > > > > vpn-umts2.svg - Slightly less crowded and more appealing I feel, only > > > > 3px tall to denote the technology, so we'll have to use vibrant colours > > > > which aren't in the tango palette :/ > > > > > > Thinking in these terms now, and maybe the signal strength bars can be > > > altered too... > > > > this is just my own opinion, but i kinda like the icon style that looks > > a bit more like radio waves [1] better as they are symmetrical and look > > more like something is transmitted over the air than the current bars > > that stand next to each other, aligned at the bottom. > > i'd like to see such icons in NM and would like to know your opinion on > > this. > > This is a good design, but I wonder about the apple-esque appearance... > It wouldn't be difficult for me to make up some new icons with that > design, and the padlock placement could end up being a little better, we > could also look at having the bars different colours to specify > different network types wifi, gprs etc... Of course this wouldn't be > ideal in code, but we could work around that i believe. I wouldn't use different colors for different connection types, as that might be bad for color blind people. > > BR, > K > 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: New icons for nm-applet
On Tue, 2008-10-28 at 17:22 +, Karl Lattimer wrote: > On Tue, 2008-10-28 at 17:11 +, Karl Lattimer wrote: > > On Tue, 2008-10-28 at 12:50 -0400, Dan Williams wrote: > > > On Tue, 2008-10-28 at 16:11 +, Karl Lattimer wrote: > > > > On Tue, 2008-10-28 at 16:07 +, Karl Lattimer wrote: > > > > > > > > So match the size of the nm-vpn-connecting-* set to the same > > > > > > > > overall > > > > > > > > size as the applet icon area, but just offset the vpn lock > > > > > > > > itself so > > > > > > > > it's positioned in the lower-right corner. The progress > > > > > > > > twirlie can > > > > > > > > probably stay where it is. > > > > > > > > > > > > > > > > Existing connection with VPN active: > > > > > > > > http://bigw.org/~dan/Screenshot.png > > > > > > > > > > > > > > Now I get what you mean... Let me ponder this, I'll get back to > > > > > > > you as > > > > > > > soon as I can see a good solution. > > > > > > > > > > > > Great, hope it's soon :) I'd think just moving the padlock down > > > > > > and to > > > > > > the right in the existing images would be just fine. > > > > > > > > > > Probably, but I'd rather do some sketches of some other ideas, I mean > > > > > it's only one image which is used as an overlay, so that one could be > > > > > fixed easily, but I'm thinking now in terms of the progress meter for > > > > > vpn. > > > > > > > > > > Maybe if we are moving the padlock down, then I could use icons which > > > > > are similar to the standard connecting animation but instead of a dot > > > > > a > > > > > keyhole or something instead. > > > > > > > > > > I'm mulling it, there's some space for flexibility. > > > > > > > > > > Hopefully i can knock up some updated icons today, and while i'm at it > > > > > classify them into sizes for 16,22 and 24 > > > > > > > > Actually as the padlock is composited we could probably benefit from > > > > compositing the icons for gsm/gprs, edge, umts, hsdpa and anything else > > > > that comes along, maybe the recently submitted patch should be updated > > > > to work in these terms? > > > > > > Yes, that's what I replied to it with. The code has "layers", and there > > > are currently two layers: device and VPN. We can certainly add a mobile > > > broadband layer in which the mobile broadband badge goes. Just need to > > > figure out where in the icon area that should go so it doesn't conflict > > > with the VPN lock. Because you certainly can have an active VPN over > > > cellular. > > > > Urgh, now we're starting to have problems... Colours are obviously going > > to be better as long as there is detailed explanation somewhere of what > > they mean. Mockups attached for discussion. > > > > vpn-umts.svg - My first impression of this is that it's starting to get > > crowded, and I can make the padlock smaller but loose detail which I > > feel is critical. > > > > vpn-umts2.svg - Slightly less crowded and more appealing I feel, only > > 3px tall to denote the technology, so we'll have to use vibrant colours > > which aren't in the tango palette :/ > > Thinking in these terms now, and maybe the signal strength bars can be > altered too... this is just my own opinion, but i kinda like the icon style that looks a bit more like radio waves [1] better as they are symmetrical and look more like something is transmitted over the air than the current bars that stand next to each other, aligned at the bottom. i'd like to see such icons in NM and would like to know your opinion on this. greets, Björn [1] http://www.o2.co.uk/assets/O2HybridNav/Static-files/Kana/wifi_50x50.gif > K, > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list 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: [REQ] Adding support for simultaneous wireless networks
ah ok then. however, i think it should be a bit more clear to the user what to do. something like a 3 step wizard like bluez-gnome has now for setting up new bluetooth devices would be nice. for example something like this: 1. select the device connected to the internet 2. select the device for others to connect to, to use the shared connection 3. (optional for wifi) select encryption and then nm sets up the shared connection on the chosen device. just an idea, open for improvements and comments ;) greets, Björn On Mon, 2008-10-27 at 11:47 -0400, Dan Williams wrote: > On Mon, 2008-10-27 at 16:37 +0100, Bjoern Martensen wrote: > > a friend of mine has a desktop pc with 2 ethernet devices onboard and > > uses one to connect to his dsl modem and one to share this pppoe > > connection over to his xbox. being able to share a connection not only > > wired <-> wifi but also wired <-> wired would be nice in such > > situations and it can't be done with the current state. > > NM 0.7 allows connection sharing between arbitrary devices. > > Dan > > > On Mon, Oct 27, 2008 at 2:01 PM, Jerone Young > > <[EMAIL PROTECTED]> wrote: > > > This is not a standard use case. The fact is most consumers would have > > > the wireless printer connected to their wifi network. I myself have a > > > wireless printer and it connects to my wifi network, where I just access > > > it like a standard network printer. > > > > > > I'm a little confused on exactly why you are connecting to your printer > > > via ad-hoc mode, unless you do not have a wifi access point. To which > > > once you did get one, you need to connect the printer to the access > > > point. > > > > > > The only common case for this connecting to a printer wirelessly > > > directly is via bluetooth, but this is handled by bluez and not > > > network-manager. Also devices that do support it, handle this easily. > > > > > > Supporting something like this actually confuses users. How do you know > > > which connection to get to the internet from ? .. it makes little > > > since ... > > > > > > On Mon, 2008-10-27 at 00:53 -0600, Brent Newland wrote: > > >> I work at a retail store selling computers, and I can tell you that > > >> all the printer manufacturer's seem to be going wireless. Out of the > > >> latest selection of HP and Canon printers we carry, nearly all of the > > >> consumer level machines have built in wireless. > > >> > > >> Alot of people expect to be able to connect to the internet (whether > > >> it's through a wireless network, a cell phone card, a cable) and also > > >> be able to connect to their printer at the same time to print > > >> wirelessly, but that's not currently an easy thing to configure. > > >> > > >> What's even worse is if you want to connect to a wireless network while > > >> being connected to a wireless printer in ad-hoc mode. Currently, to do > > >> this you would have to use airtun-ng (this is the only program I've > > >> found which does this): > > >> http://www.aircrack-ng.org/doku.php?id=airtun-ng&DokuWiki=70b54c7d04564ca6bcee0f8746f3044d#connecting_to_two_access_points > > >> > > >> That'll let you connect to two wireless networks as long as they are on > > >> the same channel. > > >> > > >> > > >> I think that these would both be excellent features to have (connect to > > >> two wireless networks with one card to load balance/access resources on > > >> both networks - useful for copying between networks as well - and easily > > >> setting up an ad-hoc connection to a printer with another connection as > > >> the primary; all via the networkmanager GUI, of course). I'm sure that > > >> in the near future there will be a lot more questions like these across > > >> the different distros. > > >> _ > > >> Store, manage and share up to 5GB with Windows Live SkyDrive. > > >> http://skydrive.live.com/welcome.aspx?provision=1?ocid=TXT_TAGLM_WL_skydrive_102008 > > >> ___ > > >> 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 > 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: issues with new wpa adhoc fixes
tried again, here some results: start nm * auto to home network * create new adhoc * from list * message to be connected, crash * same name, same pass, but re-entered it * message to be connected, crash * new connection name * grey bars * no radio focus * connected * select the connection from the list again * crash * select another existing wpa2 adhoc * message to be connected to that connection * connection fails * autoconnected to home network * select that same adhoc again from the create-list * crash 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: issues with new wpa adhoc fixes
On Tue, 2008-10-21 at 09:26 -0400, Dan Williams wrote: > On Tue, 2008-10-21 at 08:26 +0200, Björn Martensen wrote: > > Hi, > > > > I tried the adhoc wpa fixes from yesterday and found some issues: > > Can you try with svn r4200? There were a few unrelated issues that I > fixed last night/this morning that could help out some of the issues > here. it definately works better now, but still has some problems. 1. applet still shows all grey bars, another icon might be better here. 2. the first time i create the connection, the radio button in the applet's list isn't selected. none is. when i connect to my home network and back to the adhoc, it's selected. 3. say i connected to my home wifi automatically after session login. now i create a new adhoc network (select it from the list, as i created it before already), and connect to the home network again. now i switch to the adhoc network again by using the "create" option again. this works fine. now i am connected to the adhoc network and select it in the applet's list again, sometimes the daemon crashes and sometimes i just get disconnected so i auto-connect to the home network again. i'll try to figure out what action exactly is crashing the daemon as it was pretty random, but i managed to get the crash 3 times now, so it is there ;) > Also, what kernel and wpa_supplicant version are you using? They > greatly affect whether you can create adhoc networks at all. kernel 2.6.27.1, iwl3945 and wpa_supplicant 0.6.4 > Dan > > > - i am connected to my wpa2 wifi network > > - i create a new wpa/wpa2 adhoc connection > > > when the connection should be established, nm dies and i have to > > restart /etc/rc.d/networkmanager. > > - when it has restarted, i connect to my home wifi, then switch to the > > adhoc i was trying to create (selecting it from the list this time). > > - i get connected to the adhoc connection, nm-applet shows the signal > > strenght at 0, i.e. all grey bars. > > - i try to switch back to the home wifi connection, but when i should > > get connected, nm just always disconnects completely. again, restarting > > the daemon fixes this, as above (although it hasn't crashed this time). > > after restarting it, i can connect to the home wifi network again. > > > > greets, > > Björn > > > > > > ___ > > NetworkManager-list mailing list > > NetworkManager-list@gnome.org > > http://mail.gnome.org/mailman/listinfo/networkmanager-list > 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
issues with new wpa adhoc fixes
Hi, I tried the adhoc wpa fixes from yesterday and found some issues: - i am connected to my wpa2 wifi network - i create a new wpa/wpa2 adhoc connection > when the connection should be established, nm dies and i have to restart /etc/rc.d/networkmanager. - when it has restarted, i connect to my home wifi, then switch to the adhoc i was trying to create (selecting it from the list this time). - i get connected to the adhoc connection, nm-applet shows the signal strenght at 0, i.e. all grey bars. - i try to switch back to the home wifi connection, but when i should get connected, nm just always disconnects completely. again, restarting the daemon fixes this, as above (although it hasn't crashed this time). after restarting it, i can connect to the home wifi network again. greets, Björn 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
wpa(2) secrets aren't stored in keyring anymore
hi, after an update of nm from trunk in the last few days and removing and re-adding my home wifi connection, the passkey isn't stored correctly anymore. when i log in to my session, i get the dialog from nm-applet to enter the passkey, but after that i don't get a dialog to unlock the keyring so nm can store the passkey there. in the configuration settings for the connection, the security mode is correct (wpa/wpa2) but there is no password entered. when i enter one, it's not in there when i re-open that connection editor after closing it. greets, Björn 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
new avahi autoip stuff not working for me
hi, not sure what's wrong here, but after todays change to the autoip code (now using avahi-autoipd), nm just gives me a "disconnected" notification immediately when i try to activate an autoip connection. so i tried running avahi-autoipd in a terminal, which gives me this weird error: $ sudo avahi-autoipd eth0 Failed to find user 'avahi-autoipd'. what's with the user thing? is my distro doing stuff wrong and if so, what's that? or is avahi broken? greetz, björn 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: F9 Networkmanager and zeroconf
On Wed, 2008-06-18 at 22:08 +0800, [EMAIL PROTECTED] wrote: > hi, > > It seems that in F8, when nm failed to get a DHCP reply, it will use > zeroconf to get a IP address for NIC. It's something like this(fedora 8 log): > ... > Jun 8 09:27:21 freeopen avahi-daemon[2073]: Registering new address > record for fe80::216:ecff:fec0:f990 on eth0.*. > Jun 8 09:27:27 freeopen dhclient: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 8 > Jun 8 09:27:35 freeopen dhclient: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 18 > Jun 8 09:27:53 freeopen dhclient: DHCPDISCOVER on eth0 to > 255.255.255.255 port 67 interval 17 > Jun 8 09:28:05 freeopen NetworkManager: Device 'eth0' DHCP > transaction took too long (>45s), stopping it. > Jun 8 09:28:05 freeopen NetworkManager: eth0: canceled DHCP > transaction, dhclient pid 6097 > Jun 8 09:28:05 freeopen NetworkManager: Activation (eth0) > Stage 4 of 5 (IP Configure Timeout) scheduled... > Jun 8 09:28:05 freeopen NetworkManager: Activation (eth0) > Stage 4 of 5 (IP Configure Timeout) started... > Jun 8 09:28:05 freeopen NetworkManager: No DHCP reply > received. Automatically obtaining IP via Zeroconf. > Jun 8 09:28:05 freeopen NetworkManager: autoip: Sending probe > #0 for IP address 169.254.158.8. > Jun 8 09:28:05 freeopen NetworkManager: autoip: Waiting for reply... > Jun 8 09:28:06 freeopen NetworkManager: autoip: Got some data > to check for reply packet. > Jun 8 09:28:06 freeopen NetworkManager: get_autoip(): autoip: > (eth0) recv arp type=2054, op=1, > Jun 8 09:28:06 freeopen NetworkManager: get_autoip(): source > = 199.199.194.2 00:0F:E2:61:F7:8B, > Jun 8 09:28:06 freeopen NetworkManager: get_autoip(): target > = 199.199.194.2 0E:2A:65:B5:37:07#012 > Jun 8 09:28:06 freeopen NetworkManager: autoip: Sending probe > #1 for IP address 169.254.158.8. > Jun 8 09:28:06 freeopen NetworkManager: autoip: Waiting for reply... > Jun 8 09:28:07 freeopen NetworkManager: autoip: Got some data > to check for reply packet. > Jun 8 09:28:07 freeopen NetworkManager: get_autoip(): autoip: > (eth0) recv arp type=2054, op=1, > ... > BUT, it seems that in F9, nm doesn't use zeroconf anymore. It just > failed when cannot get a DHCP rely. > This is very bad for me. I am using a pppoe connection. This new > behavior make the pppoe's NIC failed to > get a IP address and ppp dial will fail. have you tried loading the ppp_generic module before trying to connect via pppoe? it solved the problem on my machine (arch linux), as ppp_generic isn't automatically loaded at boot time and it isn't loaded when nm tries to connect via pppoe either. since ppp_generic creates the /dev/ppp device, which is neccesary for pppd to function, and it doesn't exist when nm tries to connect, it just fails. so loading ppp_generic manually at boot time solves this _for me_. it's still an ugly solution, but at least it helps to work around the problem... i don't have any problem with pppoe which are related to dhcp however, so maybe you can check if this solves your problem. greets, björn 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
svn build breakage
after yesterday's changes, nm from svn doesn't build for me anymore: > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I../include -I../libnm-util > -I../marshallers -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0 > -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=2 > -DDBUS_VERSION_MICRO=1 -Wall -Werror -std=gnu89 -march=i686 -mtune=generic > -O2 -pipe -Wshadow -Wmissing-declarations -Wmissing-prototypes > -Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter > -Wno-sign-compare -fno-strict-aliasing -MT libnm_glib_la-nm-client.lo -MD -MP > -MF .deps/libnm_glib_la-nm-client.Tpo -c nm-client.c -fPIC -DPIC -o > .libs/libnm_glib_la-nm-client.o > In file included from nm-client.c:10: > nm-gsm-device.h:6:30: error: nm-serial-device.h: No such file or directory > In file included from nm-client.c:10: > nm-gsm-device.h:18: error: expected specifier-qualifier-list before > ‘NMSerialDevice’ > nm-gsm-device.h:22: error: expected specifier-qualifier-list before > ‘NMSerialDeviceClass’ > In file included from nm-client.c:11: > nm-cdma-device.h:18: error: expected specifier-qualifier-list before > ‘NMSerialDevice’ > nm-cdma-device.h:22: error: expected specifier-qualifier-list before > ‘NMSerialDeviceClass’ > make[3]: *** [libnm_glib_la-nm-client.lo] Error 1 all sources are freshly checked out. Björn 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: networkmanger .7.0
i sent you some pkgbuilds for nm 0.7 from svn and the latest packages i built from svn for i686. greetz, björn On Wed, 2008-06-04 at 16:38 +0530, sanjeev sharma wrote: > Hi all, > i am trying to build and test nm .7.0 on ubuntu version 7.10. on x86 > Arch. > > Can anyone give me some inputs about configuration and dependencies > when trying to do so? What do I specify for --with-distro in > configuration? > Thanks & Regards > sanjeev sharma > > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list 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
current svn doesn't make install properly
Hi,
I'm building snapshot packages from trunk and the last successfull
package i built was 3650. newer packages are empty when i make install.
this is the last output of the build process:
> libtool: link: gcc -shared
> .libs/libnm_settings_plugin_keyfile_la-nm-keyfile-connection.o
> .libs/libnm_settings_plugin_keyfile_la-plugin.o
> .libs/libnm_settings_plugin_keyfile_la-reader.o
> .libs/libnm_settings_plugin_keyfile_la-writer.o -Wl,-rpath
> -Wl,/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs
> -Wl,-rpath
> -Wl,/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-glib/.libs
>
> -L/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs
> ../../../libnm-util/.libs/libnm-util.so
> ../../../libnm-glib/.libs/libnm_glib.so
> /home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/libnm-util/.libs/libnm-util.so
> -lgthread-2.0 -lrt -ldbus-glib-1 -ldbus-1 -lgio-2.0 -lgobject-2.0
> -lgmodule-2.0 -ldl -lglib-2.0 -march=i686 -mtune=generic
> -Wl,--export-dynamic -pthread -Wl,-soname
> -Wl,libnm-settings-plugin-keyfile.so -o .libs/libnm-settings-plugin-keyfile.so
> libtool: link: ar cru .libs/libnm-settings-plugin-keyfile.a
> libnm_settings_plugin_keyfile_la-nm-keyfile-connection.o
> libnm_settings_plugin_keyfile_la-plugin.o
> libnm_settings_plugin_keyfile_la-reader.o
> libnm_settings_plugin_keyfile_la-writer.o
> libtool: link: ranlib .libs/libnm-settings-plugin-keyfile.a
> libtool: link: ( cd ".libs" && rm -f "libnm-settings-plugin-keyfile.la" && ln
> -s "../libnm-settings-plugin-keyfile.la" "libnm-settings-plugin-keyfile.la" )
> make[4]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins/keyfile'
> make[4]: Entering directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
> make[4]: Nothing to be done for `all-am'.
> make[4]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
> make[3]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings/plugins'
> make[3]: Entering directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
> make[3]: Nothing to be done for `all-am'.
> make[3]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
> make[2]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/system-settings'
> Making all in tools
> make[2]: Entering directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/tools'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/tools'
> Making all in policy
> make[2]: Entering directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/policy'
> make[2]: Nothing to be done for `all'.
> make[2]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build/policy'
> make[2]: Entering directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
> make[2]: Nothing to be done for `all-am'.
> make[2]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
> make[1]: Leaving directory
> `/home/baze/pkgs/networkmanager-svn/src/NetworkManager-build'
> Makefile:73: *** commands commence before first target. Stop.
and this is the build script from my arch linux PKGBUILD:
> build() {
> cd $startdir/src
> msg "Updating from SVN"
> svn co $_svntrunk -r $pkgver $_svnmod || return 1
>
> msg "SVN checkout done."
> msg "Starting make..."
>
> [ -d ./$_svnmod-build ] && rm -fr ./$_svnmod-build
> svn export ./$_svnmod ./$_svnmod-build
> cd ./$_svnmod-build
>
>
> ./autogen.sh --prefix=/usr --sysconfdir=/etc \
> --with-distro=arch --localstatedir=/var \
> --without-gnome --libexecdir=/usr/lib/networkmanager
>
> make || return 1
> sed -i -e '/\slibnm-util\s/d' -e '/\sinclude/d' -e '/\sgnome\s/d' Makefile
> make DESTDIR=${startdir}/pkg install
> install -d -m755 ${startdir}/pkg/usr/bin
> install -m755 test/nm-tool ${startdir}/pkg/usr/bin/nm-tool
> # install -m644 ${startdir}/src/NetworkManager.conf
> ${startdir}/pkg/etc/dbus-1/system.d/NetworkManager.conf
> # install -m755 ${startdir}/src/ntpdate
> ${startdir}/pkg/etc/NetworkManager/dispatcher.d/ntpdate
> # install -m755 ${startdir}/src/netfs
> ${startdir}/pkg/etc/NetworkManager/dispatcher.d/netfs
> }
the last lines have to be commented out, or else no package is created at all,
because the
directories don't exist. the only content of the package is the manually
installed nm-tool file.
can anyone confirm this?
björn
signature.asc
Description: This is a digitally signed message part
___
NetworkManager-list mailing list
NetworkManager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/net
Re: nm-tool and nm-applet problems in recent svn
On Thu, 2008-05-08 at 13:56 -0400, Dan Williams wrote: > On Tue, 2008-05-06 at 19:38 +0200, Björn Martensen wrote: > > Hi, > > > > I had this problem with nm-tool for some time now and it doesn't work in > > the latest svn of libnm, networkmanager and nm-applet yet: > > Hmm; nm-tool seems to work for me in latest SVN. it doesn't with the latest here :/ > > > > > $ nm-tool > > > > > > NetworkManager Tool > > > > > > State: connected > > > > > > > > > (process:14913): GLib-GObject-WARNING **: invalid uninstantiatable type > > > `(null)' in cast to `NMDevice' > > > > > > ** (process:14913): CRITICAL **: nm_device_get_state: assertion > > > `NM_IS_DEVICE (device)' failed > > > > > > ** (process:14913): CRITICAL **: nm_device_get_iface: assertion > > > `NM_IS_DEVICE (device)' failed > > > - Device: (null) > > > > > > > > > ** (process:14913): CRITICAL **: nm_device_get_driver: assertion > > > `NM_IS_DEVICE (device)' failed > > > Driver:(unknown) > > > Active:no > > > > > > ** (process:14913): CRITICAL **: nm_device_get_capabilities: assertion > > > `NM_IS_DEVICE (device)' failed > > > > > > Capabilities: > > > Supported: no > > > > > > > > > Segmentation fault > > > > I'm using a thinkpad t60 with iwl3945 and e100e driven devices. both work > > fine, but nm-tool doesn't seem to like my system. > > Can you try a clean rebuild of NM? Might be mismatched libnm-glib and > nm-tool. i always do svn up and then svn export that tree to a temporary build directory to create clean packages, so i always have a clean rebuild. > > since nm-applet svn 711, nm-applet doesn't start anymore. when it starts, > > bug buddy tells me, the applet has crashed. > > That sounds like the same issue as nm-tool is having. actually it was solved after a recent nm commit and now the applet works again. however, nm-tool does not. > > > $ nm-applet > > > > > > ** (nm-applet:14850): WARNING **: Could not retrieve dbus connections: > > > Launch helper exited with unknown return code 1. > > > 6d91daf9-4738-49a8-54b19ba7-45e237df is dumped > > > > the weird part is that it still connects and then crashes right away. has > > there anything important been > > changed and conflicts with old settings now in that commit or what's > > happening? I'm running arch linux and it worked > > fine with older versions, and i can still connect to all the networks i > > could before... maybe this helps: > > > > > > > ** (nm-applet:15045): WARNING **: Could not retrieve dbus connections: > > > Launch helper exited with unknown return code 1. > > > > > > Program received signal SIGSEGV, Segmentation fault. > > > [Switching to Thread 0xb728a6c0 (LWP 15045)] > > > 0xb76abb05 in free () from /lib/libc.so.6 > > > (gdb) bt full > > > #0 0xb76abb05 in free () from /lib/libc.so.6 > > > No symbol table info available. > > > #1 0xb78da096 in g_free () from /usr/lib/libglib-2.0.so.0 > > > No symbol table info available. > > > #2 0xb78aafac in g_ptr_array_free () from /usr/lib/libglib-2.0.so.0 > > > No symbol table info available. > > > #3 0xb8087422 in fetch_connections_done () from /usr/lib/libnm_glib.so.0 > > I think Tambet fixed this yesterday actually. Can you try with latest > NM svn? as stated above, the applet works fine again, thanks :) björn 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
nm-tool and nm-applet problems in recent svn
Hi, I had this problem with nm-tool for some time now and it doesn't work in the latest svn of libnm, networkmanager and nm-applet yet: > $ nm-tool > > NetworkManager Tool > > State: connected > > > (process:14913): GLib-GObject-WARNING **: invalid uninstantiatable type > `(null)' in cast to `NMDevice' > > ** (process:14913): CRITICAL **: nm_device_get_state: assertion `NM_IS_DEVICE > (device)' failed > > ** (process:14913): CRITICAL **: nm_device_get_iface: assertion `NM_IS_DEVICE > (device)' failed > - Device: (null) > > > ** (process:14913): CRITICAL **: nm_device_get_driver: assertion > `NM_IS_DEVICE (device)' failed > Driver:(unknown) > Active:no > > ** (process:14913): CRITICAL **: nm_device_get_capabilities: assertion > `NM_IS_DEVICE (device)' failed > > Capabilities: > Supported: no > > > Segmentation fault I'm using a thinkpad t60 with iwl3945 and e100e driven devices. both work fine, but nm-tool doesn't seem to like my system. since nm-applet svn 711, nm-applet doesn't start anymore. when it starts, bug buddy tells me, the applet has crashed. > $ nm-applet > > ** (nm-applet:14850): WARNING **: Could not retrieve dbus connections: Launch > helper exited with unknown return code 1. > 6d91daf9-4738-49a8-54b19ba7-45e237df is dumped the weird part is that it still connects and then crashes right away. has there anything important been changed and conflicts with old settings now in that commit or what's happening? I'm running arch linux and it worked fine with older versions, and i can still connect to all the networks i could before... maybe this helps: > ** (nm-applet:15045): WARNING **: Could not retrieve dbus connections: Launch > helper exited with unknown return code 1. > > Program received signal SIGSEGV, Segmentation fault. > [Switching to Thread 0xb728a6c0 (LWP 15045)] > 0xb76abb05 in free () from /lib/libc.so.6 > (gdb) bt full > #0 0xb76abb05 in free () from /lib/libc.so.6 > No symbol table info available. > #1 0xb78da096 in g_free () from /usr/lib/libglib-2.0.so.0 > No symbol table info available. > #2 0xb78aafac in g_ptr_array_free () from /usr/lib/libglib-2.0.so.0 > No symbol table info available. > #3 0xb8087422 in fetch_connections_done () from /usr/lib/libnm_glib.so.0 > No symbol table info available. > #4 0xb80872d1 in > org_freedesktop_NetworkManagerSettings_list_connections_async_callback () > from /usr/lib/libnm_glib.so.0 > No symbol table info available. > #5 0xb7b3279f in d_pending_call_notify () from /usr/lib/libdbus-glib-1.so.2 > No symbol table info available. > #6 0xb79a42c1 in _dbus_pending_call_complete () from /usr/lib/libdbus-1.so.3 > No symbol table info available. > #7 0xb79936d6 in complete_pending_call_and_unlock () >from /usr/lib/libdbus-1.so.3 > No symbol table info available. > #8 0xb799539c in dbus_connection_dispatch () from /usr/lib/libdbus-1.so.3 > No symbol table info available. > #9 0xb7b2e92d in message_queue_dispatch () from /usr/lib/libdbus-glib-1.so.2 > No symbol table info available. > #10 0xb78d1f88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 > ---Type to continue, or q to quit--- > No symbol table info available. > #11 0xb78d54eb in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 > No symbol table info available. > #12 0xb78d59ba in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 > No symbol table info available. > #13 0x080540bd in main () > No symbol table info available. björn 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
trunk: pppoe supposed to be working?
Hi, I'd just like to know if current svn versions of NM 0.7 are supposed to have working pppoe support. (libnm: 3571, nm: 3572, nm-applet: 685) I entered the username and the password, left the service blank, as i have no idea what is supposed to go in there and it works with rp-pppoe and on my router too without a service name. When i connect directly to the dsl modem, NM tries to connect to "Auto Ethernet" but fails because it doesn't get an IP address assigned. When I select the dsl connection from the applet's list, NM crashes. I can restart it again but the wired connections are greyed out then. When I unplug the ethernet cable and plug it back in, NM tries to connect to "Auto Ethernet" again, fails to get an IP address, and so on.. NM also crashes when I enter something into the service entry field. I'd just like to know if this is the current state, or if I should get any kind of IP address for direct connections, a zeroconf address for example, or if it's "normal" currently, that I can't get an address. And I'd also like to know if activating a dsl connection is known to crash NM at the moment. Thanks, Björn 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: patch for PPPoE problem
On Wed, 2008-04-16 at 16:03 -0400, Dan Williams wrote: > On Wed, 2008-04-16 at 21:56 +0800, 陈鑫 wrote: > > Dear Dan, > > > > I used PPPoE function of NetworkManager with ppp-2.4.4，I > > found some problems and fixed it. > > Thanks! Committed to SVN. Can you verify that the version I committed > works for you? I added a pap_check_hook that returns 1, which from > reading pppd/auth.c and PLUGINS in pppd seem to be what we should be > doing there. after the last patch svn doesn't build for me anymore: > libtool: link: ( cd ".libs" && rm -f "libppp-manager.la" && ln -s > "../libppp-manager.la" "libppp-manager.la" ) > /bin/sh ../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. > -I../.. -I../.. -I../../include -I../../libnm-util -I../../src > -I../../marshallers -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include > -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=1 > -DDBUS_VERSION_MINOR=1 -DDBUS_VERSION_MICRO=20 -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -Wall -Werror -std=gnu89 -march=i686 > -mtune=generic -O2 -pipe -Wshadow -Wmissing-declarations -Wmissing-prototypes > -Wdeclaration-after-statement -Wfloat-equal -Wno-unused-parameter > -Wno-sign-compare -MT nm_pppd_plugin_la-nm-pppd-plugin.lo -MD -MP -MF > .deps/nm_pppd_plugin_la-nm-pppd-plugin.Tpo -c -o > nm_pppd_plugin_la-nm-pppd-plugin.lo `test -f 'nm-pppd-plugin.c' || echo > './'`nm-pppd-plugin.c > libtool: compile: gcc -DHAVE_CONFIG_H -I. -I../.. -I../.. -I../../include > -I../../libnm-util -I../../src -I../../marshallers -I/usr/include/dbus-1.0 > -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0 > -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=1 > -DDBUS_VERSION_MICRO=20 -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include > -Wall -Werror -std=gnu89 -march=i686 -mtune=generic -O2 -pipe -Wshadow > -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement > -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -MT > nm_pppd_plugin_la-nm-pppd-plugin.lo -MD -MP -MF > .deps/nm_pppd_plugin_la-nm-pppd-plugin.Tpo -c nm-pppd-plugin.c -fPIC -DPIC > -o .libs/nm_pppd_plugin_la-nm-pppd-plugin.o > cc1: warnings being treated as errors > nm-pppd-plugin.c: In function 'get_credentials': > nm-pppd-plugin.c:226: error: the address of 'user' will always evaluate as > 'true' > make[4]: *** [nm_pppd_plugin_la-nm-pppd-plugin.lo] Error 1 Björn > Dan > > > ChangeLog > > > > * src/nm-device-802-3-ethernet.c > > -(real_deactivate_quickly): clear ip_iface of the device. > > nm_system_device_set_from_ip4_config() used to use pppoe interface, > > when link changes from pppoe to dhcp, > >* src/ppp-manager/nm-pppd-plugin.c > > -(get_credentials): when checking pap authentication in > > pppd, parameter passwd is NULL, check it and return 1 to support pap. > > -(plugin_init): define chap_check_hook() to support chap > > authentication. > > * src/ppp-manager/nm-ppp-manager.c > > -(create_pppd_cmd_line): fixed obvious error when creating > > pppd command line. > > > > > > Regards, > > znscn > > ___ > > 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 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: [PATCH] pppoe: handle service string empty case
On Fri, 2008-04-04 at 15:55 -0400, Dan Williams wrote:
> On Tue, 2008-04-01 at 22:56 +0400, Vitja Makarov wrote:
> > rp-pppoe could be started with empty service string, this fixes the case.
>
> Ah, interesting. What I've done instead is to make an empty service
> fail validation of the setting. I'm curious where that empty service is
> coming from, since it shouldn't be written into the setting in the first
> place... Do you have an empty 'service' item in GConf perhaps?
>
that commit broke svn for me:
> libtool: compile: gcc -DHAVE_CONFIG_H -I. -I.. -I.. -I../include
> -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -I/usr/include/dbus-1.0
> -I/usr/lib/dbus-1.0/include -I/usr/include/glib-2.0
> -I/usr/lib/glib-2.0/include -DDBUS_VERSION_MAJOR=1 -DDBUS_VERSION_MINOR=1
> -DDBUS_VERSION_MICRO=20 -DDBUS_API_SUBJECT_TO_CHANGE -DG_DISABLE_DEPRECATED
> -fPIC -Wall -Werror -std=gnu89 -march=i686 -mtune=generic -O2 -pipe -Wshadow
> -Wmissing-declarations -Wmissing-prototypes -Wdeclaration-after-statement
> -Wfloat-equal -Wno-unused-parameter -Wno-sign-compare -MT
> libnm_util_la-nm-setting-pppoe.lo -MD -MP -MF
> .deps/libnm_util_la-nm-setting-pppoe.Tpo -c nm-setting-pppoe.c -fPIC -DPIC
> -o .libs/libnm_util_la-nm-setting-pppoe.o
> cc1: warnings being treated as errors
> nm-setting-pppoe.c: In function 'verify':
> nm-setting-pppoe.c:27: warning: implicit declaration of function 'strlen'
> nm-setting-pppoe.c:27: warning: incompatible implicit declaration of built-in
> function 'strlen'
> make[2]: *** [libnm_util_la-nm-setting-pppoe.lo] Error 1
Björn
> Dan
>
> > Index: src/ppp-manager/nm-ppp-manager.c
> > ===
> > --- src/ppp-manager/nm-ppp-manager.c(revision 3521)
> > +++ src/ppp-manager/nm-ppp-manager.c(working copy)
> > @@ -509,7 +509,7 @@
> > nm_cmd_line_add_string (cmd, dev_str);
> > g_free (dev_str);
> >
> > - if (pppoe->service) {
> > + if (pppoe->service && *pppoe->service) {
> > nm_cmd_line_add_string (cmd, "rp_pppoe_service");
> > nm_cmd_line_add_string (cmd, pppoe->service);
> > }
> > ___
> > 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
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: nm 0.7 doesn't connect to wired device
On Sat, 2008-03-29 at 18:24 -0400, Dan Williams wrote: > On Fri, 2008-03-28 at 21:21 +0100, Björn Martensen wrote: > > btw, when I run nm-tool, I get this segfault: > > Should be fixed now, I think. At least I don't get this with latest > SVN. > > Dan > > > > > > $ nm-tool > > > > > > NetworkManager Tool > > > > > > State: disconnected > > > > > > > > > (process:8359): GLib-GObject-WARNING **: invalid uninstantiatable type > > > `(null)' in cast to `NMDevice' > > > > > > ** (process:8359): CRITICAL **: nm_device_get_state: assertion > > > `NM_IS_DEVICE (device)' failed > > > > > > ** (process:8359): CRITICAL **: nm_device_get_iface: assertion > > > `NM_IS_DEVICE (device)' failed > > > - Device: (null) > > > > > > > > > ** (process:8359): CRITICAL **: nm_device_get_driver: assertion > > > `NM_IS_DEVICE (device)' failed > > > Driver:(unknown) > > > Active:no > > > > > > ** (process:8359): CRITICAL **: nm_device_get_capabilities: assertion > > > `NM_IS_DEVICE (device)' failed > > > > > > Capabilities: > > > Supported: no > > > > > > > > > Segmentation fault I still get that error with svn 3514 here. maybe a bug due to libtool 2.2? Björn 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
nm 0.7 doesn't connect to wired device
Hi, I'm running NM 0.7 from trunk and connecting with the wired interface worked before when i was connecting my laptop to my router. Now I'm currently visiting my parents and have my laptop connected to their DSL modem directly and have updated NM recently to the latest version, so maybe something is broken there. Anyway, I'm using rp-pppoe to connect to the dsl modem, since NM's pppoe connection editor is not yet finished and that works fine. However, the nm-applet tries to establish the connection on the wired device, but fails to get a network address and gets back to disconnected state. The connection is there, the interface is there, but it doesn't work with NM. I don't have specified an IP adress and don't bring up the device with Arch's network script, but let it be handled by NM instead. Any Ideas why NM can't establish the connection correctly? Is something wrong with dhcp or what? btw, when I run nm-tool, I get this segfault: > $ nm-tool > > NetworkManager Tool > > State: disconnected > > > (process:8359): GLib-GObject-WARNING **: invalid uninstantiatable type > `(null)' in cast to `NMDevice' > > ** (process:8359): CRITICAL **: nm_device_get_state: assertion `NM_IS_DEVICE > (device)' failed > > ** (process:8359): CRITICAL **: nm_device_get_iface: assertion `NM_IS_DEVICE > (device)' failed > - Device: (null) > > > ** (process:8359): CRITICAL **: nm_device_get_driver: assertion `NM_IS_DEVICE > (device)' failed > Driver:(unknown) > Active:no > > ** (process:8359): CRITICAL **: nm_device_get_capabilities: assertion > `NM_IS_DEVICE (device)' failed > > Capabilities: > Supported: no > > > Segmentation fault could this be causing the problem? I don't have a wireless network here atm, but that worked fine the last time I tried (3 days ago or so). Unfortunately, the iwl3945 never worked for ad-hoc for me, so I can't try that either. The network is never created, NM always gets back to disconnected state. That's another issue, but maybe you can tell me, if it _should_ be able to create a new wireless network with that driver in in general ;) Greetings, Björn 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
nm 0.7 doesn't connect to wired
Hi, I'm running NM 0.7 from trunk and connecting with the wired interface worked before when i was connecting my laptop to my router. Now I'm currently visiting my parents and have my laptop connected to their DSL modem directly and have updated NM recently to the latest version, so maybe something is broken there. Anyway, I'm using rp-pppoe to connect to the dsl modem, since NM's pppoe connection editor is not yet finished and that works fine. However, the nm-applet tries to establish the connection on the wired device, but fails to get a network address and gets back to disconnected state. The connection is there, the interface is there, but it doesn't work with NM. I don't have specified an IP adress and don't bring up the device with Arch's network script, but let it be handled by NM instead. Any Ideas why NM can't establish the connection correctly? Is something wrong with dhcp or what? btw, when I run nm-tool, I get this segfault: > $ nm-tool > > NetworkManager Tool > > State: disconnected > > > (process:8359): GLib-GObject-WARNING **: invalid uninstantiatable type > `(null)' in cast to `NMDevice' > > ** (process:8359): CRITICAL **: nm_device_get_state: assertion `NM_IS_DEVICE > (device)' failed > > ** (process:8359): CRITICAL **: nm_device_get_iface: assertion `NM_IS_DEVICE > (device)' failed > - Device: (null) > > > ** (process:8359): CRITICAL **: nm_device_get_driver: assertion `NM_IS_DEVICE > (device)' failed > Driver:(unknown) > Active:no > > ** (process:8359): CRITICAL **: nm_device_get_capabilities: assertion > `NM_IS_DEVICE (device)' failed > > Capabilities: > Supported: no > > > Segmentation fault could this be causing the problem? I don't have a wireless network here atm, but that worked fine the last time I tried (3 days ago or so). Unfortunately, the iwl3945 never worked for ad-hoc for me, so I can't try that either. The network is never created, NM always gets back to disconnected state. That's another issue, but maybe you can tell me, if it _should_ be able to create a new wireless network with that driver in in general ;) Greetings, Björn 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: Compile error with latest NM
could you maybe look into the gcc 4.3.x issue aswell, please? On Mon, 2008-03-24 at 10:44 -0400, Dan Williams wrote: > On Mon, 2008-03-24 at 15:31 +0100, Alban Browaeys wrote: > > Le dimanche 23 mars 2008 à 19:24 +0100, Björn Martensen a écrit : > > > > > On Sun, 2008-03-23 at 19:14 +0100, Diego González wrote: > > > > I get a compile error in nm-client.c due to > > > > org_freedesktop_NetworkManager_get_active_connections not being > > > > defined. > > > > > > > > I do too . It seems libglib-nm/nm-client.c either needs an update to > > match changes in introspection/nm-manager-client.xml or the changes are > > already done but where forgotten in > > http://svn.gnome.org/viewvc/NetworkManager?view=revision&revision=3484 . > > Could someone confirm . I plan of making an attempt at making a skeleton > > to make it works (nm-client.c) if nothing is implemented yet to match > > those changes. > > I rewrote a lot of bits this weekend, going to land them today. It'll > fix up libnm-glib and the applet to match. > > Dan > > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list 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: Compile error with latest NM
yep, i get that one too. and NM from svn doesn't compile with gcc 4.3.x either :/ Greets, Björn On Sun, 2008-03-23 at 19:14 +0100, Diego González wrote: > I get a compile error in nm-client.c due to > org_freedesktop_NetworkManager_get_active_connections not being > defined. > > Best regards, > Diego > ___ > NetworkManager-list mailing list > NetworkManager-list@gnome.org > http://mail.gnome.org/mailman/listinfo/networkmanager-list 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: 0.7 this year?
On Wed, 2007-12-12 at 15:17 -0500, Stuart D. Gathman wrote: > On Tue, 11 Dec 2007, Bjoern Martensen wrote: > > > how are the chances we might get our (desperately waiting) hands on NM > > 0.7 by the end of this year? maybe a christmas present? ;) > > I am running Fedora Core 8, and it has NM 0.7. Lo and behold, WPA > works with NM! (It didn't work with NM 0.6 on EL5). So download > the werewolf and enjoy. > i'm pretty happy with arch linux, thanks ;) btw, fedora 8 uses a pre-release, not 0.7 final. if multiple active devices are already implemented, i might try building packages from svn. can anyone tell me if this works already? greets, björn 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
