Summary: | Upon reboot after getting updates plasma won't restart. [QString::operator=, Marble::WorldClock::init, Plasma::Corona::loadLayout] | ||
---|---|---|---|
Product: | [Applications] marble | Reporter: | darthanubis |
Component: | plasmoid | Assignee: | marble-bugs |
Status: | RESOLVED DUPLICATE | ||
Severity: | crash | CC: | andresbajotierra, asraniel, mjniven, moritz-kdebugs, pro.grette.mickael, qhearnshaw, stephane_bazze, timfolger |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
darthanubis
2009-07-15 04:59:46 UTC
*** Bug 200374 has been marked as a duplicate of this bug. *** *** Bug 204339 has been marked as a duplicate of this bug. *** If you can reproduce the crash at will, could you install the "kdeedu-dbg" package and generate a new backtrace to paste here ? Thanks *** Bug 205114 has been marked as a duplicate of this bug. *** From bug 213319: --- Thread 1 (Thread 0x7f64b22b5750 (LWP 3563)): [KCrash Handler] #5 QBasicAtomicInt::ref (this=0x10cbc60, other=...) at ../../include/QtCore/../../src/corelib/arch/qatomic_x86_64.h:121 #6 QString::operator= (this=0x10cbc60, other=...) at tools/qstring.cpp:1131 #7 0x00007f64923754d1 in Marble::WorldClock::init (this=0x10cbbe0) at ../../../../marble/src/plasmoid/worldclock.cpp:120 #8 0x00007f64a990515a in Plasma::Corona::loadLayout (this=0xd9b280, configName=<value optimized out>) at ../../plasma/corona.cpp:377 #9 0x00007f64a9906202 in Plasma::Corona::initializeLayout (this=0xd9b280, configName=...) at ../../plasma/corona.cpp:324 #10 0x00007f64a6181c66 in PlasmaApp::corona (this=0xc9b5e0) at ../../../../plasma/shells/desktop/plasmaapp.cpp:574 #11 0x00007f64a6181f38 in PlasmaApp::setupDesktop (this=0xc9b5e0) at ../../../../plasma/shells/desktop/plasmaapp.cpp:252 *** Bug 209362 has been marked as a duplicate of this bug. *** *** Bug 213319 has been marked as a duplicate of this bug. *** *** Bug 214036 has been marked as a duplicate of this bug. *** *** This bug has been marked as a duplicate of bug 225264 *** |