Bug#377704: marked as done (madman: Madman crashes with 'tRuntimeError' when trying to do anything!)
Your message dated Fri, 5 Feb 2010 14:40:24 +0000 (WET)
with message-id <20100205144024.2A20A6C64@kmos.homeip.net>
and subject line Package madman has been removed from Debian
has caused the Debian Bug report #377704,
regarding madman: Madman crashes with 'tRuntimeError' when trying to do anything!
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 firstname.lastname@example.org
Debian Bug Tracking System
Contact email@example.com with problems
--- Begin Message ---
Justification: renders package unusable
Someone's obviously been hard at work on madman, it's changed quite
drastically at the last update (and not entirely for the better!).
However, it now has a serious crash problem.
It loads up my existing madman.mad database alright, but then any action
on the playlist (such as double-clicking a song to play it, changing the
rating of a song, auto DJing 20 songs, pressing the forward button to go
to the next song, etc) causes it to quit with the following message:
terminate called after throwing an instance of 'tRuntimeError'
what(): Invalid field id 2097197 while sorting list of songs
The field id number is different each time, the rest of the error
is always the same.
Because it crashes un-cleanly, it leaves the database file locked
so you have to Break Lock on next run.
Here's an oddity. If instead of breaking the lock during startup, I select
Cancel, so that it doesn't load my existing database; and if I then open
said database manually using File>Open, and *then* select Break Lock,
it seems to work fine without crashing.
When creating a new database from scratch, I found that with a small set
of files it worked ok, but with a large set (ie my complete music collection)
the same crash happens -- ie as soon as it has read all the tags etc,
select any file for playback and it crashes. Ditto if instead of doing
that you save the new db and specify it on the commandline. But
again, if I save this db, quit and restart madman, and load the db
using File>Open, it works.
So in summary, if you specify a (sufficiently large) db at startup, or
you create one, it crashes on any playlist op; but if you use File>Open
to load the db, it's apparently ok.
On the bright side, one of the bugs I reported earlier (#365903) is fixed :)
Though not at all in the way I would have liked :(
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (100, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.16-qolc-2006060407
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968)
Versions of packages madman depends on:
ii libc6 2.3.6-15 GNU C Library: Shared libraries
ii libgcc1 1:4.1.1-7 GCC support library
ii libglib1.2 1.2.10-10.1 The GLib library of C routines
ii libgtk1.2 1.2.10-18 The GIMP Toolkit set of widgets fo
ii libqt3-mt 3:3.3.6-2 Qt GUI Library (Threaded runtime v
ii libstdc++6 4.1.1-7 The GNU Standard C++ Library v3
ii libtag1c2a 1.4-4 TagLib Audio Meta-Data Library
ii libx11-6 2:1.0.0-7 X11 client-side library
ii libxext6 1:1.0.0-4 X11 miscellaneous extension librar
ii libxi6 1:1.0.0-5 X11 Input extension library
ii xmms 1.2.10+cvs20060429-1 Versatile X audio player
ii zlib1g 1:1.2.3-12 compression library - runtime
madman recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
You filed the bug http://bugs.debian.org/377704 in Debian BTS
against the package madman. I'm closing it at *unstable*, but it will
remain open for older distributions.
For more information about this package's removal, read
http://bugs.debian.org/384397. That bug might give the reasons why
this package was removed and suggestions of possible replacements.
Don't hesitate to reply to this mail if you have any question.
Thank you for your contribution to Debian.
--- End Message ---