Bug 141974 - Crash when keyboard shortcuts while SCIM active in Japanese mode
Summary: Crash when keyboard shortcuts while SCIM active in Japanese mode
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 144029 146666 146956 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-02-20 12:42 UTC by Wataru Tenga
Modified: 2007-12-20 23:27 UTC (History)
3 users (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 Wataru Tenga 2007-02-20 12:42:28 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    Ubuntu Packages
OS:                Linux

Pressing a valid shortcut key, such as "R" for "reply," while SCIM is in Japanese input mode causes an immediate crash of KMail. The error log reports SCIM-related errors. This bug is nearly 100% reproducible, and has been observed in every KDE version including 3.5.6, and on a variety of distributions including openSUSE and Ubuntu.
Comment 1 Thomas McGuire 2007-02-20 12:52:40 UTC
Please provide a backtrace.

Could this be the following bug:
https://bugzilla.novell.com/show_bug.cgi?id=206547
?
Comment 2 groot 2007-02-20 14:46:59 UTC
Please also provide a description of how to set up (or give a good link) SCIM  for Japanese, since trying to reproduce the bug is going to be difficult otherwise.
Comment 3 Wataru Tenga 2007-02-21 12:13:25 UTC
Installing SCIM for Japanese is done in KDE simply by adding Japanese as a supported language. (In KDE 3.5.6 this is done in the Control Center under Regional & Accessibility | Country/Region & Language.) The SCIM and associated programs, including Anthy for Japanese input, should be installed automatically (in distros that have Japanese support, such as (K)Ubuntu or openSUSE or Fedora).

Then choose Settings | SCIM input method setup. The default keyboard shortcut for switching to Japanese mode is Ctrl+Space.

Now, in KMail, enable Japanese input mode. Then press the "R" key to reply to a message. I did that just now, with the following result:

(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 -1242297552 (LWP 4789)]
[New Thread -1284912224 (LWP 4793)]
[New Thread -1276519520 (LWP 4792)]
[New Thread -1268126816 (LWP 4791)]
[New Thread -1259734112 (LWP 4790)]
(no debugging symbols found)
  "           "
(no debugging symbols found)
[KCrash handler]
#6  0x00000019 in ?? ()
#7  0xb2e8e53e in scim::QScimInputContext::slot_hide_preedit_string ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#8  0xb2e96dc2 in scim::FunctionSlot1<void, scim::IMEngineInstanceBase*>::call
    () from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#9  0xb2de255c in scim::IMEngineInstanceBase::hide_preedit_string ()
   from /usr/lib/libscim-1.0.so.8
#10 0xb2d551d3 in scim::SocketInstance::do_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#11 0xb2d57656 in scim::SocketInstance::commit_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#12 0xb2d57e4a in scim::SocketInstance::reset ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#13 0xb2e8d350 in scim::QScimInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#14 0xb549fea9 in QMultiInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so
#15 0xb6f12db9 in QWidget::resetInputContext () from /usr/lib/libqt-mt.so.3
#16 0xb709319d in QLineEdit::setText () from /usr/lib/libqt-mt.so.3
#17 0xb705a49e in QComboBox::setLineEdit () from /usr/lib/libqt-mt.so.3
#18 0xb7054d68 in QComboBox::setUpLineEdit () from /usr/lib/libqt-mt.so.3
#19 0xb705a00b in QComboBox::QComboBox () from /usr/lib/libqt-mt.so.3
#20 0xb53bb9f4 in KMComposeWin::KMComposeWin ()
   from /usr/lib/libkmailprivate.so
#21 0xb53bdb7b in KMComposeWin::create () from /usr/lib/libkmailprivate.so
#22 0xb53bdbb4 in KMail::makeComposer () from /usr/lib/libkmailprivate.so
#23 0xb53c3763 in KMReplyToCommand::execute ()
   from /usr/lib/libkmailprivate.so
#24 0xb5111639 in KMCommand::slotPostTransfer ()
   from /usr/lib/libkmailprivate.so
#25 0xb51a7eb6 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#26 0xb51a886b in KMReplyToCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#27 0xb6fb1957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#28 0xb511175e in KMCommand::messagesTransfered ()
   from /usr/lib/libkmailprivate.so
#29 0xb5207431 in KMCommand::transferSelectedMsgs ()
   from /usr/lib/libkmailprivate.so
#30 0xb5207597 in KMCommand::slotStart () from /usr/lib/libkmailprivate.so
#31 0xb51a7ec8 in KMCommand::qt_invoke () from /usr/lib/libkmailprivate.so
#32 0xb51a886b in KMReplyToCommand::qt_invoke ()
   from /usr/lib/libkmailprivate.so
#33 0xb6fb1957 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#34 0xb733df44 in QSignal::signal () from /usr/lib/libqt-mt.so.3
#35 0xb6fd18ea in QSignal::activate () from /usr/lib/libqt-mt.so.3
#36 0xb6fd9300 in QSingleShotTimer::event () from /usr/lib/libqt-mt.so.3
#37 0xb6f48b88 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#38 0xb6f4a9b7 in QApplication::notify () from /usr/lib/libqt-mt.so.3
#39 0xb7650c82 in KApplication::notify () from /usr/lib/libkdecore.so.4
#40 0xb6edb389 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#41 0xb6f3b5d3 in QEventLoop::activateTimers () from /usr/lib/libqt-mt.so.3
#42 0xb6eefec5 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#43 0xb6f6325e in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#44 0xb6f6306e in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#45 0xb6f4a731 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#46 0x08061095 in ?? ()
#47 0xbfeaa5ec in ?? ()
#48 0x00000001 in ?? ()
#49 0x00000001 in ?? ()
#50 0x00000000 in ?? ()


wataru
Comment 4 Thomas McGuire 2007-02-21 16:47:11 UTC
This backtrace looks very much like the backtrace from the SuSE bugreport at https://bugzilla.novell.com/show_bug.cgi?id=206547.

It is not a KDE bug, but a SCIM bug, which is a third party app or library.
SuSE has updated packages at http://software.opensuse.org/download/M17N/. I don't know about Ubuntu.

That report says any app crashes when opening a second mainwindow. The report specially tells how to reproduce this for Kopete.

If my assumptions here are wrong, please reopen this report.
Comment 5 Wataru Tenga 2007-02-21 22:40:02 UTC
I can't reproduce it in Gnome applications (e.g., Evolution or Liferea). Isn't it a bug in interaction between SCIM and KDE?

If SCIM is broken in KDE, does KDE have a non-broken means for Japanese input?

wataru
Comment 6 Wataru Tenga 2007-02-22 01:16:05 UTC
To dispel any misunderstanding and controversy, I am very much pro-KDE, and consider the latest KMail to be the greatest email program for any platform available today. You are quite possibly correct that the fault is entirely with SCIM. I see that Mike Fabian over at Novell has uploaded a possible fix for a similar problem, as you have noted. But that fix is only for SUSE. Will it need to be made separately for each distribution? Is there nothing that can be done on the KDE end to fix it? If this problem is completely KDE-independent, you may close the bug and I'll try to find a fix elsewhere.
Comment 7 Thomas McGuire 2007-02-22 19:44:05 UTC
I think the problem is KDE independent.
SCIM works with all Qt apps, so this is a problem for all Qt applications, including KDE. I am not sure however.

I am not sure if this is the same problem, but you should try the workarounds at http://forum.skype.com/index.php?showtopic=64211.
Comment 8 Wataru Tenga 2007-02-23 06:00:17 UTC
Thomas, thanks for looking into this. You are probably correct that it is a SCIM + Qt issue, not the fault of KDE itself. I'll close the bug and look elsewhere.

I'm not sure how the Skype workaround can be used with KMail. Can you explain?

wataru
Comment 9 Wataru Tenga 2007-02-23 06:01:34 UTC
I'm marking as Resolved, due to the lack of clear dependence on KDE. The issue itself remains, however.
Comment 10 Wataru Tenga 2007-02-28 11:57:44 UTC
I have now updated my openSUSE installation with the revised SCIM and related files. This appears to have fixed the problem, at least for openSUSE.

Thanks, Thomas, for pointing out the fix.

wataru
Comment 11 Tommi Tervo 2007-04-10 11:24:10 UTC
*** Bug 144029 has been marked as a duplicate of this bug. ***
Comment 12 Thomas McGuire 2007-06-11 19:09:50 UTC
*** Bug 146666 has been marked as a duplicate of this bug. ***
Comment 13 Thomas McGuire 2007-12-20 23:27:29 UTC
*** Bug 146956 has been marked as a duplicate of this bug. ***