Version-Release number of selected component: libreport-gtk-2.2.2-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-06-25-17:49:56-1814 crash_function: _gdk_x11_display_error_event executable: /usr/bin/report-gtk kernel: 3.14.8-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #2 _gdk_x11_display_error_event at gdkdisplay-x11.c:2557 #5 handle_error at xcb_io.c:213 #6 handle_response at xcb_io.c:325 #8 XIGetClientPointer at XGetCPtr.c:59 #9 gdk_x11_device_manager_xi2_get_client_pointer at gdkdevicemanager-xi2.c:605 #10 Oxygen::HoverData::connect at /usr/src/debug/oxygen-gtk3-1.3.5/src/animations/oxygenhoverdata.cpp:51 #11 Oxygen::TreeViewData::connect at /usr/src/debug/oxygen-gtk3-1.3.5/src/animations/oxygentreeviewdata.cpp:61 #12 registerWidget at /usr/src/debug/oxygen-gtk3-1.3.5/src/animations/oxygengenericengine.h:58 #13 Oxygen::TreeViewEngine::registerWidget at /usr/src/debug/oxygen-gtk3-1.3.5/src/animations/oxygentreeviewengine.cpp:40 #14 Oxygen::render_background at /usr/src/debug/oxygen-gtk3-1.3.5/src/oxygenthemingengine.cpp:391
Created attachment 912020 [details] File: backtrace
Created attachment 912021 [details] File: cgroup
Created attachment 912022 [details] File: core_backtrace
Created attachment 912023 [details] File: dso_list
Created attachment 912024 [details] File: environ
Created attachment 912025 [details] File: limits
Created attachment 912026 [details] File: maps
Created attachment 912027 [details] File: open_fds
Created attachment 912028 [details] File: proc_pid_status
Created attachment 912029 [details] File: var_log_messages
Another user experienced a similar problem: I've just tried to report problem through abrt. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-07-23-08:44:03-2588 crash_function: _gdk_x11_display_error_event executable: /usr/bin/report-gtk kernel: 3.15.6-200.fc20.x86_64 package: libreport-gtk-2.2.3-1.fc20 reason: report-gtk killed by SIGTRAP runlevel: N 5 type: CCpp uid: 14741
Hello, thank you for taking the time to report this crash. Is it reproducible in gnome-shell or in another GTK base desktop?
I've just tried to report same crash through abrt in XFCE and it worked, so this is probably KDE-related issue.
Another user experienced a similar problem: Suite à cette formulaire de saisi reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-09-23-06:41:02-3811 crash_function: _gdk_x11_display_error_event executable: /usr/bin/report-gtk kernel: 3.16.2-201.fc20.x86_64 package: libreport-gtk-2.2.3-2.fc20 reason: report-gtk killed by SIGTRAP runlevel: N 5 type: CCpp uid: 1000
This problem reproduced on KDE on my machine. But I can't understand when this bug is encountered. Any ideas?
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.