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 started with an empty ~/.config/kew and started kew. I was prompted for the location of my music library and I specified: /run/media/alex/Card Vault/Test There's excactly one track, here: /run/media/alex/Card Vault/Test/Artist/Album/Track.mp3 I started kew, was shown Artist and Album, opened the Album, was shown the Track and was able to play it. I quit and restarted kew, and everything still worked. I looked at the diff between the new kewrc file and the old one I had. The following change restores the bug: fish: Job 1, 'kew' terminated by signal SIGSEGV (Address boundary error) alex@subterraneobombus ~/.c/kew [SIGSEGV]> diff-backup kewrc 15c15 < cacheLibrary=-1 --- > cacheLibrary=1 The default value is -1, so the bug is not triggered. When changed to 1, which I must have been using for a while, the bug is triggered. With the problematic setting, I can rm ~/.config/kew/kewlibrary and start kew. This writes the kewlibrary and if I quit kew and restart it, the bug is triggered. At this point, the content of the kewlibrary: 1 root 1 -1 1 Artist 1 1 1 Album 1 1 1 Track.mp3 0 1 For the moment I will set cacheLibrary=0 as the workaround. I cannot leave it at -1 or I will get asked the following: Would you like to enable a (local) library cache for quicker startup times? You can update the cache at any time by pressing 'u'. (y/n): Something is still wrong with reading the cache at startup, though. Currently, without the cache, starting up kew takes a bit more than 5s.
