Your message dated Fri, 3 Jun 2016 11:25:14 +0200
with message-id <[email protected]>
and subject line Re: Bug#773525: Randomly excludes available connections [when 
there are too many?]
has caused the Debian Bug report #773525,
regarding Randomly excludes available connections [when there are too many?]
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
773525: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=773525
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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).

Some connections show up more frequently, some less. Consider for instance:

pietro@debiousci:~$ for i in `seq 1 10`; do nmcli c | grep -i condividi; done |
sort
Condividi                             8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi                             8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi                             8a006f93-95ac-4683-a683-56413cbb95bb
802-3-ethernet   --
Condividi                             cab18fac-376f-42cf-9349-d9b4170dacce
802-3-ethernet   --
condividi con dnsmasq                 d54c2a91-f654-4d52-bdbd-cf9d8efdd9e5
802-3-ethernet   --
condividi                              daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                             daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --
condividi                           daa501b5-87eb-4a3f-a6d5-4fa73d042a66
802-3-ethernet   --

So
- one connection, "Condividi", is shown 3 times out of 10
- one connection, "condividi con dnsmasq", is shown 1 time only
- one connection, "condividi", is shown most of the times... with different
space paddings!!!!

Different runs of the above command will clearly give different results, but
some connections are indeed more rare - i.e. "condividi con dnsmasq" usually
shows in none of the 10 tries - and some exhibit (even more than 2) different
space paddings. The wireless connection I need to use at work shows up more or
less once every 100 tries. Which, by the way, is very annoying: it usually
disables autoconnect, makes it virtually impossible to use gnome-control-center
(or the GNOME 3 drop-down menu) to connect, and makes it very hard and time
consuming also with "nmcli c up" (nm-connection-editor is also affected).

This is why the bug is grave: in particular, if a remote server relies on
network-manager in order to connect at startup... you'd better hope it is not
too remote.

The bug was present also with 0.9.10.0-3. My rough guess is that the
problematic upgrade was located between July and September.

P.S: just for info: _most_ of the connections are dropped:
pietro@debiousci:~$ ls /etc/NetworkManager/system-connections | wc
    431     891    8594



-- System Information:
Debian Release: 8.0
  APT prefers testing
  APT policy: (650, 'testing'), (600, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=it_IT.utf8, LC_CTYPE=it_IT.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages network-manager depends on:
ii  adduser                3.113+nmu3
ii  dbus                   1.8.12-1
ii  init-system-helpers    1.22
ii  isc-dhcp-client        4.3.1-5
ii  libc6                  2.19-13
ii  libdbus-1-3            1.8.12-1
ii  libdbus-glib-1-2       0.102-1
ii  libgcrypt20            1.6.2-4+b1
ii  libglib2.0-0           2.42.1-1
ii  libgnutls-deb0-28      3.3.8-5
ii  libgudev-1.0-0         215-7
ii  libmm-glib0            1.4.0-1
ii  libndp0                1.4-2
ii  libnewt0.52            0.52.17-1+b1
ii  libnl-3-200            3.2.24-2
ii  libnl-genl-3-200       3.2.24-2
ii  libnl-route-3-200      3.2.24-2
ii  libnm-glib4            0.9.10.0-3
ii  libnm-util2            0.9.10.0-3
ii  libpam-systemd         215-7
ii  libpolkit-gobject-1-0  0.105-8
ii  libreadline6           6.3-8+b1
ii  libsoup2.4-1           2.48.0-1
ii  libsystemd0            215-7
ii  libteamdctl0           1.12-1
ii  libuuid1               2.25.2-3
ii  lsb-base               4.1+Debian13+nmu1
ii  policykit-1            0.105-8
ii  udev                   215-7
ii  wpasupplicant          2.3-1

Versions of packages network-manager recommends:
ii  crda            3.13-1
ii  dnsmasq-base    2.72-2
ii  iptables        1.4.21-2+b1
ii  iputils-arping  3:20121221-5+b2
ii  modemmanager    1.4.0-1
ii  ppp             2.4.6-3

Versions of packages network-manager suggests:
ii  avahi-autoipd  0.6.31-4+b1
pn  libteam-utils  <none>

-- no debconf information

--- End Message ---
--- Begin Message ---
Version: 1.2.0-1

On Wed, 12 Aug 2015 11:58:36 -0500 Dan Williams <[email protected]> wrote:
> On Fri, 2015-07-17 at 00:35 +0100, Simon McVittie wrote:
> > On 17/07/15 00:13, Dan Williams wrote:
> > > eg, think of it as each contact in Telepathy being an object
> 
> <snip>
> 
> > > The solution here is likely to transition the libnm implementation over
> > > to the ObjectManager interface's GetManagedObjects() method for the
> > > initial setup, to get everything in one call.  A lot of data, but likely
> > > faster than doing it piece-by-piece.
> > 
> > That's what I'd recommend; ObjectManager is precisely for situations
> > where clients are interested in "most" children of a parent object.
> 
> That's the path I'd like to pursue, I did an initial implementation of
> the OM interface for NM git master (what will become 1.2) based on our
> gdbus conversion (which is now merged! hurrah!!!) and filed a bug to
> track its ongoing work:
> 
> https://bugzilla.gnome.org/show_bug.cgi?id=753566


Version 1.2 is in unstable/testing now, Closing the bug accordingly.

Regards,
Michael
-- 
-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

Attachment: signature.asc
Description: OpenPGP digital signature


--- End Message ---
_______________________________________________
Pkg-utopia-maintainers mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-utopia-maintainers

Reply via email to