Bug 208056 - Kate crashed after pushing the "list"-key
Summary: Kate crashed after pushing the "list"-key
Status: RESOLVED DUPLICATE of bug 236899
Alias: None
Product: kate
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-21 10:32 UTC by Alexander Paetzelt
Modified: 2010-06-01 22:49 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 Alexander Paetzelt 2009-09-21 10:32:32 UTC
Application that crashed: kate
Version of the application: 3.3.1
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
when i push the key between alt gr and control (sometimes there is only a windows-key, but often a list with a arrow, i mean this key) crashed kate twice, so i believe it is a general bug...

 -- Backtrace:
Application: Kate (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb6c9811d in QTextLine::cursorToX () from /usr/lib/libQtGui.so.4
#7  0xb1d27155 in KateRenderer::cursorToX () from /usr/lib/kde4/katepart.so
#8  0xb1d8d720 in KateViewInternal::makeVisible () from /usr/lib/kde4/katepart.so
#9  0xb1d9267f in KateViewInternal::contextMenuEvent () from /usr/lib/kde4/katepart.so
#10 0xb6ab988f in QWidget::event () from /usr/lib/libQtGui.so.4
#11 0xb6a64994 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#12 0xb6a6c4c6 in QApplication::notify () from /usr/lib/libQtGui.so.4
#13 0xb74a743a in KApplication::notify () from /usr/lib/libkdeui.so.5
#14 0xb7ddbfcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#15 0xb6a6586e in ?? () from /usr/lib/libQtGui.so.4
#16 0xb6aff16f in ?? () from /usr/lib/libQtGui.so.4
#17 0xb6b014cc in ?? () from /usr/lib/libQtGui.so.4
#18 0xb6ad7c57 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#19 0xb6b02f92 in ?? () from /usr/lib/libQtGui.so.4
#20 0xb666ed98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#21 0xb66723e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#22 0xb6672513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#23 0xb7e066cc in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#24 0xb6b026c5 in ?? () from /usr/lib/libQtGui.so.4
#25 0xb7dda579 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#26 0xb7dda9ca in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#27 0xb7ddce3f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#28 0xb6a64817 in QApplication::exec () from /usr/lib/libQtGui.so.4
#29 0xb7ed6a8d in kdemain () from /usr/lib/libkdeinit4_kate.so
#30 0x0804de22 in _start ()

Reported using DrKonqi
Comment 1 Alexander Paetzelt 2009-09-21 10:56:29 UTC
after trying it again i recognized that kate only crashed when i close the last great source-part of the document and push then emmediatly the button without doing something else... not when i just open the document, close some other source-parts and type the key.

PS the last source part is a comment, the document ist c-code
Comment 2 Christoph Cullmann 2010-02-16 12:00:54 UTC
Fixed some similar error in smart manager yesterday, can't reproduce this one, if you have some test case, we could take a second look.
Comment 3 Alexander Paetzelt 2010-02-17 09:05:46 UTC
I realize that the error occurs because of two following comments, try this:

test c/c++ - source

/* 

first testcomment

*/

/*

second testcomment

*/
Comment 4 Alexander Paetzelt 2010-02-17 09:09:01 UTC
EDIT: you have to close both comments and then push the button... (error occurs even in kwrite)
Comment 5 Milian Wolff 2010-02-17 13:46:45 UTC
works for me with recent trunk. Please try again with 4.4.0 or better yet wait for 4.4.1 since many crashes got fixed during the last week.
Comment 6 Dominik Haumann 2010-05-23 00:49:46 UTC
probably not fixed yet...

*** This bug has been marked as a duplicate of bug 236899 ***
Comment 7 Alexander Paetzelt 2010-06-01 22:49:01 UTC
works for me, too. (4.4.3 Debian)