Summary: | gimp-2.2.6-r1 segfaults after trying to save a file opened with the 'open location' menu item | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Toon Verstraelen <Toon.Verstraelen> |
Component: | Current packages | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Toon Verstraelen
2005-06-23 00:31:33 UTC
can't reproduce, please provide a backtrace with debugging info. i could reproduce this and i went digging in gnome bugzilla, and, its been reported: http://bugzilla.gnome.org/show_bug.cgi?id=303312 dupe here: http://bugzilla.gnome.org/show_bug.cgi?id=304272 from what i gather, updating gnome-vfs to 2.10.1 and 2.2.7 will make this not happen anymore ( i'll first try just updating gnome-vfs ) . later today i will test this. It's indeed a gnome-vfs problem. When I change /desktop/gnome/interface/file_chooser_backend in gconf-editor from "gnome-vfs" to "gtk+" as sugested in one of the related bugs on the gnome bugzilla, gimp doesn't crash any more when doing the same procedure. I'll recompile both gnome-vfs and gimp with debug-info to be sure. Hi I compiled both gimp and gnome-vfs with debugging info (using debug useflag, nostrip option, no compiler optimizations) and I get this when creating the backtrace. It doesn't look really usefull. Does someone know what the "hook_stop" problem might be? GNU gdb 6.3 Copyright 2004 Free Software Foundation, Inc. GDB is free software, covered by the GNU General Public License, and you are welcome to change it and/or distribute copies of it under certain conditions. Type "show copying" to see the conditions. There is absolutely no warranty for GDB. Type "show warranty" for details. This GDB was configured as "i686-pc-linux-gnu"...Using host libthread_db library "/lib/libthread_db.so.1". gdb> run [Thread debugging using libthread_db enabled] [New Thread -1217448272 (LWP 901)] [New Thread -1228809296 (LWP 1080)] [New Thread -1237894224 (LWP 1081)] Program received signal SIG33, Real-time event 33. [Switching to Thread -1228809296 (LWP 1080)] Error while running hook_stop: Invalid type combination in ordering comparison. 0xffffe410 in __kernel_vsyscall () gdb> thread apply all bt 3 Thread -1237894224 (LWP 1081) 0xffffe410 in __kernel_vsyscall () * 2 Thread -1228809296 (LWP 1080) 0xffffe410 in __kernel_vsyscall () 1 Thread -1217448272 (LWP 901) 0xffffe410 in __kernel_vsyscall () gdb> thread apply all info stack 3 Thread -1237894224 (LWP 1081) 0xffffe410 in __kernel_vsyscall () * 2 Thread -1228809296 (LWP 1080) 0xffffe410 in __kernel_vsyscall () 1 Thread -1217448272 (LWP 901) 0xffffe410 in __kernel_vsyscall () gdb> bt #0 0xffffe410 in __kernel_vsyscall () #1 0xb78d5e55 in poll () from /lib/libc.so.6 #2 0xb7a12706 in g_main_context_poll () from /usr/lib/libglib-2.0.so.0 #3 0x08e66150 in ?? () #4 0x00000007 in ?? () #5 0xffffffff in ?? () #6 0xb7a1159e in g_main_context_query () from /usr/lib/libglib-2.0.so.0 #7 0x00000007 in ?? () #8 0xffffffff in ?? () #9 0x08e66150 in ?? () #10 0xb7a159b8 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #11 0x00000007 in ?? () #12 0xb7a70640 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x00000001 in ?? () #14 0xb6c1d3d4 in ?? () #15 0xb7a70d40 in string_mem_chunk () from /usr/lib/libglib-2.0.so.0 #16 0xb7a709c0 in g_thread_use_default_impl () from /usr/lib/libglib-2.0.so.0 #17 0xb7a709a8 in g_scanner_config_template () from /usr/lib/libglib-2.0.so.0 #18 0xb7a70d40 in string_mem_chunk () from /usr/lib/libglib-2.0.so.0 #19 0x00000000 in ?? () #20 0xffffffff in ?? () #21 0x7fffffff in ?? () #22 0xb7a70640 in ?? () from /usr/lib/libglib-2.0.so.0 #23 0x08e54160 in ?? () #24 0x08e54160 in ?? () #25 0x08e53ec8 in ?? () #26 0xb7a11b5e in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #27 0xb7372b30 in pthread_mutex_lock () from /lib/libpthread.so.0 Previous frame inner to this frame (corrupt stack?) testing with gnome-vfs-2.10.1 as the backend did not change anything. i'll take a look at the patchset that debian is using for their 2.10.1-5 that the poster in the gnome bug mentioned. i did some more research on this issue, but gnome bugzilla is down for a day or so , but here is the link from ubuntu where someone arleady reported this issue and filed an upstream bug w/gnome-vfs: https://bugzilla.ubuntu.com/show_bug.cgi?id=11018 However, since the guy on the ubuntu post asked the reporter to try with 2.11, I went ahead and bumped gnome-vfs locally to 2.11.2 and tested it. ( still crashed doing saveas ) So we'll just have to wait until gnome bugzilla comes back up. we'll follow upstream on this. http://bugzilla.gnome.org/show_bug.cgi?id=170367 |