[opensuse] Suse 10 strange cd burn problem
Hi, I can burn CDs fine on this suse 10 machine using eg gnomebaker. If I fire up K3b and try and burn it errors out with a no disc space message, yet k3b itself also reports 2+ gigs of free space. Any suggestions most welcome. TIA F -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 23 May 2007 17:12, Francesco Scaglioni wrote:
Hi, I can burn CDs fine on this suse 10 machine using eg gnomebaker. If I fire up K3b and try and burn it errors out with a no disc space message, yet k3b itself also reports 2+ gigs of free space.
Sorry for not answering, I think I just bumped the wall too this morning by burning a DVD iso using k3b. The process ran smoothly. No error or whatsoever reported. The DVD ejected automatically after finish. But then when I insert it into the drive, Opensuse thinks that it's an empty DVD, whereas it's not. I can see the burned side of the DVD, and confirm it by trying to burn it again using k3b. It refuses. Well, I have been using k3b for a long time with ups and downs. Looks like I'm on the down again. PS. the k3b version is: k3b-0.12.17-31 -- Fajar Priyanto | Reg'd Linux User #327841 | Linux tutorial http://linux2.arinet.org 6:36pm up 10:30, 2.6.18.2-34-default GNU/Linux Let's use OpenOffice. http://www.openoffice.org
On Wednesday 23 May 2007, Fajar Priyanto wrote:
On Wednesday 23 May 2007 17:12, Francesco Scaglioni wrote:
Hi, I can burn CDs fine on this suse 10 machine using eg gnomebaker. If I fire up K3b and try and burn it errors out with a no disc space message, yet k3b itself also reports 2+ gigs of free space.
Sorry for not answering, I think I just bumped the wall too this morning by burning a DVD iso using k3b. The process ran smoothly. No error or whatsoever reported. The DVD ejected automatically after finish. But then when I insert it into the drive, Opensuse thinks that it's an empty DVD, whereas it's not. I can see the burned side of the DVD, and confirm it by trying to burn it again using k3b. It refuses.
Well, I have been using k3b for a long time with ups and downs. Looks like I'm on the down again.
PS. the k3b version is: k3b-0.12.17-31 ============
Just in case you guys didn't realize, k3b is unlikely to be at fault here! K3b & gnomebaker are only the gui frontends to the programs actually being used. You might want to check to see if you can burn successfully from the terminal using the wodim programs supplied. These are the forks from the cdrecord tools presently being used by SuSE. You also may want to update to the newer version k3b, 1.x available from SuSE or Packman. It has many new features & fixes. regards, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
BandiPat schrieb:
Just in case you guys didn't realize, k3b is unlikely to be at fault here! K3b & gnomebaker are only the gui frontends to the programs actually being used.
Well, I do realize it. Wodim, cdrdao and growisofs are working perfectly here. However k3b does not. How does it fit your Theory? I don't use gnome. K3b has its ups and downs, thus I stick to the shell.
You might want to check to see if you can burn successfully from the terminal using the wodim programs supplied. These are the forks from the cdrecord tools presently being used by SuSE. You also may want to update to the newer version k3b, 1.x available from SuSE or Packman. It has many new features & fixes.
Did SUSE switch from cdrecord to wodim for the 10.0 release? The only reason I switched from 10.0 to SLED and then to 10.2 was the burning problem. Back there even in the CLI. Thx Jan -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On Wednesday 23 May 2007, Jan Tiggy wrote:
BandiPat schrieb:
Just in case you guys didn't realize, k3b is unlikely to be at fault here! K3b & gnomebaker are only the gui frontends to the programs actually being used.
Well, I do realize it. Wodim, cdrdao and growisofs are working perfectly here. However k3b does not. How does it fit your Theory? I don't use gnome. K3b has its ups and downs, thus I stick to the shell.
You might want to check to see if you can burn successfully from the terminal using the wodim programs supplied. These are the forks from the cdrecord tools presently being used by SuSE. You also may want to update to the newer version k3b, 1.x available from SuSE or Packman. It has many new features & fixes.
Did SUSE switch from cdrecord to wodim for the 10.0 release?
The only reason I switched from 10.0 to SLED and then to 10.2 was the burning problem. Back there even in the CLI.
Thx Jan
========== I don't remember when SuSE switched, it was 10.0 or 10.1, but you can easily check. Just check to see if cdrecord, etc are symlinks to the new wodim files. It may be that you just need to update k3b to the new version Are you running a new kernel? 2.19 or above? If so, you should absolutely update k3b. Gnomebaker is not as elegant a program as k3b, but it works well in either gnome or kde. K3b has always been reliable for me. There have been some oops along the way, but if it burns to success, then I always got a good cd from it. regards, Lee -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (4)
-
BandiPat -
Fajar Priyanto -
Francesco Scaglioni -
Jan Tiggy