[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#701463: kate: Kate crashes when selected text is deleted



Hello!

Am Sonntag, 24. Februar 2013 schrieben Sie:
> maybe you forgot a press of Escape here? Else you will continue to write 
> letters.

Ok, now the complete sequence to type in to get it crashed (on a new document 
or the end of an existing document):
ia<enter>b<enter>c<enter><esc>v<up><shift>+d

> > leave the cursor at the very last position and press "v", then the up
> > cursor and then "D".
> > -> crash, new report attached (seems different then the last one). On
> > another i386 laptop I got the same crash report.
> >
> > 
> >
> > Expected behaviour: last two lines should be deleted.
> 
> Ah, you are seing this only on i386 :-/
> 
> So far I couldn't reproduce it on amd64.

No, the initial bug report was from amd64.
Obove sequence was tried on amd64, see crash report attached.
So I could reproduce it on i386 and amd64.
(the backtrace seems to differ quite a lot, but that might be unrelated
to the architecture)

> Anyway, this is an upstream bug, and the only way to get it fixed is to
> file a  bug upstream.

It is already filed upstream: https://bugs.kde.org/show_bug.cgi?id=315683

But maybe it is already fixed in a later kde version and the problem only 
exists in wheezy.

> Please report it via kate's Help -> Report bug... menu item or by visiting 
> https://bugs.kde.org/ and following instructions to report a new bug.

Can you fix it for wheezy if an patch is available?

I reported it on the debian bug reporter in the hope it might be fixed in 
wheezy because it is a very annoying bug for usability.

> Whenever you open a bug report on the KDE bug tracking system, or 
> you find that the bug has been already reported on it, you can couple 
> both this Debian bug and the KDE bug together by sending a mail with 
> the text below to control@bugs.debian.org (replace KDE-BUG-URL with 
> the address of the bug report on https://bugs.kde.org/)

Thanks for the information!
Wasn't this already done by you in the last mail: "forwarded -1 
https://bugs.kde.org/show_bug.cgi?id=315683";

best regards
Application: Kate (kate), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f8bbceb7760 (LWP 6118))]

