Bug#922554: [Pkg-utopia-maintainers] Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-05 Thread Michael Biebl
Control: reassign -1 src:curl Control: found -1 7.64.0-1 Control: tags -1 + patch fixed-upstream Am 05.03.19 um 10:10 schrieb Dominique Dumont: > On Tue, 05 Mar 2019 09:03:53 +0100 Dominique Dumont wrote: >> They probably patched curl with [1] following the resolution if this curl >> bug [2]. I

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-05 Thread Dominique Dumont
On Tue, 05 Mar 2019 09:03:53 +0100 Dominique Dumont wrote: > They probably patched curl with [1] following the resolution if this curl bug > [2]. I don't know > archlinux enough to track down the patch applied to curl version 7.64.0-9 Never mind. Archlinux 's web site is easy to use. Here's the

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-05 Thread Dominique Dumont
On Sun, 03 Mar 2019 14:23:40 +0100 gpe wrote: > it seems that the issue is resolved with their last curl version 7.64.0-9, no? Looks like it. They probably patched curl with [1] following the resolution if this curl bug [2]. I don't know archlinux enough to track down the patch applied to curl

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-03 Thread gpe
On Sat, 02 Mar 2019 19:49:49 +0100 Dominique Dumont wrote: > On Mon, 18 Feb 2019 01:45:12 +0100 Jiri Palecek wrote: > > exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88) = 0 > >

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-02 Thread Dominique Dumont
On Mon, 18 Feb 2019 01:45:12 +0100 Jiri Palecek wrote: > exe->curl_multi_socket_action(0x15c4900, 24, 2, 0xbfb0bd88) > > = 0 > exe->curl_multi_info_read(0x15c4900, 0xbfb0bd80, 2,

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-03-01 Thread gpe
On Tue, 26 Feb 2019 19:26:30 +0100 Michael Biebl wrote: > Control: tags -1 + moreinfo > > Do you have network-manager-config-connectivity-debian installed or > connectivity checking enabled otherwise? Yes network-manager-config-connectivity-debian is installed > Is the server reachable for the

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-02-26 Thread Jiri Palecek
Hello, On 26. 02. 19 19:26, Michael Biebl wrote: Control: tags -1 + moreinfo Do you have network-manager-config-connectivity-debian installed oh yeah Is the server reachable for the connectivity check reachable? I think so. At least I can't see any connectivity problems. Regards    

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-02-26 Thread Michael Biebl
Control: tags -1 + moreinfo Do you have network-manager-config-connectivity-debian installed or connectivity checking enabled otherwise? Is the server reachable for the connectivity check reachable? -- Why is it that all of the instruments seeking intelligent life in the universe are pointed

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-02-20 Thread gpe92
Package: network-manager Version: 1.14.4-4 Followup-For: Bug #922554 Dear Maintainer, I've exactly the same problem since few days. BR -- System Information: Debian Release: buster/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: amd64 (x86_64) Foreign

Bug#922554: network-manager: NetworkManager continuously spinning, probably while checking for connectivity

2019-02-17 Thread Jiri Palecek
Package: network-manager Version: 1.14.4-4 Severity: normal Dear Maintainer, I've noticed network manager is consuming most of the cpu time on my system. It seems to be caused by the connectivity checking code. The symptoms are: 1. ltrace shows this repeating on and on: exe->epoll_wait(15,