I didn't have enough time/knowledge for more deliberate investigation but I
tried building tilda from source package and running under gdb. The output
is bellow. The weird thing is that when I tried to reproduce this for the
second time, tilda crashed only after I restarted it several times palying
with the settings dialog displayed with -C, trying to remove ~/.tilda ...
./autogen.sh
CFLAGS="-g" ./configure
make
gdb ./src/tilda
(gdb) run
(tilda:23018): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion
`filename != NULL' failed
(tilda:23018): Gtk-CRITICAL **: gtk_container_foreach: assertion
`GTK_IS_CONTAINER (container)' failed
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0xb719c6c0 (LWP 23167)]
focus_term (widget=0x8090850, data=0x80b1800) at tilda_window.c:163
163 gtk_widget_grab_focus (list->data);
(gdb) print list
$1 = <value optimized out>
(gdb) l
158 GtkWidget *box;
159 GtkWidget *n = GTK_WIDGET (data);
160
161 box = gtk_notebook_get_nth_page (GTK_NOTEBOOK(n),
gtk_notebook_get_current_page(GTK_NOTEBOOK(n)));
162 list = gtk_container_children (GTK_CONTAINER(box));
163 gtk_widget_grab_focus (list->data);
164 }
165
166 static void focus_out_event_cb (GtkWidget *widget, gpointer data)
167 {
(gdb) print box
$2 = <value optimized out>
(gdb) l -
148 gtk_notebook_set_current_page (GTK_NOTEBOOK (tw->notebook), 0);
149 }
150
151 static void focus_term (GtkWidget *widget, gpointer data)
152 {
153 DEBUG_FUNCTION ("focus_term");
154 DEBUG_ASSERT (data != NULL);
155 DEBUG_ASSERT (widget != NULL);
156
157 GList *list;
(gdb) print widget
$3 = (GtkWidget *) 0x8090850
(gdb) print gpointer
Attempt to use a type name as an expression
(gdb) print data
$4 = (gpointer) 0x80b1800
(gdb) print data
$5 = (gpointer) 0x80b1800
2008/10/13 Jim Kirkpatrick <[EMAIL PROTECTED]>
> Indeed, I managed to fix it by running tilda -C which I imagine is
> roughly the same as binning the ~/.tilda directory.
>
> I did notice that when I ran config mode, all my previous settings where
> gone. Now though, Tilda doesn't crash on startup, so it looks like Tilda
> corrupted its config files maybe?
>
> --
> [apport] tilda crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/92264
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "tilda" source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: tilda
>
> Triple head computer. Tilda segfaults on startup. No configuration has been
> done.
>
> ProblemType: Crash
> Architecture: i386
> CrashCounter: 1
> Date: Wed Mar 14 16:15:27 2007
> DistroRelease: Ubuntu 7.04
> ExecutablePath: /usr/bin/tilda
> Package: tilda 0.09.4-0ubuntu2 [modified: usr/bin/tilda]
> PackageArchitecture: i386
> ProcCmdline: tilda
> ProcCwd: /home/calle
> ProcEnviron:
> LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
>
> PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
> LANG=nb_NO.UTF-8
> SHELL=/bin/bash
> Signal: 11
> SourcePackage: tilda
> StacktraceTop:
> ?? () from /usr/lib/libXrandr.so.2
> ?? ()
> ?? ()
> ?? ()
> ?? () from /usr/lib/libX11.so.6
> Uname: Linux edgytriple2 2.6.20-10-generic #2 SMP Mon Mar 12 00:02:49 UTC
> 2007 i686 GNU/Linux
> UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev
> powerdev scanner video
>
--
Timur Izhbulatov -- www.timka.org
--
[apport] tilda crashed with SIGSEGV
https://bugs.launchpad.net/bugs/92264
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
