[arch-general] KDE Dolphin crashes on click

[Łukasz Redynk]

Hi,

Yes, I've got it too. There's thread on forum about this error:
https://bbs.archlinux.org/viewtopic.php?id=142964
It seems there's problem with nepomuk/strigi, workaround for that is
disbaling semantic desktop is System Settings and relogin to the kde.

---
Pozdrawiam
Łukasz Redynk


W dniu 11.06.2012 12:49, Paul Gideon Dann pisze:
> Hello all,
> 
> I'm having some trouble with Dolphin.  Clicking or right-clicking on files 
> causes a SIGSEGV with the following backtrace:
> 
> #0  0x00007ffff4e5c59c in KSycocaDict::find_string(QString const&) const ()
>    from /usr/lib/libkdecore.so.5
> #1  0x00007ffff4dc7fc8 in KMimeTypeTrader::preferredService(QString const&, 
> QString const&) () from /usr/lib/libkdecore.so.5
> #2  0x00007ffff58fc2ac in KRun::runUrl(KUrl const&, QString const&, QWidget*, 
> bool, bool, QString const&, QByteArray const&) () from /usr/lib/libkio.so.5
> #3  0x00007ffff58fc977 in KRun::foundMimeType(QString const&) ()
>    from /usr/lib/libkio.so.5
> #4  0x00007ffff58f2412 in KRun::mimeTypeDetermined(QString const&) ()
>    from /usr/lib/libkio.so.5
> #5  0x00007ffff58faff8 in KRun::init() () from /usr/lib/libkio.so.5
> #6  0x00007ffff58f4290 in KRun::slotTimeout() () from /usr/lib/libkio.so.5
> #7  0x00007ffff4923dcf in QMetaObject::activate(QObject*, QMetaObject const*, 
> int, void**) () from /usr/lib/libQtCore.so.4
> #8  0x00007ffff49230dc in QObject::event(QEvent*) () from 
> /usr/lib/libQtCore.so.4
> #9  0x00007ffff3a44f7c in QApplicationPrivate::notify_helper(QObject*, QEvent*) 
> ()
>    from /usr/lib/libQtGui.so.4
> #10 0x00007ffff3a493fa in QApplication::notify(QObject*, QEvent*) ()
>    from /usr/lib/libQtGui.so.4
> #11 0x00007ffff5376c66 in KApplication::notify(QObject*, QEvent*) ()
>    from /usr/lib/libkdeui.so.5
> #12 0x00007ffff490e8ee in QCoreApplication::notifyInternal(QObject*, QEvent*) ()
>    from /usr/lib/libQtCore.so.4
> 
> The same thing occasionally happens on hover.  I've tried running 
> kbuildsycoca4 on the offchance something got corrupted, but it didn't help.
> 
> This seems to be a separate issue from the herqq issue.
> 
> Anyone else getting this?
> 
> Paul
>