Bug 205026 - Crash on saving document using Ctrl+S
Summary: Crash on saving document using Ctrl+S
Status: RESOLVED DUPLICATE of bug 205069
Alias: None
Product: kate
Classification: Applications
Component: kwrite (show other bugs)
Version: unspecified
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: KWrite Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-25 00:54 UTC by Bernhard Friedreich
Modified: 2009-08-25 23:53 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 Bernhard Friedreich 2009-08-25 00:54:12 UTC
Application: kwrite (4.3.65 (KDE 4.3.65 (KDE 4.4 >= 20090820)))
KDE Version: 4.3.65 (KDE 4.3.65 (KDE 4.4 >= 20090820))
Qt Version: 4.5.1
Operating System: Linux 2.6.30-ARCH i686
Distribution: "(none)"

What I was doing when the application crashed:
KWrite crashed after creating a new document (Alt + F2 kwrite), pasting some content from the clipboard and pressing Ctrl + S

I'm using Qt 4.5.2 and daily kde builds provided from an external repo (build from 24.8)

 -- Backtrace:
Application: KWrite (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xb7939fde in KFileDialog::KFileDialog () from /usr/lib/libkio.so.5
#7  0xb793538e in KEncodingFileDialog::KEncodingFileDialog () from /usr/lib/libkio.so.5
#8  0xb7935a97 in KEncodingFileDialog::getSaveUrlAndEncoding () from /usr/lib/libkio.so.5
#9  0xb2029981 in KateDocument::documentSaveAs () from /usr/lib/kde4/katepart.so
#10 0xb201e28e in KateDocument::documentSave () from /usr/lib/kde4/katepart.so
#11 0xb2033f37 in KateDocument::qt_metacall () from /usr/lib/kde4/katepart.so
#12 0xb7f0581c in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#13 0xb7f05c68 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#14 0xb690dfb1 in QAction::triggered () from /usr/lib/libQtGui.so.4
#15 0xb690f532 in QAction::activate () from /usr/lib/libQtGui.so.4
#16 0xb6912018 in QAction::event () from /usr/lib/libQtGui.so.4
#17 0xb7364a23 in KAction::event () from /usr/lib/libkdeui.so.5
#18 0xb6914554 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#19 0xb691bc4c in QApplication::notify () from /usr/lib/libQtGui.so.4
#20 0xb74517ea in KApplication::notify () from /usr/lib/libkdeui.so.5
#21 0xb7eefb4b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#22 0xb694ce0d in ?? () from /usr/lib/libQtGui.so.4
#23 0xb694ec7e in ?? () from /usr/lib/libQtGui.so.4
#24 0xb691cf55 in QApplication::notify () from /usr/lib/libQtGui.so.4
#25 0xb74517ea in KApplication::notify () from /usr/lib/libkdeui.so.5
#26 0xb7eefb4b in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#27 0xb691542e in ?? () from /usr/lib/libQtGui.so.4
#28 0xb69aea2d in ?? () from /usr/lib/libQtGui.so.4
#29 0xb69b0ebc in ?? () from /usr/lib/libQtGui.so.4
#30 0xb6987757 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#31 0xb69b2982 in ?? () from /usr/lib/libQtGui.so.4
#32 0xb64d9d98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#33 0xb64dd3e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#34 0xb64dd513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#35 0xb7f1a4ec in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#36 0xb69b20b5 in ?? () from /usr/lib/libQtGui.so.4
#37 0xb7eee0f9 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#38 0xb7eee542 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#39 0xb7ef089f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#40 0xb69143d7 in QApplication::exec () from /usr/lib/libQtGui.so.4
#41 0xb48b9bb0 in kdemain () from /usr/lib/libkdeinit4_kwrite.so
#42 0x0804e062 in _start ()

Reported using DrKonqi
Comment 1 Anne-Marie Mahfouf 2009-08-25 16:49:24 UTC
No crash here, I did exactly your steps.

Did it happen just recently on trunk? Does it happen with other applications too? Can you get a better backtrace?
Comment 2 Dario Andres 2009-08-25 23:53:21 UTC
Merging with bug 205069 as the root cause is likely the same. Thanks

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