Version: 2.2 (using KDE 4.5.90) OS: Linux KSpread crashes if I type the ẞ directly in a table Reproducible: Always Steps to Reproduce: use the neo2 keyboard layout open KSpread with any document click in the tabel push ẞ (ẞ=shift+
Hi Marian, Kspread 2.3 has just come out. Can you check if the bug is also present in that version? A lot has happened since version 2.2 and it's not unlikely that the bug is already fixed.
the bug is in 2.3
Cannot reproduce with Calligra master aka upcoming 2.4. If you can still reproduce it *please* reopen the report and *please* attach a backtrace so we are able to see where it crashes and have at least a pointer to what it could be related else the report is not useful at all if we cannot reproduce the crash :-( Lot of thanks in advance!
version 2.3.3 OS: Linux aptosid backtrace #0 QTextEngine::justify (this=0xa289c0, line=...) at text/qtextengine.cpp:1862 #1 0x00007ffff6c6ed6e in alignLine (eng=0xa289c0, line=...) at text/qtextlayout.cpp:87 #2 0x00007ffff6c73546 in QTextLine::cursorToX (this=0x7fffff804010, cursorPos=0x7fffff804058, edge=QTextLine::Leading) at text/qtextlayout.cpp:2393 #3 0x00007ffff6c57b1c in cursorToX (edge=QTextLine::Leading, cursorPos=3, this=0x7fffff804010) at ../../include/QtGui/../../src/gui/text/qtextlayout.h:219 #4 QTextControlPrivate::rectForPosition (this=0xc32a10, position=<optimized out>) at text/qtextcontrol.cpp:1349 #5 0x00007ffff6c5d1cc in QTextControl::selectionRect (this=<optimized out>, cursor=...) at text/qtextcontrol.cpp:1397 #6 0x00007ffff6c5d924 in QTextControl::selectionRect (this=<optimized out>) at text/qtextcontrol.cpp:1480 #7 0x00007ffff6c5dda4 in QTextControlPrivate::repaintOldAndNewSelection (this=0xc32a10, oldSelection=...) at text/qtextcontrol.cpp:567 #8 0x00007ffff6c5fc9b in repaintSelection (this=0xc32a10) at text/qtextcontrol_p_p.h:103 #9 QTextControlPrivate::keyPressEvent (this=0xc32a10, e=0x7fffffffd240) at text/qtextcontrol.cpp:1189 #10 0x00007ffff6c6186b in QTextControl::processEvent (this=<optimized out>, e=0x7fffffffd240, matrix=..., contextWidget=0x10e95f0) at text/qtextcontrol.cpp:924 #11 0x00007ffff6c57996 in QTextControl::processEvent (this=0x189f250, e=0x7fffffffd240, coordinateOffset=..., contextWidget=0x10e95f0) at text/qtextcontrol.cpp:884 #12 0x00007ffff6e7ea60 in sendControlEvent (e=0x7fffffffd240, this=0xa50570) at widgets/qtextedit_p.h:99 #13 QTextEdit::keyPressEvent (this=<optimized out>, e=0x7fffffffd240) at widgets/qtextedit.cpp:1296 #14 0x00007ffff3422687 in keyPressEvent (event=0x7fffffffd240, this=0x78db20) at ../../kdeui/widgets/ktextedit.cpp:1078 #15 KTextEdit::keyPressEvent (this=0x78db20, event=0x7fffffffd240) at ../../kdeui/widgets/ktextedit.cpp:1069 #16 0x00007fffe1b0320b in ?? () from /usr/lib/libkspreadcommon.so.8 #17 0x00007ffff6a7311a in QWidget::event (this=0x78db20, event=0x7fffffffd240) at kernel/qwidget.cpp:8294 #18 0x00007ffff6e14156 in QFrame::event (this=0x78db20, e=0x7fffffffd240) at widgets/qframe.cpp:557 #19 0x00007ffff6e95783 in QAbstractScrollArea::event (this=0x78db20, e=0x7fffffffd240) at widgets/qabstractscrollarea.cpp:996 #20 0x00007ffff6e81f20 in QTextEdit::event (this=0x78db20, e=0x7fffffffd240) at widgets/qtextedit.cpp:1070 #21 0x00007ffff6a229f4 in notify_helper (e=0x7fffffffd240, receiver=0x78db20, this=0x63f720) at kernel/qapplication.cpp:4467 #22 QApplicationPrivate::notify_helper (this=0x63f720, receiver=0x78db20, e=0x7fffffffd240) at kernel/qapplication.cpp:4439 #23 0x00007ffff6a27f76 in QApplication::notify (this=<optimized out>, receiver=<optimized out>, e=0x7fffffffd240) at kernel/qapplication.cpp:3926 #24 0x00007ffff3338b96 in KApplication::notify (this=0x7fffffffe100, receiver=0x78db20, event=0x7fffffffd240) at ../../kdeui/kernel/kapplication.cpp:311 #25 0x00007ffff600116c in QCoreApplication::notifyInternal (this=0x7fffffffe100, receiver=0x78db20, event=0x7fffffffd240) at kernel/qcoreapplication.cpp:731 #26 0x00007fffe1b06c99 in KSpread::CellToolBase::keyPressEvent(QKeyEvent*) () from /usr/lib/libkspreadcommon.so.8 #27 0x00007ffff6a7311a in QWidget::event (this=0x11f2e50, event=0x7fffffffd240) at kernel/qwidget.cpp:8294 #28 0x00007ffff6a229f4 in notify_helper (e=0x7fffffffd240, receiver=0x11f2e50, this=0x63f720) at kernel/qapplication.cpp:4467 #29 QApplicationPrivate::notify_helper (this=0x63f720, receiver=0x11f2e50, e=0x7fffffffd240) at kernel/qapplication.cpp:4439 #30 0x00007ffff6a27f76 in QApplication::notify (this=<optimized out>, receiver=<optimized out>, e=0x7fffffffd240) at kernel/qapplication.cpp:3926 #31 0x00007ffff3338b96 in KApplication::notify (this=0x7fffffffe100, receiver=0x78db20, event=0x7fffffffd240) at ../../kdeui/kernel/kapplication.cpp:311 #32 0x00007ffff600116c in QCoreApplication::notifyInternal (this=0x7fffffffe100, receiver=0x78db20, event=0x7fffffffd240) at kernel/qcoreapplication.cpp:731
Lot of thanks Marian! Now to the backtrace; probably we are dealing here with a dangling pointer of a QTextDocument used to paint rich-text in a cell? Lot of changes where done in the richText-area since 2.3. So, it's maybe fixed meanwhile what would explain why I cannot reproduce the crash. But then maybe it's a timing-issue and therefore I cannot reproduce. In any case it would be useful if you can retest with 2.4 (if apttosid ships with one of our 2.4 alpha/beta releases? else there is the option to build from source - see http://community.kde.org/Calligra/Building ).
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
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!
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!