Bug 227578 - [steps] Crash when adding Keyboard widget after having added, activated and removed the Input Methods widget [Plasma::Corona::popupPosition, Plasma::ToolTipManagerPrivate::showToolTip]
Summary: [steps] Crash when adding Keyboard widget after having added, activated and r...
Status: RESOLVED DUPLICATE of bug 214943
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-18 21:59 UTC by rookcifer
Modified: 2010-07-22 03:12 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
New crash information added by DrKonqi (4.33 KB, text/plain)
2010-07-22 03:12 UTC, SlashDevDsp 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rookcifer 2010-02-18 21:59:17 UTC 
Application: plasma-desktop (0.3)
KDE Platform Version: 4.4.00 (KDE 4.4.0)
Qt Version: 4.6.1
Operating System: Linux 2.6.31-19-generic x86_64
Distribution: Ubuntu 9.10

-- Information about the crash:
I had just added the keyboard widget and then clicked on a key when it crashed.  Backtrace is attached.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5  0x00007ff20000a502 in ?? ()
#6  0x00007ff221f77d69 in Plasma::Corona::popupPosition (this=0x3c90f80, item=0x4273650, s=..., alignment=Qt::AlignCenter) at ../../plasma/corona.cpp:673
#7  0x00007ff2220173b1 in Plasma::ToolTipManagerPrivate::showToolTip (this=0x2464a20) at ../../plasma/tooltipmanager.cpp:375
#8  0x00007ff222017805 in Plasma::ToolTipManager::qt_metacall (this=0x2464c30, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffec6b5250) at ./tooltipmanager.moc:88
#9  0x00007ff229fcdd3f in QMetaObject::activate (sender=0x24e1250, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3275
#10 0x00007ff229fca993 in QObject::event (this=0x24e1250, e=0x7fffec6b59a0) at kernel/qobject.cpp:1212
#11 0x00007ff229159fac in QApplicationPrivate::notify_helper (this=0x21adaf0, receiver=0x24e1250, e=0x7fffec6b59a0) at kernel/qapplication.cpp:4298
#12 0x00007ff22916059b in QApplication::notify (this=0x217f010, receiver=0x24e1250, e=0x7fffec6b59a0) at kernel/qapplication.cpp:4181
#13 0x00007ff22a502d16 in KApplication::notify (this=0x217f010, receiver=0x24e1250, event=0x7fffec6b59a0) at ../../kdeui/kernel/kapplication.cpp:302
#14 0x00007ff229fbaf3c in QCoreApplication::notifyInternal (this=0x217f010, receiver=0x24e1250, event=0x7fffec6b59a0) at kernel/qcoreapplication.cpp:704
#15 0x00007ff229fe7b92 in QCoreApplication::sendEvent (this=0x21b1060) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x21b1060) at kernel/qeventdispatcher_unix.cpp:603
#17 0x00007ff229fe4798 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007ff2251c9bce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#20 0x00007ff2251cd598 in ?? () from /lib/libglib-2.0.so.0
#21 0x00007ff2251cd6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#22 0x00007ff229fe4463 in QEventDispatcherGlib::processEvents (this=0x21ad4b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#23 0x00007ff2292097ee in QGuiEventDispatcherGlib::processEvents (this=0x3c90f80, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#24 0x00007ff229fb9862 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#25 0x00007ff229fb9c3c in QEventLoop::exec (this=0x7fffec6b5c40, flags=) at kernel/qeventloop.cpp:201
#26 0x00007ff229fbd97b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#27 0x00007ff21d7930a2 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#28 0x0000000000406fb8 in launch (argc=1, _name=<value optimized out>, args=<value optimized out>, cwd=<value optimized out>, envc=0, envs=<value optimized out>, reset_env=false, tty=0x0, 
    avoid_loops=false, startup_id_str=0x40a499 "0") at ../../kinit/kinit.cpp:717
#29 0x0000000000407c70 in handle_launcher_request (sock=9, who=<value optimized out>) at ../../kinit/kinit.cpp:1209
#30 0x0000000000408121 in handle_requests (waitForPid=0) at ../../kinit/kinit.cpp:1402
#31 0x0000000000408df2 in main (argc=4, argv=<value optimized out>, envp=<value optimized out>) at ../../kinit/kinit.cpp:1841

Possible duplicates by query: bug 223092, bug 216319, bug 197806, bug 194974.

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-19 23:35:26 UTC 
- Does the application crash again if you repeat the situation you described ?
This looks related to bug 214943. Regards
Comment 2 rookcifer 2010-02-20 05:40:51 UTC 
On Friday 19 February 2010 4:35:28 pm Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=227578
> 
> 
> Dario Andres <andresbajotierra@gmail.com> changed:
> 
>            What    |Removed                     |Added
> ---------------------------------------------------------------------------
> - CC|                            |andresbajotierra@gmail.com
> 
> 
> 
> 
> --- Comment #1 from Dario Andres <andresbajotierra gmail com>  2010-02-19
> 23:35:26 --- - Does the application crash again if you repeat the
> situation you described ? This looks related to bug 214943. Regards

Yes, I can repeat it every time.  Let me be a bit more specific about how to do 
so:

1) Click add widgets and then add the "input methods" widget to the desktop.

2) Once that widget is on the desktop, click on it until the pencil appears 
(one click).  

3) Close the "input methods"  widget.

4)  Immediately put the keyboard widget on the desktop.  

5) Click anywhere on the keyboard. 

6)  You will see a cash every time on Kubuntu 9.10 with KDE 4.4.

If I just add the keyboard by itself without first adding the "input methods" 
widget, I do not get a crash when i click the keyboard.  it is only after 
adding (and closing) input methods that this happens.  So, I am not sure if it 
is an issue with input methods or with the keyboard.

Regards,
Comment 3 Dario Andres 2010-02-20 21:44:05 UTC 
I could reproduce the crash with the steps on comment 2

Here using:

Qt: 4.6.2 (kde-qt master commit 62cda737405d0f2163094c44189cfd71ca3c576a
        Date:   Mon Feb 15 14:37:02 2010 +0100)
KDE Development Platform: 4.4.63 (KDE 4.4.63 (KDE 4.5 >= 20100209))
kdelibs svn rev. 1092352 / kdebase svn rev. 1092352
on ArchLinux i686 - Kernel 2.6.32.8

- Note that the InputMethods widget can be used even if SCIM is not installed (it is only required for building the widget)

The crashing line is: kdelibs/plasma/corona.cpp:677
"QRect screenRect = screenGeometry(screen);"

I still think this report is related to bug 214943, but let's keep it separated as the backtraces are a bit different.

