Since I have a separate /home partition, I decided to reinstall Vector. So, I did, and then upgraded using strictly the packages, extra, and patches repositories (the default -- so no testing or unstable) and Brasero still isn't working. I get the exact same error that I reported yesterday.

Thanks for your response uelsk8s. I think before I do try the untested package, I'm going to see if I can somehow make my system stable. I've been having various problems since I unintentionally upgraded to testing a while back. So, as I mentioned, I reinstalled, then upgraded (with only stable repositories). However, the exact same problems occurred. So, I have reinstalled AGAIN, and this time not only did I delete the cached packages in /home/ftp/pub/veclinux/packages directory (/home is a separate partition that I maintained in the new installation), I also got rid of all the hidden files there. I'm cautiously optimistic that this time things will work (even after doing an upgrade to the newest stable packages), and that this time I'll have an uncorrupted and working Vector. If not, it'll be time to try a different distribution.

Anyway, the fresh not yet updated brasero is working. So, I'll see if that's the case after I update everything (using only stable repositories).

The brasero from the fresh install worked, but I get the same error from the updated brasero regarding "libgmime-2.4.so.2". I also tried the untested version (2.32.1-i586-2vl70) but it too gives me the same error. So, both 2.32.1-i586-1vl70 and 2.32.1-i586-2vl70 give the following error:

vector:/~mark:$ braserobrasero: error while loading shared libraries: libgmime-2.4.so.2: cannot open shared object file: No such file or directoryI recently installed k3b, so perhaps that's causing issues with brasero. Anyway, since I have k3b working, I guess I'll not worry about brasero. It did work yesterday as I mentioned in the previous post.

Almost every audio disc I burn seems to have a glitch in some track, sometimes quite bad (like a skipping cd). It doesn't seem to matter whether the source track was ogg or mp3. It doesn't matter whether I do it on my old laptop or my new one. And it doesn't seem to matter whether I use the repo version or the latest getdeb package. Ditto for trying different burning speeds. And I have tried making sure nothing else using excessive hard disk usage is running.

I know its aim is to be simple but perhaps if there was a little more in the way of configuration options I might be able to determine whether the problem is from transcoding or burning.

in the past I used to use K3B and I didn't get this problem with that application. But I'd like to exhaust all options with Brasero before I remove it.

I see a common denominator in your posts. You keep upgrading after new installs. Have you tried not upgrading? stay with the standard builds for the current install. Its a good probable chance that after your system upgrade the packages your looking to use have not been rebuilt for it. Or you can rebuild the package against your upgraded install.