| Summary: | Konsole crash | ||
|---|---|---|---|
| Product: | [Applications] konsole | Reporter: | Mark van Rossum <mark.vanrossum> |
| Component: | general | Assignee: | Konsole Developer <konsole-devel> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | rewarp, Samuele.Kaplun, zibo86 |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 3.0.1 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Mark van Rossum
2015-02-13 22:22:37 UTC
*** Bug 347883 has been marked as a duplicate of this bug. *** Could be related. Konsole throws up a segfault error every single time after closing. It's really annoying. Konsole Version 15.04.0 Using KDE Frameworks 5.11.0 Application: konsole (konsole), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [KCrash Handler] #6 QString::~QString (this=0x15fc3f8, __in_chrg=<optimized out>) at ../../src/corelib/thread/qbasicatomic.h:110 #7 0x00007f16e06a9c59 in QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x15fc3e0, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1049 #8 0x00007f16e06a9ea9 in QDBusConnectionPrivate::~QDBusConnectionPrivate (this=0x15fc3e0, __in_chrg=<optimized out>) at qdbusintegrator.cpp:1067 #9 0x00007f16e069de65 in QDBusConnectionManager::~QDBusConnectionManager (this=0x7f16e0907ca0 <(anonymous namespace)::Q_QGS__q_manager::innerFunction()::holder>, __in_chrg=<optimized out>) at qdbusconnection.cpp:98 #10 0x00007f16e069df19 in (anonymous namespace)::Q_QGS__q_manager::innerFunction()::Holder::~Holder() () at qdbusconnection.cpp:59 #11 0x00007f16e5f54bf9 in __run_exit_handlers () from /lib64/libc.so.6 #12 0x00007f16e5f54c45 in exit () from /lib64/libc.so.6 #13 0x00007f16e5f3eb0c in __libc_start_main () from /lib64/libc.so.6 #14 0x00000000004007ee in _start () at ../sysdeps/x86_64/start.S:122 I also experienced this bug. Like the reporter of bug 347883 mentioned, I experienced the crash shortly after playing with the display settings KCM. It looks like the bug in in Qt though... Thread 1 (Thread 0x7fbadc2a6940 (LWP 1936)): [KCrash Handler] #6 0x00007fbadbe829d2 in QXcbClipboard::requestor (this=this@entry=0x22209a0) at qxcbclipboard.cpp:481 #7 0x00007fbadbe840ef in QXcbClipboard::handleSelectionRequest (this=0x22209a0, req=req@entry=0x7fbad4003520) at qxcbclipboard.cpp:610 #8 0x00007fbadbe89fd1 in QXcbConnection::handleXcbEvent (this=this@entry=0x21fdd70, event=event@entry=0x7fbad4003520) at qxcbconnection.cpp:922 #9 0x00007fbadbe8ac73 in QXcbConnection::processXcbEvents (this=0x21fdd70) at qxcbconnection.cpp:1303 #10 0x00007fbaeacf81c1 in QObject::event (this=0x21fdd70, e=<optimized out>) at kernel/qobject.cpp:1245 #11 0x00007fbaeb594b8c in QApplicationPrivate::notify_helper (this=this@entry=0x21f8550, receiver=receiver@entry=0x21fdd70, e=e@entry=0x7fbad40043f0) at kernel/qapplication.cpp:3720 #12 0x00007fbaeb59a230 in QApplication::notify (this=0x7ffcc4f7dd10, receiver=0x21fdd70, e=0x7fbad40043f0) at kernel/qapplication.cpp:3503 #13 0x00007fbaeacc6a8b in QCoreApplication::notifyInternal (this=0x7ffcc4f7dd10, receiver=0x21fdd70, event=event@entry=0x7fbad40043f0) at kernel/qcoreapplication.cpp:935 #14 0x00007fbaeacc8bc7 in QCoreApplication::sendEvent (event=0x7fbad40043f0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:228 #15 QCoreApplicationPrivate::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0, data=0x219fe00) at kernel/qcoreapplication.cpp:1552 #16 0x00007fbaeacc90f8 in QCoreApplication::sendPostedEvents (receiver=receiver@entry=0x0, event_type=event_type@entry=0) at kernel/qcoreapplication.cpp:1410 #17 0x00007fbaead1da23 in postEventSourceDispatch (s=0x2233fb0) at kernel/qeventdispatcher_glib.cpp:271 #18 0x00007fbae5efefe7 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #19 0x00007fbae5eff240 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #20 0x00007fbae5eff2ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #21 0x00007fbaead1de2f in QEventDispatcherGlib::processEvents (this=0x22279d0, flags=...) at kernel/qeventdispatcher_glib.cpp:418 #22 0x00007fbaeacc42ca in QEventLoop::exec (this=this@entry=0x7ffcc4f7dbd0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:204 #23 0x00007fbaeaccbe3c in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1188 #24 0x00007fbaee3dfbfb in kdemain () from /usr/lib/x86_64-linux-gnu/libkdeinit5_konsole.so #25 0x00007fbaee036b45 in __libc_start_main (main=0x400730 <main>, argc=1, argv=0x7ffcc4f7de58, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffcc4f7de48) at libc-start.c:287 #26 0x000000000040075e in _start () Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone! Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |