Bug 195206 - Adding a panel to Plasma / setting up a new screen causes crash [QWidget::mapToParent, QWidget::mapTo, SystemTray::X11EmbedPainter::performUpdates]
Summary: Adding a panel to Plasma / setting up a new screen causes crash [QWidget::map...
Status: RESOLVED INTENTIONAL
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 208193 211624 211790 211899 213604 213813 214398 216344 221323 222862 225079 226365 227152 229974 230167 231882 231988 232559 233514 233967 233973 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-06-04 14:50 UTC by Gregor Petrin
Modified: 2010-08-14 03:54 UTC (History)
25 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
New crash information added by DrKonqi (5.00 KB, text/plain)
2010-08-14 03:54 UTC, Kenneth Lakin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Gregor Petrin 2009-06-04 14:50:41 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527)) "release 135"
Qt Version: 4.5.1
Operating System: Linux 2.6.27.21-0.1-default i686

What I was doing when the application crashed:
When adding a new panel to plasma, the action caused a crash - I was taken into the Crash Reporting Assistant and no panel was added. I have no other panels on my desktop (the one I was trying to add would be the first).

 -- Backtrace:
Application: Plasma Workspace (kdeinit), signal: Segmentation fault
[KCrash Handler]
#6  0xb6823236 in QWidget::mapToParent(QPoint const&) const () from /usr/lib/libQtGui.so.4
#7  0xb68232b3 in QWidget::mapTo(QWidget*, QPoint const&) const () from /usr/lib/libQtGui.so.4
#8  0xa912d77e in SystemTray::X11EmbedPainter::performUpdates (this=0x82050c0) at /usr/src/debug/kdebase-workspace-4.2.88svn973768/plasma/applets/systemtray/protocols/fdo/x11embedpainter.cpp:128
#9  0xa912dd2b in SystemTray::X11EmbedPainter::qt_metacall (this=0x82050c0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbf86d358)
    at /usr/src/debug/kdebase-workspace-4.2.88svn973768/build/plasma/applets/systemtray/x11embedpainter.moc:69
#10 0xb7e51dc8 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb7e53552 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0xb7e8dbd7 in QTimer::timeout() () from /usr/lib/libQtCore.so.4
#13 0xb7e5788e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb7e4c26f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#15 0xb67db69c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb67e399e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb72f9b9d in KApplication::notify (this=0x80a5d38, receiver=0x8210554, event=0xbf86d800) at /usr/src/debug/kdelibs-4.2.88svn973768/kdeui/kernel/kapplication.cpp:302
#18 0xb7e3badb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0xb7e6b176 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb7e67600 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb63819c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb6385083 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb6385241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7e67558 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb687b975 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb7e3a0fa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb7e3a53a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb7e3c9e9 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#29 0xb67db517 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#30 0xb487b760 in kdemain (argc=1, argv=0x808e0b0) at /usr/src/debug/kdebase-workspace-4.2.88svn973768/plasma/shells/desktop/main.cpp:50
#31 0x0804e2b0 in launch (argc=1, _name=0x808dbcc "/usr/bin/plasma-desktop", args=0x808dbe4 "", cwd=0x0, envc=0, envs=0x808dbe8 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051390 "0") at /usr/src/debug/kdelibs-4.2.88svn973768/kinit/kinit.cpp:671
#32 0x0804ea8d in handle_launcher_request (sock=7, who=<value optimized out>) at /usr/src/debug/kdelibs-4.2.88svn973768/kinit/kinit.cpp:1163
#33 0x0804ef23 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.2.88svn973768/kinit/kinit.cpp:1356
#34 0x0804fbca in main (argc=2, argv=0xbf86e234, envp=0xbf86e240) at /usr/src/debug/kdelibs-4.2.88svn973768/kinit/kinit.cpp:1783

Reported using DrKonqi
Comment 1 Dario Andres 2009-06-04 15:00:23 UTC
Looks related to bug 179156, but that bug should be fixed by now.
Thanks
Comment 2 Gregor Petrin 2009-06-05 10:22:12 UTC
The bug report you referenced had to do with the system tray - I had a System Tray plasmoid on my desktop, after removing it, I can now add a panel without plasma crashing.

