Hide Forgot
Version-Release number of selected component: gnome-abrt-0.3.1-1.fc19 Additional info: reporter: libreport-2.1.7 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/gnome-abrt executable: /usr/bin/python2.7 kernel: 3.11.1-200.fc19.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 ?? #2 XGetWindowProperty at GetProp.c:69 #3 gdk_x11_window_get_frame_extents at gdkwindow-x11.c:3027 #4 Oxygen::Gtk::gdk_toplevel_get_frame_size at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.cpp:890 #5 Oxygen::Gtk::gdk_window_map_to_toplevel at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.cpp:747 #6 gdk_map_to_toplevel at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygengtkutils.h:117 #7 Oxygen::Style::renderWindowBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:288 #8 Oxygen::Style::renderHoleBackground at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.cpp:792 #9 Oxygen::InnerShadowData::targetExposeEvent at /usr/src/debug/oxygen-gtk3-1.2.0/src/oxygenstyle.h:181 #10 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:85
Created attachment 801139 [details] File: backtrace
Created attachment 801140 [details] File: cgroup
Created attachment 801141 [details] File: core_backtrace
Created attachment 801142 [details] File: dso_list
Created attachment 801143 [details] File: environ
Created attachment 801144 [details] File: exploitable
Created attachment 801145 [details] File: limits
Created attachment 801146 [details] File: maps
Created attachment 801147 [details] File: open_fds
Created attachment 801148 [details] File: proc_pid_status
Created attachment 801149 [details] File: var_log_messages
Thank you for the bug report. This seems more like a bug in oxygen-gtk or gtk3. Unfortunately, we need to know how this happened. If you have time and can still reproduce the bug, please provide a textual description or better a demonstrative video [1]. 1: https://fedoraproject.org/wiki/Bugs_and_feature_requests?rd=BugsAndFeatureRequests#Graphical_User_Interfaces
The information we've requested above is required in order to review this problem report further and diagnose or fix the issue if it is still present. Since it has been thirty days or more since we first requested additional information, we're assuming the problem is either no longer present in the current Fedora release, or that there is no longer any interest in tracking the problem. Setting status to "CLOSED: INSUFFICIENT_DATA". If you still experience this problem after updating to our latest Fedora release and can provide the information previously requested, please feel free to reopen the bug report.