xfstt assert failure: *** stack smashing detected ***: /usr/bin/xfstt terminated

Bug #807726 reported by GNAServicesInc
146
This bug affects 18 people
Affects Status Importance Assigned to Milestone
xfstt (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

IDk, I just logged it and it the report came up

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: xfstt 1.8-2
Uname: Linux 3.0.6-gna3-rc6 x86_64
Architecture: amd64
AssertionMessage: *** stack smashing detected ***: /usr/bin/xfstt terminated
Date: Tue Jul 5 21:31:32 2011
ExecutablePath: /usr/bin/xfstt
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110629)
ProcCmdline: /usr/bin/xfstt --daemon --notcp
ProcEnviron: PATH=(custom, no user)
Signal: 6
SourcePackage: xfstt
StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 __libc_message (do_abort=2, fmt=0x7f5989ab8e7d "*** %s ***: %s terminated\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:189
 __fortify_fail (msg=0x7f5989ab8e65 "stack smashing detected") at fortify_fail.c:32
 __stack_chk_fail () at stack_chk_fail.c:29
Title: xfstt assert failure: *** stack smashing detected ***: /usr/bin/xfstt terminated
UpgradeStatus: Upgraded to oneiric on 2011-07-08 (0 days ago)
UserGroups:

Revision history for this message
GNAServicesInc (gnaservicesinc) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 raise (sig=1641) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:90
 __libc_message (do_abort=2, fmt=0x7f5989ab8e7d ") [%p]") at ../sysdeps/unix/sysv/linux/libc_fatal.c:164
 backtrace_helper (ctx=0x669, a=0x669) at ../sysdeps/x86_64/../ia64/backtrace.c:58

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xfstt (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Changed in xfstt (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Svartalf (frank-earlconsult) wrote :

Confirmed. I've pushed quite a few bug-crashes from Xubuntu 12.04 up. Problems are inconsistent- random crashes of this and other apps. Some hang up the machine in a manner that you WON'T be getting bug reports as there's nothing to do but hard-reset the box. This isn't hardware (i.e. RAM, etc...)- this is happening with FIVE boxes of differing types all certified hardware.

tags: added: precise
Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Happens any time my desktop starts and after that also random during usage.
Precise 12.04.

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Please, can someone look into this? I'm getting this error every hour or so?

Revision history for this message
EMCees (cees-ieee) wrote :

I do get the same problem every 25 minutes or so.

Revision history for this message
Tani Hosokawa (tani-a) wrote :

I believe I have figured out a simple workaround, as well as a pretty good clue as to the source of this error. For me, it turned out that there were a couple of broken .ttf files, specifically

/usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-BoldOblique.ttf

/usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-BoldItalic.ttf

The bug is more easily duplicated by running

# xfstt --sync

When you run that, you can see it going through the font directories in /usr/share/fonts until you hit a crash. Then you can weed out the broken fonts from that directory, and the problem will go away completely.

I also had two broken .ttf files from a private font package, which probably won't affect most people, but to find them I just copied all the fonts from the directory that had broken fonts and used this perl script to iterate through them until I got a stack trace from xfstt. It might be useful for people who have additional broken .ttf files that aren't in a standard .deb

#!/usr/bin/perl

my $dir = "ttf-dejavu";
opendir D, "/root/$dir";
while (my $filename = readdir D) {
   -f "/root/$dir/$filename" or next;
   print "$filename\n";
   system "mv","/root/$dir/$filename","/usr/share/fonts/truetype/$dir";
   system "xfstt --sync";
   <STDIN>;
}
closedir D;

Revision history for this message
Paulin Todev (paulin-todev) wrote :

I have the same problem with the same two fonts:
DejaVuSansCondensed-BoldOblique.ttf
DejaVuSerifCondensed-BoldItalic.ttf
It crashes on every startup and every once in a while during usage.

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

Removing ttf-dejavu and liberation made the "system problem detected" pop up go away.
But as a result I'm getting ugly fonts in Firefox... waiting for a solution...

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

I noticed that the system crashes everytime I'm in the process of connecting to the network (with the above fonts still installed).
Can anyone confirm this?

Revision history for this message
Joost Van Durme (joostvandurme) wrote :

I ran the script from Paulin Todev and I got a long list of broken fonts:

DejaVuSerifCondensed-BoldItalic.ttf
DejaVuSans-BoldOblique.ttf
DejaVuSansCondensed-BoldOblique.ttf
DejaVuSerif-Italic.ttf
DejaVuSansMono-Oblique.ttf
DejaVuSansCondensed-Bold.ttfDejaVuSans.ttf
DejaVuSansCondensed.ttf
DejaVuSans-Bold.ttf
DejaVuSerifCondensed.ttf
DejaVuSansMono-Bold.ttf
DejaVuSans-ExtraLight.ttf
DejaVuSansMono-BoldOblique.ttf

LiberationSansNarrow-Italic.ttf
LiberationSerif-Italic.ttf
LiberationSerif-BoldItalic.ttf
LiberationMono-BoldItalic.ttf
LiberationSans-Regular.ttf
LiberationSans-Italic.ttf
LiberationSansNarrow-Bold.ttf
LiberationMono-Italic.ttf
LiberationSansNarrow-Regular.ttf
LiberationSans-Bold.ttf
LiberationSerif-Bold.ttf
LiberationMono-Regular.ttf
LiberationMono-Bold.ttf
LiberationSansNarrow-BoldItalic.ttf
LiberationSans-BoldItalic.ttf
LiberationSerif-Regular.ttf

Is there any way I can get good versions of these fonts?

tags: added: bugpattern-needed
tags: added: trusty
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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