This bug was fixed in the package audacious - 2.1-1ubuntu3
---
audacious (2.1-1ubuntu3) lucid; urgency=low
* Add 101_ui_vis_pixmap_nullptr.patch: Check return value of
gdk_pixmap_new() before dereferencing it.
(LP: #292020)
* Add 102_playlist_compare_path_assert.patch:
Breakpoint 2, ui_vis_expose (widget=0x97c4058, event=0xbffc1264) at ui_vis.c:549
549 obj = gdk_pixmap_new(NULL, vis-width*(vis-scaled ?
cfg.scale_factor : 1), vis-height*(vis-scaled ? cfg.scale_factor : 1),
gdk_rgb_get_visual()-depth);
(gdb) print cfg.scale_factor
$5 = 0
In my case,
This started happening to me as well, this morning. I don't have time to
debug further just now, but here are the arguments being passed to
gdk_pixmap_new...
#0 IA__gdk_pixmap_new (drawable=0x0, width=0, height=0, depth=24) at
/build/buildd/gtk+2.0-2.15.4/gdk/x11/gdkpixmap-x11.c:151
--
** Summary changed:
- audacious ends in segfault after upgrading to intrepid
+ audacious ends in segfault after upgrading to intrepid, crashes in
ui_vis_expose()
** Changed in: audacious (Ubuntu)
Importance: Undecided = High
Status: New = Triaged
--
audacious ends in segfault after
Hmm, the problem here seems to be that gdk_pixmap_new() is returning
NULL. According to the gtk docs, this can only happen when
gdk_rgb_get_visual()-depth equals 0. It might be interesting to step
through that routine and see what value depth actually is in this case,
however I can't reproduce
