NM isn't working on embedded linux, ignoring interface.
Hi I am trying to get network manager working on a embedded Linux platform. The setup has a custom SOC with network controller on board. Vendor has provided us BSP that contains Linux kernel with network driver built into it. Kernel version is 2.6.22.19 and its running busy box. When I try to run NetworkManager it gives out following output: $ ./NetworkManager --no-daemon --config=/etc/NetworkManager/nm-system-settings.conf NetworkManager[909]: info NetworkManager (version 0.8.1) is starting... NetworkManager[909]: info Read config file /tmp/nm/etc/NetworkManager/nm-system-settings.conf NetworkManager[909]: info trying to start the modem manager... NetworkManager[909]:SCPlugin-Ifupdown: init! NetworkManager[909]:SCPlugin-Ifupdown: update_system_hostname NetworkManager[909]:SCPluginIfupdown: guessed connection type (eth0) = 802-3-ethernet NetworkManager[909]:SCPlugin-Ifupdown: update_connection_setting_from_if_block: name:eth0, type:802-3-ethernet, id:Ifupdown (eth0), uuid: 681b428f-beaf-8932-dce4-687ed5bae28e NetworkManager[909]:SCPlugin-Ifupdown: autoconnect NetworkManager[909]:SCPluginIfupdown: management mode: managed NetworkManager[909]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/eth0, iface: eth0) NetworkManager[909]:SCPluginIfupdown: locking wired connection setting NetworkManager[909]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/eth1, iface: eth1) NetworkManager[909]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/eth1, iface: eth1): no ifupdown configuration found. NetworkManager[909]:SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/lo, iface: lo) NetworkManager[909]:SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found. NetworkManager[909]:SCPlugin-Ifupdown: end _init. NetworkManager[909]: info Loaded plugin ifupdown: (C) 2008 Canonical Ltd. To report bugs please use the NetworkManager mailing list. NetworkManager[909]: info Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc. To report bugs please use the NetworkManager mailing list. NetworkManager[909]:SCPlugin-Ifupdown: (5082904) ... get_connections. NetworkManager[909]:SCPlugin-Ifupdown: (5082904) connections count: 1 NetworkManager[909]: info WiFi enabled by radio killswitch; enabled by state file NetworkManager[909]: info WWAN enabled by radio killswitch; enabled by state file NetworkManager[909]: info WiMAX enabled by radio killswitch; enabled by state file NetworkManager[909]: info Networking is enabled by state file NetworkManager[909]: info Setting system hostname to 'tango3' (from system configuration) NetworkManager[909]: info Updating /etc/hosts with new system hostname NetworkManager[909]: warn /sys/devices/virtual/net/eth0: couldn't determine device driver; ignoring... NetworkManager[909]: warn /sys/devices/virtual/net/eth1: couldn't determine device driver; ignoring... ifup: interface lo already configured NetworkManager[909]: warn bluez error getting default adapter: The name org.bluez was not provided by any .service files As we can see in log it has started but ignored both the network interfaces saying : NetworkManager[909]: warn /sys/devices/virtual/net/eth0: couldn't determine device driver; ignoring... NetworkManager[909]: warn /sys/devices/virtual/net/eth1: couldn't determine device driver; ignoring... I found a thread with the same issue( http://mail.gnome.org/archives/networkmanager-list/2010-July/msg00015.html), but it doesn't have any pointers to solution. Here is my output of ls -la /sys/class/net $ ls -la /sys/class/net/ drwxr-xr-x2 root root0 Dec 31 16:00 ./ drwxr-xr-x 18 root root0 Dec 31 16:00 ../ lrwxrwxrwx1 root root0 Jan 1 07:33 eth0 - ../../devices/virtual/net/eth0/ lrwxrwxrwx1 root root0 Jan 1 07:33 eth1 - ../../devices/virtual/net/eth1/ lrwxrwxrwx1 root root0 Jan 1 07:33 lo - ../../devices/virtual/net/lo/ $ ls -la /sys/class/net/eth0/ drwxr-xr-x3 root root0 Dec 31 16:00 ./ drwxr-xr-x5 root root0 Dec 31 16:00 ../ -r--r--r--1 root root16384 Jan 1 07:33 addr_len -r--r--r--1 root root16384 Jan 1 07:33 address -r--r--r--1 root root16384 Jan 1 07:33 broadcast -r--r--r--1 root root16384 Jan 1 07:33 carrier -r--r--r--1 root root16384 Jan 1 07:33 dormant -r--r--r--1 root root16384 Jan 1 07:33 features -rw-r--r--1 root root16384 Jan 1 07:33 flags -r--r--r--1 root root16384 Jan 1 07:33 ifindex -r--r--r--1 root root16384 Jan 1 07:33 iflink -r--r--r--1 root root16384 Jan 1 07:33 link_mode -rw-r--r--1 root root16384 Jan 1 07:33 mtu -r--r--r--1 root root16384 Jan 1 07:33 operstate
3g command line
Hi there, As I'm completely new surprised by network manager, my option GMT 382E umts card got working instantly, 3g with Proximus in Belgium. However, I'd like to use these kind of card with ubuntu server install, and would like to know the commands to get this working from the command-line. Any tips are welcome, seems I can't figure this out... Lennert. ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
sending persistent host name in DHCP interaction
Is there an easy way in NetworkManager to always send the persistent host name in DHCP interactions? I can't seem to find one. My understanding is that most of this is left to the distribution plugin. Under Fedora it appears that sending the host name is not done unless configuration files (like /etc/dhclient-wlan0.conf or /etc/sysconfig/network-scripts/ifcfg-eth1) are modified. So in Fedora it is possible to send *a* host name, but I wouldn't call the way of doing it easy. It appears that NetworkManager can get the persistent host name (from a plugin) and use that. However, no host name is sent unless NM_SETTING_IP4_CONFIG_DHCP_SEND_HOSTNAME is true, and this defaults to false. I guess, then, that I'm asking how to easily set this variable. Peter F. Patel-Schneider PS: I would count as easy changing the default for NM_SETTING_IP4_CONFIG_DHCP_SEND_HOSTNAME to true. :-) ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 3g command line
2010/12/2 Lennert Jansen lenn...@twixel.be: Hi there, As I'm completely new surprised by network manager, my option GMT 382E umts card got working instantly, 3g with Proximus in Belgium. However, I'd like to use these kind of card with ubuntu server install, and would like to know the commands to get this working from the command-line. Any tips are welcome, seems I can't figure this out... use nm-cli to list, start and stop connections. you can connect with VNC to your server to create initial connection settings or you could import/set everything gconftool-2. here is a discussion about that: http://mail.gnome.org/archives/networkmanager-list/2010-November/msg00082.html ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: 3g command line
On 2 December 2010 10:32, Lennert Jansen lenn...@twixel.be wrote: Hi there, As I'm completely new surprised by network manager, my option GMT 382E umts card got working instantly, 3g with Proximus in Belgium. However, I'd like to use these kind of card with ubuntu server install, and would like to know the commands to get this working from the command-line. Any tips are welcome, seems I can't figure this out... Lennert. Hi Lennert, If you want a minimal install you need something like the hso_connect.sh script which is available in the HSO driver packages from Option. You can locate the latest script here: http://www.pharscape.org/forum/index.php/topic,821.0.html Cheers, Paul -- www.pharscape.org ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: MD400G
On Tue, 2010-11-30 at 16:57 -0800, Niall Parker wrote:
Hello,
Not sure where the best place to post this, I was having trouble with my
MD400G working in Ubuntu 10.10, turned out I had to copy a line for the
MD400 in the 77-mm-ericsson-mbm.rules to get it working.
# Sony-Ericsson MD400G
ATTRS{idVendor}==0fce, ATTRS{idProduct}==d103,
ENV{ID_MM_ERICSSON_MBM}=1
Thanks, added.
Not sure what it all means but before this addition the applet wouldn't
let me enable the modem.
Since the (Sony)Ericsson devices use standard drivers like cdc-acm and
cdc-ether, we don't know that they need special handling unless we tag
them explicitly. It's a good thing they use the standard drivers, so
the tagging bit is a fair compromise.
An additional fix for automatic detection on plugin was needed in
/etc/usb_modeswitch.d/0fce:d103 ... add the following lines
SonyMode=1
Configuration=2
Mind sending a mail with that information to the usb_modeswitch people?
http://www.draisberghof.de/usb_modeswitch/#contrib
that'll allow everyone to benefit from this fix.
The SonyMode line was needed to make it switch, while the
Configuration=2 parameter was needed for Network-Manager to use it. Not
sure what it takes to use the built in GPS (another Configuration and/or
ttyACMx serial port ?)
We don't have GPS support yet for these device yet in MM, but that
should be fairly easy to add if somebody had the time... The commands
are well-known and ModemManager has good location services API that's
already used for celltower positioning if your modem can do it. GPS
would be great though.
Dan
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworManager and openconnect: using cookies
On Mon, 2010-10-11 at 15:09 -0300, muri...@br.ibm.com wrote:
@@ -590,6 +641,11 @@ int nm_process_auth_form (struct openconnect_info
*vpninfo,
keyname = g_strdup_printf(form:%s:%s, form-auth_id,
data-opt-name);
remember_gconf_key(ui_data, keyname, strdup(data-entry_text));
}
+ /* save user password in gnome-keyring */
+ if (data-opt-type == OC_FORM_OPT_PASSWORD) {
+ remember_keyring_key(data-opt-name, strdup(data-entry_text));
+ }
Hrm, why not using the *same* 'keyname' string as we're using for the
TEXT and SELECT cases? There was a reason we included the form-auth_id
in that key.
Other than that, it looks good. Will be nice to extend it to save the
*cookie* too, so that it doesn't have to log in again at all.
--
David WoodhouseOpen Source Technology Centre
david.woodho...@intel.com Intel Corporation
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworManager and openconnect: using cookies
On Thu, 2010-12-02 at 17:53 +, David Woodhouse wrote:
Hrm, why not using the *same* 'keyname' string as we're using for the
TEXT and SELECT cases? There was a reason we included the form-auth_id
in that key.
Patch below should do that. But I notice two problems now I look closer.
Firstly, it's not optional. I think it needs to be; we don't want to
*unconditionally* save the password. Not only for security reasons, but
also because it might be a one-time password.
Secondly, it's saving the password even if the authentication fails.
You'll note that 'remember_gconf_key' doesn't actually set it
immediately; it just *stores* it, and the entry later gets set when the
cookie_obtained() function walks through the ui_data-success_keys list.
(Third problem was that your patch lacked a Signed-off-by)
diff -u b/nm-auth-dialog.c b/nm-auth-dialog.c
--- b/nm-auth-dialog.c
+++ b/nm-auth-dialog.c
@@ -117,6 +117,7 @@
GNOME_KEYRING_ITEM_GENERIC_SECRET,
{
{ vpn_uuid, GNOME_KEYRING_ATTRIBUTE_TYPE_STRING },
+ { form_id, GNOME_KEYRING_ATTRIBUTE_TYPE_STRING },
{ name, GNOME_KEYRING_ATTRIBUTE_TYPE_STRING },
{ NULL, 0 }
}
@@ -498,7 +499,8 @@
}
}
-void remember_keyring_key(const char *name, const char *value)
+void remember_keyring_key(const char *form_id, const char *name,
+ const char *value)
{
char *description;
description = g_strdup_printf(openconnect %s, name);
@@ -507,6 +509,7 @@
description,
value,
vpn_uuid, vpn_uuid,
+ form_id, form_id,
name, name,
NULL);
}
@@ -521,7 +524,7 @@
return result;
}
-char *find_form_password(const char *name)
+char *find_form_password(const char *form_id, const char *name)
{
char *ret = NULL;
char *password;
@@ -530,6 +533,7 @@
res = gnome_keyring_find_password_sync(keyring_password_schema,
password,
vpn_uuid, vpn_uuid,
+ form_id, form_id,
name, name,
NULL);
@@ -583,7 +587,7 @@
if (opt-type == OC_FORM_OPT_PASSWORD) {
/* obtain password from gnome-keyring */
- data-entry_text =
find_form_password(opt-name);
+ data-entry_text =
find_form_password(form-auth_id, opt-name);
} else {
data-entry_text = find_form_answer(form, opt);
}
@@ -644,7 +648,8 @@
/* save user password in gnome-keyring */
if (data-opt-type == OC_FORM_OPT_PASSWORD) {
- remember_keyring_key(data-opt-name,
strdup(data-entry_text));
+ remember_keyring_key(form-auth_id,
data-opt-name,
+
strdup(data-entry_text));
}
}
g_slice_free (ui_fragment_data, data);
--
dwmw2
___
networkmanager-list mailing list
networkmanager-list@gnome.org
http://mail.gnome.org/mailman/listinfo/networkmanager-list
more info on: wifi not working on ubuntu, when it did before upgrade
set of package docs? [y]: Preparing package documentation...OK *** No known documentation files were found. The new package *** won't include a documentation directory. * Debian package creation selected *** * *** Warning: The package name NetworkManager contains upper case *** Warning: letters. dpkg might not like that so I changed *** Warning: them to lower case. This package will be built according to these values: 0 - Maintainer: [ r...@awhite ] 1 - Summary: [ unknown doc files for checkinstall ] 2 - Name:[ networkmanager ] 3 - Version: [ 20101202 ] 4 - Release: [ 1 ] 5 - License: [ GPL ] 6 - Group: [ checkinstall ] 7 - Architecture: [ i386 ] 8 - Source location: [ NetworkManager ] 9 - Alternate source location: [ ] 10 - Requires: [ ] 11 - Provides: [ networkmanager ] Enter a number to change any of them or press ENTER to continue: Installing with make...Installing with install... = Installation results === make: *** No rule to make target `install'. Stop. Installation failed. Aborting package creation. Cleaning up...OK Bye. awh...@awhite:/etc/NetworkManager$ == nm-applet dissapear when NetworkManager daemon is not running. Check it with ps ax | grep NetworkManager. awh...@awhite:~$ ps ax | grep NetworkManager 817 ?Ssl0:00 NetworkManager 1085 ?S 0:00 /sbin/dhclient -d -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf /var/run/dhclient-eth0.pid -lf /var/lib/dhcp3/dhclient-681b428f-beaf-8932-dce4-687ed5bae28e-eth0.lease -cf /var/run/nm-dhclient-eth0.conf eth0 3755 ?S 0:01 xfce4-terminal --geometry=56x3 --display :0.0 --role=Terminal-0x95bbad0-3688-1253980261 --show-menubar --show-borders --hide-toolbars --working-directory /home/awhite --window --geometry=76x35 --display :0.0 --role=Terminal-0x882ead0-3295-1280548273 --show-menubar --show-borders --hide-toolbars --working-directory /home/awhite --window --geometry=81x36 --display :0.0 --role=Terminal-0x8d8c9f8-3552-1283805417 --show-menubar --show-borders --hide-toolbars --working-directory /etc/NetworkManager 6644 pts/1S+ 0:00 grep NetworkManager awh...@awhite:~$ == awh...@awhite:~$ more /var/log/daemon.log | grep Nov 25 Nov 25 09:29:13 awhite modem-manager: Loaded plugin Option High-Speed Nov 25 09:29:13 awhite modem-manager: Loaded plugin Ericsson MBM Nov 25 09:29:13 awhite modem-manager: Loaded plugin Huawei Nov 25 09:29:13 awhite NetworkManager: info Wireless now enabled by radio killswitch Nov 25 09:29:13 awhite NetworkManager:SCPlugin-Ifupdown: (167406320) ... get_connections. Nov 25 09:29:13 awhite NetworkManager:SCPlugin-Ifupdown: (167406320) connections count: 2 Nov 25 09:29:13 awhite NetworkManager: info (eth0): carrier is OFF Nov 25 09:29:13 awhite NetworkManager: info (eth0): new Ethernet device (driver: 'forcedeth') Nov 25 09:29:13 awhite NetworkManager: info (eth0): exported as /org/freedesktop/NetworkManager/Devices/0 Nov 25 09:29:13 awhite modem-manager: Loaded plugin MotoC Nov 25 09:29:13 awhite modem-manager: Loaded plugin Nokia Nov 25 09:29:13 awhite modem-manager: Loaded plugin Gobi Nov 25 09:29:13 awhite NetworkManager: info (eth0): now managed Nov 25 09:29:13 awhite modem-manager: Loaded plugin ZTE Nov 25 09:29:13 awhite NetworkManager: info (eth0): device state change: 1 - 2 (reason 2) Nov 25 09:29:13 awhite modem-manager: Loaded plugin Novatel Nov 25 09:29:13 awhite modem-manager: Loaded plugin Generic Nov 25 09:29:13 awhite modem-manager: Loaded plugin Sierra Nov 25 09:29:13 awhite modem-manager: Loaded plugin Option Nov 25 09:29:13 awhite dhclient: Internet Systems Consortium DHCP Client V3.1.2 Nov 25 09:29:13 awhite dhclient: Copyright 2004-2008 Internet Systems Consortium. Nov 25 09:29:13 awhite dhclient: All rights reserved. Nov 25 09:29:13 awhite dhclient: For info, please visit http://www.isc.org/sw/dhcp/ Nov 25 09:29:13 awhite dhclient: Nov 25 09:29:13 awhite NetworkManager: info (eth0): bringing up device. Nov 25 09:29:13 awhite NetworkManager: info (eth0): preparing device. Nov 25 09:29:13 awhite NetworkManager: info (eth0): deactivating device (reason: 2). Nov 25 09:29:13 awhite NetworkManager: info (eth0): carrier now ON (device state 2) Nov 25 09:29:13 awhite NetworkManager: info (eth0): device state change: 2 - 3 (reason 40) Nov 25 09:29:13 awhite NetworkManager: WARN default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files Nov 25 09:29:13 awhite NetworkManager: info modem-manager is now available Nov 25 09:29:13 awhite NetworkManager: info Trying to start the supplicant... Nov 25 09:29:13 awhite NetworkManager: info Activation (eth0) starting connection 'Ifupdown (eth0)' Nov 25 09:29:13 awhite NetworkManager: info (eth0
more on wifi no longer working under ubuntu
Please note that when it comes to NetworkManager I'm a newbie and a user, not a programmer; my goal is to (AGAIN) have WiFi come up when booting/logging in, as it used to before an automatic upgrade via Ubuntu from 9.04 to 9.? (but before 9.10). This posting is not on the same high technical level as most of the postings here, but the lack of WiFi under Linux is certainly an issue for me. WiFi works just fine under Windows Vista when booting that OS on the same laptop, so the wireless hardware is not an issue. Left to my own resources I'd back up all my /home files and do a fresh install of the latest LTS Ubuntu on that partition, and I'll need to do that SOON, but it surely seems like overkill for what seems (to me) to be a simple mis-configuration or other simple issue. I'm ALMOST there... I think. Thanks for any assistance. Alan One answer to another question on here was use nm-cli to list, start and stop connections. Here's what I got: awh...@awhite:/etc/NetworkManager$ nm-cli nm-cli: command not found awh...@awhite:/etc/NetworkManager$ nmcli nmcli: command not found awh...@awhite:/etc/NetworkManager$ Suggestions? Continuing, the answer said you can connect with VNC to your server to create initial connection settings or you could import/set everything gconftool-2. Does this apply if my server is a wireless router? I will check a discussion about that: http://mail.gnome.org/archives/networkmanager-list/2010-November/msg00082.html; = nm-applet did not appear in the notification area. I killed the process, which was sleeping, and typed: awh...@awhite:/etc/NetworkManager$ nm-applet [1] 5381 awh...@awhite:/etc/NetworkManager$ libnotify-Message: GetServerInformation call failed: Too few arguments in reply libnotify-Message: Error getting spec version ** Message: info No keyring secrets found for phillips/802-11-wireless-security; asking user. ** (nm-applet:5381): WARNING **: security_combo_changed: no active security combo box item. ** (nm-applet:5381): WARNING **: security_combo_changed: no active security combo box item. == At this point the window popped up to ask me the password for my wireless network. The pulldown was grayed out. Only choice available was Cancel. So I chose that: awh...@awhite:/etc/NetworkManager$ ** (nm-applet:5381): WARNING **: applet-device-wifi.c.1643 (get_secrets_dialog_response_cb): canceled ** (nm-applet:5381): WARNING **: _nm_object_get_property: Error getting 'State' for /org/freedesktop/NetworkManager/ActiveConnection/3: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist ** (nm-applet:5381): WARNING **: _nm_object_get_property: Error getting 'Default' for /org/freedesktop/NetworkManager/ActiveConnection/3: Method Get with signature ss on interface org.freedesktop.DBus.Properties doesn't exist ** (nm-applet:5381): DEBUG: old state indicates that this was not a disconnect 9 ** (nm-applet:5381): DEBUG: going for offline with icon: notification-network-wireless-disconnected nm-applet never did appear in the notification area. == https://help.ubuntu.com/9.10/internet/C/troubleshooting-wireless.html#troubleshooting-wireless-connection: Check for device recognition: awh...@awhite:/etc/NetworkManager$ sudo lshw -C network [sudo] password for awhite: *-network description: Ethernet interface product: MCP77 Ethernet vendor: nVidia Corporation physical id: a bus info: p...@:00:0a.0 logical name: eth0 version: a2 serial: 00:1f:16:7f:e7:ac size: 100MB/s capacity: 100MB/s width: 32 bits clock: 66MHz capabilities: pm msi ht bus_master cap_list ethernet physical mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=forcedeth driverversion=0.64 duplex=full ip=192.168.0.71 latency=0 link=yes maxlatency=20 mingnt=1 multicast=yes port=MII speed=100MB/s resources: irq:26 memory:c0009000-c0009fff ioport:30f8(size=8) memory:c0007c00-c0007cff memory:c0007800-c000780f *-network description: Wireless interface product: AR5001 Wireless Network Adapter vendor: Atheros Communications Inc. physical id: 0 bus info: p...@:07:00.0 logical name: wlan0 version: 01 serial: 00:24:2c:6e:54:a2 width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=ath5k latency=0 multicast=yes wireless=IEEE 802.11bg resources: irq:23 memory:c200-c200 awh...@awhite:/etc/NetworkManager$ What should this tell me? = Check for a connection to the router: 1. Open a Terminal (Applications → Accessories → Terminal) and type the command: iwconfig. 2. If the ESSID for our router is shown there may be a problem with ACPI support. Boot the kernel with the pci=noacpi option. awh...@awhite:/etc/NetworkManager$ iwconfig
Re: nm-applet gone from panel
On Tue, 2010-11-30 at 15:06 -0500, Pat Suwalski wrote: Make certain he has the Notification Area in the panel. Try adding a new one to the panel. yes... actually what was happening was the icon was hidden... and still is... :( I removed the Notification Area and added it again in the middle of the top panel but stangelly, after logout-login, even in the middle, the icon is almost invisivle... only a vertical stripe of 1 or 2 pixels width is visible... something like: || oo || oo || o || || || || --- the o's being the visible part of the nm-applet icon !!! :) I don't know why this happens; but it's consistent; I created a new user and did logout-login and the icon gets hidden or something cuts it; I remove the notification bar, I add it again, and it's ok; then I logout-login and it's cut again :P This is Edubuntu-10.04 but the visible part is large enough to allow a minimum interaction; BTW the red (o) shutdown, restart, etc button also goes missing :P a mess... Joao --Pat On 30/11/10 03:01 PM, Joao Ferreira gmail wrote: Hello, A friend of mine showed me a computer in which the nm-applet control icon (top-right corner) does not appear. It used to be there before but - he does not know why - it's gone. I verified the options in System - Preferences - Startup Applications and the nm-applet option is correctly selected. I can not understando why it does not appear. We even tried to create a fresh new user and the applet appears just good for this fresh user. Can anyone point how to restore the nm-applet to the right place for that user ? Thank you. Joao ___ 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: NetworManager and openconnect: using cookies
On 12/02/2010 04:16 PM, David Woodhouse wrote: On Thu, 2010-12-02 at 17:53 +, David Woodhouse wrote: Hrm, why not using the *same* 'keyname' string as we're using for the TEXT and SELECT cases? There was a reason we included the form-auth_id in that key. Patch below should do that. But I notice two problems now I look closer. Thanks David. I appreciated your attention. Firstly, it's not optional. I think it needs to be; we don't want to *unconditionally* save the password. Not only for security reasons, but also because it might be a one-time password. By optional, you mean a save password checkbox in the GUI or a compile-time flag (e.g.: --with-gnome-keyring)? Secondly, it's saving the password even if the authentication fails. You'll note that 'remember_gconf_key' doesn't actually set it immediately; it just *stores* it, and the entry later gets set when the cookie_obtained() function walks through the ui_data-success_keys list. If I understood it correctly, in remember_keyring_key() I should only store form_id, name and value in auth_ui_data and actually save them in gnome-keyring inside cookie_obtained() function. Is that correct? (Third problem was that your patch lacked a Signed-off-by) Thanks for making me aware of this. I'll add it in the next patch. -- Murilo ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
Re: NetworManager and openconnect: using cookies
On Thu, 2010-12-02 at 17:53 -0200, Murilo Opsfelder wrote: By optional, you mean a save password checkbox in the GUI or a compile-time flag (e.g.: --with-gnome-keyring)? The former. Or *some* way of exposing that choice to the user, at least. Web browsers do it differently, with a pop-up after a successful login. Secondly, it's saving the password even if the authentication fails. You'll note that 'remember_gconf_key' doesn't actually set it immediately; it just *stores* it, and the entry later gets set when the cookie_obtained() function walks through the ui_data-success_keys list. If I understood it correctly, in remember_keyring_key() I should only store form_id, name and value in auth_ui_data and actually save them in gnome-keyring inside cookie_obtained() function. Is that correct? Yes. So you're not storing the password when it was *wrong* :) -- dwmw2 ___ networkmanager-list mailing list networkmanager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
