Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On Fri, Feb 24, 2023 at 09:50:47PM +0100, Sebastian Andrzej Siewior wrote: > On 2023-02-24 12:44:49 [-0800], Nye Liu wrote: > > On Fri, Feb 24, 2023 at 09:39:03PM +0100, Sebastian Andrzej Siewior wrote: > > > Can you re-install libtfm1 and ensure that both point to that lib? >

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On Fri, Feb 24, 2023 at 09:39:03PM +0100, Sebastian Andrzej Siewior wrote: > Can you re-install libtfm1 and ensure that both point to that lib? libtfm1 0.13-4.1 fixed the problem. Should probably be version bumped in the pkg dependency, 0.13.1-1 seems broken.

Bug#1031896: [Pkg-clamav-devel] Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

On Fri, Feb 24, 2023 at 09:16:06PM +0100, Sebastian Andrzej Siewior wrote: > Is this a debian box or do you have other additions? No other additions, pure sid > You could set Debug true in /etc/clamav/clamav.conf and check what the > additionial debug says. Feb 24 12:09:38 ln

Bug#1031896: Acknowledgement (libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis)

Feb 24 10:09:35 ? freshclam[1499626]: Fri Feb 24 10:09:35 2023 -> Received signal: wake up Feb 24 10:09:35 ? freshclam[1499626]: Fri Feb 24 10:09:35 2023 -> ClamAV update process started at Fri Feb 24 10:09:35 2023 Feb 24 10:09:36 ? freshclam[1499626]: Fri Feb 24 10:09:36 2023 -> daily.cvd

Bug#1031896: libclamav11: LibClamAV Error: Can't verify database integrity, breaks amavis

Package: libclamav11 Version: 1.0.1+dfsg-1 Severity: critical Justification: breaks unrelated software Dear Maintainer, * What led up to the situation? sudo service clamav-daemon stop sudo service clamav-daemon start * What exactly did you do (or not do) that was effective (or

Bug#1027130: libclamav11: LibClamAV Error: Can't verify database integrity

Feb 24 10:09:35 ? freshclam[1499626]: Fri Feb 24 10:09:35 2023 -> Received signal: wake up Feb 24 10:09:35 ? freshclam[1499626]: Fri Feb 24 10:09:35 2023 -> ClamAV update process started at Fri Feb 24 10:09:35 2023 Feb 24 10:09:36 ? freshclam[1499626]: Fri Feb 24 10:09:36 2023 -> daily.cvd

Bug#1027130: libclamav11: LibClamAV Error: Can't verify database integrity

Package: clamav-daemon Version: 1.0.1+dfsg-1 Followup-For: Bug #1027130 Dear Maintainer, * What led up to the situation? sudo service clamav-daemon stop sudo service clamav-daemon start * What exactly did you do (or not do) that was effective (or ineffective)? Mirrored working cvds

Bug#1019425: See also 939392

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=939392

Bug#939392: See also 1019425

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1019425

Bug#939392: please provide kmodsign like Ubuntu does

Same here Building module: Cleaning build area... 'make' KVER=5.19.0-2-amd64 src=/usr/src/rtl88x2bu-5.8.7.1... Signing module /var/lib/dkms/rtl88x2bu/5.8.7.1/build/88x2bu.ko /usr/sbin/dkms: line 1055: kmodsign: command not found Cleaning build

Bug#981236: miniupnpd: Syslogging is overly verbose due to the -d option

Package: miniupnpd Version: 2.2.1-1 Severity: normal The miniupnpd systemd unit file sets the -d option to foreground it. However, that is extremely verbose. It may be better to set `start_daemon` false in the config file instead. -- System Information: Debian Release: bullseye/sid APT

Bug#944738: Also occurs with openjdk-14-jdk 14.0.1+7-1

This bug is nearly a year old. Is anyone working on it?

Bug#960871: linux-image-amd64: iwlwifi: iwl_mvm_enable_txq NULL pointer dereference, address: 0000000000000068

Package: src:linux Version: 5.6.7-1 Severity: grave Tags: upstream Justification: renders package unusable This OOPS renders system unusable: May 17 06:28:33 kernel: [541237.462244] BUG: kernel NULL pointer dereference, address: 0068 May 17 06:28:33 kernel: [541237.462252] #PF:

Bug#952831: golang-go: Update to 1.14 and/or support update-alternatives

Package: golang-go Version: 2:1.13~1 Severity: normal Go 1.14 is out. Update this package accordingly. Also, please add /etc/alternatives support. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500,

Bug#912379: Please update the pip package

this bug is now more than a year old. Please update python3-pip and python-pip packages to >19.1

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

On 12/16/2019 3:32 AM, Arnaud Rebillout wrote: Actually, what is weird is that docker tries to use the secret service backend, even though it's not instructed to do so. From the documentation at https://docs.docker.com/engine/reference/commandline/login/#credentials-store You need to

Bug#910823: upstream has closed https://github.com/docker/docker-credential-helpers/issues/105

Please fix the dependencies for this package. https://github.com/docker/docker-credential-helpers/issues/105#issuecomment-561573736

Bug#910822: upstream has closed https://github.com/docker/docker-credential-helpers/issues/105

Please fix the dependencies for this package. https://github.com/docker/docker-credential-helpers/issues/105#issuecomment-561573736

Bug#910822: Anyone alive?

dpkg -r --ignore-depends=golang-docker-credential-helpers golang-docker-credential-helpers

Bug#910823: is anyone here? At all?

dpkg -r --ignore-depends=golang-docker-credential-helpers golang-docker-credential-helpers (Reading database ... 92450 files and directories currently installed.) Removing golang-docker-credential-helpers (0.5.0-2)

Bug#926981: golang-1.12-go: Needs /etc/alternatives/go to be useful

On 8/29/2019 8:08 AM, Shengjing Zhu wrote: That definitely does not provide update-alternatives functionality. We don't provide update-alternatives for difference versions. This is not the goal of update-alternatives. that is ABSOLUTELY one of the roles of update-alternatives, particularly

Bug#926981: golang-1.12-go: Needs /etc/alternatives/go to be useful

On Mon, 5 Aug 2019 22:10:52 +0800 YunQiang Su wrote: > On Sat, 13 Apr 2019 00:09:46 -0700 Nye Liu wrote: > > Package: golang-1.12-go > > Version: 1.12.1-1 > > Severity: normal > > > > Without /etc/alternatives/go (and friends), this package is pretty usele

Bug#887045: Reappeared 4.19.28-2

Linux stupid 4.19.0-4-amd64 #1 SMP Debian 4.19.28-2 (2019-03-15) x86_64 GNU/Linux [707082.059290] WARNING: CPU: 2 PID: 377 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1431 iwl_mvm_rx_tx_cmd+0x1e6/0x650 [iwlmvm] [707082.059292] Modules linked in: tcp_diag inet_diag nfnetlink_queue

Bug#887045: Possibly fixed?

No longer seeing it in 4.19.0-3

Bug#926981: golang-1.12-go: Needs /etc/alternatives/go to be useful

Package: golang-1.12-go Version: 1.12.1-1 Severity: normal Without /etc/alternatives/go (and friends), this package is pretty useless. -- System Information: Debian Release: buster/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386

Bug#926742: netdata: /etc/netdata/edit-config looks for config files in the wrong place

That should have read: sudo /etc/netdata/edit-config health.d/tcp_listen.conf edit-config should be something like: [ -z "${NETDATA_USER_CONFIG_DIR}"  ] && NETDATA_USER_CONFIG_DIR="/etc/netdata" [ -z "${NETDATA_STOCK_CONFIG_DIR}" ] && NETDATA_STOCK_CONFIG_DIR="/usr/lib/netdata/conf.d"

Bug#926742: netdata: /etc/netdata/edit-config looks for config files in the wrong place

Package: netdata Version: 1.12.2-2 Severity: normal $ sudo /etc/netdata/edit-config tcp_listen.conf File 'tcp_listen.conf' is not found in '/usr/local/lib/netdata/conf.d' Config files are in /usr/lib/netdata when using debian. -- debconf information excluded

Bug#924583: spamassassin: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186

I have received a response from cloudmark and they appear to have fixed the issue. $ telnet 208.83.139.205 2703 Trying 208.83.139.205... Connected to 208.83.139.205. Escape character is '^]'. sn=D=670=l=cg a=g=csl -csl=? c302.cloudmark.com c303.cloudmark.com c301.cloudmark.com . a=g=nsl -nsl=?

Bug#924583: spamassassin: razor2 had unknown error during get_server_info at /usr/share/perl5/Mail/SpamAssassin/Plugin/Razor2.pm line 186

telnet discovery.razor.cloudmark.com 2703 Trying 208.83.139.205... Connected to discovery.razor.cloudmark.com. Escape character is '^]'. sn=C=43882=l=cg a=g=csl err=240 ... a=g=nsl err=240 ... a=g=state -sn=C sv=4.007 zone=razor2.cloudmark.com ac=21 srl=43882 lm=4 bql=50 bqs=329 dre=8 srf=FF

Bug#924628: go-dep: Latest dep has different Gopkg.toml format, causing thrashing with old version

Package: go-dep Version: 0.5.0-1+b10 Severity: normal Please update dep to something relatively new. Currently, if you share repos between debian and non-debian systems (e.g. macos), the Gopkg.lock file format switches back and forth between trailing commas on the last item of an array to no

Bug#924623: Patch

:1.12~1) unstable; urgency=medium + + * Update to Go 1.12 (src:golang-1.12) + + -- Nye Liu Fri, 15 Mar 2019 00:23:11 -0700 +

