Bug 227864 - kde panels froze while idle but running apps were fine
Summary: kde panels froze while idle but running apps were fine
Status: RESOLVED DUPLICATE of bug 283723
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-20 23:02 UTC by Peter Weber
Modified: 2011-10-17 13:44 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Weber 2010-02-20 23:02:03 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I was logged in normally with my usual compliment of apps running: konsole, firefox, thunderbird, google chrome, x-moto, and google gadgets (gtk).

I wasn't here when the freeze occurred - I was at the store and when I got back my panels were frozen for about 1.5 hours, judging by the (frozen) time on the Digital Clock panel item. Everything else (all the apps listed above) were still running just fine. I closed those manually (except for konsole) and then used xkill to kill the panels. My konsole window was still running on a solid black background so I decided to re-launch chrome and poke around online for an answer. After a while my kde environment started itself back up (with no attempts by me to relaunch) and I was presented with this window.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Aborted
[KCrash Handler]
#6  0x00580422 in __kernel_vsyscall ()
#7  0x003974d1 in raise () from /lib/tls/i686/cmov/libc.so.6
#8  0x0039a932 in abort () from /lib/tls/i686/cmov/libc.so.6
#9  0x00ce6f8c in qt_message_output (msgType=QtFatalMsg, 
    buf=0x9b7a9b0 "Fatal Error: Accessed global static 'DataEngineManagerSingleton *privateDataEngineManagerSelf()' after destruction. Defined at ../../plasma/dataenginemanager.cpp:79")
    at global/qglobal.cpp:2042
#10 0x00ce706e in qFatal (msg=0x193c3c8 "Fatal Error: Accessed global static '%s *%s()' after destruction. Defined at %s:%d") at global/qglobal.cpp:2241
#11 0x0182ef34 in operator-> () at ../../plasma/dataenginemanager.cpp:79
#12 Plasma::DataEngineManager::self () at ../../plasma/dataenginemanager.cpp:83
#13 0x04410b55 in ?? () from /usr/lib/kde4/plasma_engine_weather.so
#14 0x04410d46 in ?? () from /usr/lib/kde4/plasma_engine_weather.so
#15 0x0182eb54 in ~DataEngineManagerPrivate (this=0x907e268, __in_chrg=<value optimized out>) at ../../plasma/dataenginemanager.cpp:54
#16 ~DataEngineManager (this=0x907e268, __in_chrg=<value optimized out>) at ../../plasma/dataenginemanager.cpp:93
#17 0x0182ecea in ~DataEngineManagerSingleton () at ../../plasma/dataenginemanager.cpp:74
#18 destroy () at ../../plasma/dataenginemanager.cpp:79
#19 0x017ef58b in ~KCleanUpGlobalStatic (this=0x196d7f8, __in_chrg=<value optimized out>) at ../../kdecore/kernel/kglobal.h:62
#20 0x0039c05f in ?? () from /lib/tls/i686/cmov/libc.so.6
#21 0x0039c0cf in exit () from /lib/tls/i686/cmov/libc.so.6
#22 0x04fd0d8b in qt_xio_errhandler () at kernel/qapplication_x11.cpp:707
#23 0x010a654a in KApplication::xioErrhandler (this=0x8ba96b8, dpy=0x8bed320) at ../../kdeui/kernel/kapplication.cpp:408
#24 0x010a6586 in kde_xio_errhandler (dpy=0x8bed320) at ../../kdeui/kernel/kapplication.cpp:125
#25 0x001852e6 in _XIOError () from /usr/lib/libX11.so.6
#26 0x0018cf8a in ?? () from /usr/lib/libX11.so.6
#27 0x0018d8c6 in _XEventsQueued () from /usr/lib/libX11.so.6
#28 0x001765ff in XEventsQueued () from /usr/lib/libX11.so.6
#29 0x0500ee3e in x11EventSourcePrepare (s=0x8bd3100, timeout=0xbfbf12fc) at kernel/qguieventdispatcher_glib.cpp:79
#30 0x005bcf90 in g_main_context_prepare () from /lib/libglib-2.0.so.0
#31 0x005bd351 in ?? () from /lib/libglib-2.0.so.0
#32 0x005bd863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#33 0x00e0b02c in QEventDispatcherGlib::processEvents (this=0x8bd02f8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#34 0x0500ebe5 in QGuiEventDispatcherGlib::processEvents (this=0x8bd02f8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#35 0x00ddec79 in QEventLoop::processEvents (this=0xbfbf1514, flags=) at kernel/qeventloop.cpp:149
#36 0x00ddf0ca in QEventLoop::exec (this=0xbfbf1514, flags=...) at kernel/qeventloop.cpp:201
#37 0x00de153f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#38 0x04f6ddd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#39 0x01b7780d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#40 0x0804dde1 in launch (argc=<value optimized out>, _name=<value optimized out>, args=<value optimized out>, cwd=0x0, envc=0, envs=0x8b6f708 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x80511a5 "0") at ../../kinit/kinit.cpp:677
#41 0x0804ea35 in handle_launcher_request (sock=<value optimized out>, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#42 0x0804eeac in handle_requests (waitForPid=<value optimized out>) at ../../kinit/kinit.cpp:1362
#43 0x0804fbaf in main (argc=2, argv=0xbfbf1d74, envp=0xbfbf1d80) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2010-03-21 21:44:32 UTC
The backtrace is not really useful in this case. 
When applications hang, there is a procedure to know what is happening inside it and to try to determine the freeze cause.
If you experience another Plasma freeze you can:
- Start Konsole
- Run "pidof plasma-desktop" + Enter, save the number
- Run "gdb --pid NUMBER" + Enter
- When you get the prompt, write "thread apply all backtrace" a couple of times.
- Save the Konsole output and open a new bug report, pasting that GDB output.
(more information at http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_with_GDB)

Regards
Comment 2 Nicolas L. 2011-10-17 13:44:47 UTC

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