GNOME Bugzilla – Bug 139269
Rhythmbox fails to start
Last modified: 2004-12-22 21:47:04 UTC
Distribution: Gentoo Base System version 1.4.3.13p1 Package: rhythmbox Severity: critical Version: GNOME2.6. unspecified Gnome-Distributor: Gentoo Linux Synopsis: Rhythmbox fails to start Bugzilla-Product: rhythmbox Bugzilla-Component: General Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.6.0) Description: Description of the crash: Completed Gentoo emerge of Rhythmbox 0.6.8. Startup produces the following output and fails to start. INFO (16614: 0) Initializing GStreamer Core Library version 0.6.4 INFO (16614: 0) CPU features: (00000780) MMX SSE 3DNOW MMXEXT INFO (16614: 0) registry: loaded global_registry in 0.115321 seconds (/var/lib/cache/gstreamer-0.6/registry.xml) (rhythmbox:16614): Rhythmbox-CRITICAL **: /apps/rhythmbox/state/play_order gconf key not found! (rhythmbox:16614): Rhythmbox-WARNING **: Unknown value "" in GConf key "/apps/rhythmbox/state/play_order". Using linear play order. (gnome_segv:16620): Gtk-WARNING **: Ignoring the separator setting Expected Results: A pretty application to play my legal music. How often does this happen? Everytime Additional Information: none Debugging Information: Backtrace was generated from '/usr/bin/rhythmbox' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...(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)...0x40bbe40b in waitpid () from /lib/libpthread.so.0
+ Trace 45763
------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-04-06 13:57 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "rhythmbox". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was mark@pavlidis.org. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
I manually added the /apps/rhythmbox/state/play_order key and was able to start the app. Is this an initialization problem or should I forward this on the gentoo people if it is a distro specific issue.
You should have filed this bug on bugs.gentoo.org *BEFORE* filing it here. The gentoo maintainer will take care of forwarding it here if it's a bug in rhythmbox and not in the ebuild or on your system. http://bugs.gentoo.org/show_bug.cgi?id=45417 *** This bug has been marked as a duplicate of 136036 ***
From http://bugs.gentoo.org/whatisthis.html: « Please note that bugs should BE POSTED HERE FIRST BEFORE MOVING UPSTREAM. In other words, don't bother the original package maintainers before you bother us » Sorry if I may sound a bit harsh, but I get at least 1 duplicate of this bug everyday from gentoo user when it's actually a bug in the ebuild and not in rhythmbox.
*** Bug 139609 has been marked as a duplicate of this bug. ***
The likely reason you are getting so many duplicates from Gentoo users is that the bug causes Bug Buddy to fireup, so people are trying to be helpful and report. This is an inherent problem with user bug reports. I don't know about you but I don't have time to read though every bug report to see if I might have a duplicate, but I still want to help out where I can. So, bug reporting methods need to change, but those are structural changes that require new paradigms. Then you either get dups or get nothing. </rant> Thanks for the cool software.