Package: reportbug
Version: 3.7.1
Severity: important
Hi,
I wrote a long -- well, some would say massive -- presubj message for
xserver-xfree86 (attached). It will definitely be longer than some
people's terminals are tall.
reportbug should invoke a pager (probably sensible-pager) to scroll the
presubj file. If you didn't want to do so unconditionally, you could count
the number of lines in it first, and compare it to the tty's number of
lines. I'm not sure how to do the latter in Python off the top of my head.
The former seems to be as easy as:
file = open("/usr/share/bug/%s/presubj" % (package,))
numlines = len(file.readlines())
-- Package-specific info:
** Environment settings:
EDITOR="/usr/bin/vim"
DEBEMAIL="[EMAIL PROTECTED]"
DEBFULLNAME="Branden Robinson"
** /home/branden/.reportbugrc:
reportbug_version "2.20"
mode expert
ui text
realname "Branden Robinson"
email "[EMAIL PROTECTED]"
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: powerpc (ppc)
Kernel: Linux 2.6.9-powerpc-smp
Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages reportbug depends on:
ii python2.3 2.3.5-1 An interactive high-level object-o
-- no debconf information
Before filing a bug against the XFree86 X server, please note the
following:
1) The problem you are experiencing may be a known issue that is discussed
in the Debian X FAQ. If you are unfamiliar with this document, please
consult it before filing your report.
XHTML version: file:///usr/share/doc/xfree86-common/FAQ.xhtml
plain text version: file:///usr/share/doc/xfree86-common/FAQ.gz
2) Please be cautious with your bug severities. Most bugs in the XFree86 X
server are specific to particular drivers, and often manifest only on
particular models of display adapter. This means that while the X server
may be unusable for you, it typically is not for the majority of users.
Therefore, bug severities of "critical" or "grave" are seldom appropriate.
In general, if the X server crashes, hangs, or locks up your system, the
bug should be assigned a severity of "important". If you are in doubt
about what severity to use, choose "normal". The Debian package
maintainers will upgrade reports if they have severities that are too low
-- you need not fear that your report will be ignored because it was filed
with a lower severity than was appropriate.
3) Problems with the keyboard are almost always due to bugs in the XKB (X
Keyboard Extension) data files. Reports about such issues should be filed
against the "xlibs" package, not "xserver-xfree86".
4) Problems with 3D acceleration or DRI (Direct Rendering Infrastructure)
are usually problems with the Mesa GL library, the Mesa DRI modules, or
with the Linux kernel's direct rendering manager (DRM). Bugs in these
systems can even lock up the computer. Here's a table to help you choose
which package is the most appropriate for your report:
Situation Package
--------- -------
problem has nothing to do with GL/DRI xserver-xfree86
disabling Mesa DRI modules fixes problem xlibmesa-dri
GL-related problem not affected by DRI xlibmesa-gl
changing kernel version fixes problem kernel
Note that some hardware vendors provide their own GL library
implementations, which are not always compatible with XFree86. If you
think the problem lies in xlibmesa-gl but that package is not installed,
you may have just such a compatibility problem; try the command:
reportbug --file /usr/lib/libGL.so.1
5) If you are submitting a patch -- thank you! Please make sure, however,
that the code you are contributing is not under the XFree86 1.1 License.
Most of XFree86 4.4 and later, and most commits to XFree86 CVS after
2004-02-12, are under the XFree86 1.1 license. Debian unfortunately cannot
accept such patches. The reasons for this are discussed at length in the
Debian X FAQ, in the entry "What is the story with XFree86's license?"
We appreciate your patience with this message. By following the above
guidelines, you can help Debian help our users more effectively.
