Ubuntu
rhythmbox package

rhythmbox crashed with SIGSEGV in rhythmdb_entry_lookup_by_location_refstring()

Bug #543933 reported by toto
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Rhythmbox
Expired
Critical
rhythmbox (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: rhythmbox

my Samsung (YP-U3) was charging using a USB port for the last 10 minutes.
rythmbox was on for the last hour.
As I plugged a USB to bluetooth device, Rythmbox crashed.

have good time thanks for the job you are doing

best regards

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Mon Mar 22 06:31:48 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
Package: rhythmbox 0.12.7-0ubuntu7
ProcCmdline: rhythmbox --sm-client-id 10e23e27b112836806126920469073425600000013570037
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 rhythmdb_entry_lookup_by_location_refstring ()
 rhythmdb_entry_lookup_by_location ()
 rhythmdb_entry_new () from /usr/lib/librhythmbox-core.so.0
 ?? ()
 ?? ()
Title: rhythmbox crashed with SIGSEGV in rhythmdb_entry_lookup_by_location_refstring()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
toto (otot-toto) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 rhythmdb_entry_sync_mirrored (entry=0x95eb060,
 rhythmdb_commit_internal (db=0x95eb060,
 rhythmdb_set_property (object=0x9d8ff4, prop_id=9782393,
 impl_get_free_space (source=0x9fee230)
 add_mtp_track_to_db (source=<value optimized out>,

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
Pedro Villavicencio (pedro)
visibility: private → public
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=615181

Changed in rhythmbox (Ubuntu):
status: New → Triaged
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thanks for the report toto, may you please obtain a new backtrace following the steps on https://wiki.ubuntu.com/DebuggingProgramCrash ? That'd help a lot to solve the issue, thanks in advance!.

Changed in rhythmbox (Ubuntu):
status: Triaged → Incomplete
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: Unknown → New
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Any news about this?

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
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
importance: Unknown → Critical
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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