GNOME Bugzilla – Bug 127830
Crashes when is going to start playing
Last modified: 2009-08-15 18:40:50 UTC
Distribution: Debian testing/unstable Package: rhythmbox Severity: critical Version: 0.6.0 Synopsis: Crashes when is going to start playing Bugzilla-Product: rhythmbox Bugzilla-Component: General Bugzilla-Version: 0.6.0 BugBuddy-GnomeVersion: 2.0 (2.4.0.1) Description: Description of the crash: When is goinng to start playing sometimes crashes, I don't know why :P Debugging Information: Backtrace was generated from '/usr/bin/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 1087085952 (LWP 10378)] [New Thread 1134324688 (LWP 10420)] [New Thread 1087085952 (LWP 10378)] [New Thread 1134324688 (LWP 10420)] [New Thread 1087085952 (LWP 10378)] [New Thread 1134324688 (LWP 10420)] [New Thread 1122048976 (LWP 10386)] [New Thread 1113660368 (LWP 10385)] [New Thread 1105271760 (LWP 10384)] [New Thread 1096883152 (LWP 10383)] (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)...0x40b735d7 in select () from /lib/tls/libc.so.6
+ Trace 42044
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-11-24 14:10 ------- Unknown version 0.6.0 in product rhythmbox. Setting version to the default, "unspecified". Reassigning to the default owner of the component, rhythmbox-maint@bugzilla.gnome.org.
This looks like it may be a duplicate of bug 127647.
Is it for any particular songs? Are they MP3s? Vorbis files? How often does this happen? Which backend are you using? Also, can you try getting more backtraces? It would also help to recompile Rhythmbox with debugging information.
no reply in months, bug closed. Feel free to reopen with the asked details if you still get the issue.