Bug 232661 - Desktop panel crashed when tried to add one more panel
Summary: Desktop panel crashed when tried to add one more panel
Status: RESOLVED DUPLICATE of bug 201620
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-30 09:13 UTC by ShekarKCB
Modified: 2010-04-17 14:18 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ShekarKCB 2010-03-30 09:13:45 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.3.5 (KDE 4.3.5) "release 0"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.12-0.2-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
When the digital clock is removed from the panel (right click remove digital clock selected), and tried to add one more panel, current desktop panel crashed.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f9b04ff2750 (LWP 5092))]

Thread 2 (Thread 0x7f9aeab74910 (LWP 5093)):
#0  0x00007f9b047cd049 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f9b04a3d53b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007f9b00f0e9ec in ?? () from /usr/lib64/libQtNetwork.so.4
#3  0x00007f9b04a3c485 in ?? () from /usr/lib64/libQtCore.so.4
#4  0x00007f9b047c865d in start_thread () from /lib64/libpthread.so.0
#5  0x00007f9b021d3e1d in clone () from /lib64/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f9b04ff2750 (LWP 5092)):
[KCrash Handler]
#5  0x00007f9b0294b8c0 in QWidget::mapToParent(QPoint const&) const () from /usr/lib64/libQtGui.so.4
#6  0x00007f9b0294b91b in QWidget::mapTo(QWidget*, QPoint const&) const () from /usr/lib64/libQtGui.so.4
#7  0x00007f9aec266bf4 in Plasma::Theme::font(Plasma::Theme::FontRole) const () from /usr/lib64/kde4/plasma_applet_systemtray.so
#8  0x00007f9aec267228 in Plasma::Theme::font(Plasma::Theme::FontRole) const () from /usr/lib64/kde4/plasma_applet_systemtray.so
#9  0x00007f9b04b36fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007f9b04b30f63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#11 0x00007f9b0290a2ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f9b0291157e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007f9b03505016 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x00007f9b04b21ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#15 0x00007f9b04b4d71d in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007f9b04b4a678 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007f9b01853dee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#18 0x00007f9b018577b8 in ?? () from /usr/lib64/libglib-2.0.so.0
#19 0x00007f9b018578e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#20 0x00007f9b04b4a3a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x00007f9b0299d31e in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f9b04b20712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x00007f9b04b20ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007f9b04b22c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#25 0x00007f9af9f7ce3f in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so
#26 0x0000000000406f88 in _start ()

Reported using DrKonqi
Comment 1 ShekarKCB 2010-03-30 09:16:30 UTC
Changing the title to "When" instead of "What" that was a typo.
Comment 2 Jonathan Thomas 2010-04-17 14:18:02 UTC

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