Description of problem: I keep getting an error message about a DBus service not being found for some CDs. After I get this message the CD will not show up, but restarting sound-juicer let me read the same CD without problems. The problem seemed random at first, but now I've narrowed it down to that the second CD in a sound-juicer "session" that is not in MusicBrainz causes this error. It seems like that the first MusicBrainz lookup that fails causes some problems in the internal state. Version-Release number of selected component (if applicable): sound-juicer-2.28.1-1.fc12.x86_64 How reproducible: Always Steps to Reproduce: (Several possibilities, this is the simplest) 1. Insert a CD that is not in MusicBrains 2. Eject the CD 3. Insert same CD again Actual results: The following error message (translated from Norwegian, so it may not match the English version extacly): Could not read the CD Sound Juicer could not read the track list of this CD. Cause: Can't access CD: Error while getting peer-to-peer dbus connection: The name :1.116 was not provided by any .service files Expected results: CD shows in sound-juicer. Additional info: A variant of this bug was reported as bug 543830 against 2.28.0. This error did probably cause a crash then, the fix for bug 539848 removed the crash, but the error dialogue described here persists.
Yeah, I'm seeing this too. It still exists in the rawhide package (2.28.1-2.fc13.x86_64) which isn't terribly surprising given the version number...
Hello, I also have this issue (F12 x86). The error message is the same except the end : "The name :1.77 was not provided by any .service files".
I see the same issue as Benjamin. It happens with a few audio CDs here on the first read. dmesg does not give any error. Appears to be a problem between Sound Juicer and dbus.
I'm also seeing this, in the same circumstances, on Ubuntu 10.10 - so I suspect it's a Sound Juicer bug. Could it be passed upstream? Gerv
Bug still in F14 Beta.
Bug still exists in 2.32.0-2.fc14
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping