Bug 270444 - Plasma crashes when starting microblogging
Summary: Plasma crashes when starting microblogging
Status: RESOLVED DUPLICATE of bug 270327
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-08 16:01 UTC by Zachary Spector
Modified: 2011-04-09 13:57 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Zachary Spector 2011-04-08 16:01:12 UTC
Application: plasma-desktop (0.4)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-28-generic x86_64
Distribution: Ubuntu 10.10

-- Information about the crash:
- Custom settings of the application:

Plasma runs fine as long as I don't have the Microblogging widget configured; if I configure it with my Twitter login, and save that to Kwallet, then next time I log in, Plasma crashes. So it might actually be Kwallet and not the Microblogging widget that's causing trouble.

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma Desktop Shell (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f27cffd8780 (LWP 12279))]

Thread 3 (Thread 0x7f27b4111700 (LWP 12282)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f27b4110a70 in ?? ()
#2  0x00007fff373ff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 2 (Thread 0x7f27b09f7700 (LWP 12284)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007f27b09f6a70 in ?? ()
#2  0x00007fff373ff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7f27cffd8780 (LWP 12279)):
[KCrash Handler]
#6  QGraphicsItem::setVisible (this=0x74, visible=false) at graphicsview/qgraphicsitem.cpp:2411
#7  0x00007f27b4b806df in hide (this=0xe17ff0) at /usr/include/qt4/QtGui/qgraphicsitem.h:221
#8  MicroBlog::downloadHistory (this=0xe17ff0) at ../../../applets/microblog/microblog.cpp:839
#9  0x00007f27b4b82b40 in MicroBlog::configChanged (this=0xe17ff0) at ../../../applets/microblog/microblog.cpp:368
#10 0x00007f27b4b7d957 in MicroBlog::init (this=0xe17ff0) at ../../../applets/microblog/microblog.cpp:88
#11 0x00007f27cf4fecc0 in Plasma::ContainmentPrivate::initApplets (this=0xe05ea0) at ../../plasma/containment.cpp:463
#12 0x00007f27cf513c8c in Plasma::CoronaPrivate::importLayout (this=0x94dbb0, conf=<value optimized out>, mergeConfig=<value optimized out>) at ../../plasma/corona.cpp:566
#13 0x00007f27cf514793 in Plasma::Corona::loadLayout (this=0x885d90, configName=...) at ../../plasma/corona.cpp:494
#14 0x00007f27cf515283 in Plasma::Corona::initializeLayout (this=0x885d90, configName=...) at ../../plasma/corona.cpp:397
#15 0x00007f27cfced140 in PlasmaApp::corona (this=0x8721c0) at ../../../../plasma/desktop/shell/plasmaapp.cpp:797
#16 0x00007f27cfced49c in PlasmaApp::setupDesktop (this=0x8721c0) at ../../../../plasma/desktop/shell/plasmaapp.cpp:299
#17 0x00007f27cfcefe7c in PlasmaApp::qt_metacall (this=0x8721c0, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x93ca50) at ./plasmaapp.moc:155
#18 0x00007f27ccb32bde in QObject::event (this=0x8721c0, e=0x74) at kernel/qobject.cpp:1219
#19 0x00007f27cbe8b186 in QApplication::event (this=0x8721c0, e=0x93d2c0) at kernel/qapplication.cpp:2439
#20 0x00007f27cbe87fdc in QApplicationPrivate::notify_helper (this=0x8865c0, receiver=0x8721c0, e=0x93d2c0) at kernel/qapplication.cpp:4396
#21 0x00007f27cbe8daed in QApplication::notify (this=0x8721c0, receiver=0x8721c0, e=0x93d2c0) at kernel/qapplication.cpp:4277
#22 0x00007f27cd8272f6 in KApplication::notify (this=0x8721c0, receiver=0x8721c0, event=0x93d2c0) at ../../kdeui/kernel/kapplication.cpp:311
#23 0x00007f27ccb20cdc in QCoreApplication::notifyInternal (this=0x8721c0, receiver=0x8721c0, event=0x93d2c0) at kernel/qcoreapplication.cpp:732
#24 0x00007f27ccb23c22 in sendEvent (receiver=0x0, event_type=<value optimized out>, data=0x8377a0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#25 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0x8377a0) at kernel/qcoreapplication.cpp:1373
#26 0x00007f27ccb4d653 in sendPostedEvents (s=0x889180) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220
#27 postEventSourceDispatch (s=0x889180) at kernel/qeventdispatcher_glib.cpp:277
#28 0x00007f27c4681342 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#29 0x00007f27c46852a8 in ?? () from /lib/libglib-2.0.so.0
#30 0x00007f27c468545c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#31 0x00007f27ccb4d193 in QEventDispatcherGlib::processEvents (this=0x8372b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:415
#32 0x00007f27cbf3aa4e in QGuiEventDispatcherGlib::processEvents (this=0x74, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#33 0x00007f27ccb1fa02 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#34 0x00007f27ccb1fdec in QEventLoop::exec (this=0x7fff3736e0b0, flags=) at kernel/qeventloop.cpp:201
#35 0x00007f27ccb23ebb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#36 0x00007f27cfcd1fb3 in kdemain (argc=<value optimized out>, argv=<value optimized out>) at ../../../../plasma/desktop/shell/main.cpp:118
#37 0x00007f27cf92bd8e in __libc_start_main (main=<value optimized out>, argc=<value optimized out>, ubp_av=<value optimized out>, init=<value optimized out>, fini=<value optimized out>, rtld_fini=<value optimized out>, stack_end=0x7fff3736e488) at libc-start.c:226
#38 0x0000000000400669 in _start ()

This bug may be a duplicate of or related to bug 270327.

Possible duplicates by query: bug 270374, bug 270357, bug 270346, bug 270327.

Reported using DrKonqi
Comment 1 Dario Andres 2011-04-09 13:57:32 UTC
This issue is now being tracked at bug 270327. Merging. Thanks

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