Description of problem: Just open a jpg image Version-Release number of selected component: eog-3.10.2-1.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: eog /home/helber/Documentos/Morgana/certidao_nascimento.jpg crash_function: _cairo_xlib_shm_pool_create executable: /usr/bin/eog kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #4 _cairo_xlib_shm_pool_create at cairo-xlib-surface-shm.c:619 #5 _cairo_xlib_shm_info_create at cairo-xlib-surface-shm.c:647 #6 _cairo_xlib_shm_surface_create at cairo-xlib-surface-shm.c:829 #7 _cairo_xlib_surface_create_shm at cairo-xlib-surface-shm.c:1155 #8 _cairo_xlib_surface_create_similar_shm at cairo-xlib-surface-shm.c:1180 #9 INT_cairo_surface_create_similar_image at cairo-surface.c:593 #10 gdk_cairo_set_source_pixbuf at gdkcairo.c:332 #11 create_surface_from_pixbuf at eog-scroll-view.c:203 #12 update_pixbuf at eog-scroll-view.c:2037 #13 eog_scroll_view_set_image at eog-scroll-view.c:2349 Potential duplicate: bug 982768
Created attachment 873939 [details] File: backtrace
Created attachment 873940 [details] File: cgroup
Created attachment 873941 [details] File: core_backtrace
Created attachment 873942 [details] File: dso_list
Created attachment 873943 [details] File: environ
Created attachment 873944 [details] File: limits
Created attachment 873945 [details] File: maps
Created attachment 873946 [details] File: open_fds
Created attachment 873947 [details] File: proc_pid_status
Created attachment 873948 [details] File: var_log_messages
Another user experienced a similar problem: All I did was try to open an image. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: eog '/home/omega13a/.local/share/celestia/texture repo/Marduk 4096x2048 Diffuse.jpg' crash_function: _cairo_xlib_shm_pool_create executable: /usr/bin/eog kernel: 3.14.4-200.fc20.x86_64 package: eog-3.10.2-1.fc20 reason: eog killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: I went to go view an image while I had another already opened in eog. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: eog /run/user/1000/gvfs/smb-share:server=peeves.local,share=www/fedtrek.com/web/staff/omega13a/celestia/omega_galaxy/textures/medres/Jovisar_E.jpg crash_function: _cairo_xlib_shm_pool_create executable: /usr/bin/eog kernel: 3.14.7-200.fc20.x86_64 package: eog-3.10.2-1.fc20 reason: eog 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.