Ubuntu

kactivitymanagerd crashes on login

Reported by Jonathan Riddell on 2012-03-27
36
This bug affects 5 people
Affects Status Importance Assigned to Milestone
kactivities
Won't Fix
High
soprano (Ubuntu)
High
Unassigned

Bug Description

boom. needs investigation.

Download full text (8.2 KiB)

Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.7.95 (4.8 RC1 (4.7.95) (Compiled from sources)
Qt Version: 4.7.4
Operating System: Linux 3.1.6-pf-custom x86_64
Distribution: "Gentoo Base System release 2.1"

-- Information about the crash:
- What I was doing when the application crashed:

kactivitymanagerd just crashed unexpectedly. No unusual desktop activity detected.

-- Backtrace:
Application: KDE Activity Manager (kactivitymanagerd), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f85b18ee760 (LWP 4852))]

Thread 2 (Thread 0x7f85a337b700 (LWP 4864)):
[KCrash Handler]
#6 QMutex::lock (this=<optimized out>) at qmutex.cpp:151
#7 0x00007f85ac66c868 in QMutexLocker::QMutexLocker (m=<optimized out>, m=<optimized out>) at /usr/include/qt4/QtCore/qmutex.h:102
#8 Soprano::Error::ErrorCache::clearError (this=<optimized out>) at error.cpp:238
#9 0x00007f85ac66cccb in Soprano::Error::ErrorCache::setError (this=<optimized out>, error=<optimized out>) at error.cpp:225
#10 0x00007f85ac3f8c03 in Soprano::Client::DBusModel::executeQuery (this=<optimized out>, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at dbusmodel.cpp:112
#11 0x00007f85b08a25b2 in Nepomuk::MainModel::executeQuery (this=0x78fca0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at /var/tmp/portage/kde-base/kdelibs-4.7.95/work/kdelibs-4.7.95/nepomuk/core/nepomukmainmodel.cpp:212
#12 0x00007f85ac678099 in Soprano::FilterModel::executeQuery (this=<optimized out>, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at filtermodel.cpp:164
#13 0x00007f85a33842ac in activityResource (id=<optimized out>) at NepomukCommon.cpp:49
#14 0x00007f85a338a1d6 in RankingsUpdateThread::run (this=<optimized out>) at Rankings.cpp:104
#15 0x00007f85b01a197d in QThreadPrivate::start (arg=) at qthread_unix.cpp:331
#16 0x00007f85aff12d0c in start_thread (arg=0x7f85a337b700) at pthread_create.c:301
#17 0x00007f85aecd688d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7f85b18ee760 (LWP 4852)):
#0 0x00007f85aecd0113 in select () at ../sysdeps/unix/syscall-template.S:82
#1 0x00007f85b02a3665 in qt_safe_select (nfds=<optimized out>, fdread=<optimized out>, fdwrite=<optimized out>, fdexcept=<optimized out>, orig_timeout=<optimized out>) at qcore_unix.cpp:92
#2 0x00007f85ae96ecf3 in QNativeSocketEnginePrivate::nativeSelect (this=) at qnativesocketengine_unix.cpp:1002
#3 0x00007f85ae957dc9 in QNativeSocketEngine::waitForReadOrWrite (this=<optimized out>, readyToRead=<optimized out>, readyToWrite=<optimized out>, checkRead=<optimized out>, checkWrite=<optimized out>, msecs=<optimized out>, timedOut=<optimized out>) at qnativesocketengine.cpp:952
#4 0x00007f85ae964e98 in QAbstractSocket::waitForReadyRead (this=<optimized out>, msecs=<optimized out>) at qabstractsocket.cpp:1870
#5 0x00007f85ae9704e8 in QLocalSocket::waitForReadyRead (this=<optimized out>, msecs=<optimized out>) at qlocalsocket_unix.cpp:576
#6 0x00007f85ac3dd37a in Soprano::Client::ClientConnection::executeQuery (this=) at clientconnection.cpp:259
#7 0x00007f85ac3de9a7 in Soprano::Client...

Read more...

Created attachment 67289
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4

- What I was doing when the application crashed:
KDe startup

- Unusual behavior I noticed:
Plasma widgets such as yAWP and the CPU load monitor appeared to be frozen - no updates, no animations

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x65007200634408) at thread/qmutex.cpp:151
#7 0x00007fdf6d07b432 in Soprano::Error::ErrorCache::clearError() const () from /usr/lib/libsoprano.so.4
#8 0x00007fdf6d07b9e8 in Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib/libsoprano.so.4
#9 0x00007fdf6ce1385c in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsopranoclient.so.1
#10 0x00007fdf7111b1a2 in Nepomuk::MainModel::executeQuery (this=0x1873410, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212

