rhythmbox crashed with SIGSEGV in g_object_set_valist()

Bug #552562 reported by Alexander
32
This bug affects 7 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Invalid
Undecided
Unassigned
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

just stopped and quit

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: rhythmbox 0.12.8-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-17.26-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-17-generic i686
Architecture: i386
Date: Wed Mar 31 16:34:40 2010
Disassembly: => 0x0: Cannot access memory at address 0x0
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_DK.utf8
 SHELL=/bin/bash
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_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_set () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
 ?? () from /usr/lib/librhythmbox-core.so.0
Title: rhythmbox crashed with SIGSEGV in g_object_set_valist()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alexander (anlazarov) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_object_set () from /usr/lib/libgobject-2.0.so.0
 start_stream_fade (stream=0x1, start=1, end=0,
 actually_start_stream (stream=<value optimized out>,
 stream_src_blocked_cb (pad=0x917cbf8, blocked=1,

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

Thanks for the report, will send it upstream, leaving it as confirmed for now.

visibility: private → public
Changed in rhythmbox (Ubuntu):
status: New → Confirmed
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=615170

Changed in rhythmbox (Ubuntu):
status: Confirmed → Triaged
Changed in rhythmbox:
status: Unknown → New
Changed in rhythmbox:
importance: Unknown → Critical
Revision history for this message
dino99 (9d9) wrote :

This version has expired

Changed in rhythmbox (Ubuntu):
status: Triaged → Invalid
Changed in rhythmbox:
importance: Critical → Undecided
status: New → 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.