Bug 319784 - Konsole crash on exit (not using fcitx)
Summary: Konsole crash on exit (not using fcitx)
Status: RESOLVED DUPLICATE of bug 299715
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.10.2
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
: 331309 (view as bug list)
Depends on:
Blocks:
 
Reported: 2013-05-13 13:13 UTC by Donald
Modified: 2014-02-20 13:18 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 Donald 2013-05-13 13:13:32 UTC
Application: konsole (2.10.2)
KDE Platform Version: 4.10.2
Qt Version: 4.8.4
Operating System: Linux 3.8.11-200.fc18.x86_64 x86_64
Distribution: "Fedora release 18 (Spherical Cow)"

-- Information about the crash:
- What I was doing when the application crashed:
I started the dropbox daemon (installed from dropbox.com) from the command line in Konsole. After updating the system, I quit Dropbox from the panel icon, which closed the shell and gave me a command prompt in Konsole (normal behavior so far). Then I typed "exit" and hit "enter". Konsole seemed to close normally, but the bug report dialog came up. I do not have fcitx installed. I was unable to reproduce the crash.

The crash does not seem to be reproducible.

-- Backtrace:
Application: Konsole (konsole), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
81	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7f465a095880 (LWP 10289))]

Thread 2 (Thread 0x7f464ce0a700 (LWP 10290)):
#0  0x00007fff4cd52af7 in clock_gettime ()
#1  0x00000030ff40413d in __GI_clock_gettime (clock_id=<optimized out>, tp=<optimized out>) at ../sysdeps/unix/clock_gettime.c:115
#2  0x000000310dcd18d4 in do_gettime (frac=0x7f464ce09a28, sec=0x7f464ce09a20) at tools/qelapsedtimer_unix.cpp:123
#3  qt_gettime () at tools/qelapsedtimer_unix.cpp:140
#4  0x000000310dda68ad in QTimerInfoList::updateCurrentTime (this=this@entry=0x7f4648002860) at kernel/qeventdispatcher_unix.cpp:354
#5  0x000000310dda6bf3 in QTimerInfoList::timerWait (this=0x7f4648002860, tm=...) at kernel/qeventdispatcher_unix.cpp:461
#6  0x000000310dda565c in timerSourcePrepareHelper (src=<optimized out>, timeout=0x7f464ce09b14) at kernel/qeventdispatcher_glib.cpp:136
#7  0x000000310dda5705 in timerSourcePrepare (source=<optimized out>, timeout=timeout@entry=0x7f464ce09b14) at kernel/qeventdispatcher_glib.cpp:169
#8  0x0000003100c475b8 in g_main_context_prepare (context=context@entry=0x7f46480009a0, priority=priority@entry=0x7f464ce09b78) at gmain.c:2986
#9  0x0000003100c47c4b in g_main_context_iterate (context=context@entry=0x7f46480009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3270
#10 0x0000003100c47e44 in g_main_context_iteration (context=0x7f46480009a0, may_block=1) at gmain.c:3351
#11 0x000000310dda5fa6 in QEventDispatcherGlib::processEvents (this=0x7f46480008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#12 0x000000310dd765ef in QEventLoop::processEvents (this=this@entry=0x7f464ce09cd0, flags=...) at kernel/qeventloop.cpp:149
#13 0x000000310dd76878 in QEventLoop::exec (this=0x7f464ce09cd0, flags=...) at kernel/qeventloop.cpp:204
#14 0x000000310dc78980 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#15 0x000000310dd56e1f in QInotifyFileSystemWatcherEngine::run (this=0x19db030) at io/qfilesystemwatcher_inotify.cpp:256
#16 0x000000310dc7b95c in QThreadPrivate::start (arg=0x19db030) at thread/qthread_unix.cpp:338
#17 0x00000030fec07d15 in start_thread (arg=0x7f464ce0a700) at pthread_create.c:308
#18 0x00000030fe4f248d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:114

Thread 1 (Thread 0x7f465a095880 (LWP 10289)):
[KCrash Handler]
#6  q_func (this=0x0) at ../../src/gui/kernel/qwidget_p.h:362
#7  QWidgetPrivate::assignedInputContext (this=0x0) at kernel/qwidget.cpp:426
#8  0x0000003113c07c99 in QWidgetPrivate::inputContext (this=<optimized out>) at kernel/qwidget.cpp:439
#9  0x0000003113c66d43 in QKeyMapperPrivate::translateKeyEvent (this=0x1765860, keyWidget=0x18ef6d0, event=0x7fff4cc0acb0, grab=false) at kernel/qkeymapper_x11.cpp:1727
#10 0x0000003113c446d8 in QApplication::x11ProcessEvent (this=0x7fff4cc0b1d0, event=0x7fff4cc0acb0) at kernel/qapplication_x11.cpp:3553
#11 0x0000003113c6aa5c in x11EventSourceDispatch (s=s@entry=0x1729870, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#12 0x0000003100c47a55 in g_main_dispatch (context=0x1728600) at gmain.c:2715
#13 g_main_context_dispatch (context=context@entry=0x1728600) at gmain.c:3219
#14 0x0000003100c47d88 in g_main_context_iterate (context=context@entry=0x1728600, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290
#15 0x0000003100c47e44 in g_main_context_iteration (context=0x1728600, may_block=1) at gmain.c:3351
#16 0x000000310dda5fa6 in QEventDispatcherGlib::processEvents (this=0x167cc80, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#17 0x0000003113c6a73e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#18 0x000000310dd765ef in QEventLoop::processEvents (this=this@entry=0x7fff4cc0b080, flags=...) at kernel/qeventloop.cpp:149
#19 0x000000310dd76878 in QEventLoop::exec (this=0x7fff4cc0b080, flags=...) at kernel/qeventloop.cpp:204
#20 0x000000310dd7b708 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221
#21 0x0000003104c16fd5 in kdemain (argc=1, argv=0x7fff4cc0b318) at /usr/src/debug/konsole-4.10.2/src/main.cpp:86
#22 0x00000030fe421a05 in __libc_start_main (main=0x400840 <main(int, char**)>, argc=1, ubp_av=0x7fff4cc0b318, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fff4cc0b308) at libc-start.c:225
#23 0x0000000000400871 in _start ()

Possible duplicates by query: bug 314488, bug 302715.

Reported using DrKonqi
Comment 1 Kurt Hindenburg 2014-02-20 13:16:47 UTC
*** Bug 331309 has been marked as a duplicate of this bug. ***
Comment 2 Kurt Hindenburg 2014-02-20 13:18:08 UTC

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