Ubuntu
rhythmbox package

rhythmbox crashed while enabling MTP plugin

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

Bug Description

Binary package hint: rhythmbox

I was enabling the MTP plugin to work with my Creative Zen Vision 30gb

ProblemType: Crash
Architecture: i386
Date: Thu Jul 19 21:54:15 2007
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/rhythmbox
NonfreeKernelModules: fglrx
Package: rhythmbox 0.11.1-0ubuntu3
PackageArchitecture: i386
ProcCmdline: rhythmbox
ProcCwd: /home/bhalter
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 5
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: rhythmbox crashed with signal 5
Uname: Linux runabout 2.6.22-8-generic #1 SMP Thu Jul 12 15:59:45 GMT 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin mythtv netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Bryan (bhalter-launchpad) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:load_mtp_db_idle_cb (source=0x82c40e0) at rb-mtp-source.c:324
g_idle_dispatch (source=0x8e2f7c8, callback=0x68, user_data=0x82c40e0) at /build/buildd/glib2.0-2.13.6/glib/gmain.c:4131
IA__g_main_context_dispatch (context=0x817d690) at /build/buildd/glib2.0-2.13.6/glib/gmain.c:2061
g_main_context_iterate (context=0x817d690, block=1, dispatch=1, self=0x80fa408) at /build/buildd/glib2.0-2.13.6/glib/gmain.c:2694
IA__g_main_loop_run (loop=0x854ae40) at /build/buildd/glib2.0-2.13.6/glib/gmain.c:2898

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. This bug has been reported to the developers of the software. You can track it and make comments here: http://bugzilla.gnome.org/show_bug.cgi?id=463949

Changed in rhythmbox:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: New → Confirmed
status: Confirmed → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: New → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: New → Invalid
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you try if that's an issue in hardy or intrepid?

Changed in rhythmbox:
status: Triaged → 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:
status: Incomplete → Invalid
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
importance: Unknown → Critical
status: Invalid → Unknown
Bug Watch Updater (bug-watch-updater)
Changed in rhythmbox:
status: Unknown → Invalid
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.