Bug 288100 - ActivityManager crash on logout
Summary: ActivityManager crash on logout
Status: RESOLVED DUPLICATE of bug 286627
Alias: None
Product: plasma4
Classification: Plasma
Component: activities (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-03 00:13 UTC by mgolden
Modified: 2011-12-03 09:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description mgolden 2011-12-03 00:13:28 UTC
Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.7.2 (4.7.2)
Qt Version: 4.7.4
Operating System: Linux 3.0.0-13-generic x86_64
Distribution: Ubuntu 11.10

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

This was a crash that occurred when I was logging out.  I was in a desktop icons activity.  

- Unusual behavior I noticed:

Earlier today, I noticed that plasma crashed when I logged in having been in a Search activity.

-- Backtrace:
Application: KDE Activity Manager (kactivitymanagerd), signal: Segmentation fault
[KCrash Handler]
#6  0x00007fa82d4c123c in QMutex::lock (this=0x11d5aa8) at thread/qmutex.cpp:151
#7  0x00007fa82b2bec1d in ?? () from /usr/lib/libsopranoclient.so.1
#8  0x00007fa82b2bed49 in ?? () from /usr/lib/libsopranoclient.so.1
#9  0x00007fa82d4c4107 in QThreadStorageData::set (this=0x1099ce0, p=0x0) at thread/qthreadstorage.cpp:165
#10 0x00007fa82e2a452a in qt_cleanup () at kernel/qapplication_x11.cpp:2693
#11 0x00007fa82e22fea4 in QApplication::~QApplication (this=0x7fff24e2d340, __in_chrg=<optimized out>) at kernel/qapplication.cpp:1185
#12 0x00000000004059d0 in main (argc=1, argv=0x7fff24e2d538) at ../../activitymanager/main.cpp:37

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

Possible duplicates by query: bug 282745, bug 280011, bug 259585.

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2011-12-03 09:25:32 UTC

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