k3b won't burn: stuck on "Determining maximum write speed"

lefty.crupps · 09-22-2005, 12:10 AM

So i tried to burn a cd (k3b) the other day and it failed. So I ran k3b as root and it worked fine. Now I can only get it to work as root...

right now its got the burning window open and before it even sends the cue sheet and all that, its "Determining maximum write speed" (progress bar is flashing up-and-down) which I've already set at 40x.

I am not sure if this is due to my recent apt-get dist-upgrade to kde 3.4.2 or not. I tried running

Code:

dpkg-reconfigure cdrecord

and i answered "Yes" but its still not going. I tried to uninstall and reinstall k3b, k3blibs, and cdrecord (via synaptic) and still nothing.

any ideas? Also, how does one get at the data files of a mixed mode CD?

salparadise · 09-22-2005, 12:57 AM

Have you tried k3bsetup? There should be a menu entry for it.
Or "k3bsetup" from the command line as root.

AFAIK - correct usage is to run setup first as root then run the programme as user.

If you run k3b as root it will change the owner of your .Xauthority or .ICEauthority file in your user area making logging back in impossible until you chown it back to yourself.

# chown xxx /home/xxx/.ICEauthority

What do you mean "get at the files on a mixed mode cd?"

lefty.crupps · 09-22-2005, 01:24 AM

i ran

Code:

chown xxx /home/xxx/.ICEauthority

(yes i replaced the xxx with my user name) but that didn't fix it. ran it as user and as root. didn't work though; still stuck at that burning-sreen without action.

i tried k3bsetup also; no permissions ask for updating.

my mixed mode question: i burned a cd with music in the first part and data in the second ("cd-extra" it was called) and i cannot get to my /dev/hdc or /mnt/hdc. no icons are on the desktop to mount it. i cannot seem to mount it in the shell. k3b only sees the audio part of it. my konqueror "devices" link doesn't work. so i cannot get at those files in any way that i can think of...

Nix_Hard · 09-22-2005, 03:21 PM

Nexxus6 posted this over @ MEPISlovers, got my K3b burning plastic again.
Thanks Nexxus6.

Quote:

I do monthly "default upgrades" with synaptic and after I did, my K3B starting screaming about no root access to cdrom device please run k3b setup. I did and I got that message to go away. When I create a CD now "mkisofs did not exit cleanly" appears and the writter spits out a blank cd. To fix this problem I downgraded MKISOFS to 4:2.01+01a01-4 and CDRECORD to 4:2.01+01a01-4 and ran K3B Setup again and applied writes and all is well.

[From;http://www.mepislovers.org/modules/n...=10944&forum=9]
NH

lefty.crupps · 09-22-2005, 04:17 PM

cool, i'll try that soon... how does one go about downgrading a package?

will i always have to search-and-unmark that package after I hit "mark all upgrades" to avoid this problem in the future, or will it be rectified by the debian-unstable team?

Nix_Hard · 09-22-2005, 07:45 PM

lefty.crupps,
I'm using Synaptic to drive apt, for me I searched on the 2 pkgs causing the problem, selected them, then under the "Package" menue choose "Force Version" and in the dialog box that comes up selected the early version and "OK" and "Apply" the changes.

Then search for the same 2 pkgs again and under the "Package" menue again, this time choose ""Lock Version". That will "pin" those pkgs and take care of the problem till it's rectified, when thats done you can unlock the pkgs and update them to get back to normal.
NH

Nix_Hard · 09-27-2005, 10:52 PM

New info and ideas on thread here.
http://www.mepislovers.org/modules/n...forumpost78374

Here's the drum good peoples.
[what Ive found anyway, checking across 2 PCs using other peoples info & ideas]

Just un-pinned and upgraded to the "unstable" versions of cdrecord and mkisofs 4:2.01+01a03-2 from "testing" v 4:2.01+01a01-4 which was burning fine.

Then started K3b, when the "K3bsetup" helper dialog came up I ignored it saying I had a burning permissions problem, i.e. I dismissed it.

And just started burning plastic.

Yaaaaayyyyyyy

If you let the "K3bsetup" helper set the permissions to what it thinks or wants, it will stop a working setup from burning.

Then one way to "fix" the problem is to apply Anagor and AdrianTMs' fix.
Quote:

chmod +s /usr/bin/cdrecord.mmap

Where to report this bug, looks like a mix/fight of permission ideas between K3b, cdrecord & mkisofs.

more beers and cheers
NH

lefty.crupps · 09-28-2005, 10:17 AM

I pinned cdrecord and mkisofs to the Testing repos and its all good now. Thank you all for your help!

Nix_Hard · 09-30-2005, 01:19 AM

Not the fault of cdrecord and mkisofs lefty.crupps.
Let your cdrecord and mkisofs run free :-)
Just did the update thing, and burning stopped.
Only k3b & k3blibs updated this time. [0.12.4a-2 from 0.12.4a-1]
When k3b started the k3bsetup helper said need to adjust permissions.
Did that with the helper, burning breaks, no smoke, no joy.
Reset the permissions and bingo.
Smokin...

Quote:

It's on again folks.
This only affects people updating to unstable.
k3b up a notch to 0.12.4a-2 [from 0.12.4a-1]
k3blibs too. [same ver num]
Same problem as before, wants to change your cdrecord permissions.
Don't let it, stops k3b burning again.
Updated k3b and k3blibs to 0.12.4a-2 still works, just don't let it change those permissions.

lefty.crupps · 09-30-2005, 10:05 AM

well the perms have been changed already... so by pinning those files i can burn. I'll let them free soon enough

thanks nix_hard

seanr · 10-05-2005, 12:42 PM

Quote:

Originally posted by Nix_Hard
Not the fault of cdrecord and mkisofs lefty.crupps.
Let your cdrecord and mkisofs run free :-)
Just did the update thing, and burning stopped.
Only k3b & k3blibs updated this time. [0.12.4a-2 from 0.12.4a-1]
When k3b started the k3bsetup helper said need to adjust permissions.
Did that with the helper, burning breaks, no smoke, no joy.
Reset the permissions and bingo.
Smokin...

You mind posting the files that need to have their permissions reset and _exactly_ what those permissions should be? With all the different replies in this thread, I'm currently quite confused.