K3B is evidently not yet available for Debian AMD64 ... Problem seems to be an 'uninstallable cdrdao.' Anyone successfully burning cdr-s using AMD64?

As far as I know, K3b is currently not available (in testing) at all, due to the broken dependencies issue.

Well I have never used k3b but it's certainly in the repositories.
I prefer gcdmaster which is available w/ the cdrdao source. You'll have to build it yourself.

Debian went from KDE 3.3 to 3.4. Because the kdelibs updated, all applications that depended on the old versions had to be recompiled. This included k3b; however, because there were release-critical bugs reported against it before it got to testing agian, it's been held up. The solution is to install it from unstable; all the dependencies should match at the moment (I think; correct me if I'm wrong) or compile it yourself if you so desire.

Alternatively you could grab the package from stable and manually modify the package dependencies to make it install (or alien it to RPM and back to get rid of all dependencies). This is pretty much pointless, though, unless you're morally opposed to running anything from Sid or something. Get it from unstable.

I upgraded my entire system to 'unstable'. Been considering it for a whileand k3b was a good enough excuse. Only relatedprogram that wouldn't install was k3b-i18n ... Never have understood what that one does, but it didn't stop me from writing a data disk ... Error message on that one was that it required k3b vsr. 12.8 and we got ver. 12.7 ... Hopefully, it won't be too long until that problem takes care of itself.

Now ... if only I could get OpenOffice.....

Seems like you got this squared away, but I thought I'd chime in, since I'm running an amd64 debian system and k3b works fine for me. I run testing through the 64 Studio distribution, which is optimized for audio & multimedia production - www.64studio.com. OpenOffice is a big thing I'm lacking too, though I think gnome-office tools such as abiword are ported natively to 64-bit, and if you install the ia32 libs and enable 32-bit support in your kernel (ia32_emul), you should be able to run that. I'm still running version 0.3.0 of 64studio, but I believe in the newest 0.6.0 release (out just a week ago or so), they enabled the 32-bit support so these things should be easier. Might be worth checking out...

Another good resource for checking how to run 32-bit apps in amd64 (i.e., OpenOffice):
https://alioth.debian.org/docman/vie...d64-howto.html

Good luck!

I've decided to live without any 32 bit apps requiring emulation on this machine. I have a (32 bit) laptop running Etch and an XP partition on this machine running 32 bit OpenOffice2. So I have the means to run anything I really need. I have a couple 32 bit java apps running on this machine with no problems, so evidently there is some degree of native support for them built into the AMD64 OS.

Open Office 2.0 ?

Go to this site if you even want to have it running on sarge (which I do, it works perfect)

http://www.backports.org/

cheers

i know thier thing is paying for support, which is cool, but i didn't get that impression when i downloaded the ISO last night.

now i get to the login page and it stalls(crashes) at the gnome 2.12 screen.... the first screen that appears after you hit enter when you login with your password.

anyone else get this??? i want to try it, bad... just don't know where to go for help.

thanks in advance all.

As to getting 64Studio support - it is a small project, still in Alpha phase I believe, but it's very functional and well-maintained for being small. The result is that you won't find any big forums of 64studio users like you will for something big like ubuntu, but there's help available - you can speak directly to the developers, they're nice folks. Here's the list to the 64studio development list: http://64studio.com/cgi-bin/mailman/...64studio-devel

I think I've had the same problem as you before with gnome, I'm trying to remember how I got past it. I know some of my kernel configurations don't work, and I had to boot to a "safe mode" or terminal only to figure things out...

I would take very careful notes of exactly what happens, politely post it to the development list, and see what you figure out.

Good luck!