Description of problem: I'm using LXDE or WindowMaker. Both of them have an error when starting sound-juicer "couldn't find any CD-ROM drives to read". Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3.
Created attachment 277 [details] sound-juicer error message
Can the CD drive be used with other apps? with other CD types? What's the output of: ls -l /dev/cd*
Keywords: (none) => NEEDINFO
I used to open CD with Banshee. Than sound-juicer could see it. I installed some sofware (abcde, Grip, lame and something else) so now it can open it. Anyway # ls -l /dev/cd ls: cannot access /dev/cd: No such file or directory # ls -l /dev/cdrom lrwxrwxrwx 1 root root 3 Apr 22 19:29 /dev/cdrom -> sr0 [root@AMD_x4 Various-Easy_rider]#
(In reply to comment #3) > > # ls -l /dev/cd > ls: cannot access /dev/cd: No such file or directory (There's a missing *, it's 'ls -l /dev/cd*') Does work right after a reboot (without starting any of the apps you mentioned before starting sound-juicer)?
It looks like I reboot originally. Anyway, I could overreact. It still happens on some home burned CD.
When it happens with a home-burned CD, does it work with other CD's? When it happens could you try starting sound-juicer from terminal, see if you get any useful messages there.
Standart responce: (sound-juicer:8888): Gtk-CRITICAL **: IA__gtk_widget_get_accessible: assertion `GTK_IS_WIDGET (widget)' failed ** (sound-juicer:8888): CRITICAL **: atk_object_add_relationship: assertion `ATK_IS_OBJECT (object)' failed ** (sound-juicer:8888): CRITICAL **: atk_object_add_relationship: assertion `ATK_IS_OBJECT (object)' failed Tried a few times. One CD constantly failed to be mounted. After clicking 'Close' (see attachement) and 'Re-read Disk' (Disk menu) it gives the same respond and lists tracks.
Created attachment 287 [details] Couldn' read the CD error
@ Palm Did this get solved? Or is the problem still there in current cauldron?
CC: (none) => marja11
Different message now (see attachment). I can open CD in PCManFm and play file.
Created attachment 934 [details] error getting peer-to-peer dbus connection
@ Palm Sorry, I'm sometimes not good at understanding things :/ This is with updated cauldron? Both under lxde and windowmaker? You get the error message, but apart from that: everything works fine now?
That was about Mageia1. The problem: sound-jucer can't rip some of home burn CD even when I can open and play files. I'm not using Cauldron yet.
Version: Cauldron => 1Summary: sound-juicer couldn't find any CD-ROM drives to read => sound-juicer can't rip some home burn CD's
What is your definition of "rip" ?
CD extractor - $ sound-jucer - reads a CD and lets to extract/rip songs in according to your setting.
and which settings do you choose?
cc'ing committers of sound-juicer
CC: (none) => dmorganec, eandry
You may choose/change setting after CD is present. Unfortunately, there is no CD present for sound-jucer.
(In reply to comment #18) > You may choose/change setting after CD is present. Unfortunately, there is no > CD present for sound-jucer. Outch! @ eandry Can you help to find out why that is? (I guess you know sound-juicer because you imported it)
Keywords: NEEDINFO => (none)
Kamil found some interesting links: https://bugs.launchpad.net/ubuntu/+source/sound-juicer/+bug/622213 https://bugzilla.redhat.com/show_bug.cgi?id=544843 (In reply to comment #11) > Created attachment 934 [details] > error getting peer-to-peer dbus connection When looking further, starting from those two links, I found an upstream bug report. https://bugzilla.gnome.org/show_bug.cgi?id=663459 @ Palm Can you please confirm in that report that you have the same bug? I suppose the more people report it, the more chance it'll get fixed :)
See Also: (none) => https://bugzilla.gnome.org/show_bug.cgi?id=663459Whiteboard: (none) => UPSTREAM
upstream report was closed as invalid @ Palm Did you happen to try whether this problem exists for sound-juicer in cauldron, too?
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad
Status: NEW => RESOLVEDResolution: (none) => WONTFIX