Bug#1104094: dhcpcd gets stuck after system reboot

No, I didn't. I also haven't experienced it anymore using version 1:10.2.2-5/6 from experimental. Cheers, Timo

Bug#1104094: dhcpcd gets stuck after system reboot

I understand that. Unfortunately, I have no clue which patch(es) would fix this issue. We can keep an eye on the ticket upstream, maybe we get some hints there. Cheers, Timo

Bug#1104094: dhcpcd gets stuck after system reboot

Package: dhcpcd Version: 1:10.1.0-9 Severity: important Dear Maintainer, I've encountered an issue that I've initially reported upstream: https://github.com/NetworkConfiguration/dhcpcd/issues/503 However, I just installed version 1:10.2.2-5 from experimental and it seems that this does has fix

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

> I'm currently traveling, with no access to my printer. Etienne, would you be able to produce such log in the coming days? Otherwise, I will look at it on my side when I'm back. I'm back home and managed to create log files. See: https://bugzilla.samba.org/show_bug.cgi?id=15836#c3 Cheers,

Bug#1101581: fixed in samba 2:4.22.0+dfsg-3

FYI -- there is an updated patch available that avoids compile errors on platforms that do not support O_PATH: https://gitlab.com/samba-team/samba/-/merge_requests/4018 Cheers, Timo

Bug#1101581: samba: symlink issue in samba 4.22

I have tested this (preliminary) patch and it seems to resolve the issue: https://bugzilla.samba.org/attachment.cgi?id=18624 See also: https://bugzilla.samba.org/show_bug.cgi?id=15841#c5 Cheers, Timo

Bug#1101581: samba: symlink issue in samba 4.22

Package: samba Version: 2:4.22.0+dfsg-2 Severity: important Dear Maintainer, In samba 4.22, symlinks (wide links) are not working correctly anymore. Specifically, moving files within a sylink'ed location fails. I've already reported the issue upsteam. See: https://bugzilla.samba.org/show_bug.c

Bug#1100604: Acknowledgement (PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0)

FYI - the patch that I validated to work for me, is the following: https://gitlab.com/samba-team/samba/-/merge_requests/4013.diff I've manually rebuilt the package following this guide: https://wiki.debian.org/BuildingTutorial#Get_the_source_package More specifically, using these steps: apt i

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

A patch was made available. See: https://gitlab.com/samba-team/samba/-/merge_requests/4013 https://bugzilla.samba.org/show_bug.cgi?id=15836 I will validate/confirm the fix when a new release is available. Cheers, Timo

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

> Also, for anyone who can repro this, please at least post smb.log > with log level 5, complete interaction between samba and the client > up to the assertion failure. I'm currently traveling, with no access to my printer. Etienne, would you be able to produce such log in the coming days? Otherw

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

Thanks for looking into this. I'm not sure if it's relevant, but the printer that triggers the panic is using an older protocol version (SMB2_02). In my config, I have this line: server min protocol = SMB2_02 When I increase this minimum version number, then the printer can no longer access

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

On Mon, 17 Mar 2025 20:11:47 + Etienne Dechamps wrote: > Some additional information: > > Excerpt from my smb.conf: > > unix extensions = no > wide links = yes > kernel oplocks = yes > use sendfile = yes > ea support = no > > Notably, `kernel oplocks = yes` is not the default, which may expl

Bug#1100604: Acknowledgement (PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0)

Now with the correct link: https://snapshot.debian.org/package/samba/ This version (4.21.4) works for me: https://snapshot.debian.org/package/samba/2%3A4.21.4%2Bdfsg-1/ Cheers, Timo

Bug#1100604: Acknowledgement (PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0)

You can download them here: https://snapshot.debian.org/binary/samba/ Cheers, Timo

Bug#1100604: Acknowledgement (PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0)

