Audacious - OLD, PLEASE USE GITHUB DISCUSSIONS/ISSUES

The search tool plugin doesn't access any files directly. Probably you have a corrupted file, or one that is not parsed correctly, somewhere in your playlist/library. When you have found the file, please get back to us.

I'm having the same issue when adding empty MP3 files in audacious-3.2.4-1.fc17.x86_64.

Shocking that an lseek() would be invalid on a 0 byte file...

In all seriousness though, those error messages are created by the VFS layer which has no idea what you want to do. We just added them because people were all like OMG AUDACIOUS JUST DOES NOTHING WHEN I ADD A 0 BYTE FILE!!!oneoneone.

I suppose what you're actually after is enhanced error-messages.

The lseek error with an empty file is not under our control, it's mpg123's doing. But as nenolod says, it's a very generic error message so there's no reason to suppose that Mr. Breysse is adding empty files to his playlist until he responds. And until then, "me too" comments are not helpful.

I took John's original answer (thank you) and used Rhythmbox to scan the entire 104 191 items 1.4 Tb Music folder. It found various problems, empty files etc... and they were all deleted so that Rhythmbox wouldn't report any more errors. Then I ran the search tool on Audacious again and it did go a bit further without any error message but after several tries, every time Audacious just locks during the search and has to be killed every. Is there any logs I could attach to help understand what's happening?

The first thing I would try is this:

When Audacious locks up, instead of killing it, run:

$ gdb -p `pidof audacious`
(gdb) thread apply all bt

This should tell us where (and hopefully why) it's locking up.

This backtrace doesn't show anything abnormal. The main thread is sitting in the GTK+ main loop, so in theory it should be ready to respond to user input.

OK then so what else can be done? To be a bit more clear, this happen when I scan the whole music folder to update the library. First the "Searching" windows appears and the scan proceeds without problem, then Audacious starts counting the number of minutes (lower right corner) until the counter stops at 0:00/914:00:43, then Audacious becomes dark and doesn't respond anymore.

AO Breysse wrote:

OK then so what else can be done?

If you run "audacious -V > log.txt" and look at the last few lines of the log after the program locks up, you might be able to narrow the problem down to a particular file.

As a matter of fact, the problem just doesn't happen anymore with the latest updated 3.3.1. I'm not sure why, nothing changed of late in my music folder, maybe the ltest updates got rid of it. It's all OK now.