+1 to this bug. I compiled tilda 0.9.6 myself to see if the bug would disappear and got a very similar outcome:
--GDB-- [EMAIL PROTECTED]:pts/1 ..nloads/tilda-0.9.6:139>>> gdb tilda GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i486-linux-gnu"... (gdb) handle SIG33 pass nostop noprint Signal Stop Print Pass to program Description SIG33 No No Yes Real-time event 33 (gdb) set pagination 0 (gdb) run Starting program: /usr/local/bin/tilda [Thread debugging using libthread_db enabled] [New Thread 0xb719ea40 (LWP 7457)] [New Thread 0xb7029b90 (LWP 7464)] [New Thread 0xb623db90 (LWP 7465)] (tilda:7457): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion `filename != NULL' failed (tilda:7457): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed (tilda:7457): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 0xb719ea40 (LWP 7457)] focus_term (widget=0x8092050, data=0x80b9800) at tilda_window.c:171 171 gtk_widget_grab_focus (list->data); (gdb) backtrace full #0 focus_term (widget=0x8092050, data=0x80b9800) at tilda_window.c:171 list = <value optimized out> box = (GtkWidget *) 0x0 __PRETTY_FUNCTION__ = "focus_term" #1 0xb7a1caff in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #2 0xb7a0f759 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #3 0xb7a23f8b in ?? () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #4 0xb7a25c1f in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #5 0xb7a25f69 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 No symbol table info available. #6 0xb7e39837 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0 No symbol table info available. #7 0x080505b2 in pull (tw=0x8086f30, state=PULL_DOWN) at key_grabber.c:196 i = <value optimized out> __PRETTY_FUNCTION__ = "pull" #8 0x08051826 in main (argc=Cannot access memory at address 0x0 ) at tilda.c:619 tw = (tilda_window *) 0x8086f30 sa = {__sigaction_handler = {sa_handler = 0x8051a90 <termination_handler>, sa_sigaction = 0x8051a90 <termination_handler>}, sa_mask = {__val = {0 <repeats 32 times>}}, sa_flags = 0, sa_restorer = 0} need_wizard = 0 home_dir = (gchar *) 0x8061a58 "/home/ben" config_file = (gchar *) 0x805f580 "/home/ben/.tilda/config_0" lock_file = (gchar *) 0x805f518 "/home/ben/.tilda/locks/lock_7457_0" (gdb) info registers eax 0x0 0 ecx 0x0 0 edx 0x0 0 ebx 0x0 0 esp 0xbfc3b6d0 0xbfc3b6d0 ebp 0xbfc3b6f8 0xbfc3b6f8 esi 0x80b4a48 134957640 edi 0x80b9800 134977536 eip 0x805409e 0x805409e <focus_term+126> eflags 0x10282 [ SF IF RF ] cs 0x73 115 ss 0x7b 123 ds 0x7b 123 es 0x7b 123 fs 0x0 0 gs 0x33 51 (gdb) thread apply all backtrace Thread 3 (Thread 0xb623db90 (LWP 7465)): #0 0xb7f54410 in __kernel_vsyscall () #1 0xb7555dd2 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7949077 in ?? () from /usr/lib/libgthread-2.0.so.0 #3 0xb795ee31 in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb79adbb2 in ?? () from /usr/lib/libglib-2.0.so.0 #5 0xb79abe2f in ?? () from /usr/lib/libglib-2.0.so.0 #6 0xb75514fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0xb74d3e5e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 2 (Thread 0xb7029b90 (LWP 7464)): #0 0xb7f54410 in __kernel_vsyscall () #1 0xb755899b in read () from /lib/tls/i686/cmov/libpthread.so.0 #2 0xb7984d0a in ?? () from /usr/lib/libglib-2.0.so.0 #3 0xb79abe2f in ?? () from /usr/lib/libglib-2.0.so.0 #4 0xb75514fb in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #5 0xb74d3e5e in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb719ea40 (LWP 7457)): #0 focus_term (widget=0x8092050, data=0x80b9800) at tilda_window.c:171 #1 0xb7a1caff in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0 #2 0xb7a0f759 in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0 #3 0xb7a23f8b in ?? () from /usr/lib/libgobject-2.0.so.0 #4 0xb7a25c1f in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0 #5 0xb7a25f69 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0 #6 0xb7e39837 in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0 #7 0x080505b2 in pull (tw=0x8086f30, state=PULL_DOWN) at key_grabber.c:196 #8 0x08051826 in main (argc=Cannot access memory at address 0x0 ) at tilda.c:619 (gdb) quit The program is running. Exit anyway? (y or n) y --Valgrind-- [EMAIL PROTECTED]:pts/1 ..nloads/tilda-0.9.6:>>> G_SLICE=always-malloc G_DEBUG=gc-friendly valgrind -v --tool=memcheck --leak-check=full --num-callers=40 --log-file=valgrind.log tilda I've attached valgrind.log, since it segfaulted (although the segfault might be caused by the error handling; I don't know anything about Tilda so I'm not sure). Please fix this; I'd love to be able to use Tilda! - Ben ** Attachment added: "valgrind.log" http://launchpadlibrarian.net/16735785/valgrind.log -- tilda can't start: Gtk-CRITICAL https://bugs.launchpad.net/bugs/228970 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
