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

Bug#245978: xli on this png file crashes entire xserver



reassign 245978 xserver-xfree86: crash when viewing attached PNG image with xli
severity 245978 important
tag 245978 + upstream moreinfo
thanks

On Mon, Apr 26, 2004 at 03:29:46PM +0800, Dan Jacobson wrote:
> Package: xli
> Version: 1.17.0-14
> Severity: grave
> 
> $ xli eq_namerica.png #attached below
> crashes entire xserver.

A crash in the X server is a bug in the X server, under most
circumstances.

> It doesn't happen with other viewers.
> Please reassign, reprioritize bug as appropriate.

Reassigning and altering severity.  Before much more can be done, we're
going to need more information, as described below.

[The following is a form letter.]

Dear bug submitter,

Since the XFree86 X server is a large and complex piece of software, some
more informtion is required of you before this bug can be handled.  Please
run the following commands from a shell prompt to gather and deliver this
information to us:

$ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1
$ mailx -s "Re: Bug#245978" 245978@bugs.debian.org < /tmp/output

If you do not have a "mailx" command on your system, you can get by
installing the "mailx" Debian package; for example, with the "aptitude
install mailx" or "apt-get install mailx" commands as root.  Alternatively,
you can also use a mail command that is compatible with mailx's
command-line syntax, such as "mutt".

One very good way to file bugs with the Debian Bug Tracking System is to
use the "reportbug" package and command of the same name.  The reportbug
program does a lot of automatic information-gathering that helps package
maintainers to understand your system configuration, and also ensures that
your message to the Debian Bug Tracking System is well-formed so that it is
processed correctly by the automated tools that manage the reports.  (If
you've ever gotten a "bounce" message from the Debian Bug Tracking System
that tells you your message couldn't be processed, you might appreciate
this latter feature.)

Therefore, I strongly urge you to give "reportbug" a try as your primary
bug reporting tool for the Debian System in the future.

If you *did* use reportbug to file your report, then you'r receiving this
message because the information we expected to see was not present.

If you deliberately deleted this information from the report, please don't
do that in the future, even if it seems like it makes the mail too large.
50 kB (kilobytes) of configuration and log data is typical.  Only if the
included information greatly exceeds this amount (more than 100 kB) should
you consider omitting it; instead, put it up on the World Wide Web
somewhere and provide URLs to it in your report, or in subsequent followup
by mailing <245978@bugs.debian.org>.

Thank you!

-- 
G. Branden Robinson                |      "There is no gravity in space."
Debian GNU/Linux                   |      "Then how could astronauts walk
branden@debian.org                 |       around on the Moon?"
http://people.debian.org/~branden/ |      "Because they wore heavy boots."

Attachment: signature.asc
Description: Digital signature


Reply to: