Bug 211710 - Google Calendar (python widget) crashes Plasma [memcpy, QString::realloc ,QString::utf16, QString::toUcs4]
Summary: Google Calendar (python widget) crashes Plasma [memcpy, QString::realloc ,QSt...
Status: RESOLVED WORKSFORME
Alias: None
Product: bindings
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: kde-bindings
URL:
Keywords:
: 211903 213171 213483 213634 213714 213753 214734 216076 222660 225985 229637 232932 235281 242080 243175 244604 260765 269464 272547 332342 333641 337085 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-24 23:18 UTC by Stephen Fluin
Modified: 2018-11-30 03:46 UTC (History)
37 users (show)

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


Attachments
New crash information added by DrKonqi (14.11 KB, text/plain)
2010-05-16 12:01 UTC, Keiran Sparksman
Details
New crash information added by DrKonqi (12.21 KB, text/plain)
2010-07-19 04:33 UTC, Ryan
Details
New crash information added by DrKonqi (8.50 KB, text/plain)
2010-10-13 00:09 UTC, redmacg
Details
New crash information added by DrKonqi (13.14 KB, text/plain)
2010-12-10 18:00 UTC, Morten Sjoegren
Details
New crash information added by DrKonqi (13.04 KB, text/plain)
2011-09-11 15:13 UTC, akibukis
Details
new crash log as of Dec 2014 (12.66 KB, text/plain)
2014-12-17 14:39 UTC, Cezar "ikari" Pokorski
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Stephen Fluin 2009-10-24 23:18:09 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-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Whenever I try to login as a user with KDE since my updates this morning, I get this segfault.  Windows work fine, but no panels or plasmoids are loaded.  Even KWin compositing works just fine, as well as alt-tab and window borders.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  memcpy () at ../sysdeps/x86_64/memcpy.S:78
#6  0x00007f282d7e78fe in QString::realloc (this=0x37ec748, alloc=13) at /usr/include/bits/string3.h:52
#7  0x00007f282d7e7a29 in QString::utf16 (this=0x37ec748) at tools/qstring.cpp:4624
#8  0x00007f282d7e7b4c in QString::toUcs4 (this=0x37ec748) at tools/qstring.cpp:3423
#9  0x00007f280fdcbd50 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#10 0x00007f28102e0a3b in _PyObject_Str (v=0x322ce20) at ../Objects/object.c:425
#11 0x00007f28102e0b3a in PyObject_Str (v=0x394650a) at ../Objects/object.c:446
#12 0x00007f28102efab7 in string_new (type=<value optimized out>, args=<value optimized out>, kwds=<value optimized out>) at ../Objects/stringobject.c:4075
#13 0x00007f28102f69d3 in type_call (type=0x394650a, args=0x3292e10, kwds=0x0) at ../Objects/typeobject.c:731
#14 0x00007f281029be53 in PyObject_Call (func=0x7f281069a5e0, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#15 0x00007f281033cf97 in do_call (f=0x37e4440, throwflag=<value optimized out>) at ../Python/ceval.c:3924
#16 call_function (f=0x37e4440, throwflag=<value optimized out>) at ../Python/ceval.c:3729
#17 PyEval_EvalFrameEx (f=0x37e4440, throwflag=<value optimized out>) at ../Python/ceval.c:2389
#18 0x00007f281033f975 in PyEval_EvalCodeEx (co=0x3269378, globals=<value optimized out>, locals=<value optimized out>, args=0x1, argcount=<value optimized out>, kws=<value optimized out>, 
    kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:2968
#19 0x00007f28102c7e80 in function_call (func=0x3295d70, arg=0x2bcda10, kw=0x0) at ../Objects/funcobject.c:524
#20 0x00007f281029be53 in PyObject_Call (func=0x3295d70, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#21 0x00007f28102ac64f in instancemethod_call (func=0x3295d70, arg=0x2bcda10, kw=0x0) at ../Objects/classobject.c:2579
#22 0x00007f281029be53 in PyObject_Call (func=0x28068c0, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#23 0x00007f2810337e43 in PyEval_CallObjectWithKeywords (func=0x28068c0, arg=0x2788050, kw=0x1a) at ../Python/ceval.c:3575
#24 0x00007f280fa89678 in sip_api_invoke_slot () from /usr/lib/pymodules/python2.6/sip.so
#25 0x00007f280fdc7846 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#26 0x00007f280fdc795c in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#27 0x00007f280fdc7a1a in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#28 0x00007f282d89fddc in QMetaObject::activate (sender=0x32e2e40, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x39464e0) at kernel/qobject.cpp:3113
#29 0x00007f282c4f2a22 in KWallet::Wallet::walletOpened (this=0x394650a, _t1=true) at ./kwallet.moc:139
#30 0x00007f282c4f3940 in KWallet::Wallet::qt_metacall (this=0x32e2e40, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffffc9aad40) at ./kwallet.moc:99
#31 0x00007f282d89fddc in QMetaObject::activate (sender=0x331fc20, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x39464e0) at kernel/qobject.cpp:3113
#32 0x00007f282c5b508f in OrgKdeKWalletInterface::walletAsyncOpened (this=0x394650a, _t1=0, _t2=1717867238) at kwallet_interface.moc:300
#33 0x00007f282c5b5621 in OrgKdeKWalletInterface::qt_metacall (this=0x331fc20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7ffffc9abbc0) at kwallet_interface.moc:176
#34 0x00007f282990dad4 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
    at qdbusintegrator.cpp:891
#35 0x00007f2829914def in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib/libQtDBus.so.4
#36 0x00007f282d89a0f9 in QObject::event (this=0x331fc20, e=0x38ff660) at kernel/qobject.cpp:1111
#37 0x00007f282b83aefc in QApplicationPrivate::notify_helper (this=0x22dd750, receiver=0x331fc20, e=0x38ff660) at kernel/qapplication.cpp:4056
#38 0x00007f282b8421ce in QApplication::notify (this=0x22d45f0, receiver=0x331fc20, e=0x38ff660) at kernel/qapplication.cpp:4021
#39 0x00007f282c471ab6 in KApplication::notify (this=0x22d45f0, receiver=0x331fc20, event=0x38ff660) at ../../kdeui/kernel/kapplication.cpp:302
#40 0x00007f282d88ac2c in QCoreApplication::notifyInternal (this=0x22d45f0, receiver=0x331fc20, event=0x38ff660) at kernel/qcoreapplication.cpp:610
#41 0x00007f282d88b80a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x22414d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#42 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x22414d0) at kernel/qcoreapplication.cpp:1247
#43 0x00007f282d8b3533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#44 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#45 0x00007f282a76bbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#46 0x00007f282a76f588 in ?? () from /lib/libglib-2.0.so.0
#47 0x00007f282a76f6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#48 0x00007f282d8b31a6 in QEventDispatcherGlib::processEvents (this=0x2244040, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#49 0x00007f282b8cf4be in QGuiEventDispatcherGlib::processEvents (this=0x394650a, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#50 0x00007f282d889532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#51 0x00007f282d889904 in QEventLoop::exec (this=0x7ffffc9ac4b0, flags=) at kernel/qeventloop.cpp:201
#52 0x00007f282d88bab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#53 0x00007f2821b1f4cf in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#54 0x0000000000406da8 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a299 "0") at ../../kinit/kinit.cpp:677
#55 0x0000000000407aa0 in handle_launcher_request (sock=8, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#56 0x0000000000407f51 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1362
#57 0x0000000000408bb2 in main (argc=2, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1793

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-24 23:30:16 UTC
It could be an error in Python-Qt bindings.. - Does this started happening after an update ?
Thanks
Comment 2 Stephen Fluin 2009-10-25 03:58:23 UTC
Happened again.  It appears the environment starts coming up fine, but then a KWallet prompt pops up.  The crash appears to be right after I enter my password and hit enter.  My guess would be it has something to do with the google calendar plasmoid's interaction with kwallet. Still not great that a plasmoid can crash my entire plasma environment.

Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
The current source language is "auto; currently c".
[Current thread is 1 (Thread 0x7f9a2d953750 (LWP 7591))]

Thread 3 (Thread 0x7f9a078bf910 (LWP 7612)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1  0x00007f9a2d39a462 in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x268f660, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x268f660, time=30000) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f9a2d3904f2 in QThreadPoolThread::run (this=<value optimized out>) at concurrent/qthreadpool.cpp:140
#4  0x00007f9a2d399445 in QThreadPrivate::start (arg=0x244a940) at thread/qthread_unix.cpp:188
#5  0x00007f9a2a10fa04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007f9a2acef7bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f9a070be910 (LWP 7613)):
#0  pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_timedwait.S:220
#1  0x00007f9a2d39a462 in QWaitConditionPrivate::wait (this=<value optimized out>, mutex=0x268f660, time=30000) at thread/qwaitcondition_unix.cpp:85
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x268f660, time=30000) at thread/qwaitcondition_unix.cpp:159
#3  0x00007f9a2d3904f2 in QThreadPoolThread::run (this=<value optimized out>) at concurrent/qthreadpool.cpp:140
#4  0x00007f9a2d399445 in QThreadPrivate::start (arg=0x1f81be0) at thread/qthread_unix.cpp:188
#5  0x00007f9a2a10fa04 in start_thread (arg=<value optimized out>) at pthread_create.c:300
#6  0x00007f9a2acef7bd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()
The current source language is "auto; currently asm".

Thread 1 (Thread 0x7f9a2d953750 (LWP 7591)):
[KCrash Handler]
#5  memcpy () at ../sysdeps/x86_64/memcpy.S:78
#6  0x00007f9a2d3dc8fe in QString::realloc (this=0x260e1c8, alloc=13) at /usr/include/bits/string3.h:52
#7  0x00007f9a2d3dca29 in QString::utf16 (this=0x260e1c8) at tools/qstring.cpp:4624
#8  0x00007f9a2d3dcb4c in QString::toUcs4 (this=0x260e1c8) at tools/qstring.cpp:3423
#9  0x00007f9a0f9c0d50 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#10 0x00007f9a0fed5a3b in _PyObject_Str (v=0x1f59e20) at ../Objects/object.c:425
#11 0x00007f9a0fed5b3a in PyObject_Str (v=0x260e2ba) at ../Objects/object.c:446
#12 0x00007f9a0fee4ab7 in string_new (type=<value optimized out>, args=<value optimized out>, kwds=<value optimized out>) at ../Objects/stringobject.c:4075
#13 0x00007f9a0feeb9d3 in type_call (type=0x260e2ba, args=0x1fbfe10, kwds=0x0) at ../Objects/typeobject.c:731
#14 0x00007f9a0fe90e53 in PyObject_Call (func=0x7f9a1028f5e0, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#15 0x00007f9a0ff31f97 in do_call (f=0x258eca0, throwflag=<value optimized out>) at ../Python/ceval.c:3924
#16 call_function (f=0x258eca0, throwflag=<value optimized out>) at ../Python/ceval.c:3729
#17 PyEval_EvalFrameEx (f=0x258eca0, throwflag=<value optimized out>) at ../Python/ceval.c:2389
#18 0x00007f9a0ff34975 in PyEval_EvalCodeEx (co=0x1f96378, globals=<value optimized out>, locals=<value optimized out>, args=0x1, argcount=<value optimized out>, kws=<value optimized out>, 
    kwcount=0, defs=0x0, defcount=0, closure=0x0) at ../Python/ceval.c:2968
#19 0x00007f9a0febce80 in function_call (func=0x1fc2d70, arg=0x18fda10, kw=0x0) at ../Objects/funcobject.c:524
#20 0x00007f9a0fe90e53 in PyObject_Call (func=0x1fc2d70, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#21 0x00007f9a0fea164f in instancemethod_call (func=0x1fc2d70, arg=0x18fda10, kw=0x0) at ../Objects/classobject.c:2579
#22 0x00007f9a0fe90e53 in PyObject_Call (func=0x15338c0, arg=0x0, kw=0x1a) at ../Objects/abstract.c:2492
#23 0x00007f9a0ff2ce43 in PyEval_CallObjectWithKeywords (func=0x15338c0, arg=0x14b5050, kw=0x1a) at ../Python/ceval.c:3575
#24 0x00007f9a0f67e678 in sip_api_invoke_slot () from /usr/lib/pymodules/python2.6/sip.so
#25 0x00007f9a0f9bc846 in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#26 0x00007f9a0f9bc95c in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#27 0x00007f9a0f9bca1a in ?? () from /usr/lib/pymodules/python2.6/PyQt4/QtCore.so
#28 0x00007f9a2d494ddc in QMetaObject::activate (sender=0x202ad20, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x260e290) at kernel/qobject.cpp:3113
#29 0x00007f9a2c0e7a22 in KWallet::Wallet::walletOpened (this=0x260e2ba, _t1=true) at ./kwallet.moc:139
#30 0x00007f9a2c0e8940 in KWallet::Wallet::qt_metacall (this=0x202ad20, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6c2d9940) at ./kwallet.moc:99
#31 0x00007f9a2d494ddc in QMetaObject::activate (sender=0x2083030, from_signal_index=<value optimized out>, to_signal_index=<value optimized out>, argv=0x260e290) at kernel/qobject.cpp:3113
#32 0x00007f9a2c1aa08f in OrgKdeKWalletInterface::walletAsyncOpened (this=0x260e2ba, _t1=0, _t2=337781026) at kwallet_interface.moc:300
#33 0x00007f9a2c1aa621 in OrgKdeKWalletInterface::qt_metacall (this=0x2083030, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff6c2da7c0) at kwallet_interface.moc:176
#34 0x00007f9a29502ad4 in QDBusConnectionPrivate::deliverCall (this=<value optimized out>, object=<value optimized out>, msg=<value optimized out>, metaTypes=..., slotIdx=<value optimized out>)
    at qdbusintegrator.cpp:891
#35 0x00007f9a29509def in QDBusCallDeliveryEvent::placeMetaCall(QObject*) () from /usr/lib/libQtDBus.so.4
#36 0x00007f9a2d48f0f9 in QObject::event (this=0x2083030, e=0x26103e0) at kernel/qobject.cpp:1111
#37 0x00007f9a2b42fefc in QApplicationPrivate::notify_helper (this=0x100b750, receiver=0x2083030, e=0x26103e0) at kernel/qapplication.cpp:4056
#38 0x00007f9a2b4371ce in QApplication::notify (this=0x10025f0, receiver=0x2083030, e=0x26103e0) at kernel/qapplication.cpp:4021
#39 0x00007f9a2c066ab6 in KApplication::notify (this=0x10025f0, receiver=0x2083030, event=0x26103e0) at ../../kdeui/kernel/kapplication.cpp:302
#40 0x00007f9a2d47fc2c in QCoreApplication::notifyInternal (this=0x10025f0, receiver=0x2083030, event=0x26103e0) at kernel/qcoreapplication.cpp:610
#41 0x00007f9a2d48080a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xf6f4d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#42 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xf6f4d0) at kernel/qcoreapplication.cpp:1247
#43 0x00007f9a2d4a8533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#44 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#45 0x00007f9a2a360bbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#46 0x00007f9a2a364588 in ?? () from /lib/libglib-2.0.so.0
#47 0x00007f9a2a3646b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#48 0x00007f9a2d4a81a6 in QEventDispatcherGlib::processEvents (this=0xf72040, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#49 0x00007f9a2b4c44be in QGuiEventDispatcherGlib::processEvents (this=0x260e2ba, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#50 0x00007f9a2d47e532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#51 0x00007f9a2d47e904 in QEventLoop::exec (this=0x7fff6c2db0b0, flags=) at kernel/qeventloop.cpp:201
#52 0x00007f9a2d480ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#53 0x00007f9a217144cf in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#54 0x0000000000406da8 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a299 "0") at ../../kinit/kinit.cpp:677
#55 0x0000000000407aa0 in handle_launcher_request (sock=8, who=<value optimized out>) at ../../kinit/kinit.cpp:1169
#56 0x0000000000407f51 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1362
#57 0x0000000000408bb2 in main (argc=2, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1793
The current source language is "auto; currently c".
Comment 3 Dario Andres 2009-10-25 14:03:46 UTC
Yes, the backtrace mentions KWallet so it is probably related.
Comment 4 Beat Wolf 2009-10-25 15:18:11 UTC
perhaps it's related to the google calendar applet? assigning to ggadgets now
Comment 5 Beat Wolf 2009-10-25 17:16:23 UTC
after some feedback, this is probably not a ggadgets issue
Comment 6 Beat Wolf 2009-10-26 10:51:20 UTC
*** Bug 211903 has been marked as a duplicate of this bug. ***
Comment 7 Patrick Hoogkamer 2009-10-29 19:58:13 UTC
The bug was gone after  i turnd of google calendar.
when i turn  it on again the crash came back.
so i am not gone use google calendar for a wile.
Comment 8 Beat Wolf 2009-10-29 21:51:49 UTC
hm, so probably it is a google gadgets issue, even though the backtrace does not look like it..
Comment 9 David Palacio 2009-10-30 03:06:39 UTC
(In reply to comment #8)
> hm, so probably it is a google gadgets issue, even though the backtrace does
> not look like it..

That does not make sense. It must be this Python widget:
http://www.kde-look.org/content/show.php?content=104182
Comment 10 Dario Andres 2009-10-30 12:01:06 UTC
Then, this is:
1) an downstream issue (bug in the python widget "google calendar" code)
2) a kdebindings (python-qt/python-kde) issue.
Comment 11 Dario Andres 2009-11-09 23:06:24 UTC
*** Bug 213171 has been marked as a duplicate of this bug. ***
Comment 12 Dario Andres 2009-11-09 23:06:33 UTC
*** Bug 213634 has been marked as a duplicate of this bug. ***
Comment 13 Dario Andres 2009-11-09 23:06:38 UTC
*** Bug 213753 has been marked as a duplicate of this bug. ***
Comment 14 Dario Andres 2009-11-09 23:07:26 UTC
*** Bug 213483 has been marked as a duplicate of this bug. ***
Comment 15 Dario Andres 2009-11-09 23:43:53 UTC
*** Bug 213714 has been marked as a duplicate of this bug. ***
Comment 16 Dario Andres 2009-11-16 00:42:27 UTC
*** Bug 214734 has been marked as a duplicate of this bug. ***
Comment 17 Dario Andres 2009-11-25 13:35:51 UTC
*** Bug 216076 has been marked as a duplicate of this bug. ***
Comment 18 Dario Andres 2010-01-15 12:34:30 UTC
*** Bug 222660 has been marked as a duplicate of this bug. ***
Comment 19 Carlos Blanquer 2010-01-15 16:37:10 UTC
thanks a lot , let us see whether this gets fixed.
W7 is striking hard against LX

Carlos Blanquer Bogacz
_______________________________________
skype:   carlosblanquerbogacz
_______________________________________



2010/1/15 Dario Andres <andresbajotierra@gmail.com>

> https://bugs.kde.org/show_bug.cgi?id=211710
>
>
> Dario Andres <andresbajotierra@gmail.com> changed:
>
>           What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                 CC|                            |peyotll@gmail.com
>
>
>
>
> --- Comment #18 from Dario Andres <andresbajotierra gmail com>  2010-01-15
> 12:34:30 ---
> *** Bug 222660 has been marked as a duplicate of this bug. ***
>
> --
> Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You are on the CC list for the bug.
>
Comment 20 Dario Andres 2010-02-10 13:01:30 UTC
From bug 225985:
-- What I was doing when the application crashed:
I added the Google Calendar widget, supplied my credentials, then recieved an
error about cookies being disabled. I tried to click the [?] and plasma
completely crashed.
Comment 21 Dario Andres 2010-02-10 13:01:34 UTC
*** Bug 225985 has been marked as a duplicate of this bug. ***
Comment 22 Dario Andres 2010-03-17 18:04:51 UTC
*** Bug 229637 has been marked as a duplicate of this bug. ***
Comment 23 Dario Andres 2010-04-01 14:03:56 UTC
*** Bug 232932 has been marked as a duplicate of this bug. ***
Comment 24 Jonathan Thomas 2010-04-24 22:32:18 UTC
*** Bug 235281 has been marked as a duplicate of this bug. ***
Comment 25 Keiran Sparksman 2010-05-16 12:01:02 UTC
Created attachment 43626 [details]
New crash information added by DrKonqi

Added google calendar widget to Kubuntu 9.10 KDE4 desktop.
Comment 26 Beat Wolf 2010-06-18 16:12:30 UTC
*** Bug 242080 has been marked as a duplicate of this bug. ***
Comment 27 Beat Wolf 2010-06-30 00:08:05 UTC
*** Bug 243175 has been marked as a duplicate of this bug. ***
Comment 28 Beat Wolf 2010-07-15 15:37:46 UTC
*** Bug 244604 has been marked as a duplicate of this bug. ***
Comment 29 Ryan 2010-07-19 04:33:40 UTC
Created attachment 49299 [details]
New crash information added by DrKonqi

1. Added Google Calendar Plasma Widget to desktop.
2. Logged into Google account.
3. Plasma Desktop crashed.
4. Reboot.
5. Log into KDE.
6. Google Calendar Plamsa Widget loads and causes crash.
Comment 30 Antonio 2010-08-23 13:10:05 UTC
Still crashing all of Plasma in KDE 4.5.0, using Kubuntu 10.04.1.

This is with the official Ubuntu package "plasma-widget-googlecalendar" as well as with the version from Get Hot New Stuff (manual install). Still no luck.

Thanks for looking into it!

On a side note: In both cases, the "Add widgets" info says the plasmoid version is 1.0, but it should be 1.2. Probably an error in the metadata.desktop file.
Comment 31 redmacg 2010-10-13 00:09:00 UTC
Created attachment 52467 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.1 (KDE 4.5.1) using Qt 4.7.0

- What I was doing when the application crashe: 10.10 -- just updated from 10.04 and decided to add google widgets all in one panel: google calendar -- crash.

- Unusual behavior I noticed: Every time i log in to the system -- crash report, black screen

- Custom settings of the application:

-- Backtrace (Reduced):
#6  memcpy () at ../sysdeps/x86_64/memcpy.S:78
#7  0x00007f10a97723ac in QString::realloc (this=0x32026b8, alloc=7) at /usr/include/bits/string3.h:52
#8  0x00007f10a97724f9 in QString::utf16 (this=0x32026b8) at tools/qstring.cpp:4811
#9  0x00007f10a977259a in QString::toUcs4 (this=0x32026b8) at tools/qstring.cpp:3685
[...]
#11 0x00007f108cfb96ab in _PyObject_Str (v=0x422d668) at ../Objects/object.c:425
Comment 32 Morten Sjoegren 2010-12-10 18:00:22 UTC
Created attachment 54397 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.5.85 (4.6 Beta2) using Qt 4.7.0

- What I was doing when the application crashed:

1. Logged ind on my linux
2. Entered the password to kwallet for plasma, so it can login to my  google calendar.
3. Plasma crashes.

-- Backtrace (Reduced):
#6  memcpy () at ../sysdeps/x86_64/memcpy.S:78
#7  0x00007f64af7a73ac in QString::realloc (this=0x3a19d88, alloc=13) at /usr/include/bits/string3.h:52
#8  0x00007f64af7a74f9 in QString::utf16 (this=0x3a19d88) at tools/qstring.cpp:4811
#9  0x00007f64af7a759a in QString::toUcs4 (this=0x3a19d88) at tools/qstring.cpp:3685
[...]
#11 0x00007f648fdf76ab in _PyObject_Str (v=0x7f647f7bf520) at ../Objects/object.c:425
Comment 33 Beat Wolf 2010-12-21 11:52:08 UTC
*** Bug 260765 has been marked as a duplicate of this bug. ***
Comment 34 Dario Andres 2011-04-11 01:57:53 UTC
*** Bug 269464 has been marked as a duplicate of this bug. ***
Comment 35 Dario Andres 2011-05-08 22:29:22 UTC
[Comment from a bug triager]
From bug BUG (KDE SC 4.6.2):
-- Information about the crash:
Google Calendar widget crashes when entering the settings menu. I wasn't able
to login even once.
Comment 36 Dario Andres 2011-05-08 22:29:25 UTC
*** Bug 272547 has been marked as a duplicate of this bug. ***
Comment 37 akibukis 2011-09-11 15:13:21 UTC
Created attachment 63561 [details]
New crash information added by DrKonqi

plasma-desktop (0.4) on KDE Platform 4.6.2 (4.6.2) using Qt 4.7.2

- What I was doing when the application crashed:

When clicked on a configuration button, plasma-desktop chrashes immediatelly.

-- Backtrace (Reduced):
#6  memcpy () at ../sysdeps/x86_64/memcpy.S:117
#7  0x00007f2953aa28ec in QString::realloc (this=0x4039a28, alloc=8) at /usr/include/bits/string3.h:52
#8  0x00007f2953aa2ea9 in QString::utf16 (this=0x4039a28) at tools/qstring.cpp:4845
#9  0x00007f2953aa2ef4 in QString::toUcs4 (this=0x4039a28) at tools/qstring.cpp:3719
[...]
#11 0x00007f293a3e8477 in _PyObject_Str (v=<value optimized out>) at ../Objects/object.c:430
Comment 38 Christoph Feck 2014-03-26 21:29:29 UTC
*** Bug 332342 has been marked as a duplicate of this bug. ***
Comment 39 Christoph Feck 2014-04-20 09:00:56 UTC
*** Bug 333641 has been marked as a duplicate of this bug. ***
Comment 40 Christoph Feck 2014-07-04 17:13:09 UTC
*** Bug 337085 has been marked as a duplicate of this bug. ***
Comment 41 Michael Idowu 2014-07-04 22:38:11 UTC
Can I re-install the plasma-desktop to fix the issue? Or there is a work-around for this?
Comment 42 Tom 2014-10-10 19:00:58 UTC
@Michael what I did was:
cd ~/.kde/share/config
mkdir backup
mv plasma* backup/

and then restart.  seems to reset all the desktop settings so you can get back in.
Comment 43 Cezar "ikari" Pokorski 2014-12-17 14:28:52 UTC
I have the same issue. Opening config crashed plasma and made it crash forever on start.

Had to open `~/.kde/share/config/plasma-desktop-appletsrc` and remove the entry (paragraph) with `plugin=gcal`. Anybody still needs a stack trace? (pretty much identical). Nice to permacrash the whole desktop on a 5-year-old bug.
Comment 44 Cezar "ikari" Pokorski 2014-12-17 14:39:14 UTC
Created attachment 90011 [details]
new crash log as of Dec 2014
Comment 45 Andrew Crouthamel 2018-10-31 04:03:59 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 46 Bug Janitor Service 2018-11-15 10:32:15 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 47 Bug Janitor Service 2018-11-30 03:46:21 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!