Hoping that this bug (if confermed) will be solved at least with the new 
release of K3b-2.0.3

Reply via email to