I have another problem with the panel now, though - the panel is added but it keeps resizing, slowing my system down to a crawl. If I right-click on the panel, after about half a minute I get the dialog menu, where I can click 'remove panel' and then after another minute I get a dialog window where I confirm that I do indeed want to remove the panel, which is then removed after another minute. It looks as though the panel was being very rapidly switched between a 'maxsimized' and 'normal' states. It completely blocks my UI until I remove the panel. I tried searching for the bug but couldn't find it - there were just too many matching bugs returned for my keywords. Any clue if this behaviour has been seen before, so I don't duplicate a known bug report? I'm using SuSE's Factory repositories, if that provides any clues (I noticed this info was not provided by the automatical bug reporting tool).

Thanks for the reply!
Comment 3 Dario Andres 2009-06-08 00:29:35 UTC
Could you please file a new bug report regarding the last isssue you described? (the policy here is "one report per issue").

If you confirm that the crash is no longer reproducible, the issue could be marked as WORKSFORME.

Thanks
Comment 4 Gregor Petrin 2009-06-08 09:45:04 UTC
I will report the other bug in a separate report - I will try to get a screenshot or something first, though it's not simple as my UI almost locks up when it happens and the response times keep getting longer until I am forced to reboot the computer.

As for this bug, it does not appear to be so simple. When I reboot the system, it appears not to happen (I get the other bug, which I still have to file), but after some time it starts happening again.

If somebody else could just try repeating these steps and see if it works for them:
 - remove all panels from plasma
 - add a 'system tray' plasmoid to the desktop
 - add a new panel (plasma sometimes crashes)

If nobody else can reproduce my bug this way, then we can write it down to some quirk of my computer :)
Comment 5 Shawn Starr 2009-06-22 06:39:52 UTC
Cannot reproduce with KDE 4.3 beta 2+
Comment 6 Dario Andres 2009-07-18 21:03:16 UTC
@Gregor: can you try with an updated KDE version? (4.3rc2) Thanks
Comment 7 Gregor Petrin 2009-07-19 13:12:19 UTC
I tried it a couple of times with the latest KDE version in the SUSE repositories, 4.3.60 "release 1" and all went well.

I will try it on my work laptop as soon as possible and post the results of that test as well.
Comment 8 Gregor Petrin 2009-07-21 12:44:47 UTC
Hi,

I tried it on my work laptop with RC2 and the problem repeated itself. The command 'plasma-desktop --version' gives me this:

Qt: 4.5.2
KDE: 4.2.96 (KDE 4.2.96 (KDE 4.3 RC2)) "release 142"
Plasma Workspace: 0.3


Here is the trace:

Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb6854366 in QWidget::mapToParent(QPoint const&) const () from /usr/lib/libQtGui.so.4
#7  0xb68543e3 in QWidget::mapTo(QWidget*, QPoint const&) const () from /usr/lib/libQtGui.so.4
#8  0xa93058ee in SystemTray::X11EmbedPainter::performUpdates (this=0x825c4d0) at /usr/src/debug/kdebase-workspace-4.2.96/plasma/applets/systemtray/protocols/fdo/x11embedpainter.cpp:128
#9  0xa9305e9b in SystemTray::X11EmbedPainter::qt_metacall (this=0x825c4d0, _c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbfc74f68)
    at /usr/src/debug/kdebase-workspace-4.2.96/build/plasma/applets/systemtray/x11embedpainter.moc:69
