rhythmbox crashed with SIGSEGV

Bug #523721 reported by zniavre
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: rhythmbox

randomly RB crash

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Wed Feb 17 15:55:31 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.6-1ubuntu10
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=fr_FR.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0xb31cfa47: mov (%eax,%esi,4),%eax
 PC (0xb31cfa47) ok
 source "(%eax,%esi,4)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
 ?? () from /usr/lib/libwebkit-1.0.so.2
Title: rhythmbox crashed with SIGSEGV
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
zniavre (zniavre2048-gmail) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 WebCore::TimerBase::heapDecreaseKey (this=0xb1d91d04)
 WebCore::TimerBase::setNextFireTime (this=0xb1d91d04,
 WebCore::TimerBase::stop (this=0xb1d91d04)
 WebCore::MainResourceLoader::didCancel (this=0xb1d91a00,
 WebCore::ResourceLoader::cancel (this=0xb1d91a00,

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 :

webkit crash? interesting. Do you have any steps on how to reproduce the issue?

visibility: private → public
Changed in rhythmbox (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: New → Incomplete
Revision history for this message
Pedro Villavicencio (pedro) wrote :

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!.

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.