Ubuntu
tilda package

tilda crashed with SIGSEGV in __libc_start_main()

Bug #349617 reported by bert07
38
This bug affects 3 people
Affects Status Importance Assigned to Milestone
tilda (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: tilda

In Ubuntu 9.04 beta i386.
Just logging into my account made tilda crash.

The program (tilda) just should have started hidden.
Instead it crashed, and I couldn't get it load again afterwards.

ProblemType: Crash
Architecture: i386
CrashCounter: 1
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/bin/tilda
NonfreeKernelModules: fglrx
Package: tilda 0.09.6-1
ProcCmdline: /usr/bin/tilda
ProcEnviron:
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: tilda
Stacktrace:
 #0 0x080501eb in ?? ()
 #1 0x0805159f in ?? ()
 #2 0xb74c0775 in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 #3 0x0804d3d1 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
 __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
Title: tilda crashed with SIGSEGV in __libc_start_main()
Uname: Linux 2.6.28-11-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
bert07 (marien.bert) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:tilda_keygrabber_bind (keystr=0x0, tw=0x9a36a70) at key_grabber.c:260
main (argc=) at tilda.c:599

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Changed in tilda:
importance: Undecided → Medium
Revision history for this message
bert07 (marien.bert) wrote :

I had some other troubles with tilda here: It just wouldn't start up any more when logged in as user (ir did when logged in as root).

So I removed the old (hidden) tilda files ".tilda", logged out and in again, made a new configuration, and till now it works.

Of course I have not the knowledge to say that the old configuration files were indeed the problem.

Revision history for this message
bert07 (marien.bert) wrote :

Till now, the program still runs as it should.
Perhaps the old (hidden) configuration files from previous Ubuntu's might have caused the problem?

Revision history for this message
Dimitrios Symeonidis (azimout) wrote :

So, can we consider the issue resolved?

visibility: private → public
Dimitrios Symeonidis (azimout)
Changed in tilda (Ubuntu):
status: New → Incomplete
Revision history for this message
Ken (kkinder) wrote :

On 9.10, I'm getting:

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

(tilda:22126): Gtk-CRITICAL **: gtk_container_foreach: assertion `GTK_IS_CONTAINER (container)' failed
fish: Job 1, “tilda” terminated by signal SIGSEGV (Address boundary error)

On start up, right after installing tilda via apt-get.

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in tilda (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.