Rhythmbox 0.12.5 crashes during changes with mouse-wheel

Bug #469592 reported by Brice
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

Ubuntu 9.10

Rhythmbox 0.12.5
(0.12.5-0ubuntu4)
Putting the sound low with the mouse-wheel, the program quits.
The sounds was supposed to go down until the sound stops.
But the Rhythmbox crashes

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sun Nov 1 22:46:49 2009
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.5-0ubuntu4
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 g_object_set () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 g_object_set_valist () from /usr/lib/libgobject-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_object_set()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin audio cdrom dialout lpadmin netdev plugdev sambashare video

Revision history for this message
Brice (brice-pedrono) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:?? ()
g_object_set () from /usr/lib/libgobject-2.0.so.0
gst_play_sink_set_volume (playsink=0x1,
gst_play_bin_set_property (object=0x970c058, prop_id=17,
g_object_set_valist () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in rhythmbox (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

visibility: private → public
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.