The previous upload is still in -proposed. There also needs to be a new
upload from lp_1511735_libnl3_v3.diff
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage not
I've done some more verification tests by installing as many of the
reverse depends on libnl to see if any other package implodes like
Network-Manager did.
Sniff Check OK: Tested by install and invoke binaries.
batctl
bmon
ipvsadm
keepalived
libfsobasics3
libnetcf1
libnl-3-200-dbg
libnl-3-d
v3 debdiff
- Removed unneeded spaces in debian/control Breaks entry
- Fixed up libnl-3-200.symbols file to tag private symbols as optional
(removes dpkg-gensymbols warning)
- Removed invalid use of Closes() for Debian bugs; instead use LP: #
** Patch added: "lp_1511735_libnl3_v3.diff"
I've updated the debdiff to include a Breaks: network-manager (<<
0.9.8.8-0ubuntu7.3) to ensure that users are forced to use the newer
network-manager (ie, this libnl won't install unless user has already
updated their network-manager) Thanks Mathew for the suggestion.
I've built and tested thi
There should probably be a new upload of libnl3 with
Breaks: network-manager (<< 0.9.8.8-0ubuntu7.3)
so users can't put their system into a broken state when both packages
are released to -updates.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is s
** Description changed:
[Triage Notes]
The proposed fix for this bug in libnl3 caused a regression in trusty-
- proposed, tracked in bug 1511735. The regression is caused by a latent
+ proposed, tracked in bug 1539634. The regression is caused by a latent
bug in Network Manager. We expect
this is pure sabotage? expunge the traitors!!!
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notifications about this b
This has not been released; this version is only available in trusty-
proposed. It's not been verified at this point.
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Released => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which i
I've retagged this as verification-needed since we've had one regression
(NetworkManager, a bug there) and we'd like to request other users of
libnl to test out the version included in proposed so we can ensure
we're flushing out other applications that may be exposed due to the
behavior changed in
** Changed in: libnl3 (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
** Description changed:
+ [Triage Notes]
+
+ The proposed fix for this bug in libnl3 caused a regression in trusty-
+ proposed, tracked in bug 1511735. The regression is caused by a latent
+ bug in Network Manager. We expect to fix this by landing a fix for the
+ bug in Network Manager in trusty-
** Changed in: libnl3 (Debian)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notific
Same problems as above hit me today after an update on my Ubuntu 14.04.3
LTS machine. After applying updates, networking ceased to function.
Downgraded libnl* and now networking is working again.
Luckily I was able to do the downgrade by first using recovery options
at boot from GRuB. From ther
Hi Ryan,
thank you very much for your quick help. That worked fine!
Best regards, Nick
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink soc
Hi Nick,
We've not built a new NetworkManager package with the fix. For now,
you'll need to downgrade your libnl-3 packages:
% apt-get install libnl-3-200=3.2.21-1 libnl-genl-3-200=3.2.21-1 libnl-
route-3-200=3.2.21-1
And you may need to apply a hold until a fix for NetworkManager can be
releas
Dear Ryan,
I am fighting with the same problem. So I also have to apply this patch to get
my network working again.
Can you tell me wurde I can find these deb-packages?
Thank you very much in advance!
Nico
--
You received this bug notification because you are a member of Ubuntu
Server Team, whic
I've filed
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634 to track
the updated needed there.
I attached a debdeff in the NM bug after applying the patches from comment #24.
I tested the updated NM with proposed libnl-3 and it works as expected.
1. Download 14.04.03 De
** Tags removed: verification-done
** Tags added: verification-failed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage not
Sure. Let me know if you need some help.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notifications about this bug go
Thanks Nicolas. I'm working on fixing up NetworkManager; we'll need
that fix as well to go out at the sametime.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: f
Looks like the changes in libnl exposed a bug in the N-M 0.98 code:
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf
--
You r
Tests are OK for us.
Here is a screen shot of the manuel test:
root@ubuntu1404:~# apt-get install libnl-3-200/trusty-proposed
libnl-3-dev/trusty-proposed libnl-genl-3-200/trusty-proposed
libnl-genl-3-dev/trusty-proposed libnl-nf-3-200/trusty-proposed
libnl-nf-3-dev/trusty-proposed libnl-route-3
Hi Jakub,
Thanks for testing the new package. It would be helpful to collect any
core files and backtraces.
apport-collect -p network-manager 1511735
Should collect the info for this bug report.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is sub
Hi,
after automatic update of packages libnl-3-200, libnl-route-3-200, and
libnl-genl-3-200 to version 3.2.21-1ubuntu1
in my 64-bit Ubuntu 14.04-LTS the network-manager ceased working.
/var/log/syslog shows:
init: network-manager main process (1057) killed by SEGV signal
init: network-manager m
Hello Nicolas, or anyone else affected,
Accepted libnl3 into trusty-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/libnl3/3.2.21-1ubuntu1
in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See
https://w
** Changed in: libnl3 (Ubuntu)
Importance: Undecided => Medium
** Changed in: libnl3 (Ubuntu Trusty)
Importance: Undecided => Medium
** Changed in: libnl3 (Ubuntu Trusty)
Status: New => Triaged
** Tags added: patch
--
You received this bug notification because you are a member of
Nicolas,
Thanks for the ping. I'm looking for a sponsor to review the update.
If approved, then it'll get uploaded and continue through the SRU
process.
Thanks again for following up on this.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscri
Ryan, do you know when the ubuntu-14.04 will have the new libnl3
package?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage
** Changed in: libnl3 (Debian)
Status: Unknown => New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notification
** Also affects: libnl3 (Debian) via
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808213
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bug
The bug report on debian has been created: https://bugs.debian.org/cgi-
bin/bugreport.cgi?bug=808213
** Bug watch added: Debian Bug tracker #808213
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=808213
--
You received this bug notification because you are a member of Ubuntu
Server Team, whi
On Wed, Dec 16, 2015 at 11:29 AM, Nicolas Dichtel wrote:
> Thank you.
>
> Note that the last three patches are not included in libnl 3.2.26, which
> is the version of ubuntu 16.04 /Xenial (
> https://launchpad.net/ubuntu/+source/libnl3/3.2.26-1).
>
Thank you for mentioning this.
> Should I mak
Thank you.
Note that the last three patches are not included in libnl 3.2.26, which is the
version of ubuntu 16.04 /Xenial
(https://launchpad.net/ubuntu/+source/libnl3/3.2.26-1).
Should I make a new series for this version or will the libnl 3.2.27 be
included in Xenial?
--
You received this b
Tarball of the test-case used to confirm failure and fix.
** Attachment added: "lp_1511735_test.tar"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535781/+files/lp_1511735_test.tar
** Description changed:
- The following upstream patches are needed in order to av
Attaching debdiff with changes needed to resolve the bug.
** Patch added: "lp_1511735_libnl3.diff"
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1511735/+attachment/4535780/+files/lp_1511735_libnl3.diff
--
You received this bug notification because you are a member of Ubuntu
Server T
Yes you're right. Here is an updated tar file with all patches (the first four
patches are the same).
The following patches are added:
- 9614acf4c435 lib/nl: preserve s_local if nl_connect() fails
https://github.com/thom311/libnl/commit/9614acf4c435
- f78c3e82398a socket: clear port when unable
Hi,
Thanks for the quick update. I've applied the 4 patches and built a new
test package with the changes.The example test does indeed fail on
the current version and passes on the new version as well.
I went looking for any other libnl3 tests we might run to catch any
possible regression th
The enclosed tar file contains the updated test script and the 4 patches
that can be applied cleanly over the ubuntu libnl3-3.2.21.
Before the patches:
$ if ./example.sh ; then echo success ; else echo failure ; fi
gcc -o example -I/usr/include/libnl3 example.c -lnl-3 -lnl-genl-3
set manually the
Initial look at the patches results in the following assessment:
The first 2 patches apply fine to the version included in Ubuntu Trusty
027157898708 lib/socket: don't fail if no more local ports can be assigned in
nl_socket_alloc
http://git.infradead.org/users/tgr/libnl.git/commitdiff/027157898
Ryan, please could you take a look at this? I've taken a brief look at
the patches and I follow what they're achieving and why, but I'm not
confident that I follow all possible edge cases introduced by these
patches.
If you're satisfied then please could you prepare an SRU? Thanks!
** Changed in:
>Thank you for your response. It looks like this is fixed in Wily then,
which is on 3.2.26, so this bug affects 14.04 only?
Yes.
>I'm concerned that this changes library behaviour. How can we be sure
that no existing users of libnl will not be regressed by this change in
behaviour if we backport
** Tags added: 6wind
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notifications about this bug go to:
https://bugs.l
For now I'm marking this Fix Released as it is fixed in Wily, and
opening a task for Trusty (which depending on what we decide may end up
being Won't Fix).
** Changed in: libnl3 (Ubuntu)
Status: New => Fix Released
** Also affects: libnl3 (Ubuntu Trusty)
Importance: Undecided
Sta
Thank you for your response. It looks like this is fixed in Wily then,
which is on 3.2.26, so this bug affects 14.04 only?
I'm concerned that this changes library behaviour. How can we be sure
that no existing users of libnl will not be regressed by this change in
behaviour if we backport this to
It affects ubuntu-14.04, libnl version 3.2.21
(http://packages.ubuntu.com/trusty/libnl-3-200)
The first libnl upstream release which includes these patches is 3.2.25.
The problem happens when the libnl choose a port id already used by
another application. The libnl fails instead of trying another
Thank you for taking the time to report this bug and helping to make
Ubuntu better.
Which Ubuntu releases and libnl3 package versions are affected, please?
Which upstream release first included these patches? And please could
you provide your failure use cases so that we can decide on importance
a
Any news?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl: fail to bind() netlink sockets
To manage notifications about this bug go to:
https://bugs.launchpad.ne
** Also affects: libnl3 (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libnl3 in Ubuntu.
https://bugs.launchpad.net/bugs/1511735
Title:
libnl
50 matches
Mail list logo
