Bug 146956 - Kontact crashes when Japanese is used in calendar event
Summary: Kontact crashes when Japanese is used in calendar event
Status: RESOLVED DUPLICATE of bug 141974
Alias: None
Product: korganizer
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-06-19 12:32 UTC by David Osumi
Modified: 2007-12-20 23:27 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 David Osumi 2007-06-19 12:32:56 UTC
Version:           1.2.5 (using KDE KDE 3.5.7)
Installed from:    Ubuntu Packages
Compiler:          gcc (GCC) 4.1.2 (Ubuntu 4.1.2-0ubuntu4) 
OS:                Linux

OS: Kubuntu Fiesty.  KDE version:3.5.7

Entering a (recurring) calendar event in Japanese (input via Anthy) causes Kontact to crash as soon as new event/TODO is selected.  Entering the same event in English did not cause this problem.

Here's the backtrace.

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1243224368 (LWP 5487)]
[New Thread -1287398512 (LWP 5491)]
[New Thread -1279005808 (LWP 5490)]
[New Thread -1270613104 (LWP 5489)]
[New Thread -1262220400 (LWP 5488)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x0806b485 in static_QUType_Null ()
#7  0x7f7f7f7f in ?? ()
#8  0x7f7f7f7f in ?? ()
#9  0x7f7f7f7f in ?? ()
#10 0x7f7f7f7f in ?? ()
#11 0x7f7f7f7f in ?? ()
#12 0x7f7f7f7f in ?? ()
#13 0x7f7f7f7f in ?? ()
#14 0x7f7f7f7f in ?? ()
#15 0x7f7f7f7f in ?? ()
#16 0x7f7f7f7f in ?? ()
#17 0x7f7f7f7f in ?? ()
#18 0x7f7f7f7f in ?? ()
#19 0x7f7f7f7f in ?? ()
#20 0x7f7f7f7f in ?? ()
#21 0x7f7f7f7f in ?? ()
#22 0x7f7f7f7f in ?? ()
#23 0x7f7f7f7f in ?? ()
#24 0x7f7f7f7f in ?? ()
#25 0x7f7f7f7f in ?? ()
#26 0x7f7f7f7f in ?? ()
#27 0x7f7f7f7f in ?? ()
#28 0x7f7f7f7f in ?? ()
#29 0x7f7f7f7f in ?? ()
#30 0x7f7f7f7f in ?? ()
#31 0xbf9fe058 in ?? ()
#32 0xb72748dc in ?? () from /usr/lib/libqt-mt.so.3
#33 0xbf9fe04e in ?? ()
#34 0xbf9fe04c in ?? ()
#35 0x7f7f7f7f in ?? ()
#36 0x007f7f7f in ?? ()
#37 0x00000000 in ?? ()
Comment 1 Thomas McGuire 2007-06-20 19:15:26 UTC
Please try to get a better backtrace: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports
Comment 2 David Osumi 2007-06-21 13:06:40 UTC
Some extra details:

Korganizer version 3.5.7
After adding new event to the calendar with a name in Japanese (input via Anthy/SCIM), if I then switch back to English input and choose 'add new TODO' in from TODO panel, Kontact crashes. The crash does not happen if I leave Japanese input turned on.

New backtrace here.  Hope this is better:

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1242913072 (LWP 6524)]
[New Thread -1287087216 (LWP 6528)]
[New Thread -1278694512 (LWP 6527)]
[New Thread -1270301808 (LWP 6526)]
[New Thread -1261909104 (LWP 6525)]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0xb2bb353b in scim::QScimInputContext::slot_hide_preedit_string ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#7  0xb2bbbdc2 in scim::FunctionSlot1<void, scim::IMEngineInstanceBase*>::call
    () from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#8  0xb2b1254c in scim::IMEngineInstanceBase::hide_preedit_string ()
   from /usr/lib/libscim-1.0.so.8
#9  0xb2a6ead3 in scim::SocketInstance::do_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#10 0xb2a70f76 in scim::SocketInstance::commit_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#11 0xb2a7176a in scim::SocketInstance::reset ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#12 0xb2bb2350 in scim::QScimInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#13 0xb2bfd2e9 in QMultiInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so
#14 0xb6f0ac91 in QWidget::resetInputContext () from /usr/lib/libqt-mt.so.3
#15 0xb708b0e5 in QLineEdit::setText () from /usr/lib/libqt-mt.so.3
#16 0xb6858c28 in KLineEdit::setText () from /usr/lib/libkdeui.so.4
#17 0xb67f4d1b in KDatePicker::dateChangedSlot () from /usr/lib/libkdeui.so.4
#18 0xb67f4f77 in KDatePicker::qt_invoke () from /usr/lib/libkdeui.so.4
#19 0xb6fa988b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0xb67b3b3e in KDateTable::dateChanged () from /usr/lib/libkdeui.so.4
#21 0xb67b3dbe in KDateTable::setDate () from /usr/lib/libkdeui.so.4
#22 0xb67b45bd in KDatePicker::setDate () from /usr/lib/libkdeui.so.4
#23 0xb56d2e41 in KOTodoView::popupMenu () from /usr/lib/libkorganizer.so.1
#24 0xb56d333c in KOTodoView::qt_invoke () from /usr/lib/libkorganizer.so.1
#25 0xb6fa988b in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#26 0xb734cc94 in QListView::contextMenuRequested ()
   from /usr/lib/libqt-mt.so.3
#27 0xb70a71be in QListView::contentsContextMenuEvent ()
   from /usr/lib/libqt-mt.so.3
#28 0xb70de87a in QScrollView::viewportContextMenuEvent ()
   from /usr/lib/libqt-mt.so.3
#29 0xb70e06c8 in QScrollView::eventFilter () from /usr/lib/libqt-mt.so.3
#30 0xb70a875e in QListView::eventFilter () from /usr/lib/libqt-mt.so.3
#31 0xb6fa8e38 in QObject::activate_filters () from /usr/lib/libqt-mt.so.3
#32 0xb6fa8eb6 in QObject::event () from /usr/lib/libqt-mt.so.3
#33 0xb6fe058f in QWidget::event () from /usr/lib/libqt-mt.so.3
#34 0xb6f40a60 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#35 0xb6f4309b in QApplication::notify () from /usr/lib/libqt-mt.so.3
#36 0xb767cc32 in KApplication::notify () from /usr/lib/libkdecore.so.4
#37 0xb6ed325d in QApplication::sendSpontaneousEvent ()
   from /usr/lib/libqt-mt.so.3
#38 0xb6ed1f2e in QETWidget::translateMouseEvent ()
   from /usr/lib/libqt-mt.so.3
#39 0xb6ecffac in QApplication::x11ProcessEvent () from /usr/lib/libqt-mt.so.3
#40 0xb6ee7180 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#41 0xb6f5b136 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#42 0xb6f5af46 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#43 0xb6f42609 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#44 0x08061e25 in ?? ()
#45 0xbfc8b5ec in ?? ()
#46 0x00000001 in ?? ()
#47 0x00000001 in ?? ()
#48 0x00000000 in ?? ()
Comment 3 Thomas McGuire 2007-06-21 17:38:18 UTC
See also bug 141974. This seems to be a scim bug, not a KDE bug.
Please update scim and other related packages to the very lasted version and see if it still crashes.
Comment 4 Thomas McGuire 2007-12-20 23:27:27 UTC
No response, so probably a duplicate of bug 141974.

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