[Pkg-fonts-devel] Bug#810849: marked as done (fontforge: segfault after start)
Your message dated Thu, 24 Nov 2016 05:46:59 +0100
with message-id <20161124044659.GA5674@angband.pl>
and subject line Re: [Pkg-fonts-devel] Bug#810849: Fine
has caused the Debian Bug report #810849,
regarding fontforge: segfault after start
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
810849: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810849
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
Subject: fontforge: segfault after start
Package: fontforge
Version: 20120731.b-7.1
Severity: grave
*** Please type your report below this line ***
Dear Maintainer,
Fontforge segfaults after a few seconds (input beyond the startup screen
impossible, but for the segfault, no interaction is needed) on my Debian
testing machine - gdb gives this:
Starting program: /usr/bin/fontforge
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
Copyright (c) 2000-2012 by George Williams.
Executable based on sources from 14:57 GMT 31-Jul-2012-ML.
Library based on sources from 14:57 GMT 31-Jul-2012.
Program received signal SIGSEGV, Segmentation fault.
0x00007ffff790dc3c in ?? () from /usr/lib/libfontforge.so.1
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.3.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages fontforge depends on:
ii fontforge-common 20120731.b-7.1
ii libc6 2.21-6
ii libcairo2 1.14.4-1
ii libfontconfig1 2.11.0-6.3
ii libfontforge1 20120731.b-7.1
ii libfreetype6 2.6.1-0.1
ii libgdraw4 20120731.b-7.1
ii libgif7 5.1.1-0.2
ii libglib2.0-0 2.46.2-3
ii libice6 2:1.0.9-1+b1
ii libjpeg62-turbo 1:1.4.1-2
ii libpango-1.0-0 1.38.1-1
ii libpangocairo-1.0-0 1.38.1-1
ii libpangoft2-1.0-0 1.38.1-1
ii libpangoxft-1.0-0 1.38.1-1
ii libpng12-0 1.2.54-1
ii libpython2.7 2.7.11-2
ii libsm6 2:1.2.2-1+b1
ii libspiro0 1:0.5.20150702-4
ii libtiff5 4.0.6-1
ii libuninameslist0 0.5.20150701-1
ii libx11-6 2:1.6.3-1
ii libxft2 2.3.2-1
ii libxi6 2:1.7.5-1
ii libxml2 2.9.3+dfsg1-1
ii zlib1g 1:1.2.8.dfsg-2+b1
fontforge recommends no packages.
Versions of packages fontforge suggests:
ii autotrace 0.31.1-16+nmu1
pn fontforge-doc <none>
pn fontforge-extras <none>
ii potrace 1.13-2
ii python-fontforge 20120731.b-7.1
-- no debconf information
--- End Message ---
--- Begin Message ---
On Wed, Nov 23, 2016 at 09:02:46PM +0100, Christian Petersen wrote:
>
> New version of fontforge is working fine (for me).
Cool then, thanks for testing!
--
The bill declaring Jesus as the King of Poland fails to specify whether
the addition is at the top or end of the list of kings. What should the
historians do?
--- End Message ---
Reply to: