Application that crashed: dolphin Version of the application: 1.3 KDE Version: 4.3.00 (KDE 4.3.0) Qt Version: 4.5.2 Operating System: Linux 2.6.30.5-43.fc11.i586 i686 Distribution: "Fedora release 11 (Leonidas)" What I was doing when the application crashed: absolutly as in bug #206699 Just reinstalled Xara from "xara_rev1785.package" to "xara_rev1692.package" and tried to show properties of ".xar" file... As result - Dolphin bug... During this test was opened 2 tabs in Dolphin... -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #6 KSycocaEntry::d_func (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.0/kdecore/sycoca/ksycocaentry.h:155 #7 KSycocaEntry::name (this=<value optimized out>) at /usr/src/debug/kdelibs-4.3.0/kdecore/sycoca/ksycocaentry.cpp:158 #8 0x074cd439 in KDEPrivate::KFilePropsPlugin::KFilePropsPlugin (this=0x9733188, _props=0x94a8168) at /usr/src/debug/kdelibs-4.3.0/kio/kfile/kpropertiesdialog.cpp:752 #9 0x074db335 in KPropertiesDialog::KPropertiesDialogPrivate::insertPages (this=0x9448ec8) at /usr/src/debug/kdelibs-4.3.0/kio/kfile/kpropertiesdialog.cpp:498 #10 0x074dbe72 in KPropertiesDialog::KPropertiesDialogPrivate::init (this=0x9448ec8) at /usr/src/debug/kdelibs-4.3.0/kio/kfile/kpropertiesdialog.cpp:351 #11 0x074dc0e2 in KPropertiesDialog::KPropertiesDialog(const KFileItemList &, struct QWidget *) (this=0x94a8168, _items=@0xbf838b0c, parent=0x924f340) at /usr/src/debug/kdelibs-4.3.0/kio/kfile/kpropertiesdialog.cpp:250 #12 0x052b2050 in DolphinViewActionHandler::slotProperties() () from /usr/lib/libdolphinprivate.so.4 #13 0x05297dbd in DolphinViewActionHandler::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libdolphinprivate.so.4 #14 0x06b0b853 in QMetaObject::activate (sender=0x9215500, from_signal_index=5, to_signal_index=6, argv=0xbf838c98) at kernel/qobject.cpp:3113 #15 0x06b0bcc8 in QMetaObject::activate (sender=0x9215500, m=0x4bd09b0, from_local_signal_index=1, to_local_signal_index=2, argv=0xbf838c98) at kernel/qobject.cpp:3207 #16 0x0436b331 in QAction::triggered (this=0x9215500, _t1=false) at .moc/release-shared/moc_qaction.cpp:236 #17 0x0436c8c6 in QAction::activate (this=0x9215500, event=QAction::Trigger) at kernel/qaction.cpp:1160 #18 0x047b883c in QMenuPrivate::activateCausedStack (this=0x9336a98, causedStack=@0xbf838dac, action=0x9215500, action_e=QAction::Trigger, self=true) at widgets/qmenu.cpp:967 #19 0x047bee8b in QMenuPrivate::activateAction (this=0x9336a98, action=0x9215500, action_e=QAction::Trigger, self=<value optimized out>) at widgets/qmenu.cpp:1060 #20 0x047bfa4f in QMenu::mouseReleaseEvent (this=0x9448fd8, e=0xbf8393f0) at widgets/qmenu.cpp:2254 #21 0x022bacf5 in KMenu::mouseReleaseEvent (this=0x9448fd8, e=0xbf8393f0) at /usr/src/debug/kdelibs-4.3.0/kdeui/widgets/kmenu.cpp:456 #22 0x043c6b9a in QWidget::event (this=0x9448fd8, event=0xbf8393f0) at kernel/qwidget.cpp:7549 #23 0x047c1ca4 in QMenu::event (this=0x9448fd8, e=0xbf8393f0) at widgets/qmenu.cpp:2353 #24 0x04371974 in QApplicationPrivate::notify_helper (this=0x9037910, receiver=0x9448fd8, e=0xbf8393f0) at kernel/qapplication.cpp:4056 #25 0x04379a9b in QApplication::notify (this=0xbf83d3fc, receiver=0x9448fd8, e=0xbf8393f0) at kernel/qapplication.cpp:3758 #26 0x021d0a7a in KApplication::notify (this=0xbf83d3fc, receiver=0x9448fd8, event=0xbf8393f0) at /usr/src/debug/kdelibs-4.3.0/kdeui/kernel/kapplication.cpp:302 #27 0x06af5b0b in QCoreApplication::notifyInternal (this=0xbf83d3fc, receiver=0x9448fd8, event=0xbf8393f0) at kernel/qcoreapplication.cpp:610 #28 0x043789de in QCoreApplication::sendSpontaneousEvent (event=<value optimized out>, receiver=<value optimized out>) at ../../src/corelib/kernel/qcoreapplication.h:216 #29 QApplicationPrivate::sendMouseEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qapplication.cpp:2924 #30 0x043e754f in QETWidget::translateMouseEvent (this=0x9448fd8, event=0xbf83aa3c) at kernel/qapplication_x11.cpp:4338 #31 0x043e6523 in QApplication::x11ProcessEvent (this=0xbf83d3fc, event=0xbf83aa3c) at kernel/qapplication_x11.cpp:3423 #32 0x044115d2 in x11EventSourceDispatch (s=0x902e000, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #33 0x00b3bcf8 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #34 0x00b3f370 in ?? () from /lib/libglib-2.0.so.0 #35 0x00b3f4a3 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #36 0x06b205ec in QEventDispatcherGlib::processEvents (this=0x900e8c0, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:327 #37 0x04410cb5 in QGuiEventDispatcherGlib::processEvents (this=0x900e8c0, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202 #38 0x06af40d9 in QEventLoop::processEvents (this=0xbf83ad30, flags={i = 36}) at kernel/qeventloop.cpp:149 #39 0x06af452a in QEventLoop::exec (this=0xbf83ad30, flags={i = 0}) at kernel/qeventloop.cpp:201 #40 0x047c1b1e in QMenu::exec (this=0x9448fd8, p=@0xbf83adac, action=0x0) at widgets/qmenu.cpp:1993 #41 0x080766bc in _start () This bug may be a duplicate of or related to bug 206699 Reported using DrKonqi
*** Bug 206699 has been marked as a duplicate of this bug. ***
if open Dolphin again after crash so ".xar" file properties is opening good =) bug is having place only after reinstalation Xara with Doplhin window used during it...
Probably related to the mimetype association being changed when Dolphin is open. To check this you can do: - Open Dolphin - Reinstall Xara - Run "kbuildsycoca4 --noincremental" - Then try to open the .xar file Thanks
I did... It's opening good after running "kbuildsycoca4 --noincremental"... But how to get it without additionally running??? It's not a problem, it's just not nice...
I tried defining my own mimetype and looking at the properties of a file whose extension maps to that mimetype, but I get no crash. Please give precise steps to reproduce this bug (preferrably without installing whole software packages, just check which files are added to /usr/share/mime, and if adding those by hand is enough to reproduce the problem).
Resetting assignee to default as per bug #305719
Please reopen if this still happens in KDE 4.9 and if you can provide the info requested in comment 5. Thanks!