ghostscript segfaults on amd64 when building plplot

Bug #1197967 reported by Matthias Klose
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
ghostscript (Ubuntu)
Fix Released
High
Unassigned
Saucy
Fix Released
High
Unassigned

Bug Description

on saucy/amd64, call debian/rules build-indep on amd64. fails with:

kpathsea: Running mktexpk --mfmode / --bdpi 600 --mag 1+0/600 --dpi 600 ptmb8r
mktexpk: Running gsftopk ptmb8r 600
gsftopk(k) version 1.19.2/907
[1] [2] [3] [4] [5] [6] [7] [8] [9] [11] [12] [14] [15] [16] [17] [30] [31]
[32] [33] [34] [35] [36] [37] [38] [39] [40] [41] [42] [43] [44] [45] [46] [47]
[48] [49] [50] [51] [52] [53] [54] [55] [56] [57] [58] [59] [60] [61] [62] [63]
[64] [65] [66] [67] [68] [69] [70] [71] [72] [73] [74] [75] [76] [77] [78] [79]
[80] [81] [82] [83] [84] [85] [86] [87] [88] [89] [90] [91] [92] [93] [94] [95]
[96] [97] [98] [99] [100] [101] [102] [103] [104] [105] [106] [107] [108] [109]
[110] [111] [112] [113] [114] [115] [116] [117] [118] [119] [120] [121] [122]
[123] [124] [125] [126] [130] [131] [132] [133] [134] [135] [136] [137] [138]
[139] [140] [147] [148] [149] [150] [151] [152] [153] [154] [155] [156] [159]
[161] [162] [163] [164] [165] [166] [167] [168] [169] [170] [171] [172] [173]
[174] [175] [176] [177] [178] [179] [180] [181] [182] [183] [184] [185] [186]
[187] [188] [189] [190] [191] [192] [193] [194] [195] [196] [197] [198] [199]
[200] [201] [202] [203] [204] [205] [206] [207] [208] [209] [210] [211] [212]
[213] [214] [215] [216] [217] [218] [219] [220] [221] [222] [223] [224gs died due to signal 11

grep: ptmb8r.log: No such file or directory
mktexpk: `gsftopk ptmb8r 600' failed to make ptmb8r.600pk.
kpathsea: Appending font creation commands to missfont.log.

!pdfTeX error: /usr/bin/pdfjadetex (file ptmb8r): Font ptmb8r at 600 not found
 ==> Fatal error occurred, no output PDF file produced!
make[3]: *** [doc/docbook/src/plplot-5.9.9.pdf] Error 1

Matthias Klose (doko)
Changed in ghostscript (Ubuntu):
importance: Undecided → High
milestone: none → ubuntu-13.07
status: New → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can you find out with which command line Ghostscript gets called and which PostScript or PDF file gets fed into Ghostscript here? Can you attach the file and tell us which command line got used? Thanks.

Changed in ghostscript (Ubuntu Saucy):
status: Confirmed → Incomplete
Revision history for this message
Matthias Klose (doko) wrote :

No, I won't have the time to do this. However this is reproducible in a saucy chroot.

Changed in ghostscript (Ubuntu Saucy):
status: Incomplete → New
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

I can reproduce the bug on my 64-bit Saucy real-iron system. See Apport information in bug 1200280.

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

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in ghostscript (Ubuntu):
status: New → Confirmed
Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Can be reproduced in a more straight forward way by running the command:

gsftopk ptmb8r 600

This makes Ghostscript segfault in both Raring and Saucy (both GS 9.07).

Revision history for this message
Till Kamppeter (till-kamppeter) wrote :

Works with Ghostscript 9.09rc1 (Saucy).

Changed in ghostscript (Ubuntu Saucy):
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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