Description of problem: Just crashed out of sudden Version-Release number of selected component: mate-panel-1.16.0-2.fc25 Additional info: reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 1758 kernel: 4.8.13-300.fc25.x86_64 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 gtk_drag_finish at gtkdnd.c:953 #1 gtk_drag_drop_finished at gtkdnd.c:2558 #2 gtk_drag_abort_timeout at gtkdnd.c:3236 #9 gtk_main at gtkmain.c:1301
Created attachment 1231536 [details] File: backtrace
Created attachment 1231537 [details] File: cgroup
Created attachment 1231538 [details] File: core_backtrace
Created attachment 1231539 [details] File: dso_list
Created attachment 1231540 [details] File: environ
Created attachment 1231541 [details] File: exploitable
Created attachment 1231542 [details] File: limits
Created attachment 1231543 [details] File: maps
Created attachment 1231544 [details] File: mountinfo
Created attachment 1231545 [details] File: namespaces
Created attachment 1231546 [details] File: open_fds
Created attachment 1231547 [details] File: proc_pid_status
Created attachment 1231548 [details] File: var_log_messages
*** Bug 1411770 has been marked as a duplicate of this bug. ***
Similar problem has been detected: The panel disappeared all of a sudden, I was not doing anything with it, just reading my mail. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 1779 kernel: 4.9.5-200.fc25.x86_64 package: mate-panel-1.16.0-3.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I was not interacting with the panel at the time. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 1617 kernel: 4.10.8-200.fc25.x86_64 package: mate-panel-1.16.1-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: It happened while I wasn't even touching the mouse and keyboard. reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 4632 kernel: 4.10.16-200.fc25.x86_64 package: mate-panel-1.16.2-1.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I cano see no particular couse for a crashg. It just crashed. reporter: libreport-2.8.0 backtrace_rating: 3 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 2180 kernel: 4.11.3-202.fc25.x86_64 package: mate-panel-1.16.2-2.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: no idea reporter: libreport-2.8.0 backtrace_rating: 4 cmdline: mate-panel crash_function: gtk_drag_finish executable: /usr/bin/mate-panel global_pid: 2202 kernel: 4.11.3-202.fc25.x86_64 package: mate-panel-1.16.2-2.fc25 pkg_fingerprint: 4089 D8F2 FDB1 9C98 pkg_vendor: Fedora Project reason: mate-panel killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 25 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 25. 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 '25'. 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 25 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 25 changed to end-of-life (EOL) status on 2017-12-12. Fedora 25 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.