Your message dated Sun, 07 Dec 2025 14:13:36 +0100
with message-id <[email protected]>
and subject line Re: Bug#1120775: kew: terminated by signal SIGSEGV (Address
boundary error)
has caused the Debian Bug report #1120775,
regarding kew: terminated by signal SIGSEGV (Address boundary error)
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 [email protected]
immediately.)
--
1120775: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120775
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: kew
Version: 3.5.2+ds-2
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
When I start kew, I get a SIGSEV.
fish: Job 1, 'kew' terminated by signal SIGSEGV (Address boundary error)
If I start it with gdb:
(gdb) run
Starting program: /usr/bin/kew
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/aarch64-linux-gnu/libthread_db.so.1".
Program received signal SIGSEGV, Segmentation fault.
0x0000fffff6f84150 in ?? () from /lib/aarch64-linux-gnu/libc.so.6
I'm running it on an arm64 (MNT Pocket Reform). A few hours ago it still worked,
so I'm assuming this is due to the recent upgrade.
Regards
Alex
-- System Information:
Debian Release: forky/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: arm64 (aarch64)
Kernel: Linux 6.17.7-mnt-reform-arm64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_FORCED_MODULE, TAINT_CRAP, TAINT_OOT_MODULE,
TAINT_UNSIGNED_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
Versions of packages kew depends on:
ii libc6 2.41-12
ii libchafa0t64 1.16.2-1
ii libfftw3-single3 3.3.10-2+b1
ii libgcc-s1 15.2.0-8
ii libglib2.0-0t64 2.86.1-2
ii libogg0 1.3.6-1
ii libopus0 1.5.2-2
ii libopusfile0 0.12-4+b3
ii libstdc++6 15.2.0-8
ii libtag2 2.1.1-2
ii libvorbis0a 1.3.7-3
ii libvorbisfile3 1.3.7-3
kew recommends no packages.
kew suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
On Sun, 07 Dec 2025 12:34:17 +0100 "Alex Schroeder" <[email protected]>
wrote:
On Tue Nov 25, 2025 at 11:25 PM CET, Matthias Geiger wrote:
> On Tue, 18 Nov 2025 15:33:59 +0100 "Alex Schroeder" <[email protected]>
wrote:
>> On Sun Nov 16, 2025 at 4:09 PM CET, Matthias Geiger wrote:
>> > I suspect this could be related to playlists and/or relative paths. Can
>> > you please try to find a reproducer for this crash? Does this only
>> > happen with a playlist, or does playing regular albums / titles work? It
>> > does for me.
> I uploaded 3.6.2 today; can you check if it fixed things for you?
Hi
I used 3.6.4 today and noticed the following:
- No more crashes. I used cacheLibrary -1, 0 and 1 and it always
started up.
- Strangely, with cacheLibrary=1 it didn't start any faster than with
cacheLibrary=0.
I did rough timing by starting "time kew radiohead" and hitting q all
the time so it would quit asap. The library is 1.8 MB. Right now it
seems that there is no startup speed improvement.
Fixed then, so closing.
--- End Message ---
