Version-Release number of selected component: eog-3.19.90-1.fc24 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: eog /home/yuceffrawhide/Pictures/fig15-07.jpg crash_function: INT_cairo_region_is_empty executable: /usr/bin/eog global_pid: 12549 kernel: 4.5.0-0.rc3.git3.1.fc24.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 INT_cairo_region_is_empty at cairo-region.c:816 #1 buffer_release_callback at gdkwindow-wayland.c:686 #2 ffi_call_unix64 at ../src/x86/unix64.S:76 #3 ffi_call at ../src/x86/ffi64.c:525 #4 wl_closure_invoke at src/connection.c:949 #5 dispatch_event at src/wayland-client.c:1274 #6 wl_display_dispatch_queue_pending at src/wayland-client.c:1420 #8 _gdk_wayland_display_queue_events at gdkeventsource.c:165 #9 gdk_display_get_event at gdkdisplay.c:392 #14 g_main_context_iteration at gmain.c:3901
Created attachment 1129124 [details] File: backtrace
Created attachment 1129125 [details] File: cgroup
Created attachment 1129126 [details] File: core_backtrace
Created attachment 1129127 [details] File: dso_list
Created attachment 1129128 [details] File: environ
Created attachment 1129129 [details] File: exploitable
Created attachment 1129130 [details] File: limits
Created attachment 1129131 [details] File: maps
Created attachment 1129132 [details] File: mountinfo
Created attachment 1129133 [details] File: namespaces
Created attachment 1129134 [details] File: open_fds
Created attachment 1129135 [details] File: proc_pid_status
Created attachment 1129136 [details] File: var_log_messages
Similar problem has been detected: eog segfaults whenever I try to open picture (tried with jpg and png). It doesn't happen when I open just eog. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: eog '/home/pschindl/Pictures/Screenshot from 2016-02-24 08-01-03.png' crash_function: INT_cairo_region_is_empty executable: /usr/bin/eog global_pid: 3915 kernel: 4.5.0-0.rc5.git0.1.fc24.x86_64 package: eog-3.19.90-1.fc24 reason: eog killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
I propose this bug as final blocker bug as it violates the Final criterion: "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test. "
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle. Changing version to '24'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Hit this when I tried to arrange two displays. Reproducible by: 1. open gnom-control-center 2. open Displays 3. click Arrange Combined Displays button 3. drag one display around another, release it, then start dragging it again. doing this a while, g-c-c will eventually crash
forgot to mention that I'm running current gnome-shell build using jhbuild gtk+ ee217dc8
There's a patch in the upstream bug
+1 blocker (and I can also reproduce this issue)
(In reply to Michael Catanzaro from comment #19) > There's a patch in the upstream bug oh, yep. That fixes it for me
Discussed at 2016-02-29 blocker review meeting: [1]. This bug was accepted as Final blocker: eog crashing on start clearly violates "All applications that can be launched using the standard graphical mechanism of a release-blocking desktop after a default installation of that desktop must start successfully and withstand a basic functionality test." [1] http://meetbot.fedoraproject.org/fedora-blocker-review/2016-02-29/f24-blocker-review.2016-02-29-17.00.html
Fixed in GTK+ 3.19.11, coming soon to a rawhide near you
Thanks for update, but because this bug is blocker we have to wait until the update will be pushed to stable.
*** Bug 1314409 has been marked as a duplicate of this bug. ***
Should now be fixed in F24 by gtk3-3.19.11-1.fc24. (In reply to Petr Schindler from comment #24) > Thanks for update, but because this bug is blocker we have to wait until the > update will be pushed to stable. No Bodhi yet. :)
*** Bug 1314558 has been marked as a duplicate of this bug. ***