From:  <>
To: submit@bugs.gnome.org
X-Mailer: bug-buddy 2.11.1
Subject: Rhythmbox crash

Distribution: Ubuntu 5.10 (breezy)
Package: rhythmbox
Severity: critical
Version: GNOME2.11.90 0.9.x
Gnome-Distributor: Ubuntu
Synopsis: Rhythmbox crash
Bugzilla-Product: rhythmbox
Bugzilla-Component: General
Bugzilla-Version: 0.9.x
BugBuddy-GnomeVersion: 2.0 (2.11.2)
Description:
Description of the crash:
I try to open rhythmbox and get an error dialog right away:
You can inform the developers of what happened to help them fix it. Or
you can restart the applicatino right now.

Steps to reproduce the crash:
1. Try to open rhythmbox in any way.. through any of the panels
2.
3.

Expected Results:
It never opens and the error dialog pops up to submit the bug

How often does this happen?
Whenever I try and use rhythmbox.

Additional Information:
I am using Breezy Badger 5.10 colony 3


Debugging Information:

Backtrace was generated from '/usr/bin/rhythmbox'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
`system-supplied DSO at 0xffffe000' has disappeared; keeping its
symbols.
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1225283904 (LWP 8920)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 62838

------- Bug moved to this database by unknown@gnome.bugs 2005-09-09 16:26 UTC -------


The original reporter of this bug does not have
   an account here. Reassigning to the person who moved
   it here, unknown@gnome.bugs.
   Previous reporter was javroch421@aol.com.