Bug 63174 - kaudiocreator error "/By Track/Track 01.wav" should start with "audiocd:/"
Summary: kaudiocreator error "/By Track/Track 01.wav" should start with "audiocd:/"
Status: RESOLVED FIXED
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: audiocd (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: rik
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-08-24 00:59 UTC by Roger Larsson
Modified: 2004-06-05 19:08 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Roger Larsson 2003-08-24 00:59:41 UTC
Version:           0.99 (using KDE 3.1.9)
Compiler:          gcc version 3.2
OS:          Linux (i686) release 2.4.19-4GB

Had a config error like in bug:50767
(no rw access to /dev/sg1, why is write access needed?)
But got no warning...

I did get the track list.
But Selecting and Ripping gave the error "The file or directory /By Track/Track 01.wav does not exist." 

If it had read "... audiocd:/By Track/Track 01.wav ..." I would have found out the cause much sooner...
Comment 1 icefox 2003-08-26 04:17:45 UTC
This would have to do with the audiocd:// error reporting.  Not sure why you 
needed rw.  Or would this go to KIO, Rik? 
Comment 2 icefox 2004-03-22 05:24:16 UTC
It when checking for a drive it puts out the correct error for:
-If the file even exists: ERR_DOES_NOT_EXIST
-If read permissions: ERR_CANNOT_OPEN_FOR_READING
-If write permissions: ERR_CANNOT_OPEN_FOR_WRITING
and finally defaults to just ERR_ACCESS_DENIED if it has read/write and the
file exists, but there was still and error.

Oh also change the string from "/" to the device name "/dev/cdrom" for example.
Comment 3 Jeff Johnston 2004-06-04 22:37:17 UTC
I still get this error..."The file or folder /By Track/Track 01.wav does not exist." when I try to rip a CD.

I had a plextor 8/4/32A drive when I installed KDE on SUSE 9.1. I bought a Lite-On 52/24/52 drive hoping it would fix the problem (wanted a faster drive anyway). I do not have this problem on the other two computers I have installed on. Any idea how I can fix this? I see the bug was marked as fixed.
Comment 4 Roger Larsson 2004-06-05 15:45:46 UTC
take a look at bug:50767 
Comment 5 Jeff Johnston 2004-06-05 18:57:57 UTC
I saw that, but I think my problem is something else. My cdrom file permissions look like this...
brw-------  1 jeff disk 56, 0 Apr  6 06:27 hdi
lrwxrwxrwx  1 root root 3 Jun  4 21:12 cdrecorder -> hdi
lrwxrwxrwx  1 root root 3 Jun  4 21:12 cdrom -> hdi

I even tried making the hdi rwx for everyone just to try it, but no luck.

I have two computers at home here, although I have installed SUSE 9.1 on three computers total (I got a non-techy friend into Linux now). I have a server computer and a client computer. I can rip no problem on the server computer, but not the client computer.

The strange thing is I took the cdrom drive that worked on my server computer and put it in my client computer and put the client cdrom in my server computer...so now my server computer still works but my client computer still does not. I even went the radical route and just reinstalled (twice) hoping I missed something somewhere in the install. I don't know what else to do. Like I said the other two computers I installed everything works fine. My client computer is using an Athalon XP 2100 on a Epox 8K5A Motherboard. The Motherboard is a Raid board...although I am not using the raid features currently. Any ideas?? I will try anything.
 
Comment 6 rik 2004-06-05 19:08:53 UTC
Looks like you have no permission to access hdi. It doesn't matter what the permissions on the symbolic links are. If you change the permissions on hdi, that should fix it. The error message seems like a bug to me, but it could be that is the error reported back to the KIO slave. I can't really check it at the moment, sorry.