Bug 272036 - plasma-desktop crash when changing resolution to multiple-monitors
Summary: plasma-desktop crash when changing resolution to multiple-monitors
Status: RESOLVED DUPLICATE of bug 249516
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-30 10:24 UTC by michael.przybilski
Modified: 2011-05-01 14:44 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 michael.przybilski 2011-04-30 10:24:13 UTC
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (wheezy)

-- Information about the crash:
xrandr --output LVDS1 --mode 1440x900 --output DP2 --left-of LVDS1 -
-mode 1920x1200

The crash can be reproduced every time.

 -- Backtrace:
Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f939a7d7780 (LWP 2706))]

Thread 2 (Thread 0x7f9376514700 (LWP 2709)):
#0  0x00007f93919804d9 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#1  0x00007f93967be682 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#2  0x00007f93967b2d78 in ?? () from /usr/lib/libQtCore.so.4
#3  0x00007f93967be035 in ?? () from /usr/lib/libQtCore.so.4
#4  0x00007f939197b8ba in start_thread () from /lib/libpthread.so.0
#5  0x00007f939a10102d in clone () from /lib/libc.so.6
#6  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f939a7d7780 (LWP 2706)):
[KCrash Handler]
#5  0x00007f93970a0ec0 in QWidget::mapToParent(QPoint const&) const () from /usr/lib/libQtGui.so.4
#6  0x00007f93970a0f0b in QWidget::mapTo(QWidget*, QPoint const&) const () from /usr/lib/libQtGui.so.4
#7  0x00007f9377dcfa19 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#8  0x00007f9377dcfdf8 in ?? () from /usr/lib/kde4/plasma_applet_systemtray.so
#9  0x00007f93968bc18f in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#10 0x00007f93968bad19 in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#11 0x00007f939705fd14 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#12 0x00007f93970648da in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#13 0x00007f93981e9bd6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x00007f93968a6c8c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#15 0x00007f93968d48ce in ?? () from /usr/lib/libQtCore.so.4
#16 0x00007f93968d1694 in ?? () from /usr/lib/libQtCore.so.4
#17 0x00007f938fb384a3 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#18 0x00007f938fb38c80 in ?? () from /lib/libglib-2.0.so.0
#19 0x00007f938fb38f1d in g_main_context_iteration () from /lib/libglib-2.0.so.0
#20 0x00007f93968d1d8f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#21 0x00007f93971064de in ?? () from /usr/lib/libQtGui.so.4
#22 0x00007f93968a6022 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x00007f93968a626c in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#24 0x00007f93968aa76b in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#25 0x00007f939a3cc78a in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_plasma-desktop.so
#26 0x00007f939a050c4d in __libc_start_main () from /lib/libc.so.6
#27 0x0000000000400699 in _start ()

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

Possible duplicates by query: bug 271915, bug 271887, bug 271667, bug 271646, bug 271636.

Reported using DrKonqi
Comment 1 Dario Andres 2011-05-01 14:44:06 UTC
[Comment from a bug triager]
The bug is fixed since KDE SC 4.6.0. The issue was being tracked at bug 249516, merging.
Thanks

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