[kde-overlay] app-cdr/k3b-2.0.1-r1 crach just after start. Reproducible: Always Steps to Reproduce: Alt-F2 + k3b + Enter or in konsole k3b + Enter Actual Results: $ k3b KGlobal::locale::Warning your global KLocale is being recreated with a valid main component instead of a fake component, this usually means you tried to call i18n related functions before your main component was created. You should not do that since it most likely will not work K3bQProcess::QProcess(0x0) unnamed app(4941): Communication problem with "k3b" , it probably crashed. Error message was: "org.freedesktop.DBus.Error.NoReply" : " "Message did not receive a reply (timeout by message bus)" " KCrash: Application 'k3b' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/bess/.kde4/socket-bess/kdeinit4__0 QSocketNotifier: Invalid socket 10 and type 'Read', disabling...
What version of KDE are you using? It could be a problem with missing HAL. The crash should be solved in latest git revision, but anyway, k3b does not find any optical drives after update to KDE4.6 rc1 (4.5.90).
(In reply to comment #1) > What version of KDE are you using? 4.5.90 (4.6 RC1) > It could be a problem with missing HAL. HAL enabled in all system, except xorg-server. > The crash should be solved in latest git revision, but anyway, k3b does > not find any optical drives after update to KDE4.6 rc1 (4.5.90). Ok, thx. Waiting for next revision.
Crash is fixed in git : http://gitweb.kde.org/k3b.git/shortlog/refs/heads/2.0 (bug tracker here : https://bugs.kde.org/show_bug.cgi?id=261439) Moreover, when using with kde 4.6RC1 (as you are), hal is no more needed, detection is done through solid/udisks. BUT, your drive will only be detected if there is a writable media inside. If the drive is empty, k3b will complain it cannot detect any drive.
Now all ok.