Bug#841385: This is a two year old bug

This is a completely brain damaged bug that is now going on 3 years old with no fix in sight. Meanwhile, golang-1.12-go installs go in /usr/lib/go-1.12/bin, but the only way to use it is to add it to the path or overwrite the symlinks. Insanity.

Bug#924623: golang: Both golang and dep are very out of date

Package: golang Version: 2:1.11~1 Severity: important Golang and dep are both very out of date. This causes quite a bit of problems with dep in particular. If you share repos between debian and non-debian systems (e.g. macos), the Gopkg.lock file format switches back and forth between trailing

Bug#852199: /snap is a FHS violation

How is it possible that in 2018, paths like this are hardcoded and aren’t even configurable at *compile* time? On Mon, 14 Jan 2019 08:09:52 -0500 Jeremy Bicha wrote: > Control: severity -1 normal > Control: tags -1 wontfix > > I'm lowering the severity back to its original level. > > This

Bug#917467: wmbiff: tlscomm_expect() does not handle EAGAIN or GNUTLS_E_AGAIN

Also, I'm not sure that the infinite spin wait while() makes sense in GNUTLS_E_EAGAIN either. Is some sort of select() more appropriate? On February 13, 2019 9:54:12 AM PST, Andreas Metzler wrote: >On 2019-02-13 "Torrance, Douglas" wrote: >> On 12/27/18 3:48 PM, Nye Liu

Bug#917467: wmbiff: tlscomm_expect() does not handle EAGAIN or GNUTLS_E_AGAIN

Probably not, unless some other code change changes the conventional fd to no block. I added it only for symmetry sake. It does not fix any currently known bug. On February 13, 2019 9:54:12 AM PST, Andreas Metzler wrote: >On 2019-02-13 "Torrance, Douglas" wrote: >> On 12

Bug#921409: netdata: plugins can't sudo without CAP_AUDIT_WRITE

