plasma continuously crashes after login in Kubuntu Karmic

Asked by triad on 2009-11-15

Binary package hint: kdebase-workspace-bin

Dear bugbusters

computor hardwarez: 2007 Toshiba Satellite A100
package: plasma desktop
release: Kubuntu 9.10
version:4.3.3

expected behaviour: plasma running smoothly
current behaviour:
plasma crashes moments after logging into the system

every attempt to restart using command plasma-desktop only starts it for brief moments before crashing again. no bug report is started. Only after repeatedly clicking on the desktop while trying to start it will it start the bug assistant.

a misconduct of the microblogging widget is suspected

please tell me how to get rid of the widget. I am as blind as a bat about unix and dont want to go back to windows. ever.

the report is this:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[KCrash Handler]
#6 0x02a57dad in QGraphicsItem::setFocus (this=0x2f006d, focusReason=Qt::OtherFocusReason) at graphicsview/qgraphicsitem.cpp:2146
#7 0x06cc9c9b in MicroBlog::focusInEvent (this=0x8b7bcd8, event=0xbfe192cc) at ../../../applets/microblog/microblog.cpp:157
#8 0x02a5d92a in QGraphicsItem::sceneEvent (this=0x8b7bce0, event=0xbfe192cc) at graphicsview/qgraphicsitem.cpp:4994
#9 0x02aaa9ef in QGraphicsWidget::sceneEvent (this=0x8b7bcd8, event=0xbfe192cc) at graphicsview/qgraphicswidget.cpp:1110
#10 0x02a7fe14 in QGraphicsScenePrivate::sendEvent (this=0x88b7b40, item=0x8b7bce0, event=0xbfe192cc) at graphicsview/qgraphicsscene.cpp:1159
#11 0x02a8082c in QGraphicsScene::setFocusItem (this=0x8971590, item=0x8b7bce0, focusReason=Qt::MouseFocusReason) at graphicsview/qgraphicsscene.cpp:3396
#12 0x02a8d2e3 in QGraphicsScenePrivate::mousePressEventHandler (this=0x88b7b40, mouseEvent=0xbfe19814) at graphicsview/qgraphicsscene.cpp:1271
#13 0x02a8dfa7 in QGraphicsScene::event (this=0x8971590, event=0xbfe19814) at graphicsview/qgraphicsscene.cpp:3805
#14 0x02451f54 in QApplicationPrivate::notify_helper (this=0x88ae5b0, receiver=0x8971590, e=0xbfe19814) at kernel/qapplication.cpp:4056
#15 0x0245967c in QApplication::notify (this=0x88a7310, receiver=0x8971590, e=0xbfe19814) at kernel/qapplication.cpp:3603
#16 0x010fc14a in KApplication::notify (this=0x88a7310, receiver=0x8971590, event=0xbfe19814) at ../../kdeui/kernel/kapplication.cpp:302
#17 0x04a6e6cb in QCoreApplication::notifyInternal (this=0x88a7310, receiver=0x8971590, event=0xbfe19814) at kernel/qcoreapplication.cpp:610
#18 0x02a9be49 in QCoreApplication::sendEvent (this=0x8b5d6f0, event=0xbfe19e30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#19 QGraphicsView::mousePressEvent (this=0x8b5d6f0, event=0xbfe19e30) at graphicsview/qgraphicsview.cpp:3212
#20 0x024a6ff6 in QWidget::event (this=0x8b5d6f0, event=0xbfe19e30) at kernel/qwidget.cpp:7545
#21 0x02856633 in QFrame::event (this=0x8b5d6f0, e=0xbfe19e30) at widgets/qframe.cpp:559
#22 0x028f5494 in QAbstractScrollArea::viewportEvent (this=0x2cc2868, e=0x26e9fffc) at widgets/qabstractscrollarea.cpp:962
#23 0x02a9f51f in QGraphicsView::viewportEvent (this=0x8b5d6f0, event=0xbfe19e30) at graphicsview/qgraphicsview.cpp:2919
#24 0x028f7a95 in QAbstractScrollAreaPrivate::viewportEvent (this=0x8b7bb98, o=0x8b7c7f8, e=0xbfe19e30) at widgets/qabstractscrollarea_p.h:100
#25 QAbstractScrollAreaFilter::eventFilter (this=0x8b7bb98, o=0x8b7c7f8, e=0xbfe19e30) at widgets/qabstractscrollarea_p.h:111
#26 0x04a6d83a in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=0x88ae5b0, receiver=0x8b7c7f8, event=0xbfe19e30) at kernel/qcoreapplication.cpp:726
#27 0x02451f2c in QApplicationPrivate::notify_helper (this=0x88ae5b0, receiver=0x8b7c7f8, e=0xbfe19e30) at kernel/qapplication.cpp:4052
#28 0x0245a033 in QApplication::notify (this=0x88a7310, receiver=0x8b7c7f8, e=0xbfe19e30) at kernel/qapplication.cpp:3758
#29 0x010fc14a in KApplication::notify (this=0x88a7310, receiver=0x8b7c7f8, event=0xbfe19e30) at ../../kdeui/kernel/kapplication.cpp:302
#30 0x04a6e6cb in QCoreApplication::notifyInternal (this=0x88a7310, receiver=0x8b7c7f8, event=0xbfe19e30) at kernel/qcoreapplication.cpp:610
#31 0x02458f6e in QCoreApplication::sendSpontaneousEvent (receiver=0x8b7c7f8, event=0xbfe19e30, alienWidget=0x8b7c7f8, nativeWidget=0x8b5d6f0, buttonDown=0x2cccaa0, lastMouseReceiver=...)
    at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:216
#32 QApplicationPrivate::sendMouseEvent (receiver=0x8b7c7f8, event=0xbfe19e30, alienWidget=0x8b7c7f8, nativeWidget=0x8b5d6f0, buttonDown=0x2cccaa0, lastMouseReceiver=...)
    at kernel/qapplication.cpp:2924
#33 0x024c77c0 in QETWidget::translateMouseEvent (this=0x8b5d6f0, event=0xbfe1b47c) at kernel/qapplication_x11.cpp:4409
#34 0x024c6c4b in QApplication::x11ProcessEvent (this=0x88a7310, event=0xbfe1b47c) at kernel/qapplication_x11.cpp:3428
#35 0x024f3502 in x11EventSourceDispatch (s=0x88b0db0, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#36 0x01578e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#37 0x0157c720 in ?? () from /lib/libglib-2.0.so.0
#38 0x0157c853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#39 0x04a9902c in QEventDispatcherGlib::processEvents (this=0x8891b68, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#40 0x024f2be5 in QGuiEventDispatcherGlib::processEvents (this=0x8891b68, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#41 0x04a6cc79 in QEventLoop::processEvents (this=0xbfe1b774, flags=) at kernel/qeventloop.cpp:149
#42 0x04a6d0ca in QEventLoop::exec (this=0xbfe1b774, flags=...) at kernel/qeventloop.cpp:201
#43 0x04a6f53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#44 0x02451dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#45 0x00c0780d in kdemain (argc=1, argv=0xbfe1b954) at ../../../../plasma/shells/desktop/main.cpp:50
#46 0x080485cb in main (argc=1, argv=0xbfe1b954) at plasma-desktop_dummy.cpp:3

thanks in advance

Question information

Language:
English Edit question
Status:
Answered
For:
Ubuntu kdebase-workspace Edit question
Assignee:
No assignee Edit question
Last query:
Last reply:

This question was originally filed as bug #483318.

This question was reopened

triad (milka) said : #1

can this be corrected? can I disable/uninstall the applet?

Jonathan Thomas (echidnaman) said : #2

You could try opening up ~/.kde/share/config/plasma-desktop-appletsrc, searching for "twitter", then deleting the whole block of text. Should look something like this (not exactly, though. yours will be different)

[Containments][1][Applets][43]
geometry=80,129,150,150
immutability=1
plugin=twitter
zvalue=-2

^Delete that whole section.

Jonathan Thomas (echidnaman) said : #3

Oh, to edit that file you can press Alt +F2, then run "kate ~/.kde/share/config/plasma-desktop-appletsrc"
Save, quit. Then press alt f2 again and run plasma-desktop

triad (milka) said : #4

Sorry Jonathan did not work at all.

the file you mention, when opened with kate is completely empty (?)

can I reinstall plasma somehow or revert to default???

PS i am getting used to kde without plasma by the way. its really smooth

triad (milka) said : #5

Sorry Jonathan did not work at all.

the file you mention, when opened with kate is completely empty (?)

can I reinstall plasma somehow or revert to default???

PS i am getting used to kde without plasma by the way. its really smooth

Vikram Dhillon (dhillon-v10) said : #6

Alright that's most likely because of a plasmoid. Try closing out any
plasmoid you have on and you should be fine.

Regards,
Vikram

On Mon, Nov 30, 2009 at 6:25 PM, triad
<email address hidden> wrote:
> Question #90383 on kdebase-workspace in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/kdebase-workspace/+question/90383
>
>    Status: Solved => Open
>
> triad is still having a problem:
> Sorry Jonathan did not work at all.
>
> the file you mention, when opened with kate is completely empty (?)
>
> can I reinstall plasma somehow or revert to default???
>
> PS i am getting used to kde without plasma by the way. its really smooth
>
> --
> You received this question notification because you are an answer
> contact for Ubuntu.
>

triad (milka) said : #7

Vikram, please provide more detailed process directions

Can I haz plazma noa plz?

Vikram Dhillon (dhillon-v10) said : #8

My apologies, I will agree that: "misconduct of the microblogging widget
is suspected" might be the case, the plasmoids that I referred are the
widgets, they cause the plasma to crash a lot. Now then, right click on
the menu bar at the bottom and then unlock widgets [1], then when you
hover you mouse over the widget you will see a little sidebar that has
an X to close that plasmoid. You shouldn't have more than 2 or 3
plasmoids on your desktop :) KDE is still in development but one day we
will rock the world with KDE

[1]
http://userbase.kde.org/images.userbase/6/65/Plasma_howto-widget-unlock.gif

--
Regards,
Vikram Dhillon

On Fri, 2009-12-04 at 20:29 +0000, triad wrote:
> Question #90383 on kdebase-workspace in ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/kdebase-workspace/+question/90383
>
> Status: Answered => Open
>
> triad is still having a problem:
> Vikram, please provide more detailed process directions
>
> Can I haz plazma noa plz?
>

Can you help with this problem?

Provide an answer of your own, or ask triad for more information if necessary.

To post a message you must log in.