*** Bug 290503 has been marked as a duplicate of this bug. ***

May be nepomuk. CC'ing trueg.

Created attachment 67461
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4

What I did when the KDE Activity Manager crashed:
→ Disabled/stopped Nepomuk services through kcm_nepomuk
→ Logged out from KDE session
→ Logged in to KDE session
→ Started an activity
→ Enabled/started Nepomuk services through kcm_nepomuk
→ KDE Activity Manager crashed

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x8) at thread/qmutex.cpp:151
#7 0x00007f8fb595996c in QMutexLocker (m=0x8, this=0x7f8faa882330) at /usr/include/qt4/QtCore/qmutex.h:102
#8 Soprano::Error::ErrorCache::clearError (this=0x9491e0) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/soprano/error.cpp:238
#9 0x00007f8fb5959e92 in Soprano::Error::ErrorCache::setError (this=0x9491e0, error=...) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/soprano/error.cpp:225
#10 0x00007f8fb56ec603 in Soprano::Client::DBusModel::executeQuery (this=0x9491d0, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/client/dbus/dbusmodel.cpp:112

Created attachment 67538
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.7.95 (4.8 RC1 (4.7.95) using Qt 4.7.4

- What I was doing when the application crashed:
I had just logged in when the applciation crashed, though it had no other side-effect than firing up the bug report window.

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x65007200630f08) at thread/qmutex.cpp:151
#7 0x00007fbb61c4e432 in Soprano::Error::ErrorCache::clearError() const () from /usr/lib/libsoprano.so.4
#8 0x00007fbb61c4e9e8 in Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib/libsoprano.so.4
#9 0x00007fbb619e685c in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsopranoclient.so.1
#10 0x00007fbb65cee1a2 in Nepomuk::MainModel::executeQuery (this=0x8688d0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212

Created attachment 67544
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.7.97 (4.8 RC2 (4.7.97) using Qt 4.7.4

- What I was doing when the application crashed:

Starting KDE 4.8 RC2 with no unusual settings

-- Backtrace (Reduced):
#6 0x00007f1a087689b9 in QMutex::lock() () from /usr/lib64/qt4/libQtCore.so.4
#7 0x00007f1a047d7a4c in Soprano::Error::ErrorCache::clearError() const () from /usr/lib64/libsoprano.so.4
#8 0x00007f1a047d7fa0 in Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib64/libsoprano.so.4
#9 0x00007f1a0456aa81 in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib64/libsopranoclient.so.1
#10 0x00007f1a08e571b4 in Nepomuk::MainModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib64/libnepomuk.so.4

*** Bug 291375 has been marked as a duplicate of this bug. ***

Created attachment 67775
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.7.97 (4.8 RC2 (4.7.97) using Qt 4.7.4

- What I was doing when the application crashed:
→ Logged in to KDE
→ Rightclicked on the 'Instant Messaging Presence' applet of KDE Telepathy in the systray
→ Selected 'Online'
→ Activity Manager crashed

I don't think the crash was related to the status change of KDE Telepathy, but as I'm not sure I've added it to the information. I think the crash was simply related to the KDE startup such as the other reported crashes before.

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x6500720063ca88) at thread/qmutex.cpp:151
#7 0x00007f644648b96c in QMutexLocker (m=0x6500720063ca88, this=0x7f643c5bf330) at /usr/include/qt4/QtCore/qmutex.h:102
#8 Soprano::Error::ErrorCache::clearError (this=0x8d1a40) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/soprano/error.cpp:238
#9 0x00007f644648be92 in Soprano::Error::ErrorCache::setError (this=0x8d1a40, error=...) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/soprano/error.cpp:225
#10 0x00007f644621e603 in Soprano::Client::DBusModel::executeQuery (this=0x8d1a30, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at /var/tmp/portage/dev-libs/soprano-2.7.3/work/soprano-2.7.3/client/dbus/dbusmodel.cpp:112

I'm now able to crash it nearly everytime when doing this:
→ Log in to KDE
→ Start switching between activities as soon as possible
→ Crash

It looks like there's some kind of a race condition. plasma-desktop requests an activity switch to be done, while the activity manager wasn't able yet to load the activites from Nepomuk.

I have similar problems, but I don't even need to switch activities manually. Each time I start KDE, I just have to wait a few seconds and then I get the message

"We are sorry, KDE Activity Manager close unexpectedly.
[...]
Details: Executable: kactivitymanagerd PID: 4627 Signal: Segmentation fault (11)"

It doesn't seem to affect anything. When I close the dialog, activities still work (although I don't use them), but this dialog is kinda annoying.

