[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#332431: marked as done (gs-gpl: segfault with -sDEVICE=x11 -dTextAlphaBits=4 -dGraphicsAlphaBits=2 -dMaxBitmap=10000000)

Your message dated Sun, 6 Feb 2011 23:20:35 +0100
with message-id <201102062320.36975.roucaries.bastien@gmail.com>
and subject line Done: gs-gpl: segfault with -sDEVICE=x11 -dTextAlphaBits=4 -dGraphicsAlphaBits=2 -dMaxBitmap=10000000
has caused the Debian Bug report #332431,
regarding gs-gpl: segfault with -sDEVICE=x11 -dTextAlphaBits=4 -dGraphicsAlphaBits=2 -dMaxBitmap=10000000
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.)


-- 
332431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=332431
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: gv
Version: 3.6.1-10

When viewing page 2 of http://www.arxiv.org/ps/astro-ph/0407201 ,
gv has been observed to misbehave on several of our sarge desktops
(all machines we tested this on, in fact).

1. On two systems (kernel 2.6.13.2), it displays an empty error box 
(see bug 297558) and fails to display the page. Viewing the same file 
directly with gs does display the page, however, including the figure 
it contains. Running gv under gdb shows that it's getting a SIGPIPE in 
a write() call.

2. On three machines (all running a 2.4.31 kernel) no error box appears 
but the machine locks up, remaining pingable and nmap'pable but not 
accepting keyboard input or inbound ssh. The fact that the system hangs 
obviously indicates a further problem beyond gv; I mention it here mainly 
as a caveat to anyone who wishes to reproduce the gv bug. After
upgrading one of these machines to a 2.6 kernels, the symptoms became
as in paragraph 1.

--- End Message ---
--- Begin Message --- 
do not crash in recent version

--- End Message ---
Reply to: