Your message dated Sat, 30 Jun 2007 17:39:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Mass closing of unreproducible LyX bugs
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: lyx-xforms
Version: 1.3.4-1
Severity: wishlist
When I run lyx-xforms <document>, it responses BadValue (integer
parameter out of range for operation) id: 39846052 and finishes.
-- System Information:
Debian Release: testing/unstable
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.22
Locale: LANG=es_ES, LC_CTYPE=es_ES
Versions of packages lyx-xforms depends on:
ii libaiksaurus0c102 1.0.1+cvs.2004.02.20-1 Aiksaurus, an English-language the
ii libc6 2.3.2.ds1-11 GNU C Library: Shared libraries an
ii libforms1 1.0-4 The XForms graphical interface wid
ii libgcc1 1:3.3.3-1 GCC support library
ii libice6 4.3.0-3 Inter-Client Exchange library
ii libjpeg62 6b-9 The Independent JPEG Group's JPEG
ii libsm6 4.3.0-3 X Window System Session Management
ii libstdc++5 1:3.3.3-1 The GNU Standard C++ Library v3
ii libx11-6 4.3.0-3 X Window System protocol client li
ii libxpm4 4.3.0-3 X pixmap library
ii lyx-common 1.3.4-1 High Level Word Processor - common
ii xlibs 4.3.0-3 X Window System client libraries m
-- no debconf information
--- End Message ---
--- Begin Message ---
Dear reporter,
I'm now closing your bug because of two reasons:
a) I can not reproduce the reported problem with the current LyX 1.4.4 release.
b) You did not respond to a request for more information on how to reproduce
the failure you reported.
If you have some evidence that the bug you reported still exists please
reopen the bug and provide some _new_ input on how to reproduce the reported
problem. You can read the full bug log on http://bugs.debian.org/<bugnumber>
to re-read what has been reported about the bug in question so far.
Regards,
Sven
--
If you won't forgive me the rest of my life
Let me apologize while I'm still alive
I know it's time to face all of my past mistakes
[Less than Jake - Rest Of My Life]
--- End Message ---
