Bug 324735 - When I installed VirtualBox 4.2.18 GuestAdditions, konsole crashed
Summary: When I installed VirtualBox 4.2.18 GuestAdditions, konsole crashed
Status: RESOLVED DUPLICATE of bug 323867
Alias: None
Product: konsole
Classification: Applications
Component: general (show other bugs)
Version: 2.10.5
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Konsole Developer
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2013-09-10 06:25 UTC by ItSANgo
Modified: 2013-10-01 13:05 UTC (History)
1 user (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 ItSANgo 2013-09-10 06:25:21 UTC
Application: konsole (2.10.5)
KDE Platform Version: 4.10.5 "release 1"
Qt Version: 4.8.4
Operating System: Linux 3.7.10-1.16-desktop x86_64
Distribution: "openSUSE 12.3 (x86_64)"

-- Information about the crash:
- What I was doing when the application crashed:

When I installed VirtualBox 4.2.18 GuestAdditions, konsole crashed ,

- Unusual behavior I noticed:

I installed VirtualBox 4.2.18 GuestAdditions .

- Custom settings of the application:

VirtualBox 4.2.18 GuestAdditions .

-- Backtrace:
Application: Konsole (kdeinit4), signal: Segmentation fault
Using host libthread_db library "/lib64/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f1a6179d780 (LWP 2745))]

Thread 2 (Thread 0x7f1a44df1700 (LWP 2746)):
#0  0x00007f1a5bd6881a in g_mutex_get_impl (mutex=0x7f1a400009a0) at gthread-posix.c:120
#1  0x00007f1a5bd68a99 in g_mutex_unlock (mutex=mutex@entry=0x7f1a400009a0) at gthread-posix.c:229
#2  0x00007f1a5bd2b32b in g_main_context_prepare (context=context@entry=0x7f1a400009a0, priority=priority@entry=0x7f1a44df0c78) at gmain.c:2984
#3  0x00007f1a5bd2b9cb in g_main_context_iterate (context=context@entry=0x7f1a400009a0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3270
#4  0x00007f1a5bd2bbc4 in g_main_context_iteration (context=0x7f1a400009a0, may_block=1) at gmain.c:3351
#5  0x00007f1a604312e6 in QEventDispatcherGlib::processEvents (this=0x7f1a400008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#6  0x00007f1a60401adf in QEventLoop::processEvents (this=this@entry=0x7f1a44df0dd0, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f1a60401d68 in QEventLoop::exec (this=0x7f1a44df0dd0, flags=...) at kernel/qeventloop.cpp:204
#8  0x00007f1a603040f0 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:542
#9  0x00007f1a603e229f in QInotifyFileSystemWatcherEngine::run (this=0x1277440) at io/qfilesystemwatcher_inotify.cpp:256
#10 0x00007f1a603070cc in QThreadPrivate::start (arg=0x1277440) at thread/qthread_unix.cpp:338
#11 0x00007f1a60070e0f in start_thread (arg=0x7f1a44df1700) at pthread_create.c:308
#12 0x00007f1a5ede77dd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113

Thread 1 (Thread 0x7f1a6179d780 (LWP 2745)):
[KCrash Handler]
#5  q_func (this=0x0) at ../../src/gui/kernel/qwidget_p.h:362
#6  QWidgetPrivate::assignedInputContext (this=0x0) at kernel/qwidget.cpp:426
#7  0x00007f1a5f5cdf39 in QWidgetPrivate::inputContext (this=<optimized out>) at kernel/qwidget.cpp:439
#8  0x00007f1a5f62d233 in QKeyMapperPrivate::translateKeyEvent (this=0xdcd210, keyWidget=0x25e97a0, event=0x7fff84045950, grab=false) at kernel/qkeymapper_x11.cpp:1724
#9  0x00007f1a5f60a9f8 in QApplication::x11ProcessEvent (this=0x7fff84045e70, event=0x7fff84045950) at kernel/qapplication_x11.cpp:3543
#10 0x00007f1a5f630fa2 in x11EventSourceDispatch (s=s@entry=0xea96d0, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146
#11 0x00007f1a5bd2b7d5 in g_main_dispatch (context=0xeaa110) at gmain.c:2715
#12 g_main_context_dispatch (context=context@entry=0xeaa110) at gmain.c:3219
#13 0x00007f1a5bd2bb08 in g_main_context_iterate (context=context@entry=0xeaa110, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at gmain.c:3290
#14 0x00007f1a5bd2bbc4 in g_main_context_iteration (context=0xeaa110, may_block=1) at gmain.c:3351
#15 0x00007f1a604312c6 in QEventDispatcherGlib::processEvents (this=0xea9040, flags=...) at kernel/qeventdispatcher_glib.cpp:424
#16 0x00007f1a5f630c1e in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#17 0x00007f1a60401adf in QEventLoop::processEvents (this=this@entry=0x7fff84045d20, flags=...) at kernel/qeventloop.cpp:149
#18 0x00007f1a60401d68 in QEventLoop::exec (this=0x7fff84045d20, flags=...) at kernel/qeventloop.cpp:204
#19 0x00007f1a60406a08 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1218
#20 0x00007f1a4e256a25 in kdemain (argc=1, argv=0xde6d60) at /usr/src/debug/konsole-4.10.5/src/main.cpp:86
#21 0x000000000040889a in _start ()

Possible duplicates by query: bug 323867, bug 319784, bug 314488, bug 302715, bug 299715.

Reported using DrKonqi
Comment 1 Kurt Hindenburg 2013-10-01 13:05:27 UTC

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