Hide Forgot
Version-Release number of selected component: konsole5-15.08.3-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/konsole crash_function: xcb_setup_vendor_end executable: /usr/bin/konsole global_pid: 18794 kernel: 4.2.8-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 xcb_setup_vendor_end at xproto.c:869 #1 xcb_setup_pixmap_formats at xproto.c:878 #2 find_format_by_depth at xcb_image.c:46 #3 xcb_image_native at xcb_image.c:388 #4 xcb_image_shm_put at xcb_image.c:484 #5 QXcbShmImage::put at qxcbbackingstore.cpp:227 #6 QXcbBackingStore::flush at qxcbbackingstore.cpp:402 #7 QBackingStore::flush at painting/qbackingstore.cpp:105 #8 QWidgetBackingStore::qt_flush at kernel/qwidgetbackingstore.cpp:118 #9 QWidgetBackingStore::flush at kernel/qwidgetbackingstore.cpp:1241
Created attachment 1111154 [details] File: backtrace
Created attachment 1111155 [details] File: cgroup
Created attachment 1111156 [details] File: core_backtrace
Created attachment 1111157 [details] File: dso_list
Created attachment 1111158 [details] File: environ
Created attachment 1111159 [details] File: exploitable
Created attachment 1111160 [details] File: limits
Created attachment 1111161 [details] File: maps
Created attachment 1111162 [details] File: mountinfo
Created attachment 1111163 [details] File: namespaces
Created attachment 1111164 [details] File: open_fds
Created attachment 1111165 [details] File: proc_pid_status
Created attachment 1111166 [details] File: var_log_messages
This problem has not occurred again since I reported it. I am certain that a bugfix for Fedora 23 has fixed this bug as well. I will not try to identify that solution. Thanks for the hard work to develop a stable Linux distribution.
I ran into this issue just one week ago and there hasn't been any update to konsole or any other kf5 or qt5 related piece of software. I doubt this issue is gone thus this bug report probably should stay open.
I had forgotten to check the bug history. Thanks Christian. Reopening.
Similar problem has been detected: My entire KDE session crashed after hours of normal use with konsole, Chrome, LibreOffice. Nothing exotic. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/konsole crash_function: xcb_setup_vendor_end executable: /usr/bin/konsole global_pid: 6805 kernel: 4.3.5-300.fc23.x86_64 package: konsole5-15.12.1-2.fc23 reason: konsole killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.