Description of problem: I was compiling a kernel 4.18.5 in a qterminal window and had an open directory in another qterminal window when they both dissapeared out of thin air to my knowledge they crashed immediately. This was after like 40 minutes of steady compiling in the other window that was minimised. Don't know what information I can provide but it seemed like worth reporting. Version-Release number of selected component: qterminal-0.7.1-2.fc27 Additional info: reporter: libreport-2.9.3 backtrace_rating: 4 cmdline: qterminal crash_function: QTermWidget::copyClipboard executable: /usr/bin/qterminal journald_cursor: s=6f85aecfa7d04e0fbbc63bf4729ed53a;i=473c0;b=ad0811c7cb5f46dc825001ff83886085;m=4b0577d80;t=576999aa55bb1;x=758e4410197bfb0c kernel: 4.18.5 rootdir: / runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 QTermWidget::copyClipboard at /usr/src/debug/qtermwidget-0.7.1-2.fc27.x86_64/lib/qtermwidget.cpp:498 #1 TabWidget::qt_static_metacall at /usr/src/debug/qterminal-0.7.1-2.fc27.x86_64/x86_64-redhat-linux-gnu/src/moc_tabwidget.cpp:230 #2 QMetaObject::activate at kernel/qobject.cpp:3767 #4 QAction::triggered at .moc/moc_qaction.cpp:370 #5 QAction::activate at kernel/qaction.cpp:1165 #6 QMenuPrivate::activateCausedStack at widgets/qmenu.cpp:1323 #7 QMenuPrivate::activateAction at widgets/qmenu.cpp:1400 #8 QMenu::mouseReleaseEvent at widgets/qmenu.cpp:2888 #9 QWidget::event at kernel/qwidget.cpp:9280 #10 QMenu::event at widgets/qmenu.cpp:3010
Created attachment 1486334 [details] File: backtrace
Created attachment 1486335 [details] File: cgroup
Created attachment 1486336 [details] File: core_backtrace
Created attachment 1486337 [details] File: cpuinfo
Created attachment 1486338 [details] File: dso_list
Created attachment 1486339 [details] File: environ
Created attachment 1486340 [details] File: exploitable
Created attachment 1486341 [details] File: limits
Created attachment 1486342 [details] File: maps
Created attachment 1486343 [details] File: mountinfo
Created attachment 1486344 [details] File: open_fds
Created attachment 1486345 [details] File: proc_pid_status
Created attachment 1486346 [details] File: var_log_messages
This message is a reminder that Fedora 27 is nearing its end of life. On 2018-Nov-30 Fedora will stop maintaining and issuing updates for Fedora 27. 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 '27'. 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 27 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 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.