Dolphin won't open, but the process is running. When I search for it in the task manager, it says that Dolphin is running an I can clode it. When I try opening it through the command line, it gives this error messge: dolphin(30519) KXMLGUI::ActionList::plug: Index 13 is not within range (0 - 9 Reproducible: Always Steps to Reproduce: 1. Open Dolphin Actual Results: I got this error message in the command line: dolphin(30519) KXMLGUI::ActionList::plug: Index 13 is not within range (0 - 9 Expected Results: It should have opened without any problems. I am using the default configuration. Dolphin sometimes opens if I have just logged in, but this bug usually happens.
I am usin the Dolphin version from the Kubuntu Backports PPA: https://launchpad.net/~kubuntu-ppa/+archive/backports
The message is not the reason for not running, you have to check differently why it does not run. I get the same message, but Dolphin works fine.
Thanks for the report. To find out where in the code the freeze occurs, could you try the following: gdb dolphin run (wait for some time until the application freezes) Ctrl+Z bt and paste the backtrace here? Thanks.
Please try to provide the backtrace requested in comment #3
I've come across the same symptoms and here's the backtrace: (gdb) bt #0 0xffffe424 in __kernel_vsyscall () #1 0xb5712c53 in poll () from /lib/libc.so.6 #2 0xb363395e in _dbus_poll () from /usr/lib/libdbus-1.so.3 #3 0xb3628d86 in socket_do_iteration () from /usr/lib/libdbus-1.so.3 #4 0xb3627242 in _dbus_transport_do_iteration () from /usr/lib/libdbus-1.so.3 #5 0xb36085fb in _dbus_connection_do_iteration_unlocked () from /usr/lib/libdbus-1.so.3 #6 0xb3609beb in _dbus_connection_block_pending_call () from /usr/lib/libdbus-1.so.3 #7 0xb362006e in dbus_pending_call_block () from /usr/lib/libdbus-1.so.3 #8 0xb360b50f in dbus_connection_send_with_reply_and_block () from /usr/lib/libdbus-1.so.3 #9 0xb66a81e5 in ?? () from /opt/qt/lib/libQtDBus.so.4 #10 0xb66a91c2 in ?? () from /opt/qt/lib/libQtDBus.so.4 #11 0xb66bb9df in ?? () from /opt/qt/lib/libQtDBus.so.4 #12 0xb66bbb6f in QDBusInterface::QDBusInterface () from /opt/qt/lib/libQtDBus.so.4 #13 0xb6b0e074 in KSystemTimeZonesPrivate::instance () from /opt/kde4/lib/libkdecore.so.5 #14 0xb6b0e96f in KSystemTimeZones::local () from /opt/kde4/lib/libkdecore.so.5 #15 0xb6af9423 in KDateTime::toLocalZone () from /opt/kde4/lib/libkdecore.so.5 #16 0xb72cb49e in KFileItemPrivate::setTime () from /opt/kde4/lib/libkio.so.5 #17 0xb72d2d4c in KFileItemPrivate::init () from /opt/kde4/lib/libkio.so.5 #18 0xb72d4e35 in KFileItem::KFileItem () from /opt/kde4/lib/libkio.so.5 #19 0xb75618ab in KonqOperations::pasteInfo () from /opt/kde4/lib/libkonq.so.5 #20 0xb7608bde in DolphinView::pasteInfo () from /opt/kde4/lib/libdolphinprivate.so.4 #21 0xb769681f in DolphinMainWindow::updatePasteAction () from /opt/kde4/lib/libkdeinit4_dolphin.so #22 0xb7699cd8 in DolphinMainWindow::updateEditActions () from /opt/kde4/lib/libkdeinit4_dolphin.so #23 0xb76a1e6b in DolphinMainWindow::DolphinMainWindow () from /opt/kde4/lib/libkdeinit4_dolphin.so #24 0xb76938c7 in DolphinApplication::DolphinApplication () from /opt/kde4/lib/libkdeinit4_dolphin.so #25 0xb76afccc in kdemain () from /opt/kde4/lib/libkdeinit4_dolphin.so #26 0x08048692 in main () If I launch dolphin via "dbus-launch dolphin", it starts normally.
Wait, are you implying that creating a KFileItem causes a D-Bus call? Uh oh ...
Yeah, and it looks even more strange to me that KSystemTimeZones needs D-Bus (though I don't know its implementation details).
Thanks. So does anyone (Christoph maybe?) have an idea whose fault it is? Dolphin, KFileItem, DBus, time zone stuff?
Is kded4 running correctly (i.e. isn't blocked by a faulty module)? It looks like the timezone code in kdelibs needs to contact kded4 via D-Bus.