Bug 1480898 - geeqie segfaults at start up
geeqie segfaults at start up
Status: CLOSED NOTABUG
Product: Fedora
Classification: Fedora
Component: geeqie (Show other bugs)
26
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Matthew Miller
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-08-12 14:01 EDT by Franco Comida
Modified: 2017-08-13 10:57 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-08-13 10:57:16 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Franco Comida 2017-08-12 14:01:17 EDT
Description of problem:
Run geeqie, it immediately segfaults

Version-Release number of selected component (if applicable):
geeqie-1.3-2.fc26.x86_64

How reproducible:
Always

Additional info:
Starting program: /usr/bin/geeqie 
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".
[New Thread 0x7fffe6398700 (LWP 30248)]
[New Thread 0x7fffe5b97700 (LWP 30249)]
[New Thread 0x7fffdffff700 (LWP 30250)]

Thread 1 "geeqie" received signal SIGSEGV, Segmentation fault.
0x00007fffe4a0fffe in xmlBufResize () from /lib64/libxml2.so.2
(gdb) bt
#0  0x00007fffe4a0fffe in xmlBufResize () at /lib64/libxml2.so.2
#1  0x00007fffe4a10219 in xmlBufAdd () at /lib64/libxml2.so.2
#2  0x00007fffe49c67db in xmlParserInputBufferPush () at /lib64/libxml2.so.2
#3  0x00007fffe49b2ee2 in xmlParseChunk () at /lib64/libxml2.so.2
#4  0x00007fffe4f2a732 in rsvg_handle_write () at /lib64/librsvg-2.so.2
#5  0x00007fffe5194cbf in gdk_pixbuf.svg_image_load_increment () at /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so
#6  0x00007ffff6d42394 in gdk_pixbuf_loader_write () at /lib64/libgdk_pixbuf-2.0.so.0
#7  0x00007ffff6d3db7b in load_from_stream () at /lib64/libgdk_pixbuf-2.0.so.0
#8  0x00007ffff6d3faed in gdk_pixbuf_new_from_stream_at_scale () at /lib64/libgdk_pixbuf-2.0.so.0
#9  0x00007ffff785ec8a in icon_info_ensure_scale_and_pixbuf () at /lib64/libgtk-x11-2.0.so.0
#10 0x00007ffff78620ea in gtk_icon_info_load_icon () at /lib64/libgtk-x11-2.0.so.0
#11 0x00007ffff7862276 in gtk_icon_theme_load_icon () at /lib64/libgtk-x11-2.0.so.0
#12 0x00005555555ed910 in register_theme_icon_as_stock ()
#13 0x00005555555a4578 in editor_read_desktop_file ()
#14 0x00005555555cec25 in layout_editors_reload_idle_cb ()
#15 0x00007ffff65c9c27 in g_idle_dispatch () at /lib64/libglib-2.0.so.0
#16 0x00007ffff65cd247 in g_main_context_dispatch () at /lib64/libglib-2.0.so.0
#17 0x00007ffff65cd5e8 in g_main_context_iterate.isra () at /lib64/libglib-2.0.so.0
#18 0x00007ffff65cd902 in g_main_loop_run () at /lib64/libglib-2.0.so.0
#19 0x00007ffff78920f7 in gtk_main () at /lib64/libgtk-x11-2.0.so.0
#20 0x0000555555572eeb in main ()
Comment 1 Michael Schwendt 2017-08-12 14:21:53 EDT
That's not the full story.

Your backtrace (why don't you let ABRT handle the detailed backtrace creation? you're missing the -debuginfo packages that need to be installed for a detailed stacktrace!) shows code activity related to loading .svg files:


#4  0x00007fffe4f2a732 in rsvg_handle_write () at /lib64/librsvg-2.so.2
#5  0x00007fffe5194cbf in gdk_pixbuf.svg_image_load_increment () at /usr/lib64/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so


What happens, if you start geeqie in an empty directory?

Can you figure out which .svg file causes the crash? The pixbuf SVG loader plugin has caused trouble in the past.
Comment 2 Franco Comida 2017-08-12 14:48:04 EDT
even virt-manager is segfaulting:
virt-manager[32556]: segfault at 0 ip 00007f8ea622c001 sp 00007f8e831c08e0 error 6 in libxml2.so.2.9.4[7f8ea617e000+15e000]

I ran geegie from inside an empty directory: it segfaults
Comment 3 Franco Comida 2017-08-12 15:11:28 EDT
I veryfied libxml2 and got checksum mismatch, reinstalled it, everything's fine!!!

I'll check my hd health, you can close the bug...
Comment 4 Zbigniew Jędrzejewski-Szmek 2017-08-13 10:57:16 EDT
OK, thanks for reporting back.

Note You need to log in before you can comment on or make changes to this bug.