I'd seen this, but then couldn't replicate it when debugging.
That's because I'd cleaned up my playlist so it didn't trigger
#491097, and loading another playlist triggered it.
Line numbers from 1.5.1-2, and the bug is calling
tuple_get_int(NULL, ..., ...).
playlist.c:2432
else if ((entry->tu
Hi,
Well, if you could do the following for me it will make things easier:
(1) install audacious-dbg, audacious-plugins-dbg, libglib2.0-0-dbg
(2) gdb audacious
(3) inside gdb, "br g_return_if_fail_warning"
(4) inside gdb, "run --no-log"
(5) continue each time this call is made until you find the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
William Pitcock wrote:
| severity 491655 important
| thanks
|
| Thank you for taking the time to report a bug in Audacious in Debian and
| thus make it better.
|
| This is not a critical bug however. :)
As I said in the bug report, it's probably not
severity 491655 important
thanks
Thank you for taking the time to report a bug in Audacious in Debian and
thus make it better.
This is not a critical bug however. :)
William
On Sun, 2008-07-20 at 23:44 -0700, Alex Malinovich wrote:
> Package: audacious
> Version: 1.5.1-1
> Severity: critical
>
Package: audacious
Version: 1.5.1-1
Severity: critical
Justification: causes serious data loss
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The audacious log file in ~/.config/audacious/log is growing out of
control with the following error:
tuple_get_int: assertion `tuple != NULL' failed
I do
5 matches
Mail list logo
