An empty file with name of 0xB0 with ".jpg" appended to it (a total of 5 characters) will (1) crash gthumb when it tries to browse the directory and (2) crash the mail component of evolution when an attempt is made to attach the file. The crashing behavoir does not occur with an empty file named: foo.jpg An easy way to create this file is to launch vim and then type ":w " ctrl-v "xb0.jpg" return There is a small possibility that this is a security hole: inbound attachments may be able to cause unexpected code to be run.
reproucible: (no debugging symbols found)...(no debugging symbols found)...[New Thread 2049 (LWP 26962)] [New Thread 1026 (LWP 26963)] [New Thread 2051 (LWP 26964)] [New Thread 3076 (LWP 26965)] [New Thread 4101 (LWP 26966)] [New Thread 5126 (LWP 26967)] [New Thread 6151 (LWP 26968)] (no debugging symbols found)...(no debugging symbols found)...[New Thread 7176 (LWP 26969)] ** (gthumb:26959): CRITICAL **: file gthumb-text-item.c: line 189 (update_text): assertion `utf8_text != NULL' failed ** (gthumb:26959): CRITICAL **: file gthumb-text-item.c: line 135 (update_pango_layout): assertion `priv->parsed_text != NULL' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 1024 (LWP 26959)] 0x080a362d in _gtk_label_get_locale_text () (gdb) bt #0 0x080a362d in _gtk_label_get_locale_text () #1 0x080a365d in _gtk_label_get_locale_text () #2 0x080a3aee in image_list_get_images_per_line () #3 0x080a3e88 in image_list_get_images_per_line () #4 0x080a8a58 in image_list_thaw () #5 0x0809bd32 in file_list_interrupt_set_list () #6 0x0809b9c4 in file_list_free () #7 0x40173784 in dispatch_get_file_info_callback () from /usr/lib/libgnomevfs-2.so.0 #8 0x40173dec in dispatch_job_callback () from /usr/lib/libgnomevfs-2.so.0 #9 0x40b6aefe in g_idle_dispatch () from /usr/lib/libglib-2.0.so.0 #10 0x40b6870b in g_main_dispatch () from /usr/lib/libglib-2.0.so.0 #11 0x40b6955a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #12 0x40b69937 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0 #13 0x40b6a050 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0 #14 0x40703cf8 in bonobo_main () from /usr/lib/libbonobo-2.so.0 #15 0x08091be2 in main () #16 0x40c6b671 in __libc_start_main () from /lib/libc.so.6 * x11-libs/gtk+ Latest version available: 2.2.0 Latest version installed: 2.0.9 gcc version 2.95.3 20010315 (release)
what is your locale? on this system: if LANG (locale) is unset, (POSIX) gthumb will crash, if it is set to LANG="en_GB" or other, it wont crash. I can't test with evolution.
What gtk+ version is installed? here is my debugging showing: gtk+ 2.0.9 locale "POSIX" :: Crash gtk+ 2.2.0 locale "POSIX" :: no crash gtk+ 2.0.9 locale "en_GB" :: no crash gtk+ 2.2.0 locale "en_GB" :: no crash
Not being familiar with how locales are implemented and how prelinking is affecting things, I determined the following: LC_CTYPE seems to be the setting that matters. gtk+-2.2.0 seems to fix the crashing but still has problems. evolution crashes regardless. Most likely because the 1.2.10 libraries are bad. I think this can be marked resolved as far as crashing goes unless you want to get the 1.2 libraries fixed. However, gthumb reports these errors and the file name shows up as (null): (gthumb:5230): Gdk-CRITICAL **: file gdkwindow-x11.c: line 2138 (gdk_window_set_title): assertion `title != NULL' failed (gthumb:5230): GLib-CRITICAL **: file gmarkup.c: line 1819 (g_markup_escape_text): assertion `text != NULL' failed --- Testing history: >qpkg -I -i gtk+ x11-libs/gtk+-2.1.2 * Gimp ToolKit + [ http://www.gtk.org/ ] x11-libs/gtk+-1.2.10-r9 * The GIMP Toolkit [ http://www.gtk.org/ ] LC_CTYPE C or POSIX or unset : crash en_GB : no crash >emerge gtk+-2.2.0 >qpkg -I -i gtk+ x11-libs/gtk+-1.2.10-r9 * The GIMP Toolkit [ http://www.gtk.org/ ] x11-libs/gtk+-2.2.0 * Gimp ToolKit + [ http://www.gtk.org/ ] LC_CTYPE C or POSIX or unset : crash en_GB : no crash # Given the continued crashing I blamed prelinking and tried prelink -ua to no avail. So... >emerge gthumb-1.107 LC_CTYPE C or POSIX or unset : no crash en_GB : no crash
BTW, my LANG is set to POSIX. Where is this value set?
the evolution problem looks familiar, i think theres another bug about that (ah well, evolution just is crashy) .. i think its unrelated since upgrading to latest stable fixes problems, im closing this. The LANG is set somewhere in env.d i think, maybe you should the localisation howto (i should too, i use basic stuff myself too). And according to spider there LANG not set is the same as POSIX, so..
