Control: reassign -1 libkmod2 33+20240816-1
libkmod2 seems to be the package that most directly causes the issue, since
that's where the symbol version change occurs. Additionally, reassigning
should cause apt-listbugs to generate a slightly nicer pin that doesn't block
`apt full-upgrade` so ea
Package: ddcci-dkms
Version: 0.4.4-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
Although upstream has not yet bumped the version number, I believe they have
committed changes that fix this to their GitLab repo.
*** /var/lib/dkms/ddcci/0.4.4/build/make.log
DKMS make.
ine *with* the module, so just disabling the module globally is not a good
workaround.
Ben Morris
-- System Information:
Debian Release: trixie/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.7.12-amd64
Package: whipper
Version: 0.10.0-2+b3
Severity: important
Dear Maintainer,
Whipper exits with the following messages:
Traceback (most recent call last):
File "/usr/bin/whipper", line 33, in
sys.exit(load_entry_point('whipper==0.10.0', 'console_scripts',
'whipper')())
^^^
Package: kamoso
Version: 22.12.3-1
Followup-For: Bug #984705
Dear Maintainer,
I believe kamoso should depend on gstreamer1.0-plugins-bad. Installing
that package fixes this problem.
-- System Information:
Debian Release: 12.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: a
x27;s configuration or whether an update to the client is needed.
Regards,
Ben Morris
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 6.1.0-3-amd64 (SMP
Package: gpodder
Version: 3.11.0-4
Severity: normal
Dear Maintainer,
/usr/share/applications/gpodder.desktop contains the following line:
Exec=usr/bin/gpodder
/usr/share/applications/gpodder-url-handler.desktop has a similar
problem:
Exec=usr/bin/gpodder -s %u
Note that both paths start with
unable to check what actually works,
but nvidia's website seems to suggest that the changelog is correct.
The description for nvidia-opencl-icd may have a similar problem.
Ben Morris
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, '
Available
> ZamAudio Is Not Installed On The System
`apt install mda-lv2 zam-plugins` fixes it. I believe these packages should be
added to Recommends, or at least Suggests.
Thanks for reading,
Ben Morris
-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (50
$ journalctl --user -u pipewire --user -u wireplumber --user -u
pipewire-pulse -b-1
Oct 10 09:25:54 serenity systemd[1737]: Started PipeWire Multimedia
Service.
Oct 10 09:25:54 serenity systemd[1737]: Started Multimedia Service
Session Manager.
Oct 10 09:25:55 serenity pipewire[2635]: mod.rt: Ca
Package: wireplumber
Version: 0.4.12-1
Severity: important
Dear Maintainer,
I have no sound at all on my system. Both my sound devices (the Intel
sound built in to my motherboard and the HDMI out on my Radeon) show up
as expected in Plasma, pavucontrol, etc., but nothing seems to be able
to play
The module is still failing to build on my machine.
I believe the problem is that ddcci_device_remove() returns in two
different places. The new patch wraps the return at the end of the
function in an #if, but does not fix the mid-function `return -EINVAL;`.
(In case it is useful: there is a
Package: kwin-x11
Version: 4:5.23.0-2
Severity: important
When starting compositing in kwin (either by starting kwin with compositing
enabled, or by pressing Ctrl-Alt-F12 while kwin is running), the whole screen
goes black apart from the mouse cursor.
When this happens, kwin prints `kwin_core: Fa
The upstream source checks for the ability to build against libfuse by
searching hard-coded locations for fuse.h. In the interest of multiarch
support, the Debian package instead uses the compiler to locate the header.
However, this compiler-based check was failing, not because fuse is not
avai
Package: beets
Version: 1.4.9-4
Severity: grave
Justification: renders package unusable
Since the upgrade to Python 3.8.4rc1, Beets crashes on launch with the
following output:
$ beet
Traceback (most recent call last):
File "/usr/bin/beet", line 11, in
load_entry_point('beets==1.4.9', 'con
Package: blender
Version: 2.83.1+dfsg-1
Severity: grave
Justification: renders package unusable
Blender 2.83.1+dfsg-1 is crashing on launch with the output shown below. I have
tested this with and without an existing ~/.config/blender/ directory.
$ blender
blf_load_font_default: 'fonts' data path
CLAIMS PROCESSING FORM:
Names:
Location:
Tel:
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Name: Country
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
18 matches
Mail list logo
