GNOME Bugzilla – Bug 685402
rhythmbox crashes with SIGABRT
Last modified: 2013-05-01 20:44:20 UTC
Created attachment 225688 [details] backtrace Playing any song in my library causes Rhythmbox to crash with the message: *** buffer overflow detected ***: rhythmbox terminated Seems to occur near line 1332 of rhythmdb.c in rhythmdb_emit_entry_signals_idle() Full message with backtrace attached.
Thanks for taking the time to report this bug. Without a stack trace from the crash it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Created attachment 225717 [details] stacktrace
(In reply to comment #1) > Thanks for taking the time to report this bug. > Without a stack trace from the crash it's very hard to determine what caused > it. > Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces > for more information on how to do so. Thanks in advance! Attached stacktrace
Thanks, but that doesn't include enough information. Please install debug symbols for glib, gobject-introspection and pygobject and get another stack trace.
Created attachment 225725 [details] another stacktrace
Since pygobject 3.2.2, there have been some changes to the code that appears to be causing the crash here. Any chance you could try a newer version?
(In reply to comment #6) > Since pygobject 3.2.2, there have been some changes to the code that appears to > be causing the crash here. Any chance you could try a newer version? Newer version of rhythmbox?... This bug was filed against 2.98.
Newer version of pygobject.
I can confirm that the webupd8team PPA hosting RB v2.98 is unstable in 12.04 - also that the older pygobject using is 12.04 is the issue. Uplifting to v3.4 fixes this issue. However, given that Unity seems to depend on this older version - if using this DE I wouldnt recommend upgrading pygobject on stability grounds. I'm wondering - if it isnt already - should the build requirements for RB v2.98 be changed to make pygobject version >= v3.4 ? Alternatively - could RB2.8 be patched to not "invoke" the code that is causing this stack-overflow/segmentation fault?
(In reply to comment #9) > I'm wondering - if it isnt already - should the build requirements for RB v2.98 > be changed to make pygobject version >= v3.4 ? Probably. > Alternatively - could RB2.8 be patched to not "invoke" the code that is causing > this stack-overflow/segmentation fault? No.