rhythmbox crashed with SIGSEGV in _gtk_marshal_VOID__BOXED_BOXED()

Bug #349375 reported by Duncan Lithgow
8
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

I tried to play something and got slightly melodic static at high speed... so I closed Rhythmbox, and then tried to restart it - then this bug.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.0-0ubuntu1
ProcCmdline: rhythmbox
ProcEnviron:
 PATH=(custom, user)
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/gtk-2.0/modules/libgail.so
 _gtk_marshal_VOID__BOXED_BOXED (closure=0xb2868e8,
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in _gtk_marshal_VOID__BOXED_BOXED()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :
visibility: private → public
description: updated
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:model_row_changed (tree_model=0xb369120, path=0xb2a2448, iter=0xb293db0,
_gtk_marshal_VOID__BOXED_BOXED (closure=0xb2868e8,
IA__g_closure_invoke (closure=0xb2868e8, return_value=0x0,
signal_emit_unlocked_R (node=0xa4e87c0, detail=0,
IA__g_signal_emit_valist (instance=0xb369120,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in rhythmbox:
importance: Undecided → Medium
Revision history for this message
Andreas Moog (ampelbein) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:
1. Is this reproducible?
2. If so, what specific steps should we take to recreate this bug? Be as detailed as possible.
This will help us to find and resolve the problem.

Changed in rhythmbox (Ubuntu):
assignee: nobody → desktop-bugs
status: New → Incomplete
Revision history for this message
Duncan Lithgow (duncan-lithgow) wrote :

No, I can't reproduce this at the moment.

Revision history for this message
Andreas Moog (ampelbein) wrote :

In that case, I'm closing here. Please set bug status to new if you find a testcase that makes it crash reproducibly. Thanks.

Changed in rhythmbox (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.