Bug 304679 - Yakuake randomly crashes when closing a tab
Summary: Yakuake randomly crashes when closing a tab
Status: RESOLVED FIXED
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Fedora RPMs Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-06 17:39 UTC by Romain D.
Modified: 2018-07-31 11:40 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Romain D. 2012-08-06 17:39:32 UTC
Application: yakuake (2.9.8)
KDE Platform Version: 4.9.00
Qt Version: 4.8.2
Operating System: Linux 3.5.0-2.fc17.x86_64 x86_64
Distribution (Platform): Fedora RPMs

-- Information about the crash:
- What I was doing when the application crashed:
I was closing a tab using the keyboard shortcut, nothing fancy.
I installed a few GBs of debug symbols in order to help tracking this one, hoping it helps :)

The crash can be reproduced some of the time.

-- Backtrace:
Application: Yakuake (yakuake), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
82	T_PSEUDO (SYSCALL_SYMBOL, SYSCALL_NAME, SYSCALL_NARGS)
[Current thread is 1 (Thread 0x7fd8b2f0c880 (LWP 17759))]

Thread 2 (Thread 0x7fd8a5f37700 (LWP 18392)):
#0  0x00000036e420e0ad in read () at ../sysdeps/unix/syscall-template.S:82
#1  0x0000003f1a282a5f in read (__nbytes=16, __buf=0x7fd8a5f36b30, __fd=<optimized out>) at /usr/include/bits/unistd.h:45
#2  g_wakeup_acknowledge (wakeup=0x7fd8a0001fb0) at gwakeup.c:212
#3  0x0000003f1a2474e9 in g_main_context_check (context=context@entry=0x7fd8980009a0, max_priority=2147483647, fds=fds@entry=0x7fd8980029b0, n_fds=n_fds@entry=1) at gmain.c:2980
#4  0x0000003f1a247902 in g_main_context_iterate (context=context@entry=0x7fd8980009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3143
#5  0x0000003f1a247a84 in g_main_context_iteration (context=0x7fd8980009a0, may_block=1) at gmain.c:3207
#6  0x0000003f1afa4506 in QEventDispatcherGlib::processEvents (this=0x7fd8980008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#7  0x0000003f1af7513f in QEventLoop::processEvents (this=this@entry=0x7fd8a5f36cf0, flags=...) at kernel/qeventloop.cpp:149
#8  0x0000003f1af753c8 in QEventLoop::exec (this=0x7fd8a5f36cf0, flags=...) at kernel/qeventloop.cpp:204
#9  0x0000003f1ae78650 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#10 0x0000003f1af55b4f in QInotifyFileSystemWatcherEngine::run (this=0x1c44730) at io/qfilesystemwatcher_inotify.cpp:248
#11 0x0000003f1ae7b5eb in QThreadPrivate::start (arg=0x1c44730) at thread/qthread_unix.cpp:307
#12 0x00000036e4207d14 in start_thread (arg=0x7fd8a5f37700) at pthread_create.c:309
#13 0x0000003a736f197d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:115

Thread 1 (Thread 0x7fd8b2f0c880 (LWP 17759)):
[KCrash Handler]
#6  q_func (this=0x0) at ../../src/gui/kernel/qwidget_p.h:362
#7  QWidgetPrivate::assignedInputContext (this=0x0) at kernel/qwidget.cpp:422
#8  0x0000003f1cc079e9 in QWidgetPrivate::inputContext (this=<optimized out>) at kernel/qwidget.cpp:435
#9  0x0000003f1cc668f3 in QKeyMapperPrivate::translateKeyEvent (this=0x1785fb0, keyWidget=0x2174220, event=0x7fff2149abb0, grab=false) at kernel/qkeymapper_x11.cpp:1724
#10 0x0000003f1cc443f8 in QApplication::x11ProcessEvent (this=0x7fff2149b0c0, event=0x7fff2149abb0) at kernel/qapplication_x11.cpp:3539
#11 0x0000003f1cc6a60c in x11EventSourceDispatch (s=s@entry=0x1741600, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:148
#12 0x0000003f1a247695 in g_main_dispatch (context=0x1741240) at gmain.c:2539
#13 g_main_context_dispatch (context=context@entry=0x1741240) at gmain.c:3075
#14 0x0000003f1a2479c8 in g_main_context_iterate (context=context@entry=0x1741240, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3146
#15 0x0000003f1a247a84 in g_main_context_iteration (context=0x1741240, may_block=1) at gmain.c:3207
#16 0x0000003f1afa44e6 in QEventDispatcherGlib::processEvents (this=0x1710a70, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#17 0x0000003f1cc6a2ee in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:207
#18 0x0000003f1af7513f in QEventLoop::processEvents (this=this@entry=0x7fff2149af80, flags=...) at kernel/qeventloop.cpp:149
#19 0x0000003f1af753c8 in QEventLoop::exec (this=0x7fff2149af80, flags=...) at kernel/qeventloop.cpp:204
#20 0x0000003f1af7a1b8 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1187
#21 0x000000000041255b in main (argc=3, argv=0x7fff2149b208) at /usr/src/debug/yakuake-2.9.8/app/main.cpp:73

Reported using DrKonqi
Comment 1 Christoph Feck 2014-04-20 09:34:34 UTC
Could you please check if you are running an "input method" program, such as "ibus" or "fcitx"? This could be bug 299715.
Comment 2 Romain D. 2014-04-20 10:58:15 UTC
Oh, good catch!
I use ibus actually.
Comment 3 Romain D. 2014-04-20 11:02:50 UTC
(In reply to comment #2)
Versions being used (fedora 20 + testing):

ibus-1.5.6-2.fc20.x86_64
ibus-gtk2-1.5.6-2.fc20.x86_64
ibus-gtk3-1.5.6-2.fc20.x86_64
ibus-libs-1.5.6-2.fc20.x86_64
ibus-pinyin-1.5.0-5.fc20.x86_64
ibus-rawcode-1.3.2-3.fc20.x86_64
ibus-setup-1.5.6-2.fc20.noarch
ibus-wayland-1.5.6-2.fc20.x86_64
Comment 4 Alexander Mentyu 2018-07-31 11:36:14 UTC
Cannot reproduce

Distribution: Netrunner Rolling
Kernel: 4.18.0-1-MANJARO
Plasma: 5.13.3
Apps: 18.04.3
Qt: 5.11.1
Frameworks: 5.48.0
Wayland: 1.15.0
Graphics:  Card-1: Intel Haswell-ULT Integrated Graphics 
           driver: i915 v: kernel bus ID: 00:02.0 
           chip ID: 8086:0a16 
           Display: wayland server: X.Org 1.20.0 
           driver: intel unloaded: modesetting alternate: fbdev,vesa 
           compositor: kwin wayland tty: N/A 
           OpenGL: renderer: Mesa DRI Intel Haswell Mobile 
           v:4.5 Mesa 18.1.5 compat-v: 3.0 direct render: Yes 
ibus 1.5.18-1

Is this still a relevant bug?
Comment 5 Romain D. 2018-07-31 11:40:40 UTC
Old memories :)

Must have been solved eons ago, closed!