Package: login
Version: 1:4.16.0-2+really2.40.2-5
Severity: normal
Dear Maintainer,
I was using sg like this:
```
sg fw-torrent transmission-qt
sg fw-skype skypeforlinux
```
To launch specific gui applications with changed group, and later I can
handle IP traffic of these specific applications v
No longer happens in Sid with 6.9.7-1!
> 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
A
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
```
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 script.
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
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?
I'm still having 6.1.0-9-amd64 on hold. Latest 6.5 does not fix it yet.
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 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
This is probably relevant upstream bug report:
https://bugzilla.kernel.org/show_bug.cgi?id=209839
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 net/sched/sch_gene
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 "a...@prnet.info
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).
Upgrading to bullseye-backports version 252.5-2~bpo11+1 fixes the issue.
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
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
On 2023-01-27 13:35, Romain Francoise wrote:
Do you mind if I merge them?
Sure, please merge.
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.
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 because:
reassing 973990 xtables-addons
reopen 973990
I don't see errors in:
`sudo apt install --reinstall xtables-addons-dkms`
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:
*** 3.
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 Martian
I noticed it crashing too, but also systray icons disappear, even though
applications themselves are running.
Please see screenshots attached.
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 is
wxrwx 1 root root 8 Oct 6 22:05 pci-:01:00.0-card -> ../card1
lrwxrwxrwx 1 root root 13 Oct 6 22:05 pci-:01:00.0-render -> ../renderD129
video:x:44:vincas
Alternative 'nvidia':
nvidia - auto mode
link best version is /usr/lib/nvidia/tesla
link currently poi
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
"/usr/lib
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 (de
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 any
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 vi
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.
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, th
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 suspi
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 helps.
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
Ser
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, b
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
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.
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
● pgbouncer.service
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 logrotate[2138
libreoffice-soffice"
name="/home/vincas/Darbastalis/lu7600dk8g.tmp" pid=7600
comm="soffice.bin" requested_mask="c" denied_mask="c" fsuid=1000
ouid=1000FSUID="vincas" OUID="vincas"
This one rule should the trick:
owner @{libo_user_dir
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:
https://blog.tox.chat/2021/12/stack-based-buffer-overflow-vulnerability-in-udp-packet-handling-i
: undefined symbol: _ZTIN7leveldb6Logger
```
This is list of updated packages just before first failure (from
/var/log/apt/history.log):
```
Start-Date: 2021-10-12 19:59:47
Commandline: apt full-upgrade
Requested-By: vincas (1000)
Install: libraqm0:amd64 (0.7.0-4, automatic)
Upgrade: libffi8
t:
```
sudo aa-status | fgrep i2pd
```
This means i2pd daemon is running without AppArmor confinement.
Profile *is* loaded if you reboot system or just restart AppArmor:
```
vincas@vdebian11kde:~$ sudo systemctl restart apparmor
vincas@vdebian11kde:~$ sudo aa-status | fgrep i2pd
i2pd
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" name="/var/spool/exim4/%s.
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 (n
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="s
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
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 /usr/include/boost/smart_ptr/de
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) ...
``
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 `~/.xsession-errors`:
This is due to xtables-addons failing to build on 5.9:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=972454
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
Package: apparmor-profiles
Version: 2.13.2-10
Severity: normal
Dear Maintainer,
AppArmor 2.13.3 got usr.lib.dovecot.stats profile:
https://gitlab.com/apparmor/apparmor/-/commit/36bdd6ea7011455f94106e6ea6d4aad626863815
To make dovecot work on Debian Buster, I need to modify
`/etc/apparmor.d/local
Package: apparmor-profiles
Version: 2.13.2-10
Severity: normal
Tags: upstream
Dear Maintainer,
Debian Buster,Bullseye needs usr.lib.dovecot.script-login, which was addred not
long ago [0].
I'll work for backport to AppArmor 2.13.
[0]
https://gitlab.com/apparmor/apparmor/-/commit/6e59f454b136c4
I think it's for upstream. There's more rules to add too. I'll try to work on
that.
On 2020-10-24 16:05, intrigeri wrote:
Hi Vincas!
Vincas Dargis (2020-08-27):
This is produced if usr.sbin.dovecot is copied to /etc/apparmor.d:
```
type=AVC msg=audit(1598556536.092:901): a
Package: ntp
Version: 1:4.2.8p15+dfsg-1
Severity: normal
Dear Maintainer,
In Debian Buster (same in Sid) I've noticed that I get "spam" of these
messages in syslog:
```
Sep 28 21:57:38 dl380 ntpd[739]: Soliciting pool server 193.219.61.120
Sep 28 21:57:38 dl380 ntpd[739]: Soliciting pool server
Package: calibre
Version: 4.99.12+dfsg+really4.23.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
calibre fails to start with this error:
```
Traceback (most recent call last):
File "/usr/bin/calibre", line 20, in
sys.exit(calibre())
File "/usr/lib/calibre/ca
In https://wiki.debian.org/Bumblebee#Debian_10_and_older I've found this hint:
```
[ERROR]Cannot access secondary GPU - error: [XORG] (EE) No devices detected
You may have to set the BusID manually, in /etc/bumblebee/xorg.conf.nvidia. To get the BusID, run lspci | egrep 'VGA|3D'
in a terminal.
from `/var/log/Xorg.8.log`
[ 2486.434] (II) NVIDIA dlloader X Driver 450.66 Wed Aug 12 19:44:12 UTC 2020
[ 2486.434] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs
[ 2486.435] (EE) No devices detected.
[ 2486.435] (EE)
Fatal server error:
[ 2486.435] (EE) no screens found(EE)
[
Sadly, purge & reinstall did not help this time...
:
Start-Date: 2020-09-01 18:26:20
Commandline: apt full-upgrade
Requested-By: vincas (1000)
Upgrade: libmpc3:amd64 (1.2.0~rc1-1, 1.2.0-1), libnvidia-glvkspirv:amd64 (450.57-3, 450.66-1), libnvidia-glvkspirv:i386
(450.57-3, 450.66-1), libstdc++-10-dev:amd64 (10.2.0-5, 10.2.0-6), liblouisutdml-data:am
Package: apparmor
Version: 2.13.4-3
Severity: minor
Tags: upstream
Dear Maintainer,
Just got this denial (while running some absolutely propiertary application via
Steam):
```
type=AVC msg=audit(1598788812.837:495): apparmor="DENIED" operation="open"
profile="nvidia_modprobe" name="/proc/drive
Package: apparmor-profiles
Version: 2.13.2-10
Severity: normal
Tags: upstream
Dear Maintainer,
This is produced if usr.sbin.dovecot is copied to /etc/apparmor.d:
```
type=AVC msg=audit(1598556536.092:901): apparmor="DENIED" operation="open"
profile="dovecot" name="/usr/share/dovecot/dh.pem" pid
On Thu, 14 Nov 2019 20:14:10 +0100 Jonas Smedegaard wrote:
What I expect to be realistic is including e.g. 0.20.0 shortly before
freeze of bullseye, have it included when bullseye becomes stable 3-6
months later, and then when 0.20.1 comes out...
Ping. 0.20.1 is now available.
It does right job if I change authentication method to "SASL PLAIN".
Thanks for this "solution". You probably can't tell what changed (likely
in /etc) after purge+reinstall?
Sadly, no. I could have taken copy if /etc, just haven't thought of it, sorry.
All I see is that `/etc/bumblebee/xorg.conf.d/` is still empty as it where,
can't comment any more.
Package: konversation
Version: 1.7.5-3
Severity: normal
Dear Maintainer,
Recently I've noticed that I a missing some channels after
(auto-)connecting to chat.freenode.net.
Log shows this:
[21:13] [Pastabos] -NickServ- This nickname is registered. Please choose a
different nickname, or identify
I just this:
sudo apt purge --autoremove nvidia*
sudo apt install nvidia-driver bumblebee-nvidia primus-nvidia primus-vk-nvidia
And after reinstalling driver and all other bumbleblee-related packages, it
started to work again.
$ sudo strace -efile -f -p $(pgrep bumblebeed) 2>&1 | fgrep /etc/bumblebee
[pid 7068] execve("/usr/lib/xorg/Xorg", ["/usr/lib/xorg/Xorg", ":8", "-config",
"/etc/bumblebee/xorg.conf.nouveau", "-configdir", "/etc/bumblebee/xorg.conf.d", "-sharevts",
"-nolisten", "tcp", "-noreset", "-verbose", "3"
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: "/etc/bumblebee/xorg.
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
/usr/share/foo/
On Thu, 14 Nov 2019 20:14:10 +0100 Jonas Smedegaard wrote:
What I expect to be realistic is including e.g. 0.20.0 shortly before
freeze of bullseye
Could we please have 0.19.1 a bit earlier? :)
xiscu, could you please create `/etc/apparmor.d/local/usr.bin.thunderbird` file
with this rule:
owner /run/user/[0-9]*/dconf/ w,
After that, restart AppArmor with `sudo systemctl restart apparmor`. Then, try starting Thunderbird
again, and see if that error is gone?
Control: reassign -1 thunderbird
Reassigning to thunderbird, as it ships it's AppArmor profile itself.
We have this rule there:
owner /run/user/[0-9]*/dconf/user rw,
But it it does not handle the case when parent dir is missing. It does not reproduce in my KDE
desktop. Maybe you use some mini
I've just got notification about updated https://wiki.debian.org/Bumblebee, and it mentions pvkrun,
and it works!
So we need to choose optirun vs pvkrun manually. Maybe some day optirun will
choose automatically..?
On Sun, 12 Apr 2020 19:24:03 +0100 Ben Hutchings wrote:
Is this reproducible without the nvidia drivers loaded at all?
Sorry, idk, I cannot reproduce it any more.
0-05-15 09:35, Carsten Schoenert rašė:
Hello Vincas,
seems there is some more AppArmor related stuff to fix for Thunderbird
under Xfce. Could you please have a look?
Also, it would be nice to have NEWS entry about availability of AppArmor profile, with hint how to
enable it, and link to https://wiki.debian.org/AppArmor maybe.
Control: found 1.17.2-1
Hi,
It does not seem to be fixed. Packaged does not have apparmor files:
```
$ dpkg -L qtox | fgrep apparmor
$
```
There should be `/etc/apparmor.d/usr.bin.qtox`, `/etc/apparmor.d/tunables/usr.bin.qtox`, see
https://github.com/qTox/qTox/tree/master/security/apparmor/2.
Package: src:linux
Version: 5.5.13-2
Severity: important
Dear Maintainer,
After upgrading to 5.5 on Sid, I've experiencing full computer freeze after
some time of playing, for example, minetest for some time (even though I use
`optirun` to use discrete graphics).
Problems are completely gone if
Quite some time passed since February...
My Sid just updated to 5.5, and NVidia (via optirun) no longer works, seen that
build error too.
Is there any hope to make it work again..?
I'm using Legacy because I've seen NEWS that I should use that one for my
GM107M [GeForce GTX 860M]...
Package: sysdig
Version: 0.26.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
sysdig does not run at all:
```
$ sudo sysdig
sysdig: symbol lookup error: sysdig: undefined symbol:
_ZN4grpc13ClientContextC1Ev
```
-- System Information:
Debian Release: bullseye/sid
Disabling offloading helps as workaround, see:
https://lore.kernel.org/netdev/81548409-2fd3-9645-eeaf-ab8f7789b...@gmail.com/
1 - 100 of 498 matches
Mail list logo