Bug 259531 - Konversation crash when i press the hotkey ctrl+w
Summary: Konversation crash when i press the hotkey ctrl+w
Status: RESOLVED DUPLICATE of bug 253994
Alias: None
Product: konversation
Classification: Applications
Component: general (show other bugs)
Version: 1.2.3
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Konversation Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-11 17:03 UTC by remo.piombo
Modified: 2011-06-27 11:20 UTC (History)
1 user (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 remo.piombo 2010-12-11 17:03:44 UTC
Application: konversation (1.2.3)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-25-generic i686
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
When i press ctrl+w for close a query tab it crash.
This is the first time that happen after a while. The only thing that i do before is to activate e kde-compatibility plugin.

The crash does not seem to be reproducible.

 -- Backtrace:
Application: Konversation (konversation), signal: Segmentation fault
[Current thread is 1 (Thread 0xb77ab9b0 (LWP 3024))]

Thread 2 (Thread 0xb4f33b70 (LWP 3027)):
#0  0x007afe16 in clock_gettime () from /lib/tls/i686/cmov/librt.so.1
#1  0x086cc6fb in qt_gettime () at kernel/qcore_unix.cpp:111
#2  0x086d1825 in QTimerInfoList::updateCurrentTime (this=0x9fb1c2c) at kernel/qeventdispatcher_unix.cpp:340
#3  0x086d186a in QTimerInfoList::timerWait (this=0x9fb1c2c, tm=...) at kernel/qeventdispatcher_unix.cpp:443
#4  0x086cf818 in timerSourcePrepareHelper (src=<value optimized out>, timeout=0xb4f3305c) at kernel/qeventdispatcher_glib.cpp:136
#5  0x086cf8a5 in timerSourcePrepare (source=0x0, timeout=0x7b3ff4) at kernel/qeventdispatcher_glib.cpp:169
#6  0x018a6aca in g_main_context_prepare () from /lib/libglib-2.0.so.0
#7  0x018a6ee9 in ?? () from /lib/libglib-2.0.so.0
#8  0x018a74b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#9  0x086cf60f in QEventDispatcherGlib::processEvents (this=0x9fb83b0, flags=...) at kernel/qeventdispatcher_glib.cpp:414
#10 0x086a2059 in QEventLoop::processEvents (this=0xb4f33220, flags=) at kernel/qeventloop.cpp:149
#11 0x086a24aa in QEventLoop::exec (this=0xb4f33220, flags=...) at kernel/qeventloop.cpp:201
#12 0x0859e5a8 in QThread::exec (this=0x9fe7d88) at thread/qthread.cpp:487
#13 0x08681c1b in QInotifyFileSystemWatcherEngine::run (this=0x9fe7d88) at io/qfilesystemwatcher_inotify.cpp:248
#14 0x085a132e in QThreadPrivate::start (arg=0x9fe7d88) at thread/qthread_unix.cpp:248
#15 0x007bc96e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#16 0x02c6fa4e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb77ab9b0 (LWP 3024)):
[KCrash Handler]
#6  0x00000009 in ?? ()
#7  0x0337e60a in x11EventSourceDispatch (s=0x9dd0640, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#8  0x018a35e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#9  0x018a72d8 in ?? () from /lib/libglib-2.0.so.0
#10 0x018a74b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#11 0x086cf5d5 in QEventDispatcherGlib::processEvents (this=0x9da2a60, flags=...) at kernel/qeventdispatcher_glib.cpp:412
#12 0x0337e135 in QGuiEventDispatcherGlib::processEvents (this=0x9da2a60, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#13 0x086a2059 in QEventLoop::processEvents (this=0xbfa2a814, flags=) at kernel/qeventloop.cpp:149
#14 0x086a24aa in QEventLoop::exec (this=0xbfa2a814, flags=...) at kernel/qeventloop.cpp:201
#15 0x086a669f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#16 0x032be577 in QApplication::exec () at kernel/qapplication.cpp:3579
#17 0x080a7148 in main (argc=5, argv=0xbfa2ace4) at ../../src/main.cpp:100

This bug may be a duplicate of or related to bug 253994.

Possible duplicates by query: bug 258753, bug 257262, bug 257114, bug 256777, bug 256278.

Reported using DrKonqi
Comment 1 Eike Hein 2011-06-27 11:20:32 UTC

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