Package: fonts-fantasque-sans
Version: 1.7.2~alpha.3~dfsg-2
Severity: wishlist
Dear Maintainer,
fonts-fantasque-sans package provides files in
`/usr/share/fantasque-sans/` directory, while it seems there's a common
pattern to store fonts in `/usr/share/fonts-foo-bar` directory (or
In bumblebee changelog I see:
* Simplify rules and use bumblebee.install etc. for installation.
* Remove obsolete conffile /etc/bumblebee/xorg.conf.d/10-dummy.conf.
Could these introduce some sort of regression in my case?
Package: bumblebee-nvidia
Version: 3.2.1-23
Severity: important
Dear Maintainer,
After some updates I cannot use primusrun/optirun/pvkrun on my Sid:
```
$ primusrun glxgears
primus: fatal: Bumblebee daemon reported: error: [XORG] (EE) Unable to
locate/open config directory:
I've reproduced same issue on VM.
It seems that I have go perform `full-upgrade` that removes `user-manager`.
After that KDE desktop works.
If I try to install `user-manager` again, I get suggestion to remove whole
kde-plasma-dekstop & friends...
Package: libkwaylandserver5
Version: 5.20.4-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
After today Sid upgrades my KDE desktop failed to fully load after login. I see
background and KDE spinner, but desktop does not appear.
I've found this in
Rebooted back to 5.8.0-3-amd64, it works! Something happened with Linux 5.9...
Package: shorewall
Version: 5.2.3.4-1
Severity: normal
Dear Maintainer,
I've accidentally noticed that /var/log/ulog/syslogemu.log is suspiciously
"quiet"...
`shorewall status` says `Shorewall is stopped`. Trying to
launch manually with `shorewall start` I get this errous output:
```
Starting
This is due to xtables-addons failing to build on 5.9:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972454
On Thu, 24 Dec 2020 21:56:55 +0900 Norbert Preining
wrote:
Which version of kwin do you have installed?
Seems like a missing breaks against old versions of kwin or so.
After removing user-manager, full-upgrade upgraded kwin too:
```
Unpacking kwin-x11 (4:5.20.4-3) over (4:5.19.5-3+b1) ...
Package: libboost1.74-dev
Version: 1.74.0-7
Severity: minor
Tags: upstream
Dear Maintainer,
Building bitcoind package produces bunch of warnings like this:
```
In file included from
/usr/include/boost/smart_ptr/detail/sp_thread_sleep.hpp:22,
from
Control: tags -1 -upstream
Removing upstream tag, as this is packaging bug.
Installing python3-ecdsa fixed it.
Package: electrum
Version: 4.0.9-1
Severity: important
Dear Maintainer,
Latest electrum version failds to find Ledger wallet, Install Wizard
shows this:
```
ledger: (error getting device infos)
Library version for 'ledger' is incompatible.
Installed: 0.1.31, Needed: 0.1.30 <= x < inf
I cannot reproduces this because remounting to produces "mount: /: mount point is
busy." error.
Package: exim4
Version: 4.92-8+deb10u5
Severity: minor
Dear Maintainer,
After installing Debian 10.9, I've noticed this denial (due to my own
"WIP" AppArmor profile applied):
```
type=AVC msg=audit(1616860912.170:123): apparmor="DENIED"
operation="mknod" profile="exim4"
2021-03-09 20:40, Rene Engelhard rašė:
I've looked at the
https://salsa.debian.org/libreoffice-team/libreoffice/libreoffice/-/commit/03ba395bbe21154efc8a05dfbb9f7c16946eb4d2
diff linked in one of the posts and I see 11 question marks, not 9.
> Hmm, indeed. My bad.
That means we need to do some
2021-03-08 21:51, Rene Engelhard wrote:
Yes, it is done.
In 7.1. As the version tracking info clearly showed.
Ouch.. I've missed the version number, sorry...
Changing rule into this:
owner @{libo_user_dirs}/{,**/}lu?{,?,??}.tmp rwk, #Temporary
file used when saving
Did the trick
Control: reopen -1
I see this bug marked as Done but I just got denial today:
type=AVC msg=audit(1615225628.771:1363): apparmor="DENIED" operation="mknod" profile="libreoffice-soffice"
name="/home/vincas/Dokumentai/lu4638vdjw1.tmp" pid=4638 comm="soffice.bin" requested_mask="c" denied_mask="c"
Package: i2pd
Version: 2.36.0-1
Severity: normal
Dear Maintainer,
i2pd package deploys AppArmor profile:
```
$ file /etc/apparmor.d/usr.sbin.i2pd
/etc/apparmor.d/usr.sbin.i2pd: C source, ASCII text
```
But that profile is not loaded, as there's no "i2pd" in `sudo
aa-status` output:
```
sudo
Package: bitcoind
Version: 22.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Since 2021-10-12 bitcoind fails to start on my machine:
```
# fgrep leveldb /var/log/syslog
Oct 12 20:00:34 vinco bitcoind[1103]: /usr/bin/bitcoind: symbol lookup error:
And what about Bullseye? Will there be security release for Debian stable?
Package: libtoxcore2
Version: 0.2.12-1+b1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: Debian Security Team
Dear Maintainer,
libtoxcore has CVE-2021-44847:
Package: src:linux
Version: 5.10.106-1
Severity: minor
Dear Maintainer,
After linux-image-5.10.0-12-amd64 5.10.103-1 was installed, kernel log
started to be "spammed" with "clocksource:" messages on HP ProLiant
DL380 G6 server. Same on latest 5.10.0-13 package.
Version 5.10.103-1 changelog does
I've upgraded some machines to Bullseye, and logcheck.service started to fail:
```
Feb 07 00:00:01 hostname systemd[1]: Starting Rotate log files...
Feb 07 00:00:02 hostname logrotate[2138903]: error: iptraf-ng:2
duplicate log entry for /var/log/iptraf/*.log
Feb 07 00:00:02 hostname
Package: libreoffice-common
Version: 1:7.3.0~rc2-2
Severity: normal
Tags: upstream
Dear Maintainer,
Looks like bug #905442 is back. We need rule with eight (and more) question
marks:
type=AVC msg=audit(1642615553.674:2636): apparmor="DENIED"
operation="mknod" profile="libreoffice-soffice"
It seems that this might be fixed in ~5.17, based on this [0] message in thread that speaks about problem seemingly
similar to mine:
Yes, I expect to submit it into the next merge window (not the current
v5.16 merge window, but v5.17). However, if your situation is urgent, and
if it works for
Package: pgbouncer
Version: 1.17.0-3.pgdg110+1
Severity: minor
Dear Maintainer,
After upgrading pgbouncer from pgdg and stopping pgbouncer service, that
service is reported as failed, triggering monitoring notifications we have set
up:
```
$ systemctl status pgbouncer.service
●
On Sun, 2 May 2021 14:03:24 +0200 Salvatore Bonaccorso
wrote:
is this still reproducible with a recent kernel?
I am running linux-image-5.16.0-6-amd64 5.16.18-1 with commented-out (disabled) workaround "ethtool -K enp5s0f1 tx off
sg off tso off" and I no longer see any problems.
I blieve I have similar issue with linux-image-6.1.0-0.deb11.9-amd64
and linux-image-6.1.0-0.deb11.11-amd64 from backports installed in
Debian 11.
linux-image-6.1.0-0.deb11.7-amd64 works fine.
I can boot with nomodeset too.
Debian 12.1 Live CD also hangs doring boot!
Here are some i915-related
I've found workaround: adding i915.enable_dc=0 to kernel boot
parameters fixes (workarounds) this issue.
Forgot to mention that my machine runs on i7-11700.
Also tried Testing (Trixie) LiveCD with Linux 6.4 and it works fine.
I'm still having 6.1.0-9-amd64 on hold. Latest 6.5 does not fix it yet.
I've noticed NEWS after NetworkManager upgrade about no longer supporting if-* scripts, and now `shorewall status` says
`Shorewall is stopped` :/ .
Any ideas how to "workaround" it?
On Sat, 21 Oct 2023 11:44:25 +0100 Jeremy Sowden wrote:
On 2023-10-21, at 11:53:54 +0300, Vincas Dargis wrote:
> Any ideas how to "workaround" it?
I am working on a fix atm.
Thanks!
But I was instructed in #shorewall that this is NetworkManager script, it's just named
&qu
On Sat, 21 Oct 2023 13:27:46 +0100 Jeremy Sowden wrote:
init.fedora.sh, on the other hand, is a System V init-script
Oh, sorry, I've directed to the wrong file...
Re-checked IRC logs, it was ifupdown.fedora.sh, not init.fedora.sh.
I was said that ifupdown.fedora.sh is NetworkManager
On 2022-07-09 13:36, Carsten Schoenert wrote:
In about 80% of problems some external Add-ons are the root of problems.
I see there's "SenderAddressColumn (disabled)" addon, but I doubt it was enabled before upgrade. Last addon update was
in 2016.
I blieve what helped is resetting controls
Package: thunderbird
Version: 1:102.0.1-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Please see screenshot attached - no account tree is visible after
upgrade.
In settings I do see all accounts set up as it was before though.
AppArmor profile was always enabled,
I've found a fix:
```
thunderbird --safe-mode --jsconsole
```
(--jsconsole probably is not deeded).
In a popup shown, I've selected to "Disable all addons" and "Reset toolbars and controls". Clicking "Make changes and
restart" made UI work again, even with AppArmor.
I have reproduced issue on my Sid virtual machine. I've copied (pre-upgrade) profile from backup, upgraded Thunderbird
and same issue appeared.
To fix I launched --safe-mode, and selected to reset toolbars and controls. I did not
check "Disable all addons".
Sadly, --verbose did not produce
Workaround is to downgrade python3-aiorpcx package like this:
cd /tmp/
debsnap --binary -d . python3-aiorpcx 0.18.5-1
dpkg -i python3-aiorpcx_0.18.5-1_all.deb
Package: src:linux
Version: 5.10.120-1
Severity: normal
Dear Maintainer,
I've noticed in Munin graphs that entropy dropped significantly after
reboot to 5.10.120-1. Please see images attached.
Not sure if this is actually a problem/bug, but that kind of drop "out
of nowhere" seems at least
Package: lvm2
Version: 2.03.11-2.1
Severity: normal
Dear Maintainer,
We have two similar machines working as database master & replica. They both
use same HDD drives and Areca ARC-1261 HW raid controllers, with same LVM
volume groups set up.
I've noticed that during boot, and before rebooting,
Package: src:linux
Version: 5.16.12-1~bpo11+1
Severity: normal
Dear Maintainer,
It seems we can't use Linux for cloning drive data from faulty drives
(with bad blocks) using USB SATA adapters.
I wanted to clone data from this old SSD:
```
Device Model: LITEONIT LCM-128M3S 2.5" 7mm 128GB
2022-04-24 12:20, Salvatore Bonaccorso rašė:
Would you be able to test the current kernel from unstable so we can
confirm it's fixed in 5.17.3-1?
I am not sure if I want to install kernel from unstable into production machine.. :) . I believe I'll wait for Bullseye
backport to see if it
On Sun, 24 Apr 2022 11:20:30 +0200 Salvatore Bonaccorso
wrote:
Would you be able to test the current kernel from unstable so we can
confirm it's fixed in 5.17.3-1?
I've installed 5.18 from bullseye-backports:
Aug 19 23:45:36 dl380 kernel: [0.00] Linux version 5.18.0-0.bpo.1-amd64
Workaround is to import nvidia abstraction into local include file you can
create:
```
$ cat /etc/apparmor.d/local/usr.bin.qtox
include
```
Package: qtox
Version: 1.17.6-0.1
Severity: grave
Tags: upstream
Justification: renders package unusable
Dear Maintainer,
After upgrading to nvidia-tesla-470-driver, qTox fails to start.
See https://github.com/qTox/qTox/pull/ for more details.
Marked as grave as AppArmor profile for qTox
Package: nvidia-tesla-470-driver
Version: 470.141.03-2
Severity: normal
Dear Maintainer,
I am using
https://wiki.debian.org/NVIDIA%20Optimus#Using_NVIDIA_GPU_as_the_primary_GPU
setup to enable NVIDIA by default on my Asus N551JM with GM107M [GeForce
GTX 860M] for quite some time successfully.
I
Package: salt-master
Version: 3004.1+dfsg-2
Severity: grave
Justification: renders package unusable
Dear Maintainer,
salt-master fails to start.
journalctl shows:
```
spal. 05 20:47:04 salt-master[11925]: Traceback (most recent call last):
spal. 05 20:47:04 salt-master[11925]: File
I noticed it crashing too, but also systray icons disappear, even though
applications themselves are running.
Please see screenshots attached.
On Thu, 26 Jan 2023 19:44:27 +0100 Romain Francoise
wrote:
Hi,
Isn't this already tracked as #973990?
Wait a minute, why there's two bug reports? Yes, I believe the core issue
should be in xtables.
On 2023-01-27 13:35, Romain Francoise wrote:
Do you mind if I merge them?
Sure, please merge.
reopen 973990
Package: shorewall
Version: 5.2.3.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
It seems Shorewall no longer works in Sid:
```
$ sudo shorewall start
Starting Shorewall
Initializing...
Setting up ARP filtering...
Setting up Route Filtering...
Setting up
On Tue, 10 Jan 2023 23:22:37 + Jeremy Sowden wrote:
xtables-addons 3.9 did not support linux 5.9. The upgrade to 3.11 fixed
But it's 3.23 on my machine:
```
$ LC_ALL=C apt policy xtables-addons-common
xtables-addons-common:
Installed: 3.23-1
Candidate: 3.23-1
Version table:
***
I don't see errors in:
`sudo apt install --reinstall xtables-addons-dkms`
reassing 973990 xtables-addons
Control: reopen -1
Control: reassign -1 xtables-addons
Control: severity -1 critical
On Tue, 10 Jan 2023 23:22:37 + Jeremy Sowden wrote:
xtables-addons 3.9 did not support linux 5.9. The upgrade to 3.11 fixed
Reopening, as Sid has 3.23 and it does not work.
Setting to critical
On Tue, 31 Jan 2023 23:41:54 + Jeremy Sowden wrote:
However, Vincas Dargis, the reporter, observed that shorewall worked
with Linux 5.8 and did not with 5.9 and proposed #972454 as the culprit:
I completely forgot that I wrote that bug in 2020...
Anyway, shorewall works now
Maybe we could raise severity to avoid this bug entering Stable? That would be
rather regression...
On Wed, 08 Feb 2023 13:07:49 -0700 Soren Stoutner wrote:
In the future it would be ideal to package everything in Debian necessary to fully support
hardware ledgers. However, as that is not likely to happen in the short term, I think it
would be valuable to at least document what a user needs
Here's some more info - it first crashes and then starts logging these messages:
Jun 20 19:37:31 kernel: [ cut here ]
Jun 20 19:37:31 kernel: NETDEV WATCHDOG: enp5s0f1 (r8169): transmit queue 0
timed out
Jun 20 19:37:31 kernel: WARNING: CPU: 7 PID: 0 at
This is probably relevant upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=209839
I have started getting issues again with recent 6.3 upgrade in Sid, network
become unstable:
Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have
ASPM control
Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0
(loop: 42, delay: 100).
I've just started getting this on Sid with 6.3:
Jun 19 20:17:43 kernel: r8169 :05:00.1: can't disable ASPM; OS doesn't have
ASPM control
Jun 19 20:17:43 kernel: r8169 :05:00.1 enp5s0f1: rtl_rxtx_empty_cond == 0
(loop: 42, delay: 100).
On Sat, 18 Jun 2022 16:02:28 +0200
Upgrading to bullseye-backports version 252.5-2~bpo11+1 fixes the issue.
Still happening with 6.6 on Sid...
Package: tzdata
Version: 2021a-1+deb11u10
Severity: important
Dear Maintainer,
I've started seeing these kind of log messages via logcheck on our
oldstable machines:
```
Dec 1 08:06:43 dev ntpd[963]: leapsecond file
('/usr/share/zoneinfo/leap-seconds.list'): will expire in less than 27
days
> This is because reprepro does not generate or support these
> dep11/Components-*.ym.gz files...
My workaround was to download Components files:
${YOUR_MIRROR}/dists/bookworm/main/dep11/Components-amd64.yml.gz
and
${YOUR_MIRROR}/dists/bookworm/non-free-firmware/dep11/Components-amd64.yml.gz
No longer happens in Sid with 6.9.7-1!
401 - 470 of 470 matches
Mail list logo
