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 724685 - gtk-update-icon-cache segfaults in gdk_pixbuf_io_init()
gtk-update-icon-cache segfaults in gdk_pixbuf_io_init()
Status: RESOLVED INVALID
Product: gdk-pixbuf
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: gdk-pixbuf-maint
gdk-pixbuf-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-18 19:50 UTC by Sebastien Bacher
Modified: 2014-02-26 22:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2014-02-18 19:50:04 UTC
The issue has been reported on https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1272977

it seems it started with 2.30 versions (or gtk 3.10, both got updated this cycle in Ubuntu)

"#0  0xb76add08 in gdk_pixbuf_io_init () at gdk-pixbuf-io.c:593
        n = <optimized out>
        p = 0x1 <Address 0x1 out of bounds>
        line_buf = 0x844b2e8 "\024"
        term = 3213544228
        have_error = 0
        module = <optimized out>
        flags = -1218467498
        builtin_module = <optimized out>
        channel = 0x1
        tmp_buf = 0x4
        n_patterns = 20
        pattern = <optimized out>
        error = 0xb76a5ff4
  • #1 get_file_formats
    at gdk-pixbuf-io.c line 200
  • #2 gdk_pixbuf_animation_get_width
    at gdk-pixbuf-animation.c line 615
  • #3 ??
  • #4 ??
  • #5 _DYNAMIC
    from /tmp/apport_sandbox_jIxa3p/usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-png.so
  • #6 ??

Comment 1 Matthias Clasen 2014-02-19 15:28:46 UTC
that stacktrace is pretty useless. can you get a better one ?
Comment 2 Sebastien Bacher 2014-02-26 22:26:34 UTC
looking to report those seems to happen during updates and due to the mismatch between running versions and installed one, not really a bug but a side effect of updating on running sessions...