System: Gentoo Linux AMD64, KDE 4.8.0 (didn't happen with 4.7.4).

I had the same problem on my Fedora box, but not on Arch. On Fedora, I could use the ugly workaround of throwing away all nepomuk data and start all over in that department. After that, no crashes on Fedora, and a working activity manager.
 This leads me to the suggestion that it is not so much a plasma bug, but probably a soprano version issue.

*** Bug 292436 has been marked as a duplicate of this bug. ***

I don't get this bug anymore. After the install of 4.8 RC, I noticed a new activity was created named 'New Activity' (if I remember right). So, I deleted the new activity and also others that I don't use, and I'm left with only the 'Desktop' activity. Since then, I haven't had the crash anymore.

Created attachment 68340
Application: KDE-Aktivitätenverwaltung (kactivitymanagerd), signal: Segmentation fault

I have similar problems, but I don't even need to switch activities manually.
Each time I start KDE, I just have to wait a few seconds and then I get the
message. Especially when kwallet Password request comes up, and wasn't entered fast enough. Then four more password windows comes up, i guess from kmail. That's the moment when the crash happens.

System: Gentoo Linux AMD64, KDE 4.8.0 (didn't happen with 4.7.4).

Debug Info see as attached file.

Created attachment 68341
Application: KDE-Aktivitätenverwaltung (kactivitymanagerd), signal: Segmentation fault

Attachment to my comment #15

I've the same crash with KDE and Qt 4.8 compiled from sources during session startup (logged in from KDM).

*** Bug 293087 has been marked as a duplicate of this bug. ***

Created attachment 68453
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 "release 462" using Qt 4.8.0

This also happened on login for me. System is an openSuSE 11.4 using Qt 4.8.0.

-- Backtrace (Reduced):
#6 0x00007f2d089e46e5 in lockInline (this=0x649ce8) at /usr/include/QtCore/qmutex.h:187
#7 QMutexLocker (m=0x649ce8, this=0x7f2cfed9f430) at /usr/include/QtCore/qmutex.h:109
#8 Soprano::Error::ErrorCache::clearError (this=0x7f2cf8002570) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:238
#9 0x00007f2d089e4e48 in Soprano::Error::ErrorCache::setError (this=0x7f2cf8002570, error=...) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:225
#10 0x00007f2d08775f7f in Soprano::Client::DBusModel::executeQuery (this=0x7f2cf8002560, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at /usr/src/debug/soprano-2.7.4/client/dbus/dbusmodel.cpp:112

*** Bug 293188 has been marked as a duplicate of this bug. ***

*** Bug 293308 has been marked as a duplicate of this bug. ***

*** Bug 293376 has been marked as a duplicate of this bug. ***

For me it looks like you are happy when it crashes. If it does not it will not respond to dbus calls, leading to plasma workspace being extremely laggy (i.e. will take like a minute for anything to happen on click). Killing the activity manager daemon then will make things behave properly again.

Created attachment 68569
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:

Started the system as usual and it crashed. Crashes always.

-- Backtrace (Reduced):
#7 QMutex::lock (this=0x8f30cf6) at thread/qmutex.cpp:153
#8 0xb58cbd01 in lockInline (this=0x8f30cf6) at /usr/include/qt4/QtCore/qmutex.h:198
#9 QMutexLocker (m=0x8f30cf6, this=0xb259bdcc) at /usr/include/qt4/QtCore/qmutex.h:109
#10 Soprano::Error::ErrorCache::clearError (this=0x8f30ce8) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:238
#11 0xb58cc28e in Soprano::Error::ErrorCache::setError (this=0x8f30ce8, error=...) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:225

Created attachment 68570
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:

Started the system as usual and it crashed. Crashes always.

-- Backtrace (Reduced):
#7 QMutex::lock (this=0x8f30cf6) at thread/qmutex.cpp:153
#8 0xb58cbd01 in lockInline (this=0x8f30cf6) at /usr/include/qt4/QtCore/qmutex.h:198
#9 QMutexLocker (m=0x8f30cf6, this=0xb259bdcc) at /usr/include/qt4/QtCore/qmutex.h:109
#10 Soprano::Error::ErrorCache::clearError (this=0x8f30ce8) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:238
#11 0xb58cc28e in Soprano::Error::ErrorCache::setError (this=0x8f30ce8, error=...) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:225

Created attachment 68571
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:

Started the system as usual and it crashed. Crashes always.

-- Backtrace (Reduced):
#7 QMutex::lock (this=0x8f30cf6) at thread/qmutex.cpp:153
#8 0xb58cbd01 in lockInline (this=0x8f30cf6) at /usr/include/qt4/QtCore/qmutex.h:198
#9 QMutexLocker (m=0x8f30cf6, this=0xb259bdcc) at /usr/include/qt4/QtCore/qmutex.h:109
#10 Soprano::Error::ErrorCache::clearError (this=0x8f30ce8) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:238
#11 0xb58cc28e in Soprano::Error::ErrorCache::setError (this=0x8f30ce8, error=...) at /mnt/data/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:225

Sorry for tripple-post due to a bug in a crash reporting application. It reported failed connection two times, so I tried the "retry" button. The third try reported success.

Created attachment 68624
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0) using Qt 4.8.0

- What I was doing when the application crashed:

it crashed while loadingthe desktop
fedora 17

-- Backtrace (Reduced):
#5 0x00000038a2c527d5 in lockInline (this=0x1c8cd78) at /usr/include/QtCore/qmutex.h:187
#6 QMutexLocker (m=0x1c8cd78, this=0x7f5d57d28720) at /usr/include/QtCore/qmutex.h:109
#7 Soprano::Error::ErrorCache::clearError (this=this@entry=0x7f5d500038e0) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:238
#8 0x00000038a2c52ab0 in Soprano::Error::ErrorCache::setError (this=0x7f5d500038e0, error=...) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:225
#9 0x00000038a1435bec in Soprano::Client::DBusModel::executeQuery (this=0x7f5d500038d0, query=..., language=<optimized out>, userQueryLanguage=...) at /usr/src/debug/soprano-2.7.4/client/dbus/dbusmodel.cpp:112

Created attachment 68669
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4

- What I was doing when the application crashed:

I have similar problems, but I don't even need to switch activities manually. Each time I start KDE, I just have to wait a few seconds and then I get the message. This is same experience as a user above.

-- Backtrace (Reduced):
#6 QString (other=..., this=0x7f7da750a530) at ../../include/QtCore/../../src/corelib/tools/qstring.h:728
#7 QDBusAbstractInterface::interface (this=0x151ecd0) at qdbusabstractinterface.cpp:373
[...]
#9 0x00007f7db1a4c714 in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsopranoclient.so.1
#10 0x00007f7db5d557e2 in Nepomuk::MainModel::executeQuery (this=0x14d31a0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212
#11 0x00007f7db1cc3bd7 in Soprano::FilterModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsoprano.so.4

Created attachment 68791
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4

- What I was doing when the application crashed: Happened 5 or 6 times always direct after logging in.

-- Backtrace (Reduced):
#7 0x004e1b4b in QString (other=..., this=0xb69b7ec4) at ../../include/QtCore/../../src/corelib/tools/qstring.h:728
#8 QDBusAbstractInterface::interface (this=0x9564ed0) at qdbusabstractinterface.cpp:373
[...]
#10 0x05e41f45 in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsopranoclient.so.1
#11 0x00427a91 in Nepomuk::MainModel::executeQuery (this=0x9671138, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212
#12 0x02f72703 in Soprano::FilterModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsoprano.so.4

Created attachment 68930
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.7.4

- What I was doing when the application crashed: kactivitymanagerd crashed unexpectedly.

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x6500720063bee8) at thread/qmutex.cpp:151
#7 0x00007fd8abf9c432 in Soprano::Error::ErrorCache::clearError() const () from /usr/lib/libsoprano.so.4
#8 0x00007fd8abf9c9e8 in Soprano::Error::ErrorCache::setError(Soprano::Error::Error const&) const () from /usr/lib/libsoprano.so.4
#9 0x00007fd8abd3485c in Soprano::Client::DBusModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib/libsopranoclient.so.1
#10 0x00007fd8b003d7e2 in Nepomuk::MainModel::executeQuery (this=0x29a76d0, query=..., language=Soprano::Query::QueryLanguageSparql, userQueryLanguage=...) at ../../nepomuk/core/nepomukmainmodel.cpp:212

