Bug 408760

Summary: Kate segfaults when Korean files are open with uim
Product: [Applications] kate Reporter: mycarrier
Component: generalAssignee: KWrite Developers <kwrite-bugs-null>
Status: RESOLVED UPSTREAM    
Severity: crash CC: a.samirh78
Priority: NOR Keywords: drkonqi
Version First Reported In: 19.04.2   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description mycarrier 2019-06-15 23:39:17 UTC
Application: kate (19.04.2)

Qt Version: 5.12.3
Frameworks Version: 5.59.0
Operating System: Linux 5.1.9-arch1-1-ARCH x86_64
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
I'm moderately sure I was doing something else with Kate out of focus. 3 UTF-8 Korean files were open for some hours at the time.
- Custom settings of the application:
I was using uim/Byeoru input method.

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1622b0a840 (LWP 4208))]

Thread 2 (Thread 0x7f161bad7700 (LWP 4210)):
#0  0x00007f1627602c54 in read () from /usr/lib/libc.so.6
#1  0x00007f16257d3961 in ?? () from /usr/lib/libglib-2.0.so.0
#2  0x00007f1625823f70 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#3  0x00007f1625825766 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00007f16258258ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#5  0x00007f1627b3c984 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#6  0x00007f1627ae64dc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#7  0x00007f162792b239 in QThread::exec() () from /usr/lib/libQt5Core.so.5
#8  0x00007f1627db4ba6 in ?? () from /usr/lib/libQt5DBus.so.5
#9  0x00007f162792c63c in ?? () from /usr/lib/libQt5Core.so.5
#10 0x00007f1626317a92 in start_thread () from /usr/lib/libpthread.so.0
#11 0x00007f1627611cd3 in clone () from /usr/lib/libc.so.6

Thread 1 (Thread 0x7f1622b0a840 (LWP 4208)):
[KCrash Handler]
#6  0x00007f1627ae7744 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /usr/lib/libQt5Core.so.5
#7  0x00007f16226c3fbc in QUimPlatformInputContext::commitString(QString const&) () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
#8  0x00007f16226c4042 in QUimPlatformInputContext::commit_cb(void*, char const*) () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
#9  0x00007f16226a4a3d in ?? () from /usr/lib/libuim.so.8
#10 0x00007f1620013807 in ?? () from /usr/lib/libuim-scm.so.0
#11 0x00007f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0
#12 0x00007f1620013b80 in ?? () from /usr/lib/libuim-scm.so.0
#13 0x00007f1620013d07 in ?? () from /usr/lib/libuim-scm.so.0
#14 0x00007f162001310e in ?? () from /usr/lib/libuim-scm.so.0
#15 0x00007f1620013559 in ?? () from /usr/lib/libuim-scm.so.0
#16 0x00007f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0
#17 0x00007f1620013b80 in ?? () from /usr/lib/libuim-scm.so.0
#18 0x00007f1620013807 in ?? () from /usr/lib/libuim-scm.so.0
#19 0x00007f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0
#20 0x00007f162001e963 in ?? () from /usr/lib/libuim-scm.so.0
#21 0x00007f16200137ec in ?? () from /usr/lib/libuim-scm.so.0
#22 0x00007f1620013a79 in ?? () from /usr/lib/libuim-scm.so.0
#23 0x00007f1620014094 in ?? () from /usr/lib/libuim-scm.so.0
#24 0x00007f162000325d in GCROOTS_call_with_gc_ready_stack () from /usr/lib/libgcroots.so.0
#25 0x00007f1620023644 in uim_scm_callf () from /usr/lib/libuim-scm.so.0
#26 0x00007f16226a2d4b in uim_focus_out_context () from /usr/lib/libuim.so.8
#27 0x00007f16226c22de in QUimPlatformInputContext::unsetFocus() () from /usr/lib/qt/plugins/platforminputcontexts/libuimplatforminputcontextplugin.so
#28 0x00007f162802de28 in QGuiApplicationPrivate::_q_updateFocusObject(QObject*) () from /usr/lib/libQt5Gui.so.5
#29 0x00007f16280339e8 in QGuiApplicationPrivate::processActivatedEvent(QWindowSystemInterfacePrivate::ActivatedWindowEvent*) () from /usr/lib/libQt5Gui.so.5
#30 0x00007f1628038a4e in QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*) () from /usr/lib/libQt5Gui.so.5
#31 0x00007f1628011d9c in QWindowSystemInterface::sendWindowSystemEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Gui.so.5
#32 0x00007f162257db8c in ?? () from /usr/lib/libQt5XcbQpa.so.5
#33 0x00007f162582390f in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0x00007f1625825869 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0x00007f16258258ae in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0x00007f1627b3c969 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#37 0x00007f1627ae64dc in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQt5Core.so.5
#38 0x00007f1627aee596 in QCoreApplication::exec() () from /usr/lib/libQt5Core.so.5
#39 0x0000562614aed3c4 in ?? ()
#40 0x00007f162753ace3 in __libc_start_main () from /usr/lib/libc.so.6
#41 0x0000562614aeea8e in _start ()
[Inferior 1 (process 4208) detached]

Reported using DrKonqi
Comment 1 Dominik Haumann 2019-06-16 09:00:30 UTC
https://github.com/uim/uim/issues/30 seems to report the same issue, however from 2012 or so... Can you reproduce this?

Unfortunately the backtrace is also missing more detailed debug info.

But since the backtrace does not contain Kate code at all, I assume this is either a Qt or a uim isdue.

Could you report upstream to Qt or uim?
Comment 2 Ahmad Samir 2019-07-09 17:09:55 UTC
NEEDSINFO per comment#1.
Comment 3 Bug Janitor Service 2019-07-24 04:33:09 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Bug Janitor Service 2019-08-08 04:33:10 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!
Comment 5 mycarrier 2019-09-09 20:35:07 UTC
Reported to uim--https://github.com/uim/uim/issues/148. It seems to happen when the application loses focus while Byeoru is composing a letter.
Comment 6 mycarrier 2019-09-09 20:38:39 UTC
Also, is "resolved upstream" the right status for this? It doesn't sound right, but I don't see anything better.