Your message dated Tue, 8 Jul 2008 02:31:51 -0700
with message-id <[EMAIL PROTECTED]>
and subject line Closing old AbiWord bugs
has caused the Debian Bug report #194184,
regarding abiword: printing problem with abiword
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 [EMAIL PROTECTED]
immediately.)


-- 
194184: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=194184
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: abiword
Version: 1.9.0+cvs.2003.05.10-1
Severity: normal
        The lastest version (and perhaps the 1.9 series) of abiword does not
print correctly on my postscript printer. The characters are cramped and
overlaid one upon the other. It appears that abiword uses a different
font metric for typeseting than the printer or that there is a font mismatch
(but on screen, the document is displayed correctly). The problem may be
related to the printer, but it _does not exist in earlier (<=1.0.2) versions_.
I have tested on many (MS-Word) docucments, none print correctly and worse
some does not print at all with this error message

(abiword:5349): Gtk-CRITICAL **: file gtkentry.c: line 3361 
(gtk_entry_set_text): assertion `text != NULL' failed
sh: -c: option requires an argument

        I can send you a document which print badly and one that doesn't print
if you like.

-- System Information
Debian Release: testing/unstable
Kernel Version: Linux guepard 2.4.20-686 #1 Mon Jan 13 22:22:30 EST 2003 i686 
unknown unknown GNU/Linux

Versions of the packages abiword depends on:
ii  abiword-common 1.9.0+cvs.2003 WYSIWYG word processor based on GTK2
ii  libaspell15    0.50.3-11      The GNU Aspell spell-checker runtime toolkit
ii  libatk1.0-0    1.2.3-1        The ATK accessibility toolkit
ii  libc6          2.3.1-16       GNU C Library: Shared libraries and Timezone
ii  libfontconfig1 2.2.0-2        generic font configuration library (shared l
ii  libfreetype6   2.1.4-2        FreeType 2 font engine, shared library files
ii  libfribidi0    0.10.4-1       Free Implementation of the Unicode BiDi algo
ii  libgcc1        3.3-0pre9      GCC support library
ii  libglade2-0    2.0.1-3        Library to load .glade files at runtime
ii  libglib2.0-0   2.2.1-3        The GLib library of C routines
ii  libgtk2.0-0    2.2.1-4        The GTK+ graphical user interface library
ii  libgucharmap0  0.6.0-2        Unicode browser widget library (shared libra
ii  libpango1.0-0  1.2.1-3        Layout and rendering of internationalized te
ii  libperl5.8     5.8.0-17       Shared Perl library.
ii  libpng12-0     1.2.5-10       PNG library - runtime
ii  libpopt0       1.6.4-2        lib for parsing cmdline parameters
ii  libstdc++5     3.3-0pre9      The GNU Standard C++ Library v3
ii  libxft2        2.1.1-2        advanced font drawing library for X
ii  libxml2        2.5.6-2        GNOME XML library
ii  xlibs          4.2.1-6        X Window System client libraries
ii  zlib1g         1.1.4-11       compression library - runtime


--- End Message ---
--- Begin Message ---
Hi there.

You are receiving this email because at some point, you have filed a bug
against the AbiWord package in Debian. I am now closing the bug you
filed with this email, for one of these reasons:

- The bug has been fixed upstream for a long time.
- Upstream refuses to fix your bug.
(You can check the tags on the bug report referenced by the number in
the subject line of this message to distinguish between the two above.)
- The bug is no longer relevant or applies to a version of AbiWord that
  is no longer available in Debian at all.
- You were asked to provide more information about your initial bug
  report, and either that information was not sufficient or you didn't
  get back to us at all.

If you feel that this is in error, and you have been checking your email
everyday for several years pining for more discussion about your bug only
to see this, feel free to reopen the bug and continue the party.

Thank you!

-- 
Joshua Kwan


--- End Message ---

Reply via email to