Created attachment 68993
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:

kactivitymanager crashed when kde is starting (startx from console). It crashed almost immediately after the ksplash finished. No other unusual things afterwards.

-- Backtrace (Reduced):
#6 QDBusAbstractInterface::interface (this=<optimized out>) at /var/tmp/portage/x11-libs/qt-dbus-4.8.0/work/qt-everywhere-opensource-src-4.8.0/src/dbus/qdbusabstractinterface.cpp:725
#7 0x00007fac679e9929 in Soprano::Client::DBusAbstractInterface::callWithArgumentListAndBigTimeout (this=<optimized out>, mode=<optimized out>, method=..., args=...) at dbusabstractinterface.cpp:42
#8 0x00007fac679ec4f6 in Soprano::Client::DBusModelInterface::executeQuery (this=<optimized out>, query=..., queryLanguage=..., mode=<error reading variable: Unhandled dwarf expression opcode 0x1>) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/dbus/dbusmodelinterface.h:82
#9 0x00007fac679f2238 in Soprano::Client::DBusModel::executeQuery (this=<optimized out>, query=<error reading variable: Unhandled dwarf expression opcode 0x0>, language=<optimized out>, userQueryLanguage=...) at dbusmodel.cpp:111
#10 0x00007fac6c409dee in Nepomuk::MainModel::executeQuery(QString const&, Soprano::Query::QueryLanguage, QString const&) const () from /usr/lib64/libnepomuk.so.4

