Hi Rugart, Sorry for the delay in getting back to you.
> I unsuccessfully tried to compile this beta version. When running > ./configure, the last message was "checking for X... configure: error: Can't > find X libraries. Please check your installation and add the correct paths!" > and I even updated the 'xorg', 'xdev' and 'xserver-xorg' packages. My $PATH > is > /sbin:/bin:/usr/sbin:/usr/bin:/usr/X11R6/bin:/usr/games:/usr/local/sbin:/usr/local/bin:/usr/X11R6/lib > Don't know why it was unable to 'find X libraries'. Any suggestions? It looks like you are missing the development version of some package. To build K3b 0.12.x, a number of packages need to be installed: apt-get install kdelibs4-dev libqt3-compat-headers libflac++-dev flac libdbus-qt-1-dev libhal-dev libhal-storage-dev libpopt-dev libmpcdec-dev libtag1-dev libmusicbrainz4-dev libmad0-dev > I have "cdrskin" installed. Removing the "wodim" package would remove the > "k3b" package itself. Removing the "cdrecord" package makes it impossible to > burn anything. So I just temporarily removed /usr/bin/wodim, and then it was > not able to burn the "data" part, complaining about the absence of > 'cdrecord'. Because k3b uses /usr/bin/cdrecord which is a link > to /usr/bin/wodim. Perhaps the problem is that "wodim" doesn't depend on > "cdrecord", and I was using cdrecord 4:2.01+01a03-5. I believe that the problem here is that you were using an older version of the K3b package. The latest version in unstable should allow you to remove the cdrecord and wodim packages if you have cdrskin installed. > When I upgraded cdrecord, it became a "dummy" package - 5:1.0-1. And then > the already reported warnings about "inofficial version of libscg" > disappeared, and I could successfully burn a mixed mode CD. So am I understanding you right, with the latest version of cdrecord and wodim the mixed mode CD is working again ? > Misteriously, when booting into another partition and using an older version > of k3b, 0.11.20-2, which had already failed to burn mixed mode CDs, at this > time there was success. It sounds like the problem may have come from wodim/cdrecord... Thanks for taking the time to do this extra testing, Francois -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
