rhythmbox crashed with SIGSEGV in gst_pad_send_event()

[Richard Eames]

Binary package hint: rhythmbox

I'm not sure what caused this, I left RB playing while I was away and when I returned it crashed. I think it could be a faulty music file I have.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.11.6svn20080807-0ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=/home/username/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/gstreamer-0.10/libgstadder.so
 gst_pad_send_event ()
 gst_pad_push_event ()
 gst_pad_send_event ()
 gst_pad_push_event ()
Title: rhythmbox crashed with SIGSEGV in gst_pad_send_event()
Uname: Linux 2.6.26-5-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev sambashare video

[Apport retracing service (apport)]

StacktraceTop:gst_adder_sink_event (pad=0x1f6f000, event=0xc9ca40) at gstadder.c:694
gst_pad_send_event (pad=0x1f6f000, event=0xc9ca40) at gstpad.c:4329
gst_pad_push_event (pad=0x1c8c380, event=0xc9ca40) at gstpad.c:4185
gst_pad_send_event (pad=0x1cebb10, event=0xc9ca40) at gstpad.c:4329
gst_pad_push_event (pad=0x1f7f2e0, event=0xc9ca40) at gstpad.c:4185

[Chris Halse Rogers (raof)]

I've just seen this also, although in my case it occured as rhythmbox was quitting.

[ktp420 (ktp420)]

I just ran into this also...it was playing music in the background with random and repeat set.

[Michael Nagel (nailor)]

had this, too. it happened when playing flash games with rhythmbox running in the background.

[Omer Akram (om26er)]

could anyone please confirm if the issue is still happening with rhythmbox 0.12.8 or 0.13.2

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!