No verify or data integrity check in K3b or Brasero, SUSE 11.0 (64-bit)
 

I cannot run K3b to burn an ISO to a cd-rw, nor can I run Brasero to do the same, in openSUSE 11.0 x_86_64. The "verify written data" and "data integrity check" functions after the writes always commit errors. I've tried different media, and tried cleaning the burner lens. These apps never gave me trouble verifying or integrity checking in openSUSE 10.3. Does anyone know of a repository with a good version of these burner apps for openSUSE 11.0 (64-bit)?

The following is two days later:

This is an obnoxious problem that I can't entirely eradicate, and I don't know exactly why it is. I can burn an ISO now and K3b will run the verify properly. I had to install Packman, Buildservice-KDE Backports, and Buildservice X11:XGL repositories. I also had the opensuse multimedia repository in there from a prior day. I installed the update of K3b from the Backports repository. I then searched all the repositories with the search term "lib" (without the quote marks, of course), and installed anything highlighted blue. That along with all the other things Yast demanded that I install, to resolve dependencies, got K3b running the "verify written data" function after a CD-RW burn once again.
I cannot, however, get K3b to run the "verify written data" function when I burn a data DVD-RW. The DVD-RW ejects, and will not reload and run the verify. The main K3b window greys out and it just hangs. Since I'm burning single 4GB truecrypt containers, I am using MD5sum to verify, but that's a pain....
Should I drop back to a 32-bit K3b? Is there another opensource burning app. that is better?

update solved this, caused another problem...
 

As fate would have it, some update made my K3b verify work again, but it just as suddenly displayed a dialog box that said I did not have drive access (to /dev/sr0). The same dialog box suggested that I might fix this with udev. I ended up doing so because I really couldn't sort out the recipe (or syntax, if you prefer the word) for putting it in fstab. I don't like figuring out the sudo recipes, either.

So, what I did is make a file named 97-burn_access.rules, and put it in /etc/udev/rules.d (running as root). The 97-burn_access.rules file had the following in it:
This works, providing I added my user name to the group disk, using the numb-above-neck gui interface. It probably also limits use of K3b to the disk group, though I haven't tested.

Weird, though, now the Dvd burner drawer automatically ejects and closes twice, when it should only do so once.

I can't get over the designation of the ATA Dvd burner as being SCSI, under Linux. That goes against my retired (as well as worthless for getting a job even when it wasn't retired) CompTIA A+ Certification training...

The udev "solution" only worked a little while...
 

I've done more updates, I don't know exactly what was affected, but I'm stuck again without write access to drives by K3b as a user (the rules file I posted for udev doesn't help anymore). I have to run K3b as root. Configuring K3b to not eject media after the write process seems to stop that (bug?) problem with not running verify after a burn (there's an easy GUI check-box for it). My dvd-rw acts wierd, it ejects and reloads instantly even after a single eject command...

I have fled to Ubuntu...
 

I gave up trying to get openSUSE 11.0 to serve, and went for Ubuntu 8.04.1 Hardy Heron 64-bit. What a shock to have my printer install and print. What a shock to have Brasero burn a CD and verify it without the tray acting like Thing on the Addams Family in a tug-of-war, or the burner app. saying it doesn't have /dev/sr0 access. What a shock to have my X-FI Extreme Audio Creative Labs sound card just install (using a driver with a seemingly unrelated name, but it works; bye-bye, generic USB sound)! What a shock to install my Nvidia 9600GT accelerated openGL driver by typing one command and re-starting (after I installed the downloaded driver from a GUI menu).
The network connecting for DSL is a little weird; the flat terminal pppoeconf and GUI System/Administration/Network parts for establishing an on-line connection are antagonistic in a way I can't understand just yet, but it's only been a day... Maybe all I have to do is give root "Connect to the Internet using a modem" privilege?