#10 0xb7e58788 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb7e59412 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0xb7e94fe7 in QTimer::timeout() () from /usr/lib/libQtCore.so.4
#13 0xb7e5ec0e in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4
#14 0xb7e5372f in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#15 0xb680c7fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#16 0xb6814aee in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#17 0xb730019d in KApplication::notify (this=0x80a42a0, receiver=0x83de674, event=0xbfc75410) at /usr/src/debug/kdelibs-4.2.96/kdeui/kernel/kapplication.cpp:302
#18 0xb7e4316b in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#19 0xb7e725f6 in ?? () from /usr/lib/libQtCore.so.4
#20 0xb7e6e980 in ?? () from /usr/lib/libQtCore.so.4
#21 0xb63b29c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb63b6083 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0xb63b6241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#24 0xb7e6e8d8 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#25 0xb68accc5 in ?? () from /usr/lib/libQtGui.so.4
#26 0xb7e4178a in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#27 0xb7e41bd2 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#28 0xb7e44079 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#29 0xb680c677 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#30 0xb489d9f0 in kdemain (argc=1, argv=0x808ca78) at /usr/src/debug/kdebase-workspace-4.2.96/plasma/shells/desktop/main.cpp:50
#31 0x0804e36d in launch (argc=1, _name=0x808c774 "/usr/bin/plasma-desktop", args=0x808c78c "", cwd=0x0, envc=0, envs=0x808c790 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x8051449 "0") at /usr/src/debug/kdelibs-4.2.96/kinit/kinit.cpp:676
#32 0x0804eb4d in handle_launcher_request (sock=7, who=<value optimized out>) at /usr/src/debug/kdelibs-4.2.96/kinit/kinit.cpp:1168
#33 0x0804efe3 in handle_requests (waitForPid=0) at /usr/src/debug/kdelibs-4.2.96/kinit/kinit.cpp:1361
#34 0x0804fc8a in main (argc=2, argv=0xbfc75e44, envp=0xbfc75e50) at /usr/src/debug/kdelibs-4.2.96/kinit/kinit.cpp:1788
Comment 9 Dario Andres 2009-07-21 16:01:36 UTC
What system-tray applications do you have ?
Comment 10 Gregor Petrin 2009-07-22 09:08:03 UTC
I have:
- KMix (3.5)
- KNetworkManager (0.7)
- kmail (1.12.0)
- kopete (0.70.90)
- kupdateapplet (0.8.42)
Comment 11 Dario Andres 2009-07-22 16:23:56 UTC
If you quit/close all this applications and you try to reproduce the bug. Does the plasma crash happens again ?
Thanks
Comment 12 Gregor Petrin 2009-07-22 18:52:28 UTC
Hi,

I actually wanted to do this myself, but things were (still are :)) quite hectic at work, so I didn't get around to it.. sorry.

I closed all the system tray apps and the crash did not happen. Then I added them one by one and after I added KNetworkManager, the crashes started happening. I closed everything else and only left KNetworkManager running - the crashes continued. So I suppose KNetworkManager is the culprit. Do you need a stack trace of the crash with only KNetworkManager in the system tray?
Comment 13 Dario Andres 2009-07-22 18:54:24 UTC
Nice discovery.
I guess the backtrace should be the same so a new one is not needed. Thanks
Comment 14 Aaron J. Seigo 2009-09-22 19:23:52 UTC
*** Bug 208193 has been marked as a duplicate of this bug. ***
Comment 15 Dario Andres 2009-10-24 23:52:48 UTC
*** Bug 211624 has been marked as a duplicate of this bug. ***
Comment 16 Dario Andres 2009-10-25 21:20:43 UTC
*** Bug 211790 has been marked as a duplicate of this bug. ***
Comment 17 Beat Wolf 2009-10-26 10:50:09 UTC

*** This bug has been marked as a duplicate of bug 211899 ***
Comment 18 Dario Andres 2009-10-26 13:16:36 UTC
*** Bug 211899 has been marked as a duplicate of this bug. ***
Comment 19 Dario Andres 2009-11-10 00:26:30 UTC
*** Bug 213813 has been marked as a duplicate of this bug. ***
Comment 20 Dario Andres 2009-11-10 00:36:43 UTC
*** Bug 213604 has been marked as a duplicate of this bug. ***
Comment 21 Dario Andres 2009-11-14 03:56:00 UTC
From bug 214398:
---
What I was doing when the application crashed:
My preferred desktop has 0 panels, a system tray widget at bottom right, and a
digital clock widget at top left.  If I try to add a panel to this setup,
plasma crashes.  It does not happen with an empty desktop.  Judging from the
backtrace it is related to the System Tray widget.
Comment 22 Dario Andres 2009-11-14 03:56:35 UTC
*** Bug 214398 has been marked as a duplicate of this bug. ***
Comment 23 Dario Andres 2009-11-14 03:57:54 UTC
I failed to reproduce the crash with the last description mentioned, here using:

Qt: 4.6.0
KDE: 4.3.75 (KDE 4.3.75 (KDE 4.4 >= 20091113))
kdelibs svn rev. 1048844 / kdebase svn rev. 1048570
Comment 24 Beat Wolf 2009-11-27 09:29:57 UTC
*** Bug 216344 has been marked as a duplicate of this bug. ***
Comment 25 Roman Fietze 2009-12-04 13:40:17 UTC
I still had a Plasma crash with 4.3.4 from the openSUSE repos when tying to add another panel. After that crash no new pannel was added.

Even more, when trying to add that new panel again, I could no longer find the menu button "+ Add Panel" in the plasma menu. The only things left are now screen edge, width, add widgets, add spacer, lock widgets and more settings. That button didn't even come back after logging out/in.
Comment 26 Beat Wolf 2009-12-18 10:06:32 UTC
is anybody able to reproduce this with kde 4.4 (beta 1 or later) ? thank you
Comment 27 Jonathan Thomas 2010-01-05 04:01:15 UTC
*** Bug 221323 has been marked as a duplicate of this bug. ***
Comment 28 Dario Andres 2010-01-15 17:10:37 UTC
*** Bug 222862 has been marked as a duplicate of this bug. ***
Comment 29 Jonathan Thomas 2010-02-01 00:27:43 UTC
*** Bug 225079 has been marked as a duplicate of this bug. ***
Comment 30 Jonathan Thomas 2010-02-11 20:05:35 UTC
*** Bug 226365 has been marked as a duplicate of this bug. ***
Comment 31 Dario Andres 2010-02-16 12:52:23 UTC
*** Bug 227152 has been marked as a duplicate of this bug. ***
Comment 32 Dario Andres 2010-02-16 12:55:50 UTC
As nobody reported a 4.4.0 crash, assumming it is fixed. 
Please reopen if you experience it again.
Regards
Comment 33 Dario Andres 2010-03-10 12:49:05 UTC
New case from bug 230167:
KDE Platform Version: 4.4.1 (KDE 4.4.1)
Qt Version: 4.6.2
-- Information about the crash:
Every time i add a new external display device (i tried 3 ones with native
resolitions 1024x786, 1280x1024, 1680x1050) the plasma and some other serives
(the krunner or kmix...) crashes. The crash can be reproduced some of the time.
Comment 34 Dario Andres 2010-03-10 12:49:14 UTC
*** Bug 230167 has been marked as a duplicate of this bug. ***
Comment 35 Aaron J. Seigo 2010-03-10 21:37:14 UTC
"the plasma and some other serives (the krunner or kmix...) crashes"

really doesn't sound like it's related to plasma specifically. my guess would be something lower in the stack. given the activity on these bug reports and the relative severity of it, i highly doubt any of us working on plasma will get to working on this BR.
Comment 36 Dario Andres 2010-03-23 12:37:08 UTC
*** Bug 229974 has been marked as a duplicate of this bug. ***
Comment 37 Beat Wolf 2010-03-23 13:04:38 UTC
*** Bug 231882 has been marked as a duplicate of this bug. ***
Comment 38 Dario Andres 2010-03-24 13:01:04 UTC
@Aaron: some backtraces showed that the QWidget object after SystemTray::X11EmbedPainter::performUpdates was 0x0... couldn't be useful at least to include a pointer check as a workaround (to not crash) ?

