After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 685402 - rhythmbox crashes with SIGABRT
rhythmbox crashes with SIGABRT
Status: RESOLVED OBSOLETE
Product: rhythmbox
Classification: Other
Component: playback
2.98
Other Linux
: High critical
: ---
Assigned To: RhythmBox Maintainers
RhythmBox Maintainers
Depends on:
Blocks:
 
 
Reported: 2012-10-03 15:29 UTC by Grant
Modified: 2013-05-01 20:44 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
backtrace (15.23 KB, text/x-log)
2012-10-03 15:29 UTC, Grant
Details
stacktrace (12.63 KB, application/octet-stream)
2012-10-03 21:02 UTC, Grant
Details
another stacktrace (18.65 KB, text/plain)
2012-10-03 21:50 UTC, Grant
Details

Description Grant 2012-10-03 15:29:37 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.
Comment 1 Jonathan Matthew 2012-10-03 20:50:56 UTC
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!
Comment 2 Grant 2012-10-03 21:02:57 UTC
Created attachment 225717 [details]
stacktrace
Comment 3 Grant 2012-10-03 21:03:44 UTC
(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
Comment 4 Jonathan Matthew 2012-10-03 21:29:03 UTC
Thanks, but that doesn't include enough information. Please install debug symbols for glib, gobject-introspection and pygobject and get another stack trace.
Comment 5 Grant 2012-10-03 21:50:56 UTC
Created attachment 225725 [details]
another stacktrace
Comment 6 Jonathan Matthew 2012-10-03 23:10:38 UTC
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?
Comment 7 Grant 2012-10-04 01:41:42 UTC
(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.
Comment 8 Jonathan Matthew 2012-10-04 01:44:00 UTC
Newer version of pygobject.
Comment 9 foss.freedom 2012-10-13 15:14:13 UTC
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?
Comment 10 Jonathan Matthew 2012-10-13 22:17:53 UTC
(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.