Correction: Have to add cap to /lib/systemd/system/netdata.service. Change CapabilityBoundingSet=CAP_DAC_READ_SEARCH CAP_SYS_PTRACE CAP_SETGID CAP_SETUID CAP_NET_RAW to CapabilityBoundingSet=CAP_DAC_READ_SEARCH CAP_SYS_PTRACE CAP_SETGID CAP_SETUID CAP_NET_RAW CAP_AUDIT_WRITE

Bug#921409: netdata: plugins can't sudo without CAP_AUDIT_WRITE

Package: netdata Version: 1.11.1+dfsg-7 Severity: normal Without CAP_AUDIT_WRITE, plugins that try to sudo will fail with PAM audit_log_acct_message() failed: Operation not permitted The fix is sudo setcap cap_audit_write+ep /usr/sbin/netdata -- System Information: Debian Release:

Bug#921047: netdata: mysql plugin requires further post-install work

On 2/4/2019 3:43 AM, Daniel Baumann wrote: At work we always create a 'dummy' read-only user for this, using any privileged accounts is out of the question (as you rightly pointed out). I'm not sure we can do anything about this other than documenting it in README.Debian or so. The "right

Bug#921070: plexmediaserver: 100% cpu usage

Package: plexmediaserver Version: 1.14.1.5488-cc260c476 Severity: critical Justification: breaks the whole system Since upgrading plex from 1.13.9.5456-ecd600442 to 1.14.1.5488-cc260c476, my cpu is always pegged at 100% -- System Information: Debian Release: buster/sid APT prefers

Bug#921047: netdata: mysql plugin requires further post-install work

Package: netdata Version: 1.11.1+dfsg-5 Severity: normal Out of the box, the mysql plugin does not work on debian. The /usr/lib/netdata/conf.d/python.d/mysql.conf debiancfg entry requires /etc/mysql/debian.cnf to be readable by user or group netdata, and the error log does not indicate this is

Bug#913823: apache2: dav.load does not check for an already loaded dav_module

Package: apache2 Version: 2.4.38-1 Followup-For: Bug #913823 Workaround in /etc/apache2/mods-available/dav.load: LoadModule dav_module /usr/lib/apache2/modules/mod_dav.so Alternately just make dav_fs not depend on dav, it will autoload it.

Bug#910823: Hello?

Anyone?

Bug#920018: Anyone?

Anyone? This is an extremely serious bug, AND there is a published fix for it.

Bug#920018: Please give this bug attention.

Please apply https://github.com/systemd/systemd/pull/11527 -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#918848: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#918841: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#919002: Really bad regression

https://github.com/systemd/systemd/issues/11502

Bug#887045: 887045

Not fixed in Linux stupid 4.19.0-1-amd64 #1 SMP Debian 4.19.12-1 (2018-12-22) x86_64 GNU/Linux [297269.085315] WARNING: CPU: 1 PID: 451 at drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1431 iwl_mvm_rx_tx_cmd+0x1e6/0x650 [iwlmvm] [297269.085321] Modules linked in: ufs

Bug#917993: wmbiff: gmail (and many other IMAP servers) now require SNI

Package: wmbiff Version: 0.4.31-2 Severity: important Tags: upstream patch wmbiff/gmail imap4: Need new connection to ***@gmail@imap.gmail.com wmbiff/gmail comm: certificate passed time check. wmbiff/gmail comm: server's certificate (OU=No SNI provided\; please fix your

Bug#917467: wmbiff: tlscomm_expect() does not handle EAGAIN or GNUTLS_E_AGAIN (TLS 1.3)

Package: wmbiff With TLS 1.3, gnutls will return GNUTLS_E_AGAIN even if the underlying transport socket is a blocking socket. https://gitlab.com/gnutls/gnutls/issues/644#note_123363338

Bug#917467: wmbiff: tlscomm_expect() does not handle EAGAIN or GNUTLS_E_AGAIN

