After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 725982 - eog assert failure: eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c:619: _cairo_xlib_shm_pool_create: Zusicherung »*ptr != ((void *)0)« nicht erfüllt.
eog assert failure: eog: /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-s...
Status: RESOLVED NOTGNOME
Product: eog
Classification: Core
Component: general
3.10.x
Other Linux
: Normal critical
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-03-09 14:37 UTC by Cristian Aravena Romero
Modified: 2014-06-18 18:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Cristian Aravena Romero 2014-03-09 14:37:32 UTC 
Open bug in launchpad.net
https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1277838

"In terminal I typed "eog 1.jpeg" and eog crashed. This happened every time. But opening another image in the same directory and switching to this image worked."

+ Trace 233302

  • #0 __GI_raise
    at ../nptl/sysdeps/unix/sysv/linux/raise.c line 56
  • #1 __GI_abort
    at abort.c line 89
  • #2 __assert_fail_base
  • #3 __GI___assert_fail
  • #4 _cairo_xlib_shm_pool_create
    at /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c line 619
  • #5 _cairo_xlib_shm_info_create
    at /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c line 647
  • #6 _cairo_xlib_shm_surface_create
    at /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c line 829
  • #7 _cairo_xlib_surface_create_shm
    at /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c line 1155
  • #8 _cairo_xlib_surface_create_similar_shm
    at /build/buildd/cairo-1.12.16/src/cairo-xlib-surface-shm.c line 1180
  • #9 INT_cairo_surface_create_similar_image
    at /build/buildd/cairo-1.12.16/src/cairo-surface.c line 586
  • #10 gdk_cairo_set_source_pixbuf
    at /build/buildd/gtk+3.0-3.10.7/./gdk/gdkcairo.c line 332
  • #11 create_surface_from_pixbuf
    at eog-scroll-view.c line 210
  • #12 update_pixbuf
    at eog-scroll-view.c line 2120
  • #13 eog_scroll_view_set_image
    at eog-scroll-view.c line 2432
  • #14 eog_window_display_image
    at eog-window.c line 910
  • #15 eog_job_load_cb
    at eog-window.c line 1357
  • #16 _g_closure_invoke_va
    at /build/buildd/glib2.0-2.39.4/./gobject/gclosure.c line 833
  • #17 g_signal_emit_valist
    at /build/buildd/glib2.0-2.39.4/./gobject/gsignal.c line 3215
  • #18 g_signal_emit
    at /build/buildd/glib2.0-2.39.4/./gobject/gsignal.c line 3363
  • #19 notify_finished
    at eog-jobs.c line 158
  • #20 g_main_dispatch
    at /build/buildd/glib2.0-2.39.4/./glib/gmain.c line 3065
  • #21 g_main_context_dispatch
    at /build/buildd/glib2.0-2.39.4/./glib/gmain.c line 3640
  • #22 g_main_context_iterate
    at /build/buildd/glib2.0-2.39.4/./glib/gmain.c line 3711
  • #23 g_main_context_iteration
    at /build/buildd/glib2.0-2.39.4/./glib/gmain.c line 3772
  • #24 g_application_run
    at /build/buildd/glib2.0-2.39.4/./gio/gapplication.c line 1695
  • #25 main
    at main.c line 186 






Comment 1


Felix Riemann





          2014-06-18 18:36:27 UTC
        



eog's hitting an assertion in cairo there...

Hmm, I know that cairo has a limit on the size of the surfaces it can manage, but according to the trace the image is just 2480x3508 which is far away from that limit. 

It looks like cairo's internal mempool implementation has a problem here, so I'd like to ask you to report this to cairo's bugtracker.
---
Thanks for taking the time to report this bug.
However, this application does not track its bugs in the GNOME Bugzilla. We kindly ask you to report the bug to the application authors. For a selective list of other bug tracking systems please consult http://live.gnome.org/Bugsquad/TriageGuide/NonGnome.

If the affected third party application has a bug tracking system you should investigate whether a bug for the reported issue is already filed in this system. If it has not been filed yet please do so. Also ensure that both bug reports contain a link to each other.
Thanks in advance!