Warning, /multimedia/k3b/FAQ.txt is written in an unsupported language. File is not indexed.

0001 Q: Compiling K3b fails with errors like this:
0002    base_k3badvanceddataimagesettings.cpp:185: invalid use of undefined type
0003    `struct KComboBox'
0004    base_k3badvanceddataimagesettings.h:17: forward declaration of `struct
0005    KComboBox'
0006 A: The QTDesigner tool 'uic' is not able to find the kde widget plugins.
0007    To solve this run 'qtconfig' and add '$KDEDIR/lib/kde3/plugins' to the plugin search path
0008    (replace $KDEDIR with your kde base dir).
0009 
0010 
0011 Q: Where has all the fancy graphic gone?
0012 A: Most likely you installed K3b in the wrong directory. All KDE programs are installed in the
0013    KDE dirtree (SuSE: /opt/kde3, RedHat: /usr). If you compile K3b from source it defaults
0014    to either $KDEDIR or /usr/local. To install in the correct directory you need to specify the prefix
0015    to configure like this:
0016      ./configure --prefix=`kde-config --prefix`
0017    That will install K3b relative to the correct path.
0018 
0019 
0020 Q: The linking always breaks with the missing -laudio.
0021 A: You need to install NAS.
0022 
0023 
0024 Q: Where can I find K3bSetup2?
0025 A: K3bSetup2 is a KControlCenter Module. You can find it in the System Administration section or start
0026    it manually with "kdesu kcmshell4 k3bsetup2".
0027    There also is a script since K3b 0.11 called k3bsetup.
0028 
0029 
0030 Q: My writer supports writing at speed X but K3b shows Y as a max.
0031 A: K3b determined the maximum writing speed the first time you start it. Since the speed reported by the
0032    writer always depends on the mounted medium this may not be the real max.
0033    To manually change it open the K3b settings in the device section and click on the value. You will
0034    be presented with a spinbox which allows one to change the speed.
0035 
0036 
0037 Q: Writing fails with the following cdrecord message:
0038      "Cannot allocate memory. Cannot get SCSI I/O buffer."
0039 A: Since kernel 2.6.9 suid root programs are not allowed to use the SCSI subsystem.
0040    To solve this issue either configure cdrecord to run without root privileges: chmod 755 /usr/bin/cdrecord
0041    or run K3b as root (which is not recommended but works also).
0042 
0043 
0044 Q: Writing fails with the following cdrecord message over and over again:
0045      "Error trying to open /dev/hdc exclusively (Device or resource busy)..."
0046 A: You are using a patched cdrecord version which tries to open the device exclusively which fails because
0047    your are probably also using automounting. The solutions are to disable automounting altogether (and this is
0048    the recommended solution as automounting can cause other more serious problems with CD/DVD writing) or to
0049    install a non-patched cdrecord version.
0050 
0051 Q: My DVD drive supports 16X but K3B keeps burning at 1X! What's happening?
0052 
0053 A: Your kernel most likely didn't apply optimal settings for your drive when it detected it. You can find out
0054    what are the current settings of your drive with the command "hdparm -v /dev/dvd":
0055 
0056    /dev/dvd:
0057     IO_support   =  0 (default 16-bit)
0058     unmaskirq    =  0 (off)
0059     using_dma    =  0 (off)
0060     keepsettings =  0 (off)
0061     readonly     =  0 (off)
0062     readahead    = 256 (on)
0063 
0064    The following options are known to maximize burning and playback performance:
0065 
0066      hdparm -d1 -c1 -a8 -u1 /dev/dvd
0067 
0068    To make these options permanent, a quick and dirty solution is to include the command in /etc/rc.local.
0069    Consult your distribution documentation for a tailored solution.
0070 
0071    Some drives have buggy DMA support. If you experience instability, leave these options disabled.
0072 
0073    Some useful references:
0074    http://www.togaware.com/linux/survivor/CD_DVD_Drives.shtml
0075    http://www.linuxjournal.com/article/6921