mkfontscale crashed with signal 7 in FT_Stream_ReadLong()

Bug #286419 reported by Björn Torkelsson
266
This bug affects 38 people
Affects Status Importance Assigned to Milestone
freetype (Ubuntu)
Invalid
Medium
Unassigned
Nominated for Lucid by Swâmi Petaramesh

Bug Description

Binary package hint: xfonts-utils

Something crashes mkfontscale everytime I start a new session

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/mkfontscale
NonfreeKernelModules: openafs
Package: xfonts-utils 1:7.4+1ubuntu1
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/mkfontscale -b -s -l /home/username/.gnome2/share/cursor-fonts /home/username/.gnome2/share/fonts
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_DK.UTF-8
 SHELL=/bin/bash
 LC_NUMERIC=en_US.UTF-8
Signal: 7
SourcePackage: xfonts-utils
StacktraceTop:
 FT_Stream_ReadLong () from /usr/lib/libfreetype.so.6
 ?? () from /usr/lib/libfreetype.so.6
 ?? () from /usr/lib/libfreetype.so.6
 ?? () from /usr/lib/libfreetype.so.6
 FT_Open_Face () from /usr/lib/libfreetype.so.6
Title: mkfontscale crashed with signal 7 in FT_Stream_ReadLong()
Uname: Linux 2.6.27-7-generic x86_64
UserGroups: adm admin audio cdrom dialout dip floppy kvm lpadmin netdev plugdev powerdev scanner video

Tags: apport-crash
Revision history for this message
Björn Torkelsson (torkel) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:FT_Stream_ReadLong (stream=0x1dfb460,
sfnt_init_face (stream=0x1dfb460, face=0x1dfb4c0,
tt_face_init (stream=0x1dfb460, ttface=0x1dfb4c0,
open_face (driver=0x1df68d0, stream=0x1dfb460,
FT_Open_Face (library=0x1df2720,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Changed in xfonts-utils:
importance: Undecided → Medium
Revision history for this message
Bryce Harrington (bryce) wrote :

[This is an automated message]

Hi torkel,

Please attach the output of `lspci -vvnn` too.

Changed in xfonts-utils:
status: New → Incomplete
Revision history for this message
Björn Torkelsson (torkel) wrote :

The output of lspci is attached.

Hm. it looks like I forgot to mention that I got the crashes when running $HOME/.gnome2 on ecryptfs. Moving it out of ecryptsfs made the crashes to dissapear.

Revision history for this message
Michael Vogt (mvo) wrote :

Hey Bryce. I got the same crash (after a intrepid->jaunty ugprade). I understand that lspci -vvnn is very useful for X releated crashes. But I think you should limit your script to xserver-xorg-* and not include packages like "xfont-utils".

Changed in xfonts-utils:
status: Incomplete → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Can someone who's seeing this problem please forward a tarball of the ~/.gnome2/share/cursor-fonts and ~/.gnome2/share/fonts directories mentioned in the apport commandline? This bug is not reproducible for me here on a system with no local fonts installed.

Changed in freetype:
status: Confirmed → Incomplete
Revision history for this message
C.E. (curtisekstrom) wrote :

I installed a custom font on kubuntu jaunty beta and got the same crash on restart. Those folders don't exist on my installation. (.gnome2 has only one folder in it, and it isn't "share") Is there a path with the necessary info in KDE? If so, I'd be happy to upload it. I just don't have that much experience with linux and bug reporting in general...

Revision history for this message
sun-wukong (sun-wukong) wrote :

I ran into this bug on a fresh Kubuntu 9.04 beta install.
Thus, Gnome is not installed.

Attached, the output of lspci -vvnn

Revision history for this message
starslights (starslights) wrote :

Hello,

I run on Kubuntu Karmic 64 bits , 2.6.31-11-generic and after have crashes all system it appeare at start this bug report.

Revision history for this message
Martin Nowack (martin-nowack) wrote :

I have the same problem too with an Kubuntu Karmic (which was upgraded).
The following last lines in dmesg occur multiple times (even when I try to invoke it by hand):
[ 193.625888] ecryptfs_read_lower: octets_read = [-21]; expected [4096]

Revision history for this message
Christian González (droetker) wrote :

same crash here on each session start on Kubuntu Karmic, $HOME encrypted; I have no ~/.gnome* directory.

Revision history for this message
Thalis (kamakas57) wrote :

This is kubuntu karmic bug. after the installation of the pre-release

Revision history for this message
Matthew Brooks (mjbrooks) wrote :

This happens to me fairly randomly and it doesn't even require that I do anything. For example, there was no error last night but I left my system on all night and when I checked it in the morning, the error had occurred.

Is this related to having custom fonts installed?

Revision history for this message
Randall Leeds (randall-leeds) wrote :

I can confirm this behavior on Kubuntu Karmic 9.10. Installed around Alpha 2 and been updating. Only noticed it today. Can't verify whether it was package upgrade or installation of new font (http://www.ms-studio.com/FontSales/anonymouspro.html) that caused it. Removing the font doesn't seem to help, though. It was installed through System Settings -> Font Installer. In any case, the font functions normally, so I suspect it's (at least mostly) unrelated. Having anything crash at login is a very poor user experience.

Changed in freetype (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Christian (christian-bley2) wrote :

it`s the same as on x86 architecture systems...

Revision history for this message
Randall Leeds (randall-leeds) wrote :

Ok... well. This just went away as mysteriously as it appeared.

Revision history for this message
Alim Akyol (alimakyol) wrote :

It happened to me after lucid beta2 upgrade from karmic. Everything went well during upgrade, except grub install. I think I misplaced /boot partition.
After restarting my computer, I received this crash report.

Revision history for this message
Matthew Mott (orbweaver) wrote :

Confirmed on Lucid Beta2 amd64, upgraded from Karmic.

Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

Changed in freetype (Ubuntu):
status: Confirmed → Invalid
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.