GNOME Bugzilla – Bug 109723
Crash if you try to start a soundfile
Last modified: 2004-12-22 21:47:04 UTC
Package: rhythmbox Severity: normal Version: 0.4.5 Synopsis: Crash if you try to start a soundfile Bugzilla-Product: rhythmbox Bugzilla-Component: General BugBuddy-GnomeVersion: 2.0 (2.2.0.1) Description: Description of Problem: The Problem is, if I import some music files and I want to start them (double click) every time rhythmbox crash. Steps to reproduce the problem: 1. 2. 3. Actual Results: Expected Results: How often does this happen? Every time Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/net-rhythmbox' (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)...[New Thread 16384 (LWP 1389)] [New Thread 32769 (LWP 1390)] [New Thread 16386 (LWP 1391)] [New Thread 32771 (LWP 1392)] (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)... 0x40be1b89 in wait4 () from /lib/libc.so.6
+ Trace 35463
Thread 1 (Thread 16384 (LWP 1389))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-04-01 15:59 ------- The original reporter (benedikt@gnome-de.org) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, rhythmbox-maint@bugzilla.gnome.org.
*** Bug 110614 has been marked as a duplicate of this bug. ***
*** Bug 112691 has been marked as a duplicate of this bug. ***
This bug and both duplicates are crashes in net-rhythmbox. I believe the rythmbox maintainers just close bugs in that product, but I don't remember, so I'm leaving this open. Extra comments from bug 112691: Version: 0.4.8 Description of Problem: after a fresh install of the new version I've added more than 500 song to check if the program still crash, and it didn't, but after i dunno how many songs i get this crash Steps to reproduce the problem: 1. add a,lot of song more than 500 2. start playing these songs 3. wait :-) How often does this happen? dunno yet this is the first time that i run this version Since this stack trace appears to be unique (other than the duplicates which I have already marked), I'm setting severity->critical & priority->high (it's a crasher), adding the bugsquad keyword, and marking as new.
*** Bug 113192 has been marked as a duplicate of this bug. ***
Failed to duplicate. Marking this as FIXED in cvs HEAD. If you feel this is still relevant, please feel free to reopen. -harshy