Thread 2 (Thread 0x7f8ba91ec700 (LWP 6119)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f8baa322e77 in QTWTF::TCMalloc_PageHeap::scavengerThread (this=0x7f8baa630640) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:2359
#2  0x00007f8baa322ea9 in QTWTF::TCMalloc_PageHeap::runScavengerThread (context=<optimized out>) at ../3rdparty/javascriptcore/JavaScriptCore/wtf/FastMalloc.cpp:1464
#3  0x00007f8bb9e16b50 in start_thread (arg=<optimized out>) at pthread_create.c:304
#4  0x00007f8bbc822a7d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#5  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f8bbceb7760 (LWP 6118)):
[KCrash Handler]
#6  KateLineLayout::viewLineCount (this=0x0) at ../../part/render/katelinelayout.cpp:173
#7  0x00007f8baa9b103b in KateLayoutCache::lastViewLine (this=0x0, this@entry=0x14ea9c0, realLine=21932480) at ../../part/render/katelayoutcache.cpp:461
#8  0x00007f8baa9b1089 in KateLayoutCache::viewLineCount (this=this@entry=0x14ea9c0, realLine=<optimized out>) at ../../part/render/katelayoutcache.cpp:466
#9  0x00007f8baa9b1661 in KateLayoutCache::displayViewLine (this=0x14ea9c0, virtualCursor=..., limitToVisible=true) at ../../part/render/katelayoutcache.cpp:437
#10 0x00007f8baa9fc058 in KateViewInternal::cursorToCoordinate (this=this@entry=0x1725710, cursor=..., realCursor=realCursor@entry=true, includeBorder=includeBorder@entry=false) at ../../part/view/kateviewinternal.cpp:715
#11 0x00007f8baaa00376 in KateViewInternal::inputMethodQuery (this=0x1725710, query=<optimized out>) at ../../part/view/kateviewinternal.cpp:3415
#12 0x00007f8bbc218bb4 in QXIMInputContext::update (this=<optimized out>) at inputmethod/qximinputcontext_x11.cpp:819
#13 0x00007f8bbbcb0218 in QWidget::updateMicroFocus (this=0x1725710) at kernel/qwidget.cpp:11389
#14 0x00007f8baaa009c1 in KateViewInternal::updateCursor (this=0x1725710, newCursor=..., force=<optimized out>, center=false, calledExternally=false) at ../../part/view/kateviewinternal.cpp:1857
#15 0x00007f8baaa1f20d in KateViNormalMode::commandDeleteToEOL (this=0x1834eb0) at ../../part/vimode/katevinormalmode.cpp:708
#16 0x00007f8baaa2b5b6 in KateViNormalMode::executeCommand (this=this@entry=0x1834eb0, cmd=cmd@entry=0x183ad80) at ../../part/vimode/katevinormalmode.cpp:433
#17 0x00007f8baaa2c6c0 in KateViNormalMode::handleKeypress (this=0x1834eb0, e=<optimized out>) at ../../part/vimode/katevinormalmode.cpp:362
#18 0x00007f8baaa14404 in KateViInputModeManager::handleKeypress (this=0x182e4d0, e=0x7fffa958f410) at ../../part/vimode/kateviinputmodemanager.cpp:102
#19 0x00007f8baaa05efe in keyPressEvent (e=0x7fffa958f410, this=0x1725710) at ../../part/view/kateviewinternal.cpp:2282
#20 KateViewInternal::keyPressEvent (this=0x1725710, e=0x7fffa958f410) at ../../part/view/kateviewinternal.cpp:2215
#21 0x00007f8baa9fe22b in KateViewInternal::eventFilter (this=0x1725710, obj=0x1725710, e=0x7fffa958f410) at ../../part/view/kateviewinternal.cpp:2167
#22 0x00007f8bba6e6cc6 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<optimized out>, receiver=0x1725710, event=0x7fffa958f410) at kernel/qcoreapplication.cpp:1025
#23 0x00007f8bbbc6e6dc in QApplicationPrivate::notify_helper (this=this@entry=0xc1f5e0, receiver=receiver@entry=0x1725710, e=e@entry=0x7fffa958f410) at kernel/qapplication.cpp:4552
#24 0x00007f8bbbc73704 in QApplication::notify (this=<optimized out>, receiver=0x1725710, e=0x7fffa958f410) at kernel/qapplication.cpp:3997
#25 0x00007f8bbaf14886 in KApplication::notify (this=0x7fffa9590670, receiver=0x1725710, event=0x7fffa958f410) at ../../kdeui/kernel/kapplication.cpp:311
#26 0x00007f8bba6e6b5e in QCoreApplication::notifyInternal (this=0x7fffa9590670, receiver=0x1725710, event=0x7fffa958f410) at kernel/qcoreapplication.cpp:915
#27 0x00007f8bbbd0ba9a in QKeyMapper::sendKeyEvent (keyWidget=keyWidget@entry=0x1725710, grab=grab@entry=false, type=QEvent::KeyPress, code=68, modifiers=..., text=..., autorepeat=autorepeat@entry=false, count=1, nativeScanCode=40, nativeVirtualKey=68, nativeModifiers=1) at kernel/qkeymapper_x11.cpp:1866
#28 0x00007f8bbbd0bed1 in QKeyMapperPrivate::translateKeyEvent (this=0xc62310, keyWidget=0x1725710, event=0x7fffa958fe30, grab=false) at kernel/qkeymapper_x11.cpp:1836
#29 0x00007f8bbbce8b28 in QApplication::x11ProcessEvent (this=0x7fffa9590670, event=0x7fffa958fe30) at kernel/qapplication_x11.cpp:3539
#30 0x00007f8bbbd0fbc2 in x11EventSourceDispatch (s=0xc20800, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#31 0x00007f8bb9948355 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#32 0x00007f8bb9948688 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#33 0x00007f8bb9948744 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#34 0x00007f8bba715276 in QEventDispatcherGlib::processEvents (this=0xbe9b30, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#35 0x00007f8bbbd0f83e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#36 0x00007f8bba6e58af in QEventLoop::processEvents (this=this@entry=0x7fffa9590200, flags=...) at kernel/qeventloop.cpp:149
#37 0x00007f8bba6e5b38 in QEventLoop::exec (this=0x7fffa9590200, flags=...) at kernel/qeventloop.cpp:204
#38 0x00007f8bba6eacf8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#39 0x00007f8bbcad881d in kdemain (argc=<optimized out>, argv=0x7fffa9590700) at ../../../kate/app/katemain.cpp:377
#40 0x00007f8bbc766ead in __libc_start_main (main=<optimized out>, argc=<optimized out>, ubp_av=<optimized out>, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa95907e8) at libc-start.c:228
#41 0x0000000000400761 in _start ()

Reply to: