| Summary: | Plasma (and kactivitymanagerd) crashes after logging out [QMutex::lock, Soprano::Client::SocketHandler::~SocketHandler, QThreadStorage<QFontCache*>::deleteData] | ||
|---|---|---|---|
| Product: | [Plasma] plasma4 | Reporter: | Gregor Petrin <gregap> |
| Component: | general | Assignee: | Chani <chanika> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | andresbajotierra, bruno, jason.mours, plasma-bugs, sebastian, stephaniedasgupta, trapni, trueg |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi |
||
|
Description
Gregor Petrin
2010-11-30 12:41:00 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 from a bug triager] Reverting last change. Sorry about that. (didn't see the bug's history) 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. 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 ()
I have the same problem. I went to log out and plasma crashed. I have KDE 4.6.1 - Kubuntu 10.10 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 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. *** Bug 282745 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 251795 *** |