I ve got Ubuntu Hardy on my Gigabyte device. On matchbox WM+Mobilin Network
Manager works correctly, unlock button and wireless settings are available.
But when i start xfwm+xfce4, this button becomes unclickable, and network
settings are unavailable, even with gksudo. Please, help me!
De: Thiago Teixeira
Enviado el: dom 11/05/2008 0:10
Para: networkmanager-list@gnome.org
Asunto: Edit wireless networks dialog improvement
Hi all,
First of all, I want to congratulate you all on consistently making network
manager a better tool. One of the
On Mon, 2008-05-12 at 18:20 -0400, Tony Espy wrote:
Dan Williams wrote:
On Mon, 2008-05-12 at 17:46 +0200, Khashayar Naderehvandi wrote:
I really might be misunderstanding something here, but deactivating
wireless through nm-applet should in fact (as things are currently
with NM from
The attach patch fixes some syntax sins in the installed headers, which the
compiler barfs on when using -pedantic - this is what the KDE build dashboard
uses.
Will
--- include/NetworkManager.h
+++ include/NetworkManager.h
@@ -129,7 +129,7 @@
typedef enum {
NM_802_11_MODE_UNKNOWN = 0,
On Tue, 2008-05-13 at 13:52 +0200, Will Stephenson wrote:
The attach patch fixes some syntax sins in the installed headers, which the
compiler barfs on when using -pedantic - this is what the KDE build dashboard
uses.
Committed, thanks!
Dan
___
On Sun, 2008-05-11 at 22:36 +0200, Felix Möller wrote:
Hi,
I can successfully connect to my universities wlan with the following
config:
# cat /etc/wpa_supplicant/wpa_supplicant.conf
ctrl_interface=/var/run/wpa_supplicant
ctrl_interface_group=wheel
network={
ssid=uni-ms
On Monday 12 May 2008 13:05:26 Bill Nottingham wrote:
Dan Williams ([EMAIL PROTECTED]) said:
Now, the question is: What does this change screw up???
Originally we did monitor /etc/sysconfig/networking/profiles/default
(which is one of the 3 hardlink locations) but many people expect to
On Friday 09 May 2008 12:38:46 Dan Williams wrote:
For the immediate time, lets pursue a quick fix for the existing inotify
code; I think a small modification to look up the full path in the watch
hash table and then emit the event correctly should work. I'll poke
around with the logs you've
On Sat, May 10, 2008 at 5:42 PM, Nathaniel McCallum
[EMAIL PROTECTED] wrote:
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
However, NetworkManager doesn't work with these devices because HAL
gives them the capability
Gene Czarcinski ([EMAIL PROTECTED]) said:
If /etc/sysconfig/network/scripts/ is the correct main directory, then
system-config-network should be fixed to also use it as the main directory
(I don't see s-c-network going away anytime soon).
s-c-network uses the profile dir itself to maintain
Hi Nathaniel,
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
However, NetworkManager doesn't work with these devices because HAL
gives them the capability and category of net.bluetooth. Attached
are a patch and a
On Tue, 2008-05-13 at 15:20 -0400, Gene Czarcinski wrote:
On Monday 12 May 2008 13:05:26 Bill Nottingham wrote:
Dan Williams ([EMAIL PROTECTED]) said:
Now, the question is: What does this change screw up???
Originally we did monitor /etc/sysconfig/networking/profiles/default
I have a laptop with both a working wireless interface and a working ethernet
wired interface. Normally, I run wireless.
On Fedora 9, if I plug into the wired interface, it is brought up also so I
now have both the wired and wireless interfaces enabled. Fortunately, both
interfaces are on
On Tue, 2008-05-13 at 21:53 +0200, Marcel Holtmann wrote:
Hi Nathaniel,
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
However, NetworkManager doesn't work with these devices because HAL
gives them the
On Tuesday 13 May 2008 15:59:39 Dan Williams wrote:
You actually do want to match the watch descriptor to the one that we're
saving; the patch (while it works) is essentially a big club when we
need to be a bit more elegant. The problem is that the watch
descriptors increase as you add new
On Sat, 2008-05-10 at 14:42 -0700, Nathaniel McCallum wrote:
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
Can you send me the lshal output for when you've got one of these
devices plugged in?
Also, what sets up the
On Tuesday 13 May 2008 15:41:11 Bill Nottingham wrote:
Gene Czarcinski ([EMAIL PROTECTED]) said:
If /etc/sysconfig/network/scripts/ is the correct main directory, then
system-config-network should be fixed to also use it as the main
directory (I don't see s-c-network going away anytime
On Tue, 2008-05-13 at 16:05 -0400, Gene Czarcinski wrote:
I have a laptop with both a working wireless interface and a working
ethernet
wired interface. Normally, I run wireless.
On Fedora 9, if I plug into the wired interface, it is brought up also
so I
now have both the wired and
Fedora 8,
NetworkManager-devel-0.7.0-0.6.7.svn3370.fc8
NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8
NetworkManager-glib-0.7.0-0.6.7.svn3370.fc8
NetworkManager-gnome-0.7.0-0.6.7.svn3370.fc8
NetworkManager-openvpn-0.7.0-8.svn3302.fc8
NetworkManager-glib-devel-0.7.0-0.6.7.svn3370.fc8
Hi Dan,
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
However, NetworkManager doesn't work with these devices because HAL
gives them the capability and category of net.bluetooth. Attached
are a patch
On Tue, May 13, 2008 at 4:11 PM, Dan Williams [EMAIL PROTECTED] wrote:
On Sat, 2008-05-10 at 14:42 -0700, Nathaniel McCallum wrote:
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they emulate an ethernet device.
Can you send me the lshal output for
On Tuesday 13 May 2008 16:32:44 Aaron Konstam wrote:
On Tue, 2008-05-13 at 16:05 -0400, Gene Czarcinski wrote:
I have a laptop with both a working wireless interface and a working
ethernet
wired interface. Normally, I run wireless.
On Fedora 9, if I plug into the wired interface, it is
On Tue, 2008-05-13 at 16:12 -0400, Gene Czarcinski wrote:
On Tuesday 13 May 2008 15:59:39 Dan Williams wrote:
You actually do want to match the watch descriptor to the one that we're
saving; the patch (while it works) is essentially a big club when we
need to be a bit more elegant. The
On Tue, 2008-05-13 at 15:32 -0500, Aaron Konstam wrote:
On Tue, 2008-05-13 at 16:05 -0400, Gene Czarcinski wrote:
I have a laptop with both a working wireless interface and a working
ethernet
wired interface. Normally, I run wireless.
On Fedora 9, if I plug into the wired
On Tue, 2008-05-13 at 17:39 -0400, Nathaniel McCallum wrote:
On Tue, May 13, 2008 at 4:11 PM, Dan Williams [EMAIL PROTECTED] wrote:
On Sat, 2008-05-10 at 14:42 -0700, Nathaniel McCallum wrote:
Bluetooth NAP devices are pretty simple really. You connect and (at
least in Linux) they
On Tue, 2008-05-13 at 17:52 -0400, Gene Czarcinski wrote:
On Tuesday 13 May 2008 16:32:44 Aaron Konstam wrote:
On Tue, 2008-05-13 at 16:05 -0400, Gene Czarcinski wrote:
I have a laptop with both a working wireless interface and a working
ethernet
wired interface. Normally, I run
On Tue, 2008-05-13 at 15:58 -0500, Brian Millett wrote:
Fedora 8,
NetworkManager-devel-0.7.0-0.6.7.svn3370.fc8
NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8
NetworkManager-glib-0.7.0-0.6.7.svn3370.fc8
NetworkManager-gnome-0.7.0-0.6.7.svn3370.fc8
NetworkManager-openvpn-0.7.0-8.svn3302.fc8
Dan Williams escribío:
On Tue, 2008-05-13 at 15:58 -0500, Brian Millett wrote:
Fedora 8,
NetworkManager-devel-0.7.0-0.6.7.svn3370.fc8
NetworkManager-vpnc-0.7.0-0.6.3.svn3109.fc8
NetworkManager-glib-0.7.0-0.6.7.svn3370.fc8
NetworkManager-gnome-0.7.0-0.6.7.svn3370.fc8
Hi Dan,
Unfortunately, I left my cell phone at home. I'll have to provide
lshal output later. However, I don't really think it is necessary.
An Access Point is to wifi what a NAP (Network Access Point) is to
bluetooth.
Right; where does the NAP get defined?
the Bluetooth network
So what is the right way to scan for devices and determine what
features they support? How is that handled in balance with battery
life?
On Tue, May 13, 2008 at 7:38 PM, Marcel Holtmann [EMAIL PROTECTED] wrote:
Hi Dan,
Unfortunately, I left my cell phone at home. I'll have to provide
On Mon, 2008-05-12 at 22:17 +0200, Khashayar Naderehvandi wrote:
We do need to mark the device down when it's disabled; that
somehow went
away when rewriting the device state handling. Should be a
pretty easy
fix in
On Tue, 2008-05-13 at 21:09 -0400, Nathaniel McCallum wrote:
So what is the right way to scan for devices and determine what
features they support? How is that handled in balance with battery
life?
We don't scan with Bluetooth automatically. We should scan when
initially setting up the DUN
If we aren't periodically scanning for bluetooth devices than I assume
we will NEVER autoconnect... Is that the intention?
So for the UI, we'd have something like VPNs?
If that is correct, can you point me to where I need to start in the code?
On Tue, May 13, 2008 at 10:13 PM, Dan Williams
33 matches
Mail list logo
