Tilda X crash

[Kurt Kraut]

Binary package hint: tilda

After installing Tilda and attemped to change some default configs, I'm not able to start tilda again. Thru terminal I get this error:

ktk@ktk6:~/delme$ tilda --sync
The program 'tilda' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 11 error_code 10 request_code 33 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

[Daniel Holbach (dholbach)]

Thanks for your bug report. Can you attach the output of the following instructions?

gdb tilda
...
(gdb) break gdk_x_error
(gdb) run
...
(gdb) thread apply all bt full
...

[Kurt Kraut (kurtkraut)]

This is what I got:

ktk@ktk6:~$ gdb tilda
GNU gdb 6.6-debian
Copyright (C) 2006 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 "i486-linux-gnu"...
(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run
Starting program: /usr/bin/tilda
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1220494688 (LWP 14992)]
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
---Type <return> to continue, or q <return> to quit---
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
(no debugging symbols found)
[New Thread -1222358128 (LWP 15001)]

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed
(no debugging symbols found)
[New Thread -1230775408 (LWP 15007)]
(no debugging symbols found)

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICAL **: gtk_window_resize: assertion `height > 0' failed

(tilda:14992): Gtk-CRITICA...

[Anonym25712 (anonym25712)]

Hi,

I just got the same error on a fresh Feisty install. I had to remove the ~/.tilda directory to get it to work again. Now it works even with my own preferences, I don't know what happened exactly.

[Phrozen (contact-stonedgenius)]

I was getting same error but after disabling 'Animated Pulldown' under 'Appearance' options it works fine.

[Áron Sisak (asisak)]

Can you please try if it still happens with latest Gutsy x86 tilda (0.09.4-4)?
I tried to reproduce and failed.

[Pau Oliva (poliva)]

I had the same problem on Ubuntu 7.10 (fresh install) and tilda 0.09.4-4:

$ tilda

(tilda:10582): Gdk-CRITICAL **: gdk_window_set_geometry_hints: assertion `GDK_IS_WINDOW (window)' failed
The program 'tilda' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAccess (attempt to access private resource denied)'.
  (Details: serial 11 error_code 10 request_code 33 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)

Then I launched tilda as root using 'gksudo tilda' and it started properly but I couldn't use the default keybinding (NONE+F1) to launch it. So this made me think the problem was caused because I had the F1 key customized in "System -> Preferences -> Keyboard Shorcuts".

The solution is to change the tilda key binding on ~/.tilda/config_0 or to remove the custom key binding in Gnome settings that uses the same key binding as tilda.

Hope this helps. Let me know if you need more testing to reproduce the bug.

[Batwam (batwam)]

Thanks Pau, same problem, same fix for tilda 0.09.4 on Gentoo

[Dan (orblivion)]

I can confirm this problem in version 0.94. Having dropdown keyboard shortcut the same as "System -> Preferences -> Keyboard Shorcuts" causes it to crash. However it is fixed circa .95; it prompts for a new keybinding if it collides with the one in the control panel. .96 is in Intrepid, so closing as Fix Released.