Bug 258365 - Plasma (and kactivitymanagerd) crashes after logging out [QMutex::lock, Soprano::Client::SocketHandler::~SocketHandler, QThreadStorage<QFontCache*>::deleteData]
Summary: Plasma (and kactivitymanagerd) crashes after logging out [QMutex::lock, Sopra...
Status: RESOLVED DUPLICATE of bug 251795
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Chani
URL:
Keywords:
: 282745 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-11-30 12:41 UTC by Gregor Petrin
Modified: 2011-09-29 14:04 UTC (History)
8 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (1.12 KB, text/plain)
2010-12-07 08:45 UTC, jason.mours
Details
New crash information added by DrKonqi (6.06 KB, text/plain)
2011-05-19 02:35 UTC, Christian Parpart
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Petrin 2010-11-30 12:41:00 UTC
Application: kactivitymanagerd (1.0)
KDE Platform Version: 4.5.80 (4.6 Beta1)
Qt Version: 4.7.1
Operating System: Linux 2.6.34.7-0.5-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
- What I was doing when the application crashed:
I was logging out of my KDE session after problems with activities.

- Unusual behavior I noticed:
The reason I was logging out was that first my active activity disapeared with all its widgets and I got the default desktop, and second when I wanted to add a new activity, the new activity dialog was unresponsive and would not even close.

-- Backtrace:
Application: KDE Activity Manager (kactivitymanagerd), signal: Segmentation fault
[KCrash Handler]
#7  QMutex::lock (this=0x8138dfc) at thread/qmutex.cpp:151
#8  0xb5a09488 in QMutexLocker (this=0x8141080, __in_chrg=<value optimized out>) at /usr/include/QtCore/qmutex.h:102
#9  Soprano::Client::SocketHandler::~SocketHandler (this=0x8141080, __in_chrg=<value optimized out>) at /usr/src/debug/soprano-2.5.63/client/clientconnection.cpp:58
#10 0xb5a09632 in Soprano::Client::SocketHandler::~SocketHandler (this=0x8141080, __in_chrg=<value optimized out>) at /usr/src/debug/soprano-2.5.63/client/clientconnection.cpp:61
#11 0xb65ec7e3 in QThreadStorage<QFontCache*>::deleteData (x=0x8141080) at ../../src/corelib/thread/qthreadstorage.h:133
#12 0xb6d804d3 in QThreadStorageData::set (this=0x80cdf78, p=0x0) at thread/qthreadstorage.cpp:148
#13 0xb65e8b7d in qThreadStorage_setLocalData<QFontCache> () at ../../src/corelib/thread/qthreadstorage.h:92
#14 setLocalData () at ../../src/corelib/thread/qthreadstorage.h:148
#15 QFontCache::cleanup () at text/qfont.cpp:2632
#16 0xb66c30c4 in QFont::cleanup () at text/qfont_x11.cpp:182
#17 0xb642394a in qt_cleanup () at kernel/qapplication_x11.cpp:2624
#18 0xb63a1636 in QApplication::~QApplication (this=0xbff14760, __in_chrg=<value optimized out>) at kernel/qapplication.cpp:1163
#19 0xb74d0688 in KApplication::~KApplication (this=0xbff14760, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.5.80/kdeui/kernel/kapplication.cpp:892
#20 0xb74d06f8 in KUniqueApplication::~KUniqueApplication (this=0xbff14760, __in_chrg=<value optimized out>) at /usr/src/debug/kdelibs-4.5.80/kdeui/kernel/kuniqueapplication.cpp:343
#21 0x08054109 in _start ()

Reported using DrKonqi
Comment 1 Chani 2010-11-30 16:50:17 UTC
soprano? wtf?
the backtrace makes no sense to me :( all I know is that it's probably not related to activities.

as for your problems with activities, yes, I took a week off sick and *someone* managed to completely break them just in time for the beta. *sigh* I'll make sure they work before the actual release.
Comment 2 Dario Andres 2010-11-30 20:56:01 UTC
[Comment from a bug triager]
Reverting last change. Sorry about that. (didn't see the bug's history)
Comment 3 Gregor Petrin 2010-12-01 10:03:51 UTC
Yeah, the whole nepomuk/striki/akonadi stack is acting really wierd on my machine, don't know how it got into the backtrace but I'm constantly getting dialogs and warnings triggered by those apps. I'm still considering whether to start filing bugs, wait for a new build or ask around on IRC.
Comment 4 jason.mours 2010-12-07 08:45:05 UTC
Created attachment 54231 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.5.80 (4.6 Beta1) using Qt 4.7.1

- What I was doing when the application crashed:

- Unusual behavior I noticed:
Preforming a logout. Desktop Crashed. openSUSE 11.3 / update Factory KDE: 4.6beta

-- Backtrace (Reduced):
#13 0x0000000000407610 in _start ()
Comment 5 Stephanie Das Gupta 2011-04-02 10:13:51 UTC
I have the same problem.

I went to log out and plasma crashed.

I have KDE 4.6.1 - Kubuntu 10.10
Comment 6 Christian Parpart 2011-05-19 02:35:15 UTC
Created attachment 60138 [details]
New crash information added by DrKonqi

kactivitymanagerd (1.0) on KDE Platform 4.6.3 (4.6.3) using Qt 4.7.2

- What I was doing when the application crashed:
i was logging in. nothing more :)


--
I don't know what else to say, except the above, in fact, that's what I was doing *but* the crash reporting assistant wants me to write more, so I do :-)

Hope it helps anyways :)

-- Backtrace (Reduced):
#6  0x00007fa89927b45c in QMutex::lock (this=0x6bf6e8) at thread/qmutex.cpp:151
#7  0x00007fa89658a34d in QMutexLocker (this=0x6c1a00, __in_chrg=<value optimized out>) at /usr/include/qt4/QtCore/qmutex.h:102
#8  Soprano::Client::SocketHandler::~SocketHandler (this=0x6c1a00, __in_chrg=<value optimized out>) at /var/tmp/portage/dev-libs/soprano-2.6.0/work/soprano-2.6.0/client/clientconnection.cpp:58
#9  0x00007fa89658a469 in Soprano::Client::SocketHandler::~SocketHandler (this=0x6c1a00, __in_chrg=<value optimized out>) at /var/tmp/portage/dev-libs/soprano-2.6.0/work/soprano-2.6.0/client/clientconnection.cpp:61
#10 0x00007fa89927e266 in QThreadStorageData::set (this=0x6b70c0, p=0x6b70f0) at thread/qthreadstorage.cpp:165
Comment 7 Dario Andres 2011-09-29 13:27:58 UTC
[Comment from a bug triager]
From bug 282745 (KDE SC 4.7.1):
-- Information about the crash:
- What I was doing when the application crashed: During my session I've
upgraded packages, and then disconnect to shutdown the computer.
The crash happen at that time.
Comment 8 Dario Andres 2011-09-29 13:28:21 UTC
*** Bug 282745 has been marked as a duplicate of this bug. ***
Comment 9 Sebastian Trueg 2011-09-29 14:04:35 UTC

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