-- Backtrace:
#6  0xb7139983 in Plasma::Corona::popupPosition (this=0xa6efe60, item=0xa715220, s=..., alignment=Qt::AlignCenter) at /home/kde-devel/kde/src/KDE/kdelibs/plasma/corona.cpp:677
#7  0xb71e6985 in Plasma::ToolTipManagerPrivate::showToolTip (this=0x9d980a0) at /home/kde-devel/kde/src/KDE/kdelibs/plasma/tooltipmanager.cpp:375
#8  0xb71e6e7e in Plasma::ToolTipManager::qt_metacall (this=0x9d76b28, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf9c3e60) at /home/kde-devel/kde/build/KDE/kdelibs/plasma/tooltipmanager.moc:88
#9  0xb544fed8 in QMetaObject::metacall (object=0x9d76b28, cl=QMetaObject::InvokeMetaMethod, idx=6, argv=0xbf9c3e60) at kernel/qmetaobject.cpp:237
#10 0xb5463fc4 in QMetaObject::activate (sender=0x9d632b0, m=0xb55a76e4, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3293
#11 0xb54c304b in QTimer::timeout (this=0x9d632b0) at .moc/debug-shared/moc_qtimer.cpp:134
#12 0xb546c974 in QTimer::timerEvent (this=0x9d632b0, e=0xbf9c44c4) at kernel/qtimer.cpp:271
#13 0xb5460022 in QObject::event (this=0x9d632b0, e=0xbf9c44c4) at kernel/qobject.cpp:1212
#14 0xb57bdcd6 in QApplicationPrivate::notify_helper (this=0x9c02220, receiver=0x9d632b0, e=0xbf9c44c4) at kernel/qapplication.cpp:4300
#15 0xb57bb418 in QApplication::notify (this=0x9bf9d18, receiver=0x9d632b0, e=0xbf9c44c4) at kernel/qapplication.cpp:3704
#16 0xb6909bb0 in KApplication::notify (this=0x9bf9d18, receiver=0x9d632b0, event=0xbf9c44c4) at /home/kde-devel/kde/src/KDE/kdelibs/kdeui/kernel/kapplication.cpp:302
#17 0xb5448935 in QCoreApplication::notifyInternal (this=0x9bf9d18, receiver=0x9d632b0, event=0xbf9c44c4) at kernel/qcoreapplication.cpp:704
#18 0xb57ae29d in QCoreApplication::sendEvent (receiver=0x9d632b0, event=0xbf9c44c4) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#19 0xb54832ae in QTimerInfoList::activateTimers (this=0x9c05074) at kernel/qeventdispatcher_unix.cpp:603
#20 0xb547f18c in timerSourceDispatch (source=0x9c05040) at kernel/qeventdispatcher_glib.cpp:184
#21 0xb547f245 in idleTimerSourceDispatch (source=0x9c050b0) at kernel/qeventdispatcher_glib.cpp:231
#22 0xb35c2378 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb35c5bf0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#24 0xb35c5d23 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb5480338 in QEventDispatcherGlib::processEvents (this=0x9bcae50, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#26 0xb58938c6 in QGuiEventDispatcherGlib::processEvents (this=0x9bcae50, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#27 0xb5445d0f in QEventLoop::processEvents (this=0xbf9c47bc, flags=...) at kernel/qeventloop.cpp:149
#28 0xb5445e54 in QEventLoop::exec (this=0xbf9c47bc, flags=...) at kernel/qeventloop.cpp:201
#29 0xb5449011 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#30 0xb57bb026 in QApplication::exec () at kernel/qapplication.cpp:3579
#31 0xb7729d31 in kdemain (argc=1, argv=0xbf9c49d4) at /home/kde-devel/kde/src/KDE/kdebase/workspace/plasma/desktop/shell/main.cpp:118
#32 0x080487c9 in main (argc=1, argv=0xbf9c49d4) at /home/kde-devel/kde/build/KDE/kdebase/workspace/plasma/desktop/shell/plasma-desktop_dummy.cpp:3
Comment 4 Beat Wolf 2010-02-22 10:12:54 UTC 

*** This bug has been marked as a duplicate of bug 214943 ***
Comment 5 SlashDevDsp 2010-07-22 03:12:57 UTC 
Created attachment 49379 [details]
New crash information added by DrKonqi

plasma-desktop (0.3) on KDE Platform 4.5.60 (KDE 4.5.60 (KDE 4.6 >= 20100627)) using Qt 4.6.3

- What I was doing when the application crashed:

Todays trunk 4.5.60 with qt 4.6.3, plasma-desktop crashed when I was browsing through the panel - add widgets when a popup notification appeared, when the notification disappeared plasma-desktop crashed with bt below

-- Backtrace (Reduced):
#6  0x00007fb85b759260 in Plasma::Corona::popupPosition (this=0x32f2ee0, item=0x1632a00, s=@0x7fff2cb9ba60, alignment=39) at /home/kde-devel/kdesvn/kdelibs/plasma/corona.cpp:780
#7  0x00007fb85b805b5d in Plasma::ToolTipManagerPrivate::showToolTip (this=0x9003f0) at /home/kde-devel/kdesvn/kdelibs/plasma/tooltipmanager.cpp:381
#8  0x00007fb85b805f09 in Plasma::ToolTipManager::qt_metacall (this=0x8ec810, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff2cb9bb90)
    at /home/kde-devel/kdesvn/build/kdelibs/plasma/tooltipmanager.moc:88
[...]
#10 0x00007fb857d0b413 in QObject::event (this=0x8ec840, e=0x0) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qobject.cpp:1212
#11 0x00007fb856e5c4ad in QApplicationPrivate::notify_helper (this=0x757a70, receiver=0x8ec840, e=0x7fff2cb9c390) at /home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qapplication.cpp:4302