Application: nepomukserver (0.2) KDE Platform Version: 4.7.2 (4.7.2) Qt Version: 4.7.4 Operating System: Linux 3.0.0-13-generic i686 Distribution: Ubuntu 11.10 -- Information about the crash: - What I was doing when the application crashed: I'm using openbox wm and the few times I've started up konversation after upgrading til ubuntu 11.10 I always get this crash (which I'm not sure what is all about), however konversation doesn't seem to be bothered by it, so then I guess, neither am I. The crash can be reproduced every time. -- Backtrace: Application: Nepomuk Server (nepomukserver), signal: Segmentation fault [KCrash Handler] #7 0x06ee92f4 in XInternAtom () from /usr/lib/i386-linux-gnu/libX11.so.6 #8 0x01d66f6b in DBusConnection::getAccessibilityBusAddress() const () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #9 0x01d67046 in DBusConnection::connectDBus() () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #10 0x01d6746f in DBusConnection::DBusConnection() () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #11 0x01d48cb9 in QSpiAccessibleBridge::QSpiAccessibleBridge() () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #12 0x01d66b78 in QSpiAccessibleBridgePlugin::create(QString const&) () from /usr/lib/qt4/plugins/accessiblebridge/libqspiaccessiblebridge.so #13 0x016df152 in QAccessible::initialize() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #14 0x016df27d in QAccessible::setRootObject(QObject*) () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #15 0x0114d8ef in QApplication::exec() () from /usr/lib/i386-linux-gnu/libQtGui.so.4 #16 0x002d7eef in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_nepomukserver.so #17 0x0804850b in ?? () #18 0x00129113 in __libc_start_main () from /lib/i386-linux-gnu/libc.so.6 #19 0x08048531 in _start () Possible duplicates by query: bug 288250, bug 287485, bug 285551, bug 284290. Reported using DrKonqi
*** Bug 288661 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 284290 ***