Your message dated Wed, 19 Nov 2025 17:05:10 +0000 with message-id <E1vLlcE-00CZ2G-1u@fasolo.debian.org> and subject line Bug#1107296: fixed in libid3tag 0.16.3-2 has caused the Debian Bug report #1107296, regarding libid3tag: When processing tags with multiple entries, text is replaced by random chinese characters to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 1107296: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1107296 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libid3tag: When processing tags with multiple entries, text is replaced by random chinese characters
- From: Brian Arnold <connect@brian-arnold.dev>
- Date: Wed, 04 Jun 2025 18:53:36 -0500
- Message-id: <174908121692.51026.1487821338027433208.reportbug@conductor>
Source: libid3tag Version: 0.16.3-1 Severity: important Tags: patch upstream X-Debbugs-Cc: connect@brian-arnold.dev Dear Maintainer, * What led up to the situation? When mp3 files contain multiple "Artists", the secondary and beyond artists lose the Byte-Order-Mark, and become random chinese characters. This is due to a truly ANCIENT bug in libid3tag that affects all applications that use it. (Only seems to apply to tags that use utf-16?) * What exactly did you do (or not do) that was effective (or ineffective)? Read multiple artists from an mp3 with multiple artists, stored in UTF-16 * What was the outcome of this action? Standard Latin characters were converted into random chinese characters. * What outcome did you expect instead? Regular Latin text should not be converted into random chinese characters when reading tags with libid3tag I have already opened a pull request on the upstream repository to address the issue, just waiting for my pull request to be merged. See upstream package pull request #19: https://codeberg.org/tenacityteam/libid3tag/pulls/19 (Could we get this into Trixie before release? It makes libid3tag completely unusable if using UTF-16. I keep all my music stored in UTF-16, so I don't have any ASCII, UTF-8, or UTF-24 files to test against libid3tag) -- System Information: Debian Release: 13.0 APT prefers unstable APT policy: (500, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 6.12.30-amd64 (SMP w/16 CPU threads; PREEMPT) Kernel taint flags: TAINT_PROPRIETARY_MODULE, TAINT_OOT_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE not set Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled
--- End Message ---
--- Begin Message ---
- To: 1107296-close@bugs.debian.org
- Subject: Bug#1107296: fixed in libid3tag 0.16.3-2
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Wed, 19 Nov 2025 17:05:10 +0000
- Message-id: <E1vLlcE-00CZ2G-1u@fasolo.debian.org>
- Reply-to: Andreas Tille <tille@debian.org>
Source: libid3tag Source-Version: 0.16.3-2 Done: Andreas Tille <tille@debian.org> We believe that the bug you reported is fixed in the latest version of libid3tag, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1107296@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Andreas Tille <tille@debian.org> (supplier of updated libid3tag package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Wed, 19 Nov 2025 09:31:06 +0100 Source: libid3tag Architecture: source Version: 0.16.3-2 Distribution: unstable Urgency: medium Maintainer: Debian Multimedia Maintainers <debian-multimedia@lists.debian.org> Changed-By: Andreas Tille <tille@debian.org> Closes: 1106283 1107296 1113157 Changes: libid3tag (0.16.3-2) unstable; urgency=medium . * Team upload. . [ Andreas Tille ] * d/watch: version=5 * Standards-Version: 4.7.2 (routine-update) * Fix processing tags with multiple entries Closes: #1107296 * Remove erroneously included 10_utf16.patch Closes: #1106283 * debputy lint --auto-fix (routine-update) . [ Adrian Bunk ] * Add Homepage * Backport upstream fix for FTBFS with CMake 4. (Closes: #1113157) Checksums-Sha1: 227a435eaba85d23d4e215651e61fb2a053639ec 2063 libid3tag_0.16.3-2.dsc 3f6117d2979902dceb6c814771fb32d0938ceac2 7956 libid3tag_0.16.3-2.debian.tar.xz 82034eb57165abc407e91023e534601ef210d988 7177 libid3tag_0.16.3-2_amd64.buildinfo Checksums-Sha256: 4abc9177af8e340138d3ecbdd29a0027b20bb8cdfd3beda300ee1a7a12e73163 2063 libid3tag_0.16.3-2.dsc b6fd0b3f1c5673a5b394d6bd1a177ff4886b34cc4185edaa88a5764d75e9c07e 7956 libid3tag_0.16.3-2.debian.tar.xz f89571bf2e607302d0943a1486924dfd6e1efbd0151c5ce24e8a4cd61bb32f78 7177 libid3tag_0.16.3-2_amd64.buildinfo Files: c9bb18a2fecb525f51a0123b59c98c9c 2063 sound optional libid3tag_0.16.3-2.dsc 082badc5d897412fe8445d4c5de26db4 7956 sound optional libid3tag_0.16.3-2.debian.tar.xz 996afb68ee89b1bc9457a08a39e703fd 7177 sound optional libid3tag_0.16.3-2_amd64.buildinfo -----BEGIN PGP SIGNATURE----- iQJFBAEBCgAvFiEE8fAHMgoDVUHwpmPKV4oElNHGRtEFAmkd9EoRHHRpbGxlQGRl Ymlhbi5vcmcACgkQV4oElNHGRtG+6w/9GhBdXtq0aHSEjysMp7s+LOYxA/ZAkQwL VyyFd60bLpFAHGUQ2+kBg8cKeimMQBHVQeFkGezWlKDa1DYJBgV5JuHT5cMyv8WC y8aa5270CKL2iKjzqv+zUucskfl6O0VViI44J8IjGQw4CeTaqkdyVqarFv2jLuTT dqYzLQF/eHIVzPzn8SdLhIRW6rvZAO9AgCJHIkR5oN0dVUqPJyiBZgYETYieoEcS /GM2NHUQpxuOeth1CbZ00obue+KcHu9JX/hvPbqLwswbkOtcdzfKxeSGJhQ046vR Dr91CUv0Ivk9eBImFYLI7pGHMCD6Nm4VH56pNXdu7/AsW+nOU6XgM9eg428rDqga onnPwSqL7T6lt6fvQ38n2hdLyrTTqLSql6B3fx5XVV8eYMuNmN4qeBlVZ/K+dEUL g5hlUjdZTeE4AY5c0oTQX6E9ocstTu1r1KAEBH1OGy7Zeew5jzWIIYHYMkh8DXMm PAQTErGYP01D3kKbf2X/lQWFjyLVOCoqe37wPjQ5N0TcNUYB+EHKtjMohrtASnHu O/SwQiNdSKzI3ZxHpNpvORNn++jrQY0/FkBokvM4AoQTIt15fUY+ZOU2ZV9HgtJz 03rNAX1ieuHc/+2wG2O3ioY7KMWyYDkn9kKvh4IOHJ6NqqcNXB/6HkBLfllCdQJ3 w0PuyQRsWUw= =tdlr -----END PGP SIGNATURE-----Attachment: pgpKsoGKuATcY.pgp
Description: PGP signature
--- End Message ---