Package: wmbiff Version: 0.4.31-1 Severity: important Tags: upstream patch If gnutls_read() or read() report EAGAIN, tlscomm_expect() fails: wmbiff/nyet comm: wrote a000 CAPABILITY wmbiff/nyet comm: imap.***.***:993: expecting: * CAPABILITY wmbiff/nyet comm: imap.***.***:993: gnutls error

Bug#913588: munin-plugins-core: diskstats consistently reports 100% utilization of NVME devices

Package: munin-plugins-core Version: 2.0.42-5 Severity: normal Tags: patch upstream For some reason, NVME drives report near 100% utilization when using /proc/diskstats to calculate utilization using the ticks data. $ cat /proc/diskstats | awk '{print $3, $7, $11, $7+$11, $13, $14}' | grep nvme

Bug#886456: python-pip: segfault when running 'pip install --upgrade ...'

I think this is fixed upstream in pip 18.0 https://pip.pypa.io/en/stable/news/ "Check for file existence and unlink first when clobbering existing files during a wheel install. (#5366)" Debian package is very very far behind, please update pip.

Bug#886456: Segfault in wheel/clobber

Likely fixed upstream https://github.com/pypa/pip/pull/5405/commits/ba80574225488e30569d787ef7e5b0b59305adeb See also https://github.com/pypa/pip/issues/5366 https://github.com/pyca/cryptography/issues/4206 https://github.com/vmware/vcd-cli/issues/235#event-1941328070 Maintainer: please

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

> On Oct 30, 2018, at 4:08 PM, Felipe Sateler wrote: > > > docker login > > error getting credentials - err: exit status 1, out: Cannot autolaunch > > D-Bus without X11 $DISPLAY > > Sounds like docker-credential-helpers can't work without dbus, thus > reassigning there. > > Do you have

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910822 Is there anyone actually maintaining this package?

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

See also https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910823 Is there anyone actually maintaining this package?

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

Sorry, missed the rest of the log: Oct 11 20:07:15 dbus-daemon[29865]: [session uid=1012 pid=29865] Activating service name='org.gnome.keyring.SystemPrompter' requested by ':1.34' (uid=1012 pid=1611 comm="/usr/bin/gnome-keyring-daemon --start --foreground") Oct 11 20:07:15

Bug#910822: golang-docker-credential-helpers: headless gnome-keyring failure

Likely due to gnome-keyring needing d-bus to have a DISPLAY: gnome-keyring-daemon[1611]: couldn't initialize prompt: GDBus.Error:org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.gnome.keyring.SystemPrompter exited with status 1 This is fundamentally broken with respect to headless

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

The current recommended workaround is here: https://github.com/docker/docker-credential-helpers/issues/105#issuecomment-420480401 sudo apt-get remove golang-docker-credential-helpers docker login sudo apt-get install docker-compose This is not at all reasonable.

Bug#910823: docker-compose: remove broken dependency on golang-docker-credential-helpers or fix golang-docker-credential-helpers

Package: docker-compose Version: 1.21.0-3 Severity: normal docker-compose installs golang-docker-credential-helpers, which breaks `docker login` https://github.com/docker/compose/issues/6023 https://github.com/docker/docker-credential-helpers/issues/105

Bug#910822: Subject: golang-docker-credential-helpers: headless gnome-keyring failure

Package: golang-docker-credential-helpers Version: 0.6.1-1 Severity: important The docker-compose package automatically installs golang-docker-credential-helpers, which causes docker login problems on headless machines: On docker login: 1) without gnome-keyring installed: Remote error from

Bug#887045: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd NOT RESOLVED in 4.18.8

https://github.com/torvalds/linux/commit/20932750d9c78d307e4f2f18f9c6a32b82b1e0e8 is not in https://elixir.bootlin.com/linux/v4.18.8/source/net/mac80211/rx.c#L1614

Bug#887045: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd

Not fixed in 4.18.8-1 WARNING: CPU: 3 PID: 379 at /build/linux-GZkygY/linux-4.18.8/drivers/net/wireless/intel/iwlwifi/mvm/tx.c:1410 iwl_mvm_rx_tx_cmd+0x3d1/0x630 [iwlmvm]

