Package: reportbug
Version: 3.10
Severity: important

This looks like it might be related to:

  #306343: reportbug: "--no-config-files" doesn't work for some packages.

At any rate happens with the same task I was trying with #306343.  
Here's the output of a run that goes wrong:

<output start>
% reportbug  --no-config-files --no-check-available --paranoid --severity=minor 
--tag=patch  --no-query-bts  xserver-xfree86
*** Welcome to reportbug.  Use ? for help at prompts. ***
Using 'A Costa <[EMAIL PROTECTED]>' as your from address.
Detected character set: us-ascii
Please change your locale if this is incorrect.

Getting status for xserver-xfree86...
Verifying package integrity...
Looking up dependencies of xserver-xfree86...
Maintainer for xserver-xfree86 is 'Debian X Strike Force 
<debian-x@lists.debian.org>'.
*** The following debconf settings were detected:
* xserver-xfree86/config/monitor/screen-size: 17 inches (430 mm)
  xserver-xfree86/config/device/use_fbdev:
* xserver-xfree86/config/monitor/selection-method: Simple
  xserver-xfree86/config/doublequote_in_string_error:
* xserver-xfree86/config/device/bus_id:
* xserver-xfree86/config/device/video_ram:
* xserver-xfree86/config/monitor/lcd: false
  xserver-xfree86/config/inputdevice/keyboard/internal:
* xserver-xfree86/config/device/driver: ati
* xserver-xfree86/config/monitor/vert-refresh: 50-160
* xserver-xfree86/config/display/default_depth: 24
* xserver-xfree86/config/display/modes: 1152x864, 1024x768, 800x600, 640x480
* xserver-xfree86/config/modules: GLcore, bitmap, dbe, ddc, dri, extmod, 
freetype, glx, int10, record, speedo, type1, vbe
* xserver-xfree86/config/monitor/range_input_error:
  xserver-xfree86/autodetect_video_card: true
* xserver-xfree86/config/inputdevice/keyboard/variant:
* xserver-xfree86/config/inputdevice/mouse/port: /dev/gpmdata
* xserver-xfree86/config/write_files_section: true
  xserver-xfree86/autodetect_monitor: true
* xserver-xfree86/config/device/identifier: ATI Technologies Inc 3D Rage Pro 
AGP 1X/2X
* shared/default-x-server: xserver-xfree86
* xserver-xfree86/config/inputdevice/mouse/emulate3buttons: false
* xserver-xfree86/config/inputdevice/keyboard/layout: us
* xserver-xfree86/config/monitor/horiz-sync: 30-70
* xserver-xfree86/config/monitor/identifier: RIC 770
  shared/no_known_x-server:
  xserver-xfree86/autodetect_mouse: true
  xserver-xfree86/config/monitor/mode-list: 1280x960 @ 60Hz
* xserver-xfree86/config/inputdevice/keyboard/rules: xfree86
  xserver-xfree86/multiple_possible_x-drivers:
* xserver-xfree86/config/inputdevice/keyboard/model: pc101
* xserver-xfree86/config/write_dri_section: true
* xserver-xfree86/config/inputdevice/mouse/zaxismapping: true
  xserver-xfree86/config/device/bus_id_error:
* xserver-xfree86/config/inputdevice/keyboard/options:
* xserver-xfree86/config6/config/inputdevice/keydel: pc104
  xserver-xfree86/config/nonnumeric_string_error:
* xserver-xfree86/config/inputdevice/mouse/protocol: IntelliMouse
  shared/multiple_possible_x-servers:
* xserver-xfree86/config/null_string_error:
Include these settings in your report [Y|n|q|?]? n

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.

Please briefly describe your problem (you can elaborate in a moment; an empty 
response will stop
reportbug). This should be a concise summary of what is wrong with the package, 
for example, "fails to
send email" or "does not start with -q option specified."
> whatever
Rewriting subject to 'xserver-xfree86: whatever'
Traceback (most recent call last):
  File "/usr/bin/reportbug", line 1668, in ?
    main()
  File "/usr/bin/reportbug", line 1549, in main
    if addinfo and incfiles:
UnboundLocalError: local variable 'addinfo' referenced before assignment
% echo $?    # error code was?
0                    # no help here...  
<output end>


Hope this helps...


-- Package-specific info:
** Environment settings:
EDITOR="mcedit"
EMAIL="[EMAIL PROTECTED]"

** /home/alfie/.reportbugrc:
reportbug_version "3.2"
mode standard
ui text
realname "A Costa"
email "[EMAIL PROTECTED]"

-- System Information:
Debian Release: 3.1
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.9-1-686
Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) (ignored: LC_ALL set to C)

Versions of packages reportbug depends on:
ii  python2.3                     2.3.5-2    An interactive high-level object-o

-- no debconf information


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to