Your message dated Wed, 30 Nov 2022 14:50:27 +0100 with message-id <12103362.O9o76ZdvQC@bagend> and subject line Re: libc6: Version 2.36-6 causes intermittent network resolution/connection failures has caused the Debian Bug report #1025152, regarding libc6: Version 2.36-6 causes intermittent network resolution/connection failures 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 owner@bugs.debian.org immediately.) -- 1025152: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1025152 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libc6: Version 2.36-6 causes intermittent network resolution/connection failures
- From: Diederik de Haas <didi.debian@cknow.org>
- Date: Wed, 30 Nov 2022 12:15:41 +0100
- Message-id: <[🔎] 166980694170.11075.15311460011492078103.reportbug@prancing-pony.home.cknow.org>
Package: libc6 Version: 2.36-6 Severity: important -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Since upgrading to 2.36-6 I regularly, but not always, get network resolution/connection failures, most visibly in Firefox, but the same issue has also occured with qutebrowser and on different devices with version 2.36-6. With 2.36-5 I did not get those failures. "An error occurred during a connection to site.tld" is the error I'm getting. If I "F5" often/long enough, it usually does load the site at some point, but it is annoying. I've rebooted all the relevant network devices (routers/switches) in my LAN and that didn't resolve the issue, but downgrading to 2.36-5 seems to resolve the issue (I haven't seen the issue since on 1 PC). Severity important seems the most appropriate given the issues, so I choose that, but I think it should be prevented from transitioning to Testing, which 'important' will not do. I'll leave it up to a maintainer make it RC (or not). - -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (990, 'testing'), (500, 'stable-security'), (500, 'unstable'), (500, 'stable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 6.0.0-5-amd64 (SMP w/4 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages libc6 depends on: ii libgcc-s1 12.2.0-9 Versions of packages libc6 recommends: ii libidn2-0 2.3.3-1+b1 Versions of packages libc6 suggests: ii debconf [debconf-2.0] 1.5.80 pn glibc-doc <none> ii libc-l10n 2.36-6 ii libnss-nis 3.1-4 ii libnss-nisplus 1.3-4 ii locales 2.36-6 - -- debconf information: glibc/restart-failed: glibc/kernel-not-supported: glibc/disable-screensaver: * libraries/restart-without-asking: true * glibc/upgrade: true glibc/kernel-too-old: glibc/restart-services: -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQT1sUPBYsyGmi4usy/XblvOeH7bbgUCY4c7VAAKCRDXblvOeH7b bpM2AQDv4zrChnxculyDj45RaT8S5pKQqc65yylRfTsE8lpreQEAkBlZCylgiyF6 iF1tm6PCxsNE+VsNRmjvTkB/31x2/wI= =9VtK -----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
- To: 1025152-done@bugs.debian.org
- Subject: Re: libc6: Version 2.36-6 causes intermittent network resolution/connection failures
- From: Diederik de Haas <didi.debian@cknow.org>
- Date: Wed, 30 Nov 2022 14:50:27 +0100
- Message-id: <12103362.O9o76ZdvQC@bagend>
- In-reply-to: <[🔎] 166980694170.11075.15311460011492078103.reportbug@prancing-pony.home.cknow.org>
On 30 Nov 2022 12:15:41 +0100 Diederik de Haas <didi.debian@cknow.org> wrote: > Package: libc6 > Version: 2.36-6 > Severity: important > > I've rebooted all the relevant network devices (routers/switches) in my > LAN and that didn't resolve the issue, but downgrading to 2.36-5 seems > to resolve the issue (I haven't seen the issue since on 1 PC). It's (far) less frequent (so far), but it did happen again, so must be some other issue.Attachment: signature.asc
Description: This is a digitally signed message part.
--- End Message ---