Bug 173307 - Kate crashed when pasting (from X selection) text in a new document
Summary: Kate crashed when pasting (from X selection) text in a new document
Status: RESOLVED DUPLICATE of bug 171027
Alias: None
Product: kate
Classification: Applications
Component: general (other bugs)
Version First Reported In: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-10-22 16:31 UTC by Raphael Leplae
Modified: 2008-12-15 11:50 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Raphael Leplae 2008-10-22 16:31:40 UTC
Version:           3.1.1 (using 4.1.1 (KDE 4.1.0 (4.1 >= 20080722)) "release 26.3", KDE:KDE4:Factory:Desktop / openSUSE_11.0)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.25.16-0.1-default

Hi,

Kate crahed when pasting in a new document one piece of text from the X selection (middle click). I couldn't reproduce the bug.
Here is the backtrace:

Application: Kate (kate), signal SIGSEGV
[?1034h(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 0x7fc4992e1700 (LWP 3621)]
(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)
(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)
(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)
[KCrash handler]
#5  0x00007fc493577fd2 in QTextLine::cursorToX () from /usr/lib64/libQtGui.so.4
#6  0x00007fc48def790d in ?? () from /usr/lib64/kde4/katepart.so
#7  0x00007fc48def7ab1 in ?? () from /usr/lib64/kde4/katepart.so
#8  0x00007fc49384d7b5 in ?? () from /usr/lib64/libQtGui.so.4
#9  0x00007fc4933f71aa in QWidget::updateMicroFocus ()
   from /usr/lib64/libQtGui.so.4
#10 0x00007fc48def9ec0 in ?? () from /usr/lib64/kde4/katepart.so
#11 0x00007fc48defd8ab in ?? () from /usr/lib64/kde4/katepart.so
#12 0x00007fc48de807f4 in ?? () from /usr/lib64/kde4/katepart.so
#13 0x00007fc48de85297 in ?? () from /usr/lib64/kde4/katepart.so
#14 0x00007fc48def9221 in ?? () from /usr/lib64/kde4/katepart.so
#15 0x00007fc48defa758 in ?? () from /usr/lib64/kde4/katepart.so
#16 0x00007fc48def8e7d in ?? () from /usr/lib64/kde4/katepart.so
#17 0x00007fc496114188 in QCoreApplicationPrivate::sendThroughObjectEventFilters () from /usr/lib64/libQtCore.so.4
#18 0x00007fc4933b58fc in QApplicationPrivate::notify_helper ()
   from /usr/lib64/libQtGui.so.4
#19 0x00007fc4933bcc41 in QApplication::notify () from /usr/lib64/libQtGui.so.4
#20 0x00007fc497576d1b in KApplication::notify () from /usr/lib64/libkdeui.so.5
#21 0x00007fc496114e9c in QCoreApplication::notifyInternal ()
   from /usr/lib64/libQtCore.so.4
#22 0x00007fc493433014 in ?? () from /usr/lib64/libQtGui.so.4
#23 0x00007fc4934350ef in ?? () from /usr/lib64/libQtGui.so.4
#24 0x00007fc4934122a5 in QApplication::x11ProcessEvent ()
   from /usr/lib64/libQtGui.so.4
#25 0x00007fc49343669c in ?? () from /usr/lib64/libQtGui.so.4
#26 0x00007fc4961137f2 in QEventLoop::processEvents ()
   from /usr/lib64/libQtCore.so.4
#27 0x00007fc496113985 in QEventLoop::exec () from /usr/lib64/libQtCore.so.4
#28 0x00007fc496115a25 in QCoreApplication::exec ()
   from /usr/lib64/libQtCore.so.4
#29 0x00007fc498efee9d in kdemain () from /usr/lib64/libkdeinit4_kate.so
#30 0x00007fc491b41436 in __libc_start_main () from /lib64/libc.so.6
#31 0x00000000004008c9 in _start ()
#0  0x00007fc491bc5230 in nanosleep () from /lib64/libc.so.6
Comment 1 Dario Andres 2008-11-29 17:39:23 UTC
Have you experienced this bug again with a recent KDE version? (4.1.3, 4.2beta1 / 4.2svn)
Comment 2 Dario Andres 2008-12-10 12:48:23 UTC
This may be related to bug 171027.
Comment 3 Dominik Haumann 2008-12-15 11:50:17 UTC
yes, probably duplicate of bug #171027.

*** This bug has been marked as a duplicate of bug 171027 ***