Floating point exception while populating playlist from folder with MIDI files

[Keantoken]

Binary package hint: audacious

Hello everyone. I realized I put this in the wrong place previously (https://answers.launchpad.net/ubuntu/+source/audacious/+question/118046), so I moved it here. I'm running version 2.3-1ubuntu4.

I just installed Ubuntustudio, Lucid. I chose to encrypt my home directory.

If I go to Open, and select my music folder, Audacious will begin playing the first file. After several seconds, audacious disappears. If I run from the terminal, this is what's left afterwards:

~$ audacious
Floating point exception
~$

If I run with the Sudo command, Audacious doesn't see the drive my music is on, I think this is because they are not owned by root (?).

 - keantoken

[Benjamin Drung (bdrung)]

Can you install the debug package and run audacious with gdb?

[Keantoken (keantoken)]

Alright, I ran with gdb and I got this while trying to get to the file.

Program received signal SIGSEGV, Segmentation fault.
0x001a7cc6 in g_slice_alloc () from /lib/libglib-2.0.so.0

Tried again, and ended up with this:

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb766ab70 (LWP 3578)]
0x01b6a7ab in __divdi3 () from /usr/lib/audacious/Input/amidi-plug.so

This reminds me, I think I selected the ALSA output plugin once and it brought up a bunch of error messages about not having plugins for certain files I think, and I remember it said something about MIDI (I have a few of those). I tried again but the errors didn't show up again, it just died.

 - keantoken

[Bryce Harrington (bryce)]

We'll need a more comprehensive bug report including backtraces and actual error message text (so we can search the codebase for the exact messages). Since many of us don't use encrypted home directories, providing exact steps to set up an environment to reproduce the problem is pretty vital here, too.

[Keantoken (keantoken)]

To create a test system, you would install Ubuntustudio, select all software installs. The installer will prompt you whether to use an encrypted home directory. That is all I did.

The directory holding my music is an NTFS drive from windows.

Here is the full text error message:

==============
$ gdb audacious
GNU gdb (GDB) 7.1-ubuntu
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/audacious...Reading symbols from /usr/lib/debug/usr/bin/audacious2...done.
done.
(gdb) run
Starting program: /usr/bin/audacious
[Thread debugging using libthread_db enabled]
[New Thread 0xb7e6bb70 (LWP 2908)]
[New Thread 0xb3669b70 (LWP 2909)]
[Thread 0xb3669b70 (LWP 2909) exited]
[New Thread 0xb3669b70 (LWP 2910)]
[New Thread 0xb65a7b70 (LWP 2911)]
[New Thread 0xb5da6b70 (LWP 2912)]
[New Thread 0xb55a5b70 (LWP 2913)]
[Thread 0xb55a5b70 (LWP 2913) exited]
[New Thread 0xb55a5b70 (LWP 2914)]
[Thread 0xb55a5b70 (LWP 2914) exited]
[New Thread 0xb55a5b70 (LWP 2915)]
[New Thread 0xb47ffb70 (LWP 2916)]

Program received signal SIGFPE, Arithmetic exception.
[Switching to Thread 0xb3669b70 (LWP 2910)]
0x01b377ab in __divdi3 () from /usr/lib/audacious/Input/amidi-plug.so
(gdb)
==========

If I select the folders or files individually, I can get it working without problems, save for the occasional MIDI error message (I don't have a MIDI synth set up).

I just tried opening a MIDI file. This time Audacious hangs, save for the scrolling filename. I get the output below, except it repeats several times every second with the number increasing by 1 every time. I tried ending it through the system monitor, but it won't exit! It is looking to me like the playlist loads until it encounters a MIDI file, and then that's what crashes it.

==========
[Thread 0xb4bfeb70 (LWP 5274) exited]
[New Thread 0xb4bfeb70 (LWP 5275)]
[Thread 0xb4bfeb70 (LWP 5275) exited]
[New Thread 0xb4bfeb70 (LWP 5276)]
[Thread 0xb4bfeb70 (LWP 5276) exited]
==========

 - keantoken

[Keantoken (keantoken)]

Alright, if I deliberately avoid folders with MIDI files, all is well! So it must be when it encounters MIDI files that it crashes.

 - keantoken

[Ross Gammon (rosco2)]

Hi,
I am just going through some old audacious bugs. Unfortunately, I cannot reproduce this bug on Audacious 3.4.3-1 (Trusy), nor on 3.2.4-1 (Debian Wheezy), and neither on 2.3-2 (Debian Squeeze).
The only thing different in my set up is that my home directory is not encrypted (I did test having the files on a Windows partition with the Debian Squeeze machiine).
Do you still have this problem? Have you tried one of the newer versions of Adacious?
Regards,
Ross

[Keantoken (keantoken)]

It's been 4 years since then, and I've changed distros several times. I haven't had the problem since and I cannot tell you how to reproduce it after so long.

[Launchpad Janitor (janitor)]

[Expired for audacious (Ubuntu) because there has been no activity for 60 days.]