Bug#1057790: linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode

Yes, you're right, my mistake. It should be that one: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/net/ethernet/realtek?h=v6.6.5=fbe43b7f02a2b578d547cec93dbca81e94c0dbb5 Cheers, Timo

Bug#1057790: linux-image-6.5.0-5-amd64: deadlock on RTL8125 in jumbo mtu mode

Package: linux-image-6.5.0-5-amd64 Version: linux-image-6.5.0-5-amd64 Severity: important Dear Maintainer, My RTL8125 NIC stoped working after upgrading the kernel (linux-image-amd64) from version 6.5.10+1 to 6.5.13+1. More specifically, the previous kernel that this meta package depends on

Bug#928300: secure boot via removable media path unavailable

Dear Steve, I just upgraded shim-signed and shim-signed-common to version 1.39+15.7-1; but unfortunately, secure boot still fails with the same message. I also turned on shim debug. A recording of the debug output, which is only visible when disabling secure boot in the (UEFI) BIOS, is

Bug#1023177: sogo: CalDAV/CardDAV synchronization broken due to unexpected UTF-8 BOM in calendar and contact data

It seems that this bug was fixed in version 5.8.0 (upstream). See this commit: https://github.com/Alinto/sogo/commit/d5ad0ddf5d4a8a8b08cffc6f2a2629455c6a4362 Best regards, Timo

Bug#1019857: fetchmail: Running as root is discouraged / no mailservers have been specified

Thanks, László. The issue indeed seems to be gone after disabling the systemd service. Best regards, Timo

Bug#1004350: php-common: Conflict with php7.4

Hi Ondřej, First of all, thanks for maintaining the PHP packages. Much appreciated. I understand from this thread, as well as bug #1004350) that it's intentional that only one version of PHP can be installed on Debian. Nonetheless, I had to find a way to run PHP 7.4 next to PHP 8.1, as two

Bug#928300: secure boot via removable media path unavailable

Dear Chris, Steve, Was there any further follow-up on this issue? It seems that I've got pretty much the same situation here on an Intel DB75EN motherboard. Regarding the keys, pretty much the same situation: - same keys/content in the secure boot signature store (db) - similar contents in

Bug#980503: dnsmasq: incorrect version reported.

Never mind. I had manually upgraded the dnsmasq package and I just noticed that I forgot to also upgrade the corresponding dnsmasq-base package. And therefore, I was actually still running the v2.82 binary. So this bug can be closed. Cheers, Timo

Bug#980503: dnsmasq: incorrect version reported.

Package: dnsmasq Version: 2.83-1 Severity: minor Dear Maintainer, The version reported by dnsmasq seems incorrect. The command 'dnsmasq -v' returns 'Dnsmasq version 2.82 (...)', while the package version is 2.83-1. I think the command should return 'Dnsmasq version 2.83 (...)' instead.

Bug#928661: UnicodeDecodeError for pyzor -s mbox

I believe this bug was fixed in version 1:1.0.0-6. Cheers, Timo

Bug#979984: breaks on check with "NameError: name 'get_binary_stdin' is not defined"

This bug was fixed in version 1:1.0.0-6. Cheers, Timo

Bug#923077: fixed in pyzor 1:1.0.0-5

Addition on the above: this is effectively patch 67b471d upstream: https://github.com/SpamExperts/pyzor/commit/67b471dd168db9468548aef3ffadca9554164ac0#diff-747109b54d67454f173b2571e6d1e7ecef06cae9c26c665477e88ad7a4b5156c This one complements the already included patch 6332a42:

Bug#923077: fixed in pyzor 1:1.0.0-5

Dear maintainer, Related to this one: * [0e1593] Include patch from upstream (Closes: 923077 ) I forgot to report above that this patch on its own isn't enough, as it will throw the following error: internal error, python traceback

Bug#923077: pyzor: crashes on certain emails

I encounter the same issue with the latest version of Pyzor (1:1.0.0-3.1) in testing. I concur with the observations above (by Matthijs) that: - The issue is known, and has been fixed, in upstream: https://github.com/SpamExperts/pyzor/issues/64 - There is unfortunately no new release that

