Am 19.12.2014 um 15:32 schrieb Pietro Battiston: > Package: network-manager > Version: 0.9.10.0-4 > Severity: grave > > Copypasted from a shell: > > pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | wc; done > 127 637 12827 > 127 637 12827 > 127 627 12827 > 126 628 12726 > 127 629 12573 > 127 634 12828 > 127 629 12827 > 127 630 12319 > 127 631 12827 > 127 627 12827 > > > I am clearly not changing my list of available connections (so quick!). So > what > is happening is that network-manager is dropping some of my registered > connections, in a random way. Initially I though "it is unable to handle more > than 127", but then I saw that sometimes it only lists 126. The output of > "nmcli c" is otherwise almost sane (see below).
Seeing the latest upstream release, it noticed the following commit [1]: > dbus: increase 'max_replies_per_connection' limit in D-Bus configuration > D-Bus default limit of replies per connection has been lowered to 128 due to > CVE-2014-3638, see: > http://cgit.freedesktop.org/dbus/dbus/commit/?id=5bc7f9519ebc6117ba300c704794b36b87c2194b > https://bugs.freedesktop.org/show_bug.cgi?id=81053 > > The limit seems to be too low and causes problems in libnm-glib, that will not > return all NetworkManager connection profiles if there are too many of them > (roughly more than the limit). As a consequence, libnm-glib based clients will > not work properly. This looks like it could be the reason for the problem you are seeing. That said, I'm not sure if individual daemon packages overriding the dbus policy in that regard is a good idea (and a proper fix). I've CCed the upstream maintainers of NM and dbus. Maybe we can find a solution for this. Michael [1] http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=2c299ba65c51e9c407090dc83929d692c74ee3f2 -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
