Bug 206957 - google gadget support: plasma crashes after login
Summary: google gadget support: plasma crashes after login
Status: RESOLVED DUPLICATE of bug 197754
Alias: None
Product: plasma4
Classification: Plasma
Component: scriptengines (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 12:28 UTC by Jay Ambee
Modified: 2009-09-17 00:31 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kacrash-report I get when plasma crashes ... (4.28 KB, text/plain)
2009-09-10 12:29 UTC, Jay Ambee
Details
kcrash-report of plasma crash with debuginfo but without reboot (3.94 KB, text/plain)
2009-09-10 13:01 UTC, Jay Ambee
Details
kcrash-report of plasma crash with debuginfo after reboot (3.94 KB, text/plain)
2009-09-10 13:02 UTC, Jay Ambee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jay Ambee 2009-09-10 12:28:49 UTC
Version:           OpenSuse 11.1 (i586), KDE 4.3.1 (KDE 4.3.1) "release 163" (using KDE 4.3.1)
OS:                Linux
Installed from:    SuSE RPMs

After todays update of some packages from OpenSuse 11.1 to my KDE 4.3.1 (V163) system, plasma crashes each time directly after logging into my User Account (root still works, though). All attempts to restart plasma-desktop via krunner (which still works) fail and produce crashes with kcrash-report which I add.

I hope this is helpfull, since I don't have enough room for devel-packages on my laptop.
Since I can't access some of my important work-files now, I would be gratefull for al fast solution ...

Thanks a lot, Jay
Comment 1 Jay Ambee 2009-09-10 12:29:26 UTC
Created attachment 36837 [details]
kacrash-report I get when plasma crashes ...
Comment 2 Will Stephenson 2009-09-10 12:36:57 UTC
It would help if you installed kdebase4-workspace-debuginfo (145Mb too much for your laptop) and repeated the crash.


To get your desktop back in a hurry, outside KDE:

mv ~/.kde4/share/config/plasma-desktop-appletsrc  ~/.kde4/share/config/plasma-desktop-appletsrc.bad
mv ~/.kde4/share/config/plasma-desktoprc  ~/.kde4/share/config/plasma-desktoprc.bad

should get you a vanilla Plasma back. Then don't add the google gadget causing the crash.
Comment 3 Jay Ambee 2009-09-10 13:00:03 UTC
okay, I have, at least temporarily added the debuginfo-package and tried to relogin to my user account 2 two times (one without and second after a restart) and will add both kcrash-reports here. Hope they will help fixing the bug.

hope I can't reproduce the crash then, after changing the config-file ... 

Thanky for your help, Jay
Comment 4 Jay Ambee 2009-09-10 13:01:40 UTC
Created attachment 36838 [details]
kcrash-report of plasma crash with debuginfo but without reboot
Comment 5 Jay Ambee 2009-09-10 13:02:23 UTC
Created attachment 36839 [details]
kcrash-report of plasma crash with debuginfo after reboot
Comment 6 Jay Ambee 2009-09-12 11:37:30 UTC
Okay ... to get back my plasma desktop working this was okay, but now there is a follow-up to this ...

since yesterday, without any special changes (no new istallations or else) xorg and plasma started to eat up constantly at least 70% (or more) of the cpu-time. this is very annoying, since it slows down my system significantly (single core pentium-m cpu 1.7 GHz) and also leaves the fans running like mad.

And still: this only seems to happen under my user account, root still seems to be okay ... and it remains althoug there are no mor plasmoids, except trashbin and compositing is turned off!!
Hardware: dell inspiron 9200, ati 9700, 

sorry, but this is not really funny ...

Thanks for your help, jay
Comment 7 Dario Andres 2009-09-17 00:28:53 UTC
Pasted backtrace:
---------

Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0xb5e17700 (LWP 10374))]

Thread 2 (Thread 0xa87efb90 (LWP 10381)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb7ca0c35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb7d00592 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb7572ef2 in ?? () from /usr/lib/libQtNetwork.so.4
#4  0xb7cff582 in ?? () from /usr/lib/libQtCore.so.4
#5  0xb7c9d1b5 in start_thread () from /lib/libpthread.so.0
#6  0xb64df3be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb5e17700 (LWP 10374)):
[KCrash Handler]
#6  0xa7a512fb in ggadget::smjs::JSScriptContext::MaybeGC(JSContext*) () from /usr/lib/google-gadgets/modules/smjs-script-runtime.so
#7  0xa7a4e5fe in ggadget::smjs::JSFunctionSlot::Call(ggadget::ScriptableInterface*, int, ggadget::Variant const*) const () from /usr/lib/google-gadgets/modules/smjs-script-runtime.so
#8  0xa8b72c24 in ggadget::Signal::Emit(int, ggadget::Variant const*) const () from /usr/lib/libggadget-1.0.so.0
#9  0xa8b5acba in ggadget::SignalSlot::Call(ggadget::ScriptableInterface*, int, ggadget::Variant const*) const () from /usr/lib/libggadget-1.0.so.0
#10 0xa8b9c8ba in ggadget::View::Impl::FireEvent(ggadget::ScriptableEvent*, ggadget::Signal0<void> const&) () from /usr/lib/libggadget-1.0.so.0
#11 0xa8b983b3 in ggadget::View::OnOtherEvent(ggadget::Event const&) () from /usr/lib/libggadget-1.0.so.0
#12 0xa8b65558 in ggadget::ScriptableView::Impl::InitFromXML(std::string const&, char const*) () from /usr/lib/libggadget-1.0.so.0
#13 0xa8b618be in ggadget::ScriptableView::InitFromXML(std::string const&, char const*) () from /usr/lib/libggadget-1.0.so.0
#14 0xa8afe2c6 in ggadget::Gadget::Impl::Initialize() () from /usr/lib/libggadget-1.0.so.0
#15 0xa8af2bdf in ggadget::Gadget::Gadget(ggadget::HostInterface*, char const*, char const*, int, ggadget::Permissions const&, ggadget::Gadget::DebugConsoleConfig) ()
   from /usr/lib/libggadget-1.0.so.0
#16 0xa8ee981f in ?? () from /usr/lib/kde4/plasma_scriptengine_ggl.so
#17 0xa8ee85e0 in ?? () from /usr/lib/kde4/plasma_scriptengine_ggl.so
#18 0xa8ee87cd in ?? () from /usr/lib/kde4/plasma_scriptengine_ggl.so
#19 0xb7e08f78 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#20 0xb7e09c02 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#21 0xb7e0eda7 in ?? () from /usr/lib/libQtCore.so.4
#22 0xb7e0eecc in ?? () from /usr/lib/libQtCore.so.4
#23 0xb7e03f1f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#24 0xb67b67fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#25 0xb67beaee in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#26 0xb72ab72d in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#27 0xb7df38eb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#28 0xb7e22f36 in ?? () from /usr/lib/libQtCore.so.4
#29 0xb7e1f1a0 in ?? () from /usr/lib/libQtCore.so.4
#30 0xb635c9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#31 0xb6360083 in ?? () from /usr/lib/libglib-2.0.so.0
#32 0xb6360241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#33 0xb7e1f0f8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#34 0xb6856d55 in ?? () from /usr/lib/libQtGui.so.4
#35 0xb7df1f0a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#36 0xb7df2352 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0xb7df47f9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#38 0xb67b6677 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#39 0xb4833b90 in kdemain (argc=1, argv=0x808eb90) at /usr/src/debug/kdebase-workspace-4.3.1/plasma/shells/desktop/main.cpp:50
#40 0x0804e505 in _start ()
Comment 8 Dario Andres 2009-09-17 00:31:05 UTC
@Jay: about the Plasma CPU usage, what are the settings of your System Tray widget ?
BTW, the GoogleGadgets crash is reported at bug 197754. Merging.
Thanks

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