[apport] tilda crashed with SIGSEGV

StacktraceTop:XRRGetScreenInfo (dpy=0x81b9a80, window=1012) at ../../src/XrrConfig.c:351
get_display_dimension (dimension=0) at tilda.c:480
appearance (tw=0x805e008, tt=0x805e030) at wizard.c:457
wizard (argc=1, argv=0xbf816444, tw=0x805e008, tt=0x805e030) at wizard.c:995

Thank you for your bug

Can you please try if tilda 0.09.4-4 (latest Gutsy version) is still affected.

calle@gutsy:~$ tilda -v
tilda 0.09.4

Copyright (c) 2005,2006 Tristan Sloughter (<email address hidden>)
Copyright (c) 2005,2006 Ira W. Snyder (<email address hidden>)

This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

calle@gutsy:~$ tilda
Segmentation fault (core dumped)
calle@gutsy:~$

Synaptic confirms that version 0.09.4-4 is installed. Sorry.

New crash report is sendt trough Launchpad

Regards
Calle

2007/8/24, Áron Sisak <email address hidden>:
>
> Can you please try if tilda 0.09.4-4 (latest Gutsy version) is still
> affected.
>
> --
> [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.
>

I have the same problem with tilda 0.9.5pre. Should I send the core files and/or other debugging info and how, if so?

timur@tizhbulatov:~$ tilda

(tilda:23835): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion `filename != NULL' failed

(tilda:23835): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
zsh: segmentation fault (core dumped) tilda

Tilda (0.09.6-1 on Intrepid) appeared to be working fine as I was using it when I first installed it.

So I added it to my session startup programs with command /usr/bin/tilda. Now it is crashing on startup and also when I try to run it manually i get "Segmentation fault (core dumped)"

From messages.log:
    tilda[8240]: segfault at 0 ip 080501eb sp bfd734a0 error 4 in tilda[8048000+14000]

i had this problem after a system update, but i was able to fix it by removing ~/.tilda and reinstalling it

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?

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 address hidden>

> 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
> ?? ()
> ?? ()
> ?? ()
> ??...

It's doing it again. Next reboot and Tilda segfaults on startup.

I think I've worked out why though: In the .tilda directory is the config_0 created when you run it with -C. When I looked at the folder after a crash, config_0 was completely empty and config_1 appeared to have its contents.

So it was fixed for me by doing a mv .tilda/config_1 .tilda/config_0 (before = segfault, after = Tilda goodness)

In other words, .tilda attempts to backup its settings, wipes the current set, then looks in an empty file and crashes. Attached a zip of my .tilda folder just after a crash and after running with -C.

Hope this helps.

Empty config_0 produced crash. Problem solved with:
  mv .tilda/config_1 .tilda/config_0

I have the same problem with tilda(0.9.6) after a system update, as well. To fix it, I've just delete ~/.tilda and now it is working, however I'm still getting the error:

(tilda:25603): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed

Just after start tilda.

I'm having the same issues on an Intrepid amd64 install. Clean install of tilda, no .tilda/ directory.

$ tilda
Unable to open lock directory: /home/bismark/.tilda/locks
Unable to open lock directory: /home/bismark/.tilda/locks
(tilda:7222): Gtk-WARNING **: GtkSpinButton: setting an adjustment with non-zero page size is deprecated
<snip - repeated 14x>
(tilda:7222): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion `filename != NULL' failed
(tilda:7222): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed
(tilda:7222): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
[1] 7222 segmentation fault tilda
$

$ tilda

(tilda:17385): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed

(tilda:17385): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed

Segfault still exists in jaunty

#0 focus_term (widget=0x8d53830, data=0x8d5c000) at tilda_window.c:171
#1 0xb79e73a4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
#2 0xb79d9c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
#3 0xb79efe57 in ?? () from /usr/lib/libgobject-2.0.so.0
#4 0xb79f14b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
#5 0xb79f1936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
#6 0xb7f571cc in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
#7 0x08050922 in pull (tw=0x8ceafe0, state=PULL_DOWN) at key_grabber.c:196
#8 0x08051ac1 in main (argc=Cannot access memory at address 0x0
) at tilda.c:619

frames:

(gdb) frame 0
#0 focus_term (widget=0x8d53830, data=0x8d5c000) at tilda_window.c:171
171 gtk_widget_grab_focus (list->data);
(gdb) frame 1
#1 0xb79e73a4 in g_cclosure_marshal_VOID__VOID () from /usr/lib/libgobject-2.0.so.0
(gdb) frame 2
#2 0xb79d9c7b in g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
(gdb) frame 3
#3 0xb79efe57 in ?? () from /usr/lib/libgobject-2.0.so.0
(gdb) frame 4
#4 0xb79f14b9 in g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
(gdb) frame 5
#5 0xb79f1936 in g_signal_emit () from /usr/lib/libgobject-2.0.so.0
(gdb) frame 6
#6 0xb7f571cc in gtk_widget_show () from /usr/lib/libgtk-x11-2.0.so.0
(gdb) frame 7
#7 0x08050922 in pull (tw=0x8ceafe0, state=PULL_DOWN) at key_grabber.c:196
196 gtk_widget_show (GTK_WIDGET(tw->window));
(gdb) frame 8
#8 0x08051ac1 in main (argc=Cannot access memory at address 0x0
) at tilda.c:619
619 pull (tw, PULL_DOWN);

Core attached

$ tilda -v

Tilda 0.9.6

Copyright (c) 2005-2008 Tristan Sloughter (<email address hidden>)
Copyright (c) 2005-2008 Ira W. Snyder (<email address hidden>)

General Information: http://launchpad.net/tilda
Bug Reports: http://bugs.launchpad.net/tilda

This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it
under certain conditions. See the file COPYING for details.

having the same problem here. karmic amd64
purging tilda, deleting ~./tilda didn't help

any suggestions?

Use Guake )

because Tilda crashed so many times I wrote a script to restart it with a safe working config file

You need to have a copy of the safe config file in your .tilda folder with this filename:
config_0_safe

#!/bin/bash
cd ~/.tilda
echo pwd
size=`du config_0`
mv config_0 old/
cp config_0_safe config_0
cd ..
sleep 3
tilda &

I had tilda crash when I upgraded from 8.10 to 9.04, and deleting ~./tilda made it work. Basically, my situation is like described by gustavoyr in https://bugs.launchpad.net/ubuntu/+source/tilda/+bug/92264/comments/14

It seems to me that people are talking about different problems here - one that is fixed by removing configuration files, and the other that is persistent.

I can reproduce this bug in Jaunty amd64:

a3_nm@eta:~$ tilda
Unable to open lock directory: /home/a3_nm/.tilda/locks
Unable to open lock directory: /home/a3_nm/.tilda/locks

(tilda:6150): Gtk-CRITICAL **: gtk_file_chooser_select_filename: assertion `filename != NULL' failed

(tilda:6150): Gdk-CRITICAL **: gdk_x11_window_set_user_time: assertion `GDK_IS_WINDOW (window)' failed

(tilda:6150): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
Segmentation fault

This was the first time I installed Tilda, and deleting ~/.tilda does not solve this issue.

antoine, any idea why tilda is unable to open the lock directory? have you tried removing ~/.tilda ?

gerhard, is this still an issue for you? i assume you removed ~/.tilda, not ~./tilda ...

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Thank you for taking the time to report this bug and helping to make Ubuntu better. My apologies as I should not have marked this Invalid. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release - Maverick Meerkat. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

In Lucid, installed via Ubuntu Software Center, at the Terminal typed:

tilda

opened no problem (please see attached screenshot).

lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04

apt-cache policy tilda
tilda:
  Installed: 0.09.6-2
  Candidate: 0.09.6-2
  Version table:
 *** 0.09.6-2 0
        500 http://us.archive.ubuntu.com/ubuntu/ lucid/universe Packages
        100 /var/lib/dpkg/status

[Expired for tilda (Ubuntu) because there has been no activity for 60 days.]

Screenshot attached

ProblemType: Crash
Architecture: i386
CurrentDesktop: MATE
Date: Mon Aug 14 13:52:49 2017
DistroRelease: Ubuntu 17.10
ExecutablePath: /usr/bin/tilda
ExecutableTimestamp: 1467418488
ProcCmdline: tilda
ProcCwd: /home/charlie
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_GB.UTF-8
 SHELL=/bin/bash

apport log

ERROR: apport (pid 2269) Mon Aug 14 13:52:49 2017: called for pid 1540, signal 11, core limit 0
ERROR: apport (pid 2269) Mon Aug 14 13:52:49 2017: executable: /usr/bin/tilda (command line "tilda")
ERROR: apport (pid 2269) Mon Aug 14 13:52:49 2017: debug: session gdbus call: (true,)
ERROR: apport (pid 2269) Mon Aug 14 13:52:54 2017: wrote report /var/crash/_usr_bin_tilda.1000.crash