I've reverted the udev usage and test now for 'easytether' when checking
for the driver and assign driver to 'easytether' if so. I've diff'ed vs
latest git, but tested vs 0.8.4 rc1 and it works fine for me.
Torsten
diff --git a/src/nm-udev-manager.c b/src/nm-udev-manager.c
index 853c4fe..f20fe78
Hi,
I tried to compile 0.8.4-rc1 on Ubuntu 10.04 LTS. For me the autogen.sh
script fails upon the tools directory:
tools/Makefile.am:1: required directory tools/tools does not exist
Makefile.am: installing `./INSTALL'
autoreconf: automake failed with exit status: 1
When removing that directory
Hello,
I try to 'clone' a wireless system connection to several machines. My
naive attempt was to copy the file
from /etc/NetworkManager/system-connections/file on a master machine
to a package and then install the package on the cloned systems. While
the connection can be seen, when I try to
Hello,
I've changed the hack to now check for a udev environment variable
'NM_PSEUDODRIVER'. If set, the lack of a driver is ignored.
The /etc/udev/rules.d/easytether.rules declares this if an easytether0
device is detected.
If need be I can revert it to check for 'easytether' in the code, but I
On Wed, 2011-03-16 at 15:50 -0500, Dan Williams wrote:
...
That said, the best way to go about this is likely to use udev scripts
to initially create the easytether0 interface, and then we could add
some custom code to NM to recognize the easytether0 interface as a
normal ethernet device and
Hello Phil,
On Sun, 2011-03-06 at 09:48 +, Phil Thompson wrote:
...
I now have the am PPA and still the same error
checking for DBUS... yes
checking for GLIB... no
configure: error: Package requirements (gthread-2.0 glib-2.0 = 2.26
gobject-2.0) were not met:
Requested 'glib-2.0 =
After some hacking at the debian files the Network Manager built in the
PPA for Lucid, though the applet is still outstanding. It depends on gtk
+3 = 2.91.4, which seems to be quite a huge dependency.
Torsten
___
networkmanager-list mailing list
On Sun, 2011-03-06 at 17:14 +, Phil Thompson wrote:
...
it did move me forward to the next glitch :-
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for DBUS... yes
checking for GLIB... yes
checking for GMODULE... yes
On Sun, 2011-03-06 at 17:12 +, Phil Thompson wrote:
On Sun, 2011-03-06 at 16:11 +0100, Torsten Spindler wrote:
After some hacking at the debian files the Network Manager built in
the PPA for Lucid, though the applet is still outstanding. It depends
on gtk+3 = 2.91.4, which seems
On the gtk+3 dependency, I've found the --with-gtkver=2 option for
autogen.sh. Unfortunately the command errs with this message:
$ ./autogen.sh --with-gtkver=2You should add the contents of
'/usr/share/aclocal/intltool.m4' to 'aclocal.m4'.
configure: WARNING: unrecognized options:
Following up on this, I go further with running the auto toolchain
commands:
* Run autogen.sh with --gtkver=2 and other autotools to get there:
- aclocal
- autoconf
- autoheader
- automake -a
The network-manager-applet package is being upload to the PPA now,
hopefully it will
On Sat, 2011-03-05 at 20:06 +0100, Torsten Spindler wrote:
...
You can get a backported dbus-glib from this PPA on Launchpad:
https://launchpad.net/~mathieu-tl/+archive/ppa/
Works fine for me.
I discovered I had already installed the following packages from
Maverick on my test machine
Hello,
a 3G modem is no longer recognized by modem-manager when the system
resumes. It seems the USB identification changes upon resume, from
usb6/6-1 to usb6/6-2. This might be caused by udev rules?
I've collected some logs here on Launchpad:
dmesg after resume:
On Wed, 2010-03-31 at 21:35 -0400, Yclept Nemo wrote:
... Furthermore ubuntu just implemented a
complete interface redesign after a lengthy evaluation of many
individual components and applications. I'm sure you could find
someone on one of the ubuntu teams to provide a much more professional
Hello,
On Thu, 2010-04-01 at 20:52 +1300, Simon Geard wrote:
...
Your link doesn't seem to be publicly accessible - I get You are not
allowed to view this page when I click on it...
you are right. My wrong for sending out an internal link. I guess the
work results will be published some time
On Fri, 2010-01-22 at 14:42 -0800, Dan Williams wrote:
On Fri, 2010-01-22 at 11:49 +0100, Torsten Spindler wrote:
Hello,
there seems to be a problem for some devices which modemmanager probes
over the serial line. Namely Palm devices [1] and a Smart Card reader
[2]. Is there any
On Tue, 2010-03-02 at 09:43 +0100, Alessandro Bono wrote:
...
-d -4 -sf /usr/lib/NetworkManager/nm-dhcp-client.action -pf
/var/run/dhclient-eth0.pid -lf
/var/lib/dhcp3/dhclient-7ee3e5ee-deb8-46e7-9440-86db49cfdcdd-eth0.lease -cf
/var/run/nm-dhclient-eth0.conf eth0
Seems that the -4 is not
Hello Alessandro,
the latest network-manager needs dhclient version 4, Ubuntu only ships
version 3. I tried to compile network-manager with the options
--with-dhclient=no --with-dhcpcd=yes
but it still seems to want to use dhclient. As a test I packaged
dhclient version 4 and it seems to work.
On Fri, 2010-01-22 at 14:42 -0800, Dan Williams wrote:
...
when you get a bug like this, try getting the user to (1) stop NM and
MM, (2) plug the device in, and (3) run the lsudev utility included in
the modem-manager sources in test/ like so:
sudo lsudev tty
and then hit Ctrl+C and get
Hello,
there seems to be a problem for some devices which modemmanager probes
over the serial line. Namely Palm devices [1] and a Smart Card reader
[2]. Is there any possibility to make the probing configurable?
There seems to be a work around available by removing
20 matches
Mail list logo
