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 #234673,
regarding abiword-plugins: plugins causing Abiword to seg fault
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.)
--
234673: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=234673
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: abiword-plugins
Version: 2.0.3+cvs.2004.02.22-1
Severity: normal
Tags: sid
It seems that every time I try to load a plugin, abiword seg faults.
I've tried this with a number of different plugins, and I've tried
loading the .so's as well as the .la's. I can get a strace if need be.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.24-1-k7
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8
Versions of packages abiword-plugins depends on:
ii abiword-common 2.0.3+cvs.2004.02.22-1 WYSIWYG word processor based on GT
ii libaiksaurus0c102 1.0.1+cvs.2004.02.20-1 Aiksaurus, an English-language the
ii libaiksaurusgtk0c 1.0.1+cvs.2004.02.20-1 graphical interface to the Aiksaur
ii libart-2.0-2 2.3.16-1 Library of functions for 2D graphi
ii libatk1.0-0 1.4.1-1 The ATK accessibility toolkit
ii libbz2-1.0 1.0.2-1 A high-quality block-sorting file
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libexpat1 1.95.6-6 XML parsing C library - runtime li
ii libfontconfig1 2.2.1-16 generic font configuration library
ii libfreetype6 2.1.7-2 FreeType 2 font engine, shared lib
ii libfribidi0 0.10.4-1 Free Implementation of the Unicode
ii libgcc1 1:3.3.3-1 GCC support library
ii libglade2-0 2.0.1-6 Library to load .glade files at ru
ii libglib2.0-0 2.2.3-1 The GLib library of C routines
ii libgsf-1 1.8.2-6 Structured File Library - runtime
ii libgtk2.0-0 2.2.4-3 The GTK+ graphical user interface
ii libice6 4.3.0-2 Inter-Client Exchange library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libncurses5 5.3.20030719-5 Shared libraries for terminal hand
ii libots0 0.4.2+cvs.2004.02.20-1 Open Text Summarizer (library)
ii libpango1.0-0 1.2.5-2.1 Layout and rendering of internatio
ii libpng12-0 1.2.5.0-5 PNG library - runtime
ii libpsiconv5 0.8.3+cvs.2004.02.14-1 a library for handling Psion files
ii libreadline4 4.3-10 GNU readline and history libraries
ii librsvg2-2 2.4.0-3 SAX-based renderer library for SVG
ii libsm6 4.3.0-2 X Window System Session Management
ii libstdc++5 1:3.3.3-1 The GNU Standard C++ Library v3
ii libwmf0.2-7 0.2.8-1.1 Windows metafile conversion librar
ii libwpd7 0.7.1-2 Library for handling WordPerfect d
ii libx11-6 4.3.0-2 X Window System protocol client li
ii libxft2 2.1.2-5 FreeType-based font drawing librar
ii libxml2 2.6.6-1 GNOME XML library
ii libxrender1 0.8.3-5 X Rendering Extension client libra
ii python2.3 2.3.3-6 An interactive high-level object-o
ii xlibs 4.3.0-2 X Window System client libraries m
ii zlib1g 1:1.2.1-4 compression library - runtime
-- no debconf information
--- 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 ---
