Description of problem: Reporting a vlc crash - wasn't able to complete the report by the way Version-Release number of selected component: libreport-gtk-2.2.3-2.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-09-26-15:58:26-10760 crash_function: poll_for_event executable: /usr/bin/report-gtk kernel: 3.16.2-201.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 poll_for_event at xcb_io.c:271 #5 poll_for_response at xcb_io.c:289 #6 _XEventsQueued at xcb_io.c:363 #7 XEventsQueued at Pending.c:43 #8 _cairo_xlib_shm_info_cleanup at cairo-xlib-surface-shm.c:481 #9 _cairo_xlib_shm_info_create at cairo-xlib-surface-shm.c:640 #10 _cairo_xlib_shm_surface_create at cairo-xlib-surface-shm.c:829 #11 _cairo_xlib_surface_create_shm at cairo-xlib-surface-shm.c:1155 #12 _cairo_xlib_surface_create_similar_shm at cairo-xlib-surface-shm.c:1180 #13 INT_cairo_surface_create_similar_image at cairo-surface.c:593
Created attachment 941805 [details] File: backtrace
Created attachment 941806 [details] File: cgroup
Created attachment 941807 [details] File: core_backtrace
Created attachment 941808 [details] File: dso_list
Created attachment 941809 [details] File: environ
Created attachment 941810 [details] File: limits
Created attachment 941811 [details] File: maps
Created attachment 941812 [details] File: open_fds
Created attachment 941813 [details] File: proc_pid_status
Created attachment 941814 [details] File: var_log_messages
Another user experienced a similar problem: I was trying to fill in the report for gnome tracker service. I guess something is missing for the report and then the libreport failed, too. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2014-10-08-19:05:24-1741 crash_function: poll_for_event executable: /usr/bin/report-gtk kernel: 3.16.3-200.fc20.x86_64 package: libreport-gtk-2.2.3-2.fc20 reason: report-gtk killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
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.