Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 17862 bytes cmdline: tilda component: tilda Attached file: coredump, 47853568 bytes crash_function: IA__gdk_x11_window_set_user_time executable: /usr/bin/tilda kernel: 2.6.35.12-90.fc14.x86_64 package: tilda-0.9.6-4.fc14 rating: 4 reason: Process /usr/bin/tilda was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1304356628 uid: 500 How to reproduce ----- 1. 2. 3. .
Created attachment 496313 [details] File: backtrace
Package: tilda-0.9.6-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Tilda 2. Close it. Comment ----- I am not even sure why tilda is on my computer. I simply tried to close the application from inside its GUI and got a crash report.
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Just start and close initial configuration window.
Package: tilda-0.9.6-4.fc14 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- Just installed tilda, config window popped up, hit close with no changes. Then this crash happened.
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.kann dazu nichts sagen 2. 3. Comment -----
Package: tilda-0.9.6-4.fc14 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- crashes on startup
Package: tilda-0.9.6-4.fc14 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- install tilda and run it - it opens theconfiguration dialogue on the first run - i accepted the defaults and closed it. Run tilda again and it seg faults
Package: tilda-0.9.6-4.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Crashed at startup with xfce4, doesn't with gnome. 2. 3.
A workaround for me on F15 x86_64: start the config with 'tilda -C' and make sure 'Start Tilda hidden' is checked. YMMV. I guess the GdkWindow* that is passed to gdk_x11_window_set_user_time(...) is not getting init'd properly when Tilda starts pulled down.
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Installed Tilda, clicked OK without making changes when initial configuration dialog popped up. Hit F1 to drop down the Tilda terminal, and it crashed. 2. 3.
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- Just try start tilda
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I've just logged in after a fresh boot this isn't the first time it happened to me, but it doesn't happen always
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- launching it immediately throws a segfault. gnome 2.32.0
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I can't start it 2. 3.
Package: tilda-0.9.6-4.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Start TILDA 2. 3.
installed updates installed tilda via yum after first ran, configuration window appeared and then hanged rating: 4 Package: tilda-0.9.6-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
installed updates installed tilda via yum after first ran, configuration window appeared and then hanged running tilda -C showed again the settings dialog and after i have did same settings as before it has been successfully ran... So tilda -C fixed my issue. rating: 4 Package: tilda-0.9.6-6.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne)
Backtrace analysis found this bug to be similar to bug #538645, closing as duplicate. Bugs which were found to be similar to this bug: bug #538645, bug #541786, bug #544419, bug #545457, bug #547125, bug #547466, bug #553909, bug #555229, bug #581742, bug #583268, bug #585547, bug #585550, bug #588087, bug #589875, bug #589901, bug #590185, bug #591437, bug #592267, bug #592564, bug #592606, bug #592807, bug #593595, bug #597465, bug #597531, bug #597613, bug #598785, bug #599454, bug #601916, bug #601975, bug #603080, bug #606729, bug #611659, bug #611998, bug #612846, bug #615645, bug #616889, bug #617830, bug #618212, bug #620774, bug #627156, bug #627363, bug #627873, bug #644269, bug #748144, bug #756236, bug #756237 This comment is automatically generated. *** This bug has been marked as a duplicate of bug 538645 ***