Bug#973472: fetchmail: Fails to connect using SSL

On Sun, 01 Nov 2020 14:25:03 -0800 Bill Wohler wrote: > Thanks for explaining the situation. Sounds like just some bad luck. > Even so, it would still be good if a mechanism could be created that > would prevent this from happening in the future. Yes, some mechanism to prevent this would be

Bug#935133: [Pkg-openssl-devel] Bug#935133: Bug#935133: slow TLS handshake renders browsers and email client unusable

On Thu, 29 Aug 2019 12:28:16 -0700 nbi wrote: > While I may be the first to report this to Debian bugs casual googling > turns up other reports of this to the Internet at large. > > The good news is that the MTU workaround seems to be working as there > has not been any TLS handshake issues

Bug#932290: insserv: Script has overlapping Default-Start and Default-Stop runlevels

Same issue here. I get the following output when upgrading initscripts: Preparing to unpack .../07-initscripts_2.96-5_all.deb ... Unpacking initscripts (2.96-5) over (2.96-4) ... (...) Setting up initscripts (2.96-5) ... Installing new version of config file /etc/init.d/mountdevsubfs.sh ...

Bug#951144: libpam-cap: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file

I haven't seen this anymore after Feb. 23. So I assume it was some temporary glitch indeed.

Bug#951144: libpam-cap: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file

I see the same issue: Feb 23 16:22:06 hostname smbd[522826]: PAM unable to dlopen(pam_cap.so): /lib/security/pam_cap.so: cannot open shared object file: No such file or directory Feb 23 16:22:06 hostname smbd[522826]: PAM adding faulty module: pam_cap.so This started after the upgrade of

Bug#907063: fetchmail: sslcertck fails with GMAIL

The following patch is available upstream: Commit 9b8b6343: https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615 As plain diff: https://gitlab.com/fetchmail/fetchmail/commit/9b8b634312f169fab872f3580c2febe5af031615.diff It would be great if the Debian package

Bug#913088: iptables: nftables layer breaks rule parameter -f , --fragment

Hi Sven, Thanks for submitting this bug report. When I reconfigured my firewall today, I ran into issues and your bug report actually helped me to pinpoint the issue to this specific firewall rule. :) (Note: I don't use package 'arno-iptables-firewall', but I do apply the same rule '-A

Bug#890127: phpldapadmin: phpLDAPadmin uses features that are deprecated in PHP 7.2

Thanks, Luciano! Those patches works fine, indeed. Cheers, Timo

Bug#885348: linux-image-4.14.0-2-amd64: aLatest kernel (linux-image-4.14.0-2-amd64) breaks e1000e driver on Intel 82579V Gigabit adapter

Hi Salvatore, On 26-12-2017 16:37, Salvatore Bonaccorso wrote: Hi Timo, On Tue, Dec 26, 2017 at 03:38:24PM +0100, T.A. van Roermund wrote: Package: src:linux Version: 4.14.7-1 Severity: critical Tags: patch upstream Justification: breaks the whole system Dear Maintainer, This morning, I

Bug#636592: horde3: New versions of horde are available: 3.3.12 and 4.0.8

Package: horde3 Version: 3.3.8+debian0-2 Severity: wishlist There are new versions available, v3.3.12 and - more importantly - v4.0.8. Could you please add these versions to the Debian testing repository? Best regards, Timo van Roermund -- System Information: Debian Release: wheezy/sid APT

Bug#623306: Plugin config files should be moved to /etc (e.g. /etc/phpsysinfo/plugins/*)

Package: phpsysinfo Version: 3.0.10-1 Severity: important The new phpsysinfo version supports plugins, which have their own configuration files. The default location of these configuration files is /usr/share/phpsysinfo/plugins/plugin-name/plugin-name.config.php. Just like the main

Bug#589924: dnsmasq: Add stop-dns-rebind to default config file to prevent DNS rebinding attacks

Package: dnsmasq Version: 2.55-1 Severity: wishlist Recently, there is a lot of fuzz around DNS rebinding attacks. I think it is a good idea to add the 'stop-dns-rebind' option to the default configuration file for Debian in order to prevent such attacks. -- System Information: Debian