rhythmbox crashed with SIGSEGV in g_file_get_child()

Bug #524925 reported by brownknight
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

1. Using Ubuntu Lucid
2. I was updating music library location from preferences then rhythmbox crashed.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Feb 20 07:02:59 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.6git20100218-0ubuntu1
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-13.18-generic
SegvAnalysis:
 Segfault happened at: 0xab6e29 <g_file_get_child+41>: mov (%esi),%edx
 PC (0x00ab6e29) ok
 source "(%esi)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
 destination "%edx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 g_file_get_child () from /usr/lib/libgio-2.0.so.0
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0
Title: rhythmbox crashed with SIGSEGV in g_file_get_child()
Uname: Linux 2.6.32-13-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev ramil sambashare tape vboxusers video

Revision history for this message
brownknight (ramilclarin) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_file_get_child () from /usr/lib/libgio-2.0.so.0
 gtk_file_system_model_got_files (object=0x9ee1018,
 ?? () from /usr/lib/libgio-2.0.so.0
 g_simple_async_result_complete ()
 ?? () from /usr/lib/libgio-2.0.so.0

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
visibility: private → public
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in rhythmbox (Ubuntu):
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.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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