Version: 2.0.1 (using Devel) OS: Linux In kde4.6 (latest SVN) k3b will not open unless there is a disk in the optical drive. It appears to be opening but then a crash screen opens instead. This is not a major problem of course but not normal behaviour previously. It does open if the disk is inserted first. I suspect it is a KDE problem as I am using the same K3b which works as expected in openSuse 11.3 with KDE 4.5.3 if you forget the disk first. Reproducible: Always Steps to Reproduce: Click in menu icon, desktop icon or use terminal. Actual Results: as above - crashes unless disk present.
I see the same behaviour on openSUSE 11.3 with KDE 4.5.80 (4.6 Beta 1) installed. On startup I get the following messages. My assumption is that this might be a problem with dbus. myuser@mymachine:~> 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) K3bQProcess::QProcess(0x0) kde(15722): 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)" " myuser@mymachine:~> KCrash: Application 'k3b' crashing... KCrash: Attempting to start /usr/lib64/kde4/libexec/drkonqi from kdeinit sock_file=/home/myuser/.kde4/socket-mymachine/kdeinit4__0 QSocketNotifier: Invalid socket 10 and type 'Read', disabling... If a media is in my DVD drive I don't get this problem as stated in the initial bug report. Startup messages are then myuser@mymachine:~> 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) K3bQProcess::QProcess(0x0) K3bQProcess::QProcess(0x0) K3bQProcess::QProcess(0x0) myuser@mymachine:~> kde(16318)/kdeui (kdelibs): Attempt to use QAction "view_projects" with KXMLGUIFactory! kde(16318)/kdeui (kdelibs): Attempt to use QAction "view_dir_tree" with KXMLGUIFactory! kde(16318)/kdeui (kdelibs): Attempt to use QAction "view_contents" with KXMLGUIFactory! kde(16318)/kdeui (kdelibs): Attempt to use QAction "location_bar" with KXMLGUIFactory! Advanced probing on /dev/sr0 failed while reading block size
probably, a duplicate of bug 249371.
I don't see the same behaviour here on a VirtualBox machine (openSUSE 11.4 milestone 4, Qt 4.7.1, KDE 4.5.80); K3b doesn't crash if there's no CD/DVD present.
Problem is solved with rpm k3b-2.0.1-44.1.x86_64 on openSUSE 11.3.
BugSquad: it is fixed for Andreas. Pete we need a backtrace of the crash please, thanks in advance!
Backtrace file attached On 29/11/10 19:55, Anne-Marie Mahfouf wrote: > https://bugs.kde.org/show_bug.cgi?id=257349 > > > Anne-Marie Mahfouf<annma@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|UNCONFIRMED |NEEDSINFO > CC| |annma@kde.org > Resolution| |BACKTRACE > > > > > --- Comment #5 from Anne-Marie Mahfouf<annma kde org> 2010-11-29 20:55:15 --- > BugSquad: it is fixed for Andreas. > Pete we need a backtrace of the crash please, thanks in advance! >
There is no backtrace here. When you get the crash, you should get the KDE crash dialog and the backtrace can be seen from there.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!