Bug#887045: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd

Yes, this patch fixes the issue but I don't think it will actually appear in a release until 4.19 or even later. For now I have to hand patch home built kernels. -- Sent from my Android device with K-9 Mail. Please excuse my brevity.

Bug#887045: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd

199967 – iwlwifi: 3160: warning at intel/iwlwifi/mvm/tx.c:1369 triggers frequently https://github.com/torvalds/linux/commit/20932750d9c78d307e4f2f18f9c6a32b82b1e0e8

Bug#907851: snapd: /snap, /var/snap, /var/lib/snapd, and ~/snap should all be configurable locations

Package: snapd Version: 2.30-5+b1 Severity: normal Tags: upstream snapd drops huge amounts of crap in /snap (a FHS violation, incidentally), /var/snap, /var/lib/snapd, and $HOME/snap *none* of which are configurable locations. Their excuse is that you can just bind mount any/all of the three

Bug#852199: snapd is an inexcusable mess

snapd drops huge amounts of crap in /snap, /var/snap and /var/lib/snapd, *none* of which are configurable locations. Their inane excuse is that you can just bind mount any/all of the three. Imagine if all developers pulled that crap and I you had to set up 3 bind mounts for every piece of

Bug#900379: php-common, php-apcu-bc: sessionclean spams errors if apcu_bc is enabled

Package: php-common Version: 1:61 Severity: minor With apcu_bc enabled, sessionclean looks for the apc.so file in /usr/lib/php/20151012/ even though it only exists in /usr/lib/php/20170718/: PHP Warning: PHP Startup: Unable to load dynamic library '/usr/lib/php/20151012/apc.so' -

Bug#900301: libcurl4 and libcurl3 cannot coeixst, which breaks php

Package: curl Version: 7.60.0-2 Severity: critical Justification: breaks the whole system libcurl3 and libcurl4 cannot coexist, which breaks php (among quite a few other packages): The following NEW packages will be installed: curl libcurl4{ab} 0 packages upgraded, 2 newly installed, 0 to

Bug#885957: Not fixed.

Not fixed random: Trying to read entropy from /dev/random Configuration file: /etc/hostapd/hostapd.conf ctrl_interface_group=4 (from group name 'adm') nl80211: TDLS supported nl80211: TDLS external setup nl80211: Supported cipher 00-0f-ac:1 nl80211: Supported cipher 00-0f-ac:5 nl80211: Supported

Bug#896709: innobackupex: Error: Unsupported server version: '5.7.21-1-log'

Package: percona-xtrabackup Version: 2.2.3-2.1 Severity: grave Justification: renders package unusable InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy and Percona LLC and/or its affiliates 2009-2013. All Rights Reserved. This software is published under the GNU GENERAL

Bug#890595: This is an easy fix.