Additional information: I can confirm that this issue was introduced in version 4.22. When I revert the packages to 4.21, it works again without panics. So specifically: - downgrade samba* from 2:4.22.0+dfsg-1+b1 to 2:4.21.4+dfsg-1 - downgrade libldb2 from 2:2.11.0+samba4.22.0+dfsg-1+b1 to 2:2

Bug#1100604: PANIC: assert failed at source3/smbd/smb2_oplock.c(156): sconn->oplocks.exclusive_open>=0

Package: samba Version: 2:4.22.0+dfsg-1+b1 Severity: important Dear Maintainer, Since a recent update of the samba package, samba panics when one client (a HP Color LaserJet Pro MFP M477fdw printer) tries to access a share. Before, this worked without any issue. The panis log: [2025/03/15 23:

Bug#1098311: AH01630: client denied by server configuration: /usr/lib/GNUstep

Thanks for the prompt response. With these changes it indeed works again. On February 19, 2025 9:29:33 AM GMT+01:00, Yavor Doganov wrote: >Yavor Doganov wrote: >> > Include /usr/share/doc/sogo/apache.conf >> >> Yes, it's due to the switch to the multiarch layout. Does it work if >> you change

Bug#1098311: AH01630: client denied by server configuration: /usr/lib/GNUstep

Package: sogo Version: 5.11.2-3 Severity: normal Dear Maintainer, After upgrading to version 5.11.2-3, SOGo is no longer displaying correctly. I also see the following error multiple times in /var/log/apache2/error.log: [authz_core:error] ... AH01630: client denied by server configuration: /us

Bug#1091683: spamassassin: Multiple warnings "Use of uninitialized value $_"

Thanks, Noah. I will certainly add another update here in case I would see the same warnings again, despite having applied this patch. Note that I didn't see the issue reoccur so far, even without the patch. Which seems to be because a specific set of conditions needs to be met before it is

Bug#1091683: spamassassin: Multiple warnings "Use of uninitialized value $_"

According to the upstream bug report, the issue was already resolved and the fix should be part of the next release. The patch can be found here: https://svn.apache.org/viewvc/spamassassin/trunk/lib/Mail/SpamAssassin/Plugin/PDFInfo.pm?r1=1919365&r2=1919364&pathrev=1919365 It is unclear (to me)

Bug#1091683: spamassassin: Multiple warnings "Use of uninitialized value $_"

Package: spamassassin Version: 4.0.1-2 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** Since recently, I see the following messages in the syslog: Use of uninitialized value $_ in pattern match (m//) at /usr/share/perl5/Mail/Spam

Bug#1073969: samba: Referenced but unset environment variable evaluates to an empty string

Package: samba Version: 2:4.20.2+dfsg-2 Severity: minor Dear Maintainer, The smbd and nmbd services throw the following warnings when they get started: (smbd)[75315]: smbd.service: Referenced but unset environment variable evaluates to an empty string: SMBDOPTIONS (nmbd)[75101]: nmbd.service: R

Bug#1073252: samba: INTERNAL ERROR: Signal 11: Segmentation fault in smbd

After skimming through many other samba-related bug reports, I finally found another one that seems very similar: https://bugzilla.redhat.com/show_bug.cgi?id=2282238 It's also tracked here: https://bugzilla.samba.org/show_bug.cgi?id=15659 Assuming this is indeed the same issue, then it's somet

Bug#1073252: samba: INTERNAL ERROR: Signal 11: Segmentation fault in smbd

Package: samba Version: 2:4.20.1+dfsg-5 Severity: important Dear Maintainer, Since the end of March, smbd sporadically crashes with the following error: INTERNAL ERROR: Signal 11: Segmentation fault in smbd I´m not sure what causes this. It was working stable before and my Samba configuration h

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&id=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 (p

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 avail

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 w

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 t

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. Cheers,

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: https://githu

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 incor

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 goo

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 si

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 ... insse

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 pack

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 c

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 INPUT

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 upd

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//.config.php. Just like the main configuration file, these files s

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 Release