Bug 298478 - Activity Manager crashes after login
Summary: Activity Manager crashes after login
Status: RESOLVED DUPLICATE of bug 290234
Alias: None
Product: plasma4
Classification: Unmaintained
Component: activities (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-04-20 09:36 UTC by Pedro de Carvalho Gomes
Modified: 2012-04-20 10:05 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro de Carvalho Gomes 2012-04-20 09:36:50 UTC
Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.8.2 (4.8.2) "release 491"
Qt Version: 4.8.1
Operating System: Linux 3.1.9-1.4-desktop x86_64
Distribution: "openSUSE 12.1 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed: I just logged in, and Activity Manager crashed right next

- Unusual behavior I noticed: none.

- Custom settings of the application: I run some desktop apps, such as comics and weather. Moreover, I have several activities that start in the task bar: KrandR, Nepomuk, KPackageKit....

The crash can be reproduced every time.

-- Backtrace:
Application: KDE:s aktivitetshantering (kactivitymanagerd), signal: Segmentation fault
[KCrash Handler]
#6  0x00007f1bbe5dd71a in lockInline (this=0x73ab58) at /usr/include/QtCore/qmutex.h:187
#7  QMutexLocker (m=0x73ab58, this=<synthetic pointer>) at /usr/include/QtCore/qmutex.h:109
#8  Soprano::Client::SocketHandler::~SocketHandler (this=0x76d640, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:58
#9  0x00007f1bbe5dd859 in Soprano::Client::SocketHandler::~SocketHandler (this=0x76d640, __in_chrg=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:61
#10 0x00007f1bc286553d in QThreadStorageData::set (this=0x7b1410, p=0x81d6f0) at thread/qthreadstorage.cpp:165
#11 0x00007f1bbe5db1e0 in qThreadStorage_setLocalData<Soprano::Client::SocketHandler> (d=<optimized out>, t=<optimized out>) at /usr/include/QtCore/qthreadstorage.h:92
#12 setLocalData (t=0x81d6f0, this=<optimized out>) at /usr/include/QtCore/qthreadstorage.h:155
#13 Soprano::Client::ClientConnection::socketForCurrentThread (this=0x770000) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:95
#14 0x00007f1bbe5db259 in Soprano::Client::ClientConnection::connectInCurrentThread (this=<optimized out>) at /usr/src/debug/soprano-2.7.5/client/clientconnection.cpp:800
#15 0x00007f1bbe5da81a in Soprano::Client::LocalSocketClient::connect (this=0x7720c8, name=...) at /usr/src/debug/soprano-2.7.5/client/localsocketclient.cpp:141
#16 0x00007f1bc2f94591 in init (forced=true, this=0x7720a0) at /usr/src/debug/kdelibs-4.8.2/nepomuk/core/nepomukmainmodel.cpp:102
#17 Nepomuk::MainModel::init (this=0x7b6180) at /usr/src/debug/kdelibs-4.8.2/nepomuk/core/nepomukmainmodel.cpp:176
#18 0x00007f1bc2f8b901 in Nepomuk::ResourceManager::init (this=0x81ad30) at /usr/src/debug/kdelibs-4.8.2/nepomuk/core/resourcemanager.cpp:326
#19 0x00007f1bc2f8f0d5 in Nepomuk::ResourceManagerPrivate::_k_storageServiceInitialized (this=0x7b70f0, success=<optimized out>) at /usr/src/debug/kdelibs-4.8.2/nepomuk/core/resourcemanager.cpp:225
#20 0x00007f1bc2f8f24b in Nepomuk::ResourceManager::qt_metacall (this=0x81ad30, _c=QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fffc4bca560) at /usr/src/debug/kdelibs-4.8.2/build/nepomuk/resourcemanager.moc:112
#21 0x00007f1bc2ce1f6b in QDBusConnectionPrivate::deliverCall (this=0x643fe0, object=0x81ad30, msg=..., metaTypes=..., slotIdx=10) at qdbusintegrator.cpp:947
#22 0x00007f1bc297e2b6 in QObject::event (this=0x81ad30, e=<optimized out>) at kernel/qobject.cpp:1204
#23 0x00007f1bc1cea0d4 in notify_helper (e=0x76ff50, receiver=0x81ad30, this=0x65f1a0) at kernel/qapplication.cpp:4554
#24 QApplicationPrivate::notify_helper (this=0x65f1a0, receiver=0x81ad30, e=0x76ff50) at kernel/qapplication.cpp:4526
#25 0x00007f1bc1ceef53 in QApplication::notify (this=0x7fffc4bcaf90, receiver=0x81ad30, e=0x76ff50) at kernel/qapplication.cpp:4415
#26 0x00007f1bc3464886 in KApplication::notify (this=0x7fffc4bcaf90, receiver=0x81ad30, event=0x76ff50) at /usr/src/debug/kdelibs-4.8.2/kdeui/kernel/kapplication.cpp:311
#27 0x00007f1bc296522c in QCoreApplication::notifyInternal (this=0x7fffc4bcaf90, receiver=0x81ad30, event=0x76ff50) at kernel/qcoreapplication.cpp:876
#28 0x00007f1bc2968aca in sendEvent (event=0x76ff50, receiver=0x81ad30) at kernel/qcoreapplication.h:231
#29 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x6293d0) at kernel/qcoreapplication.cpp:1500
#30 0x00007f1bc2993e53 in sendPostedEvents () at kernel/qcoreapplication.h:236
#31 postEventSourceDispatch (s=0x6549b0) at kernel/qeventdispatcher_glib.cpp:279
#32 0x00007f1bbd8a858d in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#33 0x00007f1bbd8a8d88 in ?? () from /usr/lib64/libglib-2.0.so.0
#34 0x00007f1bbd8a8f59 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#35 0x00007f1bc299427f in QEventDispatcherGlib::processEvents (this=0x6290b0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#36 0x00007f1bc1d8d76e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#37 0x00007f1bc2964012 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#38 0x00007f1bc2964267 in QEventLoop::exec (this=0x7fffc4bcaf20, flags=...) at kernel/qeventloop.cpp:204
#39 0x00007f1bc2968dc5 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1148
#40 0x00000000004061e4 in ?? ()
#41 0x00007f1bc149323d in __libc_start_main () from /lib64/libc.so.6
#42 0x0000000000406239 in _start ()

This bug may be a duplicate of or related to bug 290234.

Possible duplicates by query: bug 295755, bug 294849, bug 294765, bug 293308, bug 291935.

Reported using DrKonqi
Comment 1 Jekyll Wu 2012-04-20 10:05:23 UTC

*** This bug has been marked as a duplicate of bug 290234 ***