[Bug 192568] New: plasma-desktop crashs when shutdown or call "kquitapp plasma-desktop"
Felix Lemke
hobbyblobby at arcor.de
Wed May 13 13:44:10 BST 2009
https://bugs.kde.org/show_bug.cgi?id=192568
Summary: plasma-desktop crashs when shutdown or call "kquitapp
plasma-desktop"
Product: kde
Version: unspecified
Platform: Unlisted Binaries
OS/Version: Linux
Status: UNCONFIRMED
Severity: crash
Priority: NOR
Component: general
AssignedTo: unassigned-bugs at kde.org
ReportedBy: hobbyblobby at arcor.de
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1)) "release 3.2"
Qt Version: 4.5.1
Operating System: Linux 2.6.27.4 i686
-- Backtrace:
Application: Plasma-Arbeitsfläche (plasma-desktop), signal: Aborted
[KCrash Handler]
#6 0xffffe424 in __kernel_vsyscall ()
#7 0xb622e900 in raise () from /lib/libc.so.6
#8 0xb6230238 in abort () from /lib/libc.so.6
#9 0xb64c9365 in qt_message_output (msgType=QtFatalMsg,
buf=0x87374f0 "Fatal Error: Accessed global static
'DataEngineManagerSingleton *privateDataEngineManagerSelf()' after destruction.
Defined at
/usr/src/packages/BUILD/kdelibs-4.2.85/plasma/dataenginemanager.cpp:79") at
global/qglobal.cpp:2017
#10 0xb64c9451 in qFatal (msg=0xb7f2728c "Fatal Error: Accessed global static
'%s *%s()' after destruction. Defined at %s:%d") at global/qglobal.cpp:2216
#11 0xb7e1bfb3 in Plasma::DataEngineManager::self () from
/usr/lib/libplasma.so.3
#12 0xa7b8f466 in WeatherEngine::~WeatherEngine () from
/usr/lib/kde4/plasma_engine_weather.so
#13 0xb7e1ac5f in Plasma::DataEngineManager::~DataEngineManager () from
/usr/lib/libplasma.so.3
#14 0xb7e1adfa in Plasma::._173::destroy () from /usr/lib/libplasma.so.3
#15 0xb7de07bb in KCleanUpGlobalStatic::~KCleanUpGlobalStatic () from
/usr/lib/libplasma.so.3
#16 0xb62318f1 in exit () from /lib/libc.so.6
#17 0xb621a5fd in __libc_start_main () from /lib/libc.so.6
#18 0x08048681 in _start ()
--
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list