--- sql.lib.php.dist2018-04-15 01:55:18.675402718 -0700 +++ sql.lib.php 2018-04-15 01:53:46.787216745 -0700 @@ -610,7 +610,7 @@ || $analyzed_sql_results['is_analyse']) && $analyzed_sql_results['select_from'] && ((empty($analyzed_sql_results['select_expr'])) -

Bug#466407: Automated way to get suite names

It has now been 10 years. I will work on this if someone can suggest a way to deterministically map stable/testing to suite names.

Bug#895330: slim: pam_mail.so dir= is ignored

Package: slim Version: 1.3.6-5.1 Severity: normal slim is ignoring pam_mail.so directives, such that there is no way to override the MAIL environment variable I have the following in /etc/pam.d/common-session: session optional pam_mail.so dir=~/Maildir MAIL is still set to /var/mail/

Bug#873581: fixed in python-certbot 0.20.0-3

This bug should not have been closed. Log rotation does not fix the problem of certbot dumping tons of useless debug information into its logs. It is inexcusable for an app that generates log files to not have a way to adjust log level. https://github.com/certbot/certbot/issues/3481

Bug#885960: - patch

Upstream has added support for backwards compatibility, so you can compile with igd2 and the user has the choice between reporting igd v1 and v2 in rootdesc by using "-1" or specifying "force_igd_desc_v1=yes" in miniupnpd.conf https://github.com/miniupnp/miniupnp/pull/282 Thanks for your

Bug#885960: - patch

From https://github.com/miniupnp/miniupnp/pull/282/files From c6bf0ba6f33b96386455b410586755367f596b01 Mon Sep 17 00:00:00 2001 From: Nye Liu <n...@nyet.org> Date: Mon, 19 Feb 2018 22:14:05 -0800 Subject: [PATCH] Allow runtime override of igd to v1 for people running binaries with v2 e

Bug#885960: Upstream recommends only advertising v1

https://github.com/miniupnp/miniupnp/issues/277#issuecomment-363704497 quote: so the solutions are : compile with default option which is advertising IGD v1. This it the DEFAULT option, and will work for 99% of users which just need the UPnP IGD functionality to open a few IPv4 port

Bug#877133: systemd is a pile of crap

There a ton of other /etc/init.d scripts that have the exact same problem - they fail silently and systemd doesn't know about it, nor does it report anything useful to the user. systemd is garbage.

Bug#885960: closed by Thomas Goirand <z...@debian.org> (Bug#885960: fixed in miniupnpd 2.0.20171212-1)

As noted in the upstream bug, I believe this should be a runtime (not compile time) option: https://github.com/miniupnp/miniupnp/issues/277#issuecomment-362868926

Bug#885960: closed by Thomas Goirand <z...@debian.org> (Bug#885960: fixed in miniupnpd 2.0.20171212-1)

Looking at the  source code, i see config.h has both: #define UPNP_VERSION_MAJOR  1 #define UPNP_VERSION_MINOR  1 and #define IGD_V2 This results in urn:schemas-upnp-org:device:InternetGatewayDevice:2 and not urn:schemas-upnp-org:device:InternetGatewayDevice:1

Bug#887045: iwlwifi: TX_STATUS_FAIL_DEST_PS at iwlwifi/mvm/tx.c:1363 using hostapd

Package: src:linux Version: 4.14.12-2 Severity: important Tags: upstream Problematic code here (line 1359): https://elixir.free-electrons.com/linux/v4.14.12/source/drivers/net/wireless/intel/iwlwifi/mvm/tx.c case TX_STATUS_FAIL_DEST_PS: /* the FW should

Bug#886292: (no subject)

Package: src:linux Version: 4.14.7-1 Severity: normal Tags: upstream Problematic code here (line 1359): https://elixir.free-electrons.com/linux/v4.14.7/source/drivers/net/wireless/intel/iwlwifi/mvm/tx.c case TX_STATUS_FAIL_DEST_PS: /* the FW should have

Bug#886174: ntpdate: On ifup, ntpdate always fails if using a local DNS server.

Package: ntpdate Version: 1:4.2.8p10+dfsg-5 Severity: important Similar to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=766838 If a local DNS service is used, ntpdate when run from ifup will always fail, since the BIND named server is not started until well after network interfaces are

Bug#766838: ntpdate runs before bind9 is up

Even worse, if the DNS resolver is a local bind9/named service, this ifup crap will also not work Moving ntpdate to ifup/ifdown was a very dumb idea.

Bug#514319: ntpdate takes ages to fail in the case of DNS problems

Even worse, in the latest incarnation of ntpdate, it is run via ipup, which runs long before bind9. In the case where the system's DNS resolver is a local bind9, this is a non-starter, since ntpdate will NEVER work. Ever.

Bug#885973: isc-dhcp-server: provide way for dhcp-eval to rewrite invalid DHCP client hostnames for DDNS

Package: isc-dhcp-server Version: 4.3.5-3+b2 Severity: wishlist Tags: upstream DHCP clients often send hostnames with characters not allowed in DNS such as spaces. dhcp-eval should provide a way to rewrite those via hardcoded mechanism (e.g translate all invalid characters to '-'), or

Bug#885960: miniupnpd: allow (mis?)reporting IGDv1 to fool broken igd clients

Package: miniupnpd Version: 1.8.20140523-4.2 Severity: wishlist Tags: upstream Many IGD clients (most notably MS BITS) look for IGD v1 and do not recognize v2 as a valid igd service Since v2 is backwards compatible with v1, perhaps there should be a way to force miniupnpd to report v1 -- System

Bug#885958: hostapd: iwlwifi 5GHz hw_mode=a causes microcode fault

Package: hostapd Version: 2:2.6-15 Severity: important [51085.431307] iwlwifi :03:00.0: Microcode SW error detected. Restarting 0x8200. [51085.431410] iwlwifi :03:00.0: Start IWL Error Log Dump: [51085.431412] iwlwifi :03:00.0: Status: 0x0100, count: 6 [51085.431413] iwlwifi

Bug#885957: hostapd: no ACS support for iwlwifi -

Package: hostapd Version: 2:2.6-15 Severity: important I'm trying to get my iwlwifi chip to work with 5GHz and ACS lspci: 03:00.0 Network controller: Intel Corporation Device 24fb (rev 10) Subsystem: Intel Corporation Device 2110 Flags: bus master, fast devsel, latency 0, IRQ

Bug#885825: miniupnpd: listen needs to be set to an interface, not an ip addres

On 12/30/2017 8:09 AM, Thomas Goirand wrote: On 12/30/2017 05:19 AM, Nye Liu wrote: While I may agree with the above (I should check, as using the IP used to work), how is this a Severity: serious? Please read the severity definition: serious is a severe violation of Debian policy

Bug#885826: linux-igd: /etc/init.d/linux-igd requires $network

Package: linux-igd Version: 1.0+cvs20070630-5 Severity: serious Tags: patch Justification: Policy 9.3.2 /etc/init.d/linux-igd requires $network or it will fail to start. --- linux-igd.dist 2017-12-28 22:07:28.512055702 -0800 +++ linux-igd 2016-09-22 09:01:57.0 -0700 @@ -1,8 +1,8

Bug#885825: miniupnpd: listen needs to be set to an interface, not an ip addres

Package: miniupnpd Version: 1.8.20140523-4.2 Severity: serious Justification: Policy 9.3.2 In /etc/default/miniupnpd, i have: MiniUPnPd_LISTENING_IP=192.168.19.1 But this results in: Error: please specify LAN network interface by name instead of IPv4 address : 192.168.19.1 can't parse

Bug#381040: There is no excuse for this not being fixed

the upstream has had the fix for this for a long time.

Bug#789196: debsecan: Support SUITE=buster

And now buster/testing. Is there an actual maintainer for this? Perhaps an NMU is in order?

Bug#862357: pidx % serv->sv_nrpools causes segfault

At net/sunrpc/svc.c line 355 svc_pool_for_cpu(), srv->sv_nrpools can be zero: return >sv_pools[pidx % serv->sv_nrpools];

Bug#862357: divide error in 4.9.30-1

Similar to the problem reported here: https://bugzilla.redhat.com/show_bug.cgi?id=1427493#c31 Jun 5 11:41:06 ospylac kernel: [ 1155.573913] divide error: [#1] SMP Jun 5 11:41:06 ospylac kernel: [ 1155.573929] Modules linked in: joydev rpcsec_gss_krb5 nfsv4 dns_resolver nfs fscache

Bug#862357: 1000+ nfs threads after 5 days

This is getting ridiculous $ ps -ef | grep "NFSv4 callback" | wc 12311087998 $ uptime 10:44:26 up 5 days, 18:28, 1 user, load average: 0.11, 0.06, 0.07

  1   2   3   >