Bug 149512 - Kdesktop lock crashes when scim is active
Summary: Kdesktop lock crashes when scim is active
Status: CLOSED UNMAINTAINED
Alias: None
Product: kdesktop
Classification: Miscellaneous
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
: 150136 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-09-03 12:17 UTC by z0idberg
Modified: 2009-01-02 20:34 UTC (History)
2 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 z0idberg 2007-09-03 12:17:28 UTC
Version:            (using KDE KDE 3.5.7)
Installed from:    Gentoo Packages
OS:                Linux

I have skim (scim) active with Anthy and Cangjie for inputting Japanese and Chinese.

When I have switched the input method to anthy or cangjie or any other complex input method (e.g. Hangul) and then lock the desktop with kdesktop_lock, I cannot enter any password, because I cannot switch back to my ordinary keyboard layout (German).

I would have no chance to unlock the desktop, because the input methods do not enter any ascii chars.

But after I click on “Cancel” to let the window with the username and password disappear, kdesktop_lock crashes and I am back on my Desktop.

I think this poses a great security risk, because when someone does not think of resetting his input method to ordinary keyboard, kdesktop_lock is useless. 

Also, there should be a possibility to switch the input method during kde_lock (not only for xkb keyboard layouts, but also for scim and other input methods). If this bug is fixed and the user still has anthy or something similar active, he would have no chance to unlock the desktop, because the input method does not enter any ascii characters.

I think this would partly be solved if scim/skim is integrated correctly into the desktop and not being implemented as a hack (imho).

the bug report is the following:

(no debugging symbols found)
Using host libthread_db library "/lib/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)
[Thread debugging using libthread_db enabled]
[New Thread -1242359056 (LWP 549)]
[KCrash handler]
#6  0xb762edd9 in typeinfo for QTextFormatterBreakInWords ()
   from /usr/qt/3/lib/libqt-mt.so.3
#7  0xb5a932f0 in ?? () from /usr/lib/libscim-1.0.so.8
#8  0xb5ad443e in scim::QScimInputContext::slot_hide_preedit_string ()
   from /usr/qt/3/plugins/inputmethods/libqscim.so
#9  0xb5ae6182 in scim::FunctionSlot1<void, scim::IMEngineInstanceBase*>::call
    () from /usr/qt/3/plugins/inputmethods/libqscim.so
#10 0xb5a1c356 in scim::IMEngineInstanceBase::hide_preedit_string ()
   from /usr/lib/libscim-1.0.so.8
#11 0xb5aad46d in ?? () from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#12 0xb5aaf986 in ?? () from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#13 0xb5ab01ce in ?? () from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#14 0xb5ad9710 in scim::QScimInputContext::reset ()
   from /usr/qt/3/plugins/inputmethods/libqscim.so
#15 0xb5af20bd in QMultiInputContext::reset ()
   from /usr/qt/3/plugins/inputmethods/libqimsw-multi.so
#16 0xb715a6f8 in QWidget::resetInputContext ()
   from /usr/qt/3/lib/libqt-mt.so.3
#17 0xb72b88c2 in QLineEdit::setText () from /usr/qt/3/lib/libqt-mt.so.3
#18 0xb7b94402 in KPasswordEdit::focusInEvent ()
   from /usr/kde/3.5/lib/libkdeui.so.4
#19 0xb722558b in QWidget::event () from /usr/qt/3/lib/libqt-mt.so.3
#20 0xb72b90f7 in QLineEdit::event () from /usr/qt/3/lib/libqt-mt.so.3
#21 0xb7b9409c in KPasswordEdit::event () from /usr/kde/3.5/lib/libkdeui.so.4
#22 0xb718cf67 in QApplication::internalNotify ()
   from /usr/qt/3/lib/libqt-mt.so.3
#23 0xb718dda9 in QApplication::notify () from /usr/qt/3/lib/libqt-mt.so.3
#24 0xb77eda2e in KApplication::notify ()
   from /usr/kde/3.5/lib/libkdecore.so.4
#25 0xb737517e in QDialog::show () from /usr/qt/3/lib/libqt-mt.so.3
#26 0x08058ce1 in ?? ()
#27 0xbfa61bf8 in ?? ()
#28 0x00000000 in ?? ()
Comment 1 Tommi Tervo 2007-09-24 10:02:29 UTC
*** Bug 150136 has been marked as a duplicate of this bug. ***
Comment 2 moku 2008-04-12 10:57:17 UTC
Same problem here, with Kubuntu 7.10 (Gutsy) and kdesktop 3.5.8.

I have almost Japanese input disabled all of the time.

When screensaver is on, clicking on Cancel on the password prompt would simply remove the prompt: the screensaver is still active and the screen locked.

But if I enable Japanese input (Shift + Space on this machine) while in the password prompt, and then click on the Cancel button, the screensaver is killed, and I get back a full access to the machine, without need of the password!!

(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)
[Thread debugging using libthread_db enabled]
[New Thread -1244526880 (LWP 8773)]
(no debugging symbols found)
(no debugging symbols found)
[...]
(no debugging symbols found)
(no debugging symbols found)
[KCrash handler]
#6  0x412f412f in ?? ()
#7  0xb55bfece in scim::QScimInputContext::slot_hide_preedit_string ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#8  0xb55c8752 in scim::FunctionSlot1<void, scim::IMEngineInstanceBase*>::call
    () from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#9  0xb5529650 in scim::IMEngineInstanceBase::hide_preedit_string ()
   from /usr/lib/libscim-1.0.so.8
#10 0xb545cc61 in scim::SocketInstance::do_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#11 0xb545f178 in scim::SocketInstance::commit_transaction ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#12 0xb545f93c in scim::SocketInstance::reset ()
   from /usr/lib/scim-1.0/1.4.0/IMEngine/socket.so
#13 0xb55bece0 in scim::QScimInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqscim.so
#14 0xb5abf2c9 in QMultiInputContext::reset ()
   from /usr/lib/qt3/plugins/inputmethods/libqimsw-multi.so
#15 0xb764dce1 in QWidget::resetInputContext () from /usr/lib/libqt-mt.so.3
#16 0xb77ce181 in QLineEdit::setText () from /usr/lib/libqt-mt.so.3
#17 0xb6907563 in KPasswordEdit::focusInEvent () from /usr/lib/libkdeui.so.4
#18 0xb77239e6 in QWidget::event () from /usr/lib/libqt-mt.so.3
#19 0xb77cdbe7 in QLineEdit::event () from /usr/lib/libqt-mt.so.3
#20 0xb6907213 in KPasswordEdit::event () from /usr/lib/libkdeui.so.4
#21 0xb7683af0 in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#22 0xb76864ba in QApplication::notify () from /usr/lib/libqt-mt.so.3
#23 0xb7e49cd2 in KApplication::notify () from /usr/lib/libkdecore.so.4
#24 0xb7616209 in QApplication::sendEvent () from /usr/lib/libqt-mt.so.3
#25 0xb78a085b in QDialog::show () from /usr/lib/libqt-mt.so.3
#26 0x08054431 in ?? ()
#27 0xbfa483dc in ?? ()
#28 0x00000000 in ?? ()
Comment 3 FiNeX 2008-12-10 14:02:12 UTC
Kdesktop is no more mantained. Fortunatly this bug seems not to be valid for
KDE 4. Please reopen if this bug is not a kdesktop one (and it is not solved)
or it can be reproduced on KDE 4.

Thanks.
Comment 4 FiNeX 2009-01-02 20:34:38 UTC
Bug closed. Kdesktop is no more mantained.