#6  QWidget::mapToParent (this=0x0, pos=...) at kernel/qwidget.cpp:3997
#7  0x0711a79b in QWidget::mapTo (this=0x0, parent=0x895c0f0, pos=...) at
kernel/qwidget.cpp:3953
#8  0x068bdea6 in SystemTray::X11EmbedPainter::performUpdates (this=0x895e158)
at
../../../../../plasma/generic/applets/systemtray/protocols/fdo/x11embedpainter.cpp:127
Comment 39 Dario Andres 2010-03-24 13:01:42 UTC
From bug 231988:
-- Information about the crash:
Whene i close firestarter window plasma-desktop crash.
my running plasmoids are, calculator, rssnow, stoke quote, yawp, birthdaylist,
bibleverse, luna2 and analoge clock.
Comment 40 Dario Andres 2010-03-24 13:01:47 UTC
*** Bug 231988 has been marked as a duplicate of this bug. ***
Comment 41 Nicolas L. 2010-03-29 11:55:29 UTC
*** Bug 232559 has been marked as a duplicate of this bug. ***
Comment 42 Dario Andres 2010-04-07 14:06:52 UTC
*** Bug 233514 has been marked as a duplicate of this bug. ***
Comment 43 Dario Andres 2010-04-10 22:06:05 UTC
From bug 233973:
Sometimes when I attach an external monitor with Nvidia-Settings (Twinview)
plasma crashes..

From bug 233967:
After login I try to use dual monitors and then plasma crashes.

4.4.2 backtrace:
#6  QWidget::mapToParent (this=0x0, pos=...) at kernel/qwidget.cpp:3997
#7  0x022f080b in QWidget::mapTo (this=0x0, parent=0x904fcf8, pos=...) at
kernel/qwidget.cpp:3953
#8  0x055eff36 in SystemTray::X11EmbedPainter::performUpdates (this=0x8a6c538)
at
../../../../../plasma/generic/applets/systemtray/protocols/fdo/x11embedpainter.cpp:127
#9  0x055f0381 in SystemTray::X11EmbedPainter::qt_metacall (this=0x8a6c538,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbfea88cc) at
./x11embedpainter.moc:75
Comment 44 Dario Andres 2010-04-10 22:06:27 UTC
*** Bug 233973 has been marked as a duplicate of this bug. ***
Comment 45 Dario Andres 2010-04-10 22:06:30 UTC
*** Bug 233967 has been marked as a duplicate of this bug. ***
Comment 46 Kenneth Lakin 2010-08-14 03:54:44 UTC
Created attachment 50512 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3

- What I was doing when the application crashed:

I'm adding a "me too" and a backtrace. I had just clicked "Add an empty panel" when the crash occurred. My Desktop activity had no panels on it, before I tried to add one. Subsequent attempts to add panels work perfectly... after plasma-desktop gets restarted after the crash.

I'm running on Gentoo Linux with KDE 4.5.0 from the KDE overlay.
$ kdeinit4 --version
Qt: 4.6.3
KDE: 4.5.00 (KDE 4.5.0)

All this is compiled with GCC 4.4.4-r1 on an x86 platform.

-- Backtrace (Reduced):
#7  0xb662fad5 in QWidget::mapToParent (this=0x0, pos=...) at kernel/qwidget.cpp:4021
#8  0xb662fb45 in QWidget::mapTo (this=0x0, parent=0x9e82d40, pos=...) at kernel/qwidget.cpp:3977
#9  0xabcae42b in SystemTray::X11EmbedPainter::performUpdates (this=0x9dc2440)
    at /var/tmp/portage/kde-base/plasma-workspace-4.5.0/work/plasma-workspace-4.5.0/plasma/generic/applets/systemtray/protocols/fdo/x11embedpainter.cpp:134
#10 0xabcae83e in SystemTray::X11EmbedPainter::qt_metacall (this=0x9dc2440, _c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbf8dc62c)
    at /var/tmp/portage/kde-base/plasma-workspace-4.5.0/work/plasma-workspace-4.5.0_build/plasma/generic/applets/systemtray/x11embedpainter.moc:75
[...]
[...]
#13 0xb70987ae in QTimer::timeout (this=0x9dff6ac) at .moc/release-shared/moc_qtimer.cpp:134