Package: libxine2
Version: 1.2.13-1
Severity: normal

Dear Maintainer,

version 1.2.11 of xine changed how volume scaling is done: it switched from
linear to logaritmic volume scaling. See this commit:

https://sourceforge.net/p/xine/xine-lib-1.2/ci/59544d4f4a763bd47a5e8b629e1afc74e0c9a719/

With the release of Bookworm this change made it into stable Debian (Bullseye 
used version 
1.2.10). This change seriously breaks volume control in applications that 
depend on libxine2. In
particular Amarok and Kaffeine shipped by Trinity Desktop Environment 
(currently not part of 
official Debian repositories).  More specifically it makes lower part of the 
volume scale to 
quiet to be usable, while the upper part of volume scale lacks necessary 
granularity.  There is a 
fix for this in upstream libxine2:

https://sourceforge.net/p/xine/xine-lib-1.2/ci/0a32d4509b39181da6553b85e4d35829716d23c7/

Would it be possible to pull latest upstream version of libxine2 into sid so 
that the TDE team can 
work on fixing applications that depend on xine?

P.S. Library versions listed below point to version of xine released with 
Bullseye. This is due to 
downgrade I had to make to work around the bug.

-- System Information:
Debian Release: 12.0
  APT prefers stable-security
  APT policy: (500, 'stable-security'), (500, 'stable'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 6.1.0-9-amd64 (SMP w/24 CPU threads; PREEMPT)
Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE
Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8), 
LANGUAGE=en_GB.UTF-8
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages libxine2 depends on:
ii  libxine2-bin           1.2.10-4+b1
ii  libxine2-misc-plugins  1.2.10-4+b1
ii  libxine2-plugins       1.2.10-4

Versions of packages libxine2 recommends:
ii  libxine2-ffmpeg  1.2.10-4+b1

Versions of packages libxine2 suggests:
pn  libxine2-doc  <none>
pn  xine-ui       <none>

-- no debconf information

Reply via email to