Bug 256203 - Control bar crashed
Summary: Control bar crashed
Status: RESOLVED DUPLICATE of bug 256087
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-systemtray (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-11-06 01:03 UTC by Jens Mander
Modified: 2010-11-06 14:58 UTC (History)
2 users (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 Jens Mander 2010-11-06 01:03:40 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.5.3 (KDE 4.5.3) "release 8"
Qt Version: 4.6.3
Operating System: Linux 2.6.34.7-0.5-default i686
Distribution: "openSUSE 11.3 (i586)"

-- Information about the crash:
I upgraded to KDE 4.5.3    btw: it was not the best idea

Now the Control bar crashes once in a while.
- No K-Menu
- No systray
- no prog-switch
- no other widgets......

ALT-F2 works.

The other annoyence:
- the windows just have no "minimize" "maximize" "close" buttons

The crash can be reproduced every time.

-- Backtrace:
Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#7  QWidget::mapToParent (this=0x0, pos=...) at kernel/qwidget.cpp:4021
#8  0xb63a1e74 in QWidget::mapTo (this=0x8cfeef8, parent=0x8352b98, pos=...) at kernel/qwidget.cpp:3977
#9  0xaaf4cd4e in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#10 0xaaf4d19e in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#11 0xb6e27efd in QMetaObject::metacall (object=0x8597870, cl=QMetaObject::InvokeMetaMethod, idx=4, argv=0xbf842ccc) at kernel/qmetaobject.cpp:237
#12 0xb6e36fe8 in QMetaObject::activate (sender=0x876c934, m=0xb6f3e5a4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3295
#13 0xb6e83a35 in QTimer::timeout (this=0x876c934) at .moc/release-shared/moc_qtimer.cpp:134
#14 0xb6e3c8e6 in QTimer::timerEvent (this=0x876c934, e=0xbf843200) at kernel/qtimer.cpp:271
#15 0xb6e34774 in QObject::event (this=0x876c934, e=0xbf843200) at kernel/qobject.cpp:1212
#16 0xb635ac64 in QApplicationPrivate::notify_helper (this=0x80a90e0, receiver=0x876c934, e=0xbf843200) at kernel/qapplication.cpp:4302
#17 0xb6362bf7 in QApplication::notify (this=0x80a09b0, receiver=0x876c934, e=0xbf843200) at kernel/qapplication.cpp:3706
#18 0xb743f941 in KApplication::notify (this=0x80a09b0, receiver=0x876c934, event=0xbf843200) at /usr/src/debug/kdelibs-4.5.3/kdeui/kernel/kapplication.cpp:310
#19 0xb6e21e0e in QCoreApplication::notifyInternal (this=0x80a09b0, receiver=0x876c934, event=0xbf843200) at kernel/qcoreapplication.cpp:726
#20 0xb6e5070e in sendEvent (this=0x80ac234) at kernel/qcoreapplication.h:215
#21 QTimerInfoList::activateTimers (this=0x80ac234) at kernel/qeventdispatcher_unix.cpp:618
#22 0xb6e4d642 in timerSourceDispatch (source=0x80ac200) at kernel/qeventdispatcher_glib.cpp:184
#23 0xb5ba8b49 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5ba9350 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5ba960e in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb6e4dd4b in QEventDispatcherGlib::processEvents (this=0x80a8e20, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#27 0xb640b19a in QGuiEventDispatcherGlib::processEvents (this=0x80a8e20, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb6e2111d in QEventLoop::processEvents (this=0xbf8434c4, flags=...) at kernel/qeventloop.cpp:149
#29 0xb6e21319 in QEventLoop::exec (this=0xbf8434c4, flags=...) at kernel/qeventloop.cpp:201
#30 0xb6e25c70 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#31 0xb6358164 in QApplication::exec () at kernel/qapplication.cpp:3581
#32 0xb2d3562a in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#33 0x0804e3f1 in _start ()

Possible duplicates by query: bug 256087, bug 252823, bug 252125, bug 249516, bug 245892.

Reported using DrKonqi
Comment 1 Aaron J. Seigo 2010-11-06 01:42:22 UTC
sounds like a catastrophic failure during upgrade, e.g. the upgrade didn't complete, some packages weren't updated as they should have been, etc. all the symptoms you describe come down to "incompatible libraries and plugins". can you double check that the upgrade process completed successfully?
Comment 2 Beat Wolf 2010-11-06 14:58:01 UTC
as mentioned, try to reinstall your kde and contact the support of you distribution. this is most probably a distribution problem and not a kde bug.

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