Does this bug still exist with the latest version of k3b for your distribution?
If so, cna you tell me what version of k3b you're using and provide hardware info.
Does this bug still exist with the latest version of k3b for your distribution?
If so, cna you tell me what version of k3b you're using and provide hardware info.