Created attachment 69068
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.00 (4.8.0 using Qt 4.8.0

- What I was doing when the application crashed:

Looks like this time it crashed at a different point, I removed /var/tmp/kdecache-* before startx, don't know whether that's related.

-- Backtrace (Reduced):
#9 0x00007f1b3b19ed5a in QByteArray::realloc (this=<optimized out>, alloc=<optimized out>) at qbytearray.cpp:1452
#10 0x00007f1b3b19ef07 in QByteArray::resize (this=<optimized out>, size=<optimized out>) at qbytearray.cpp:1420
#11 0x00007f1b3987d87c in QRingBuffer::reserve (this=<error reading variable: Unhandled dwarf expression opcode 0x0>, bytes=<optimized out>) at /var/tmp/portage/x11-libs/qt-core-4.8.0-r1/work/qt-everywhere-opensource-src-4.8.0/src/network/../../include/QtCore/private/../../../src/corelib/tools/qringbuffer_p.h:158
#12 0x00007f1b398f7925 in QAbstractSocket::writeData (this=<optimized out>, data=<optimized out>, size=<optimized out>) at qabstractsocket.cpp:2315
#13 0x00007f1b3b22c1b1 in QIODevice::write (this=<error reading variable: Unhandled dwarf expression opcode 0x0>, data=<error reading variable: Unhandled dwarf expression opcode 0x0>, maxSize=<optimized out>) at qiodevice.cpp:1370

*** Bug 294825 has been marked as a duplicate of this bug. ***

*** Bug 294882 has been marked as a duplicate of this bug. ***

*** Bug 294718 has been marked as a duplicate of this bug. ***

*** Bug 294993 has been marked as a duplicate of this bug. ***

*** Bug 295007 has been marked as a duplicate of this bug. ***

I see this now every time I log in. I don't ever use activities but when I checked, I found they had multiplied enormously, with many having identical names (but not identical icons). Some are disabled, some enabled, some active, some can be configured, some not. I deleted a number with spherical icons as opposed to meaningful icons. I've not got one spherical one left which seems to be default so I guess I can't get rid of it and 3 disabled ones with meaningful icons (search, desktop icons, photos). I've never been sure what these were for. I think this means I've lost the original main activity but I'm not sure.

kde 4.8.0: arch package: 4.8.0-1

*** Bug 295579 has been marked as a duplicate of this bug. ***

Created attachment 69479
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

- What I was doing when the application crashed:
Starting a session. Everything is frozen/slow to respond until the crash reporter starts.

This happens everytime, and there are no customizations.

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x6500720063b428) at thread/qmutex.cpp:150
#7 0x00007ff62447ea3c in QMutexLocker (m=<optimized out>, this=0x7ff61aca4360) at /usr/include/qt4/QtCore/qmutex.h:102
#8 Soprano::Error::ErrorCache::clearError (this=0x15145d0) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:238
#9 0x00007ff62447ef90 in Soprano::Error::ErrorCache::setError (this=0x15145d0, error=...) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/soprano/error.cpp:225
#10 0x00007ff624211be1 in Soprano::Client::DBusModel::executeQuery (this=0x15145c0, query=..., language=<optimized out>, userQueryLanguage=...) at /var/tmp/portage/dev-libs/soprano-2.7.4/work/soprano-2.7.4/client/dbus/dbusmodel.cpp:112

*** Bug 296046 has been marked as a duplicate of this bug. ***

*** Bug 296120 has been marked as a duplicate of this bug. ***

I have nothing new to add to this, but I'm also affected. I could generate a backtrace and post it, but the automated debug package installer fails. What package do I need for the debug symbols?

Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.8.1 (4.8.1)
Qt Version: 4.8.0
Operating System: Linux 3.0.0-16-generic x86_64
Distribution: Ubuntu 11.10

-- Information about the crash:
Crashes on each start-up, but doesn't prevent me from starting/stopping/changing activities.

The crash can be reproduced every time.

-- Backtrace:
A useful backtrace could not be generated

Report to https://bugs.kde.org

*** Bug 294730 has been marked as a duplicate of this bug. ***

*** Bug 295755 has been marked as a duplicate of this bug. ***

*** Bug 296418 has been marked as a duplicate of this bug. ***

*** Bug 288888 has been marked as a duplicate of this bug. ***

*** Bug 291800 has been marked as a duplicate of this bug. ***

*** Bug 296661 has been marked as a duplicate of this bug. ***

*** Bug 296790 has been marked as a duplicate of this bug. ***

*** Bug 296846 has been marked as a duplicate of this bug. ***

Jonathan Riddell (jr) on 2012-03-27
Changed in kactivities (Ubuntu):
milestone: none → ubuntu-12.04-beta-2
importance: Undecided → High
tags: added: kubuntu
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/966247

tags: added: iso-testing

*** Bug 297051 has been marked as a duplicate of this bug. ***

Changed in kactivities (Ubuntu):
milestone: ubuntu-12.04-beta-2 → ubuntu-12.04

Created attachment 70020
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.1 (4.8.1) "release 483" using Qt 4.8.0

- What I was doing when the application crashed:
It just crashes every time on login, but I do not see any unusualties in activity list as other people already reported. Moreover, it seems to me my backtrace is slightly different from the others...

-- Backtrace (Reduced):
#6 0x00007f9968f526e5 in lockInline (this=0x648818) at /usr/include/QtCore/qmutex.h:187
#7 QMutexLocker (m=0x648818, this=0x7f995ec9d460) at /usr/include/QtCore/qmutex.h:109
#8 Soprano::Error::ErrorCache::clearError (this=0x7f9958004240) at /usr/src/debug/soprano-2.7.5/soprano/error.cpp:238
#9 0x00007f9968f52e48 in Soprano::Error::ErrorCache::setError (this=0x7f9958004240, error=...) at /usr/src/debug/soprano-2.7.5/soprano/error.cpp:225
#10 0x00007f9968ce43af in Soprano::Client::DBusModel::executeQuery (this=0x7f9958004230, query=<optimized out>, language=<optimized out>, userQueryLanguage=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/dbus/dbusmodel.cpp:112

*** Bug 297279 has been marked as a duplicate of this bug. ***

*** Bug 297386 has been marked as a duplicate of this bug. ***

Knock on wood - since the KDE 4.8.2 update on Kubuntu 12.04 I haven't seen this bug for the last 3 reboots.

You shouldn't see this bug in 4.8.2 (and later) simply because the nepomuk plugin is not used anymore - so there is no mutithreaded nepomuk access anymore.

KAMD still saves some data into nepomuk, but not as much as before.

That is the reason I haven't closed this report - the multithreaded nepomuk access issue is still here, just kamd is not triggering it anymore.

In order to reproduce, kamd needs to be build with KACTIVITIES_BUILD_NEPOMUK_PLUGIN option activated (and the sqlite plugin needs to be disabled when starting kamd)

Created attachment 70219
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.1 (4.8.1) using Qt 4.8.0

This crash occurs when logging in to KDE 4 (every time)
It might be linked to another segfault with Kmix, which comes first and is raised as a duplicate of this lead ticket https://bugs.kde.org/show_bug.cgi?id=290742

-- Backtrace (Reduced):
#7 QMutex::lock (this=0x9df4be4) at thread/qmutex.cpp:153
#8 0x428daed8 in lockInline (this=<optimized out>) at /usr/include/QtCore/qmutex.h:198
#9 QMutexLocker (m=<optimized out>, this=0xb63c3df4) at /usr/include/QtCore/qmutex.h:109
#10 Soprano::Error::ErrorCache::clearError (this=0xb5a02908) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:238
#11 0x428db228 in Soprano::Error::ErrorCache::setError (this=0xb5a02908, error=...) at /usr/src/debug/soprano-2.7.4/soprano/error.cpp:225

*** Bug 297943 has been marked as a duplicate of this bug. ***

Hello,

is there a temporary solution available?
I am using openSuse 64 bit current with Tumbleweed.
I cannot send emails via kmail and furthermore I cannot access my emails
stored in kmail.
For the permanent solution: How long will it take to make 4.8.2 available
in the Tumbleweed repo?
Thanks
Stefan

2012/4/12 Ivan Čukić <email address hidden>

> https://bugs.kde.org/show_bug.cgi?id=290234
>
> Ivan Čukić <email address hidden> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> CC| |<email address hidden>
>
> --- Comment #60 from Ivan Čukić <email address hidden> ---
> *** Bug 297943 has been marked as a duplicate of this bug. ***
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

You can try the following (but I don't know whether it will work) - open .kde/share/config/activitymanager-pluginsrc and add the following to the [Global] section:

disabledPlugins=activitymanager_plugin_nepomuk

So the file would look something like this (and restart KAMD)
[Global] disabledPlugins=activitymanager_plugin_nepomuk

Thanks,

I do not have this file.
I checked .kde and .kde4.
Is there an easy way to create this file?
Something to consider like header or format to save the file?
An example is appreciated ;-)

2012/4/12 Ivan Čukić <email address hidden>

> https://bugs.kde.org/show_bug.cgi?id=290234
>
> Ivan Čukić <email address hidden> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> CC| |<email address hidden>
> Component|general |general
> Resolution|--- |FIXED
> Assignee|<email address hidden> |<email address hidden>
> Product|nepomuk |kactivities
>
> --- Comment #62 from Ivan Čukić <email address hidden> ---
> You can try the following (but I don't know whether it will work) - open
> .kde/share/config/activitymanager-pluginsrc and add the following to the
> [Global] section:
>
> disabledPlugins=activitymanager_plugin_nepomuk
>
> So the file would look something like this (and restart KAMD)
> [Global]
>
> disabledPlugins=activitymanager_plugin_nepomuk
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

Here you go:

--- snip after this ----
[Global]
disabledPlugins=activitymanager_plugin_nepomuk
--- till here -----

Thanks for your effort but this solution does not work.
Is it possible to add a stable kde repo to my above mentioned environment?
Up to now I am afraid that adding an additonal repo can cause an instable
system.
By accident I renamed my activitymanagerrc file and now all desktop icons
are gone.
Renaming this file back to its original name does not show any success.
I think I should stop here playing around with my productive environment.

2012/4/12 Ivan Čukić <email address hidden>

> https://bugs.kde.org/show_bug.cgi?id=290234
>
> --- Comment #64 from Ivan Čukić <email address hidden> ---
> Here you go:
>
> --- snip after this ----
> [Global]
> disabledPlugins=activitymanager_plugin_nepomuk
> --- till here -----
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.
>

No clue. I don't use suse. Guessing TWeed will get 4.8.2 soon.

*** Bug 297996 has been marked as a duplicate of this bug. ***

*** Bug 298478 has been marked as a duplicate of this bug. ***

Created attachment 70547
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.2 (4.8.2) using Qt 4.8.1

When kde is startup and loggin to session every time.

-- Backtrace (Reduced):
#6 0x00007f80b3f5971a in lockInline (this=0x797bf8) at /usr/include/QtCore/qmutex.h:187
#7 QMutexLocker (m=0x797bf8, this=<synthetic pointer>) at /usr/include/QtCore/qmutex.h:109
#8 Soprano::Client::SocketHandler::~SocketHandler (this=0x79b560, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:58
#9 0x00007f80b3f59859 in Soprano::Client::SocketHandler::~SocketHandler (this=0x79b560, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:61
#10 0x00007f80b81e153d in QThreadStorageData::set (this=0x797d50, p=0x812360) at thread/qthreadstorage.cpp:165

Mitch Golden (mgolden) wrote :

This is probably this bug over on kde.org

https://bugs.kde.org/show_bug.cgi?id=290234

This is now marked RESOLVED UPSTREAM. Is there some explanation of what the upstream problem is, and which ticket is attached to it? I don't see anything indicating what is believed to be going on.

*** Bug 299325 has been marked as a duplicate of this bug. ***

*** Bug 299485 has been marked as a duplicate of this bug. ***

*** Bug 281955 has been marked as a duplicate of this bug. ***

*** Bug 298909 has been marked as a duplicate of this bug. ***

*** Bug 299567 has been marked as a duplicate of this bug. ***

*** Bug 299938 has been marked as a duplicate of this bug. ***

*** Bug 300828 has been marked as a duplicate of this bug. ***

*** Bug 300874 has been marked as a duplicate of this bug. ***

*** Bug 300913 has been marked as a duplicate of this bug. ***

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in kactivities (Ubuntu):
status: New → Confirmed
Jonathan Thomas (echidnaman) wrote :

Actually is a soprano bug, and it's fixed with soprano 2.8.

affects: kactivities (Ubuntu) → soprano (Ubuntu)
Changed in soprano (Ubuntu):
milestone: ubuntu-12.04 → none
status: Confirmed → Fix Released
Changed in kactivities:
importance: Unknown → High
status: Unknown → Won't Fix

Created attachment 72025
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.3 (4.8.3) using Qt 4.8.2

- What I was doing when the application crashed:

I logged into the desktop.
Kactivityd crashes with a seg fault every single time I login.
It waits until I have launched an application.

-- Backtrace (Reduced):
#7 0x41100174 in lockInline (this=0x8df6d8c) at /usr/include/QtCore/qmutex.h:187
#8 QMutexLocker (m=0x8df6d8c, this=<synthetic pointer>) at /usr/include/QtCore/qmutex.h:109
#9 Soprano::Client::SocketHandler::~SocketHandler (this=0x8eb0818, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:58
#10 0x41100343 in Soprano::Client::SocketHandler::~SocketHandler (this=0x8eb0818, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:61
#11 0x41100534 in qThreadStorage_deleteData<Soprano::Client::SocketHandler> (d=0x8eb0818) at /usr/include/QtCore/qthreadstorage.h:97

*** Bug 301998 has been marked as a duplicate of this bug. ***

*** Bug 297082 has been marked as a duplicate of this bug. ***

Every time i logged on, kactivitimanager crashed sooner or later. Also Kmail crashes very often while using.
Virtuoso-t process consumes about 30% of my Quad-Core CPU load, although strigi doesn't index anything.
I also noticed a strong delay when logging in, until kmix, klipper and strigi symbols came up.

Some of my interestingly findings:
After logging into the desktop, before the activitymangerd crashes, the akonadi test results was fine, after the crash the following fault was in:
Nepomuk search service not registered at D-Bus.
If the crash happens very early after log in, the kmix, klipper and strigi symbols doesn't came up at all sometimes.

I tried every forum and bug report hints i could find, nothing works until...
I deleted the following directory ~/.kde4/share/apps/nepomuk (while not logged into kde of course).

Logging in is pretty fast now, kmail much more responsive than before, and kactivitymanagerd doesn't crash once since this.
Akonadi's error log is clean now and hopefully stays so.

So that's the solution for me and also for another guy who takes this advice, I gave to him in the gentoo forum. Eventually this is the reason for some other bugs like the virtuoso CPU consumption Bug 293641 and one reason for kmail crashes too - hopefully.

So give it a try, but beware of the fact that if you've done some tagging of indexed files, this would be lost in this case and a new re-indexing of your hard drive is necessary!
Do a backup before or something else to save your work, if its important for you.

Much success, Andy.

You should really address only one issue per bug report.
The virtuoso problems you describe are well known, but you shouldn't mix everything together. ;-)

(In reply to comment #85)
> You should really address only one issue per bug report.
> The virtuoso problems you describe are well known, but you shouldn't mix
> everything together. ;-)

Ok Janek,

I will respect this hint next time.

*** Bug 304119 has been marked as a duplicate of this bug. ***

Created attachment 74817
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.4 (4.8.4) using Qt 4.8.2

some programs crash after login

-- Backtrace (Reduced):
#6 QMutex::lock (this=0x1847478) at thread/qmutex.cpp:153
#7 0x00007f2d5cf3b097 in lockInline (this=0x1847478) at /usr/include/qt4/QtCore/qmutex.h:198
#8 QMutexLocker (m=0x1847478, this=<synthetic pointer>) at /usr/include/qt4/QtCore/qmutex.h:109
#9 Soprano::Client::SocketHandler::~SocketHandler (this=0x1870f40, __in_chrg=<optimized out>) at ../../client/clientconnection.cpp:58
#10 0x00007f2d5cf3b0f9 in Soprano::Client::SocketHandler::~SocketHandler (this=0x1870f40, __in_chrg=<optimized out>) at ../../client/clientconnection.cpp:61

Created attachment 75115
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.8.5 (4.8.5) "release 2" using Qt 4.8.1

- What I was doing when the application crashed:

Logging out of KD, after doing an update using YAST.

-- Backtrace (Reduced):
#6 0x00007ff3b4b5b606 in lockInline (this=0x75eaa8) at /usr/include/QtCore/qmutex.h:187
#7 QMutexLocker (m=0x75eaa8, this=<synthetic pointer>) at /usr/include/QtCore/qmutex.h:109
#8 Soprano::Client::SocketHandler::~SocketHandler (this=0x885d70, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:58
#9 0x00007ff3b4b5b739 in Soprano::Client::SocketHandler::~SocketHandler (this=0x885d70, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.6/client/clientconnection.cpp:61
#10 0x00007ff3b9098bd0 in QThreadStorageData::set (this=<optimized out>, p=0x78c090) at thread/qthreadstorage.cpp:165

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.