retitle 257302 xfree86: general complaint about XFree86 on Dell Latitude D400 tag 257302 + moreinfo thanks
On Fri, Jul 02, 2004 at 10:18:05AM -0700, Debian Bug Tracking System wrote: > Processing commands for [EMAIL PROTECTED]: > > > # Automatically generated email from bts, devscripts version 2.7.95.1 > > reassign 257302 xserver-xfree86 > Bug#257302: Install on DELL Latitude D400 - some X problems > Bug reassigned from package `installation-reports' to `xserver-xfree86'. Doesn't d-i install mdetect to autodetect the mouse? If it failed, that's a bug in mdetect. Doesn't d-i install discover to autodetect the video hardware and recommend an appropriate X server and driver? If it failed, that's a bug in discover (probably in discover-data, technically). Finally, even if there is a bug in XFree86 there's nothing I can do about it until I have a *lot* more information. See below. That "third OS" on your hard drive probably has a QA staff that provides meaningful information to the engineering staff. I wonder what heights Debian could reach if *we* had that... (And by the way, "no flames here" doesn't magically make a flame message not one; if you don't want to flame, then don't say fiery things.) [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more information is required of you before this bug can be handled. Please run the following commands from a shell prompt to gather and deliver this information to us: $ /usr/share/bug/xserver-xfree86 > /tmp/output 3>&1 $ mailx -s "Re: Bug#257302" [EMAIL PROTECTED] < /tmp/output If you do not have a "mailx" command on your system, you can get by installing the "mailx" Debian package; for example, with the "aptitude install mailx" or "apt-get install mailx" commands as root. Alternatively, you can also use a mail command that is compatible with mailx's command-line syntax, such as "mutt". One very good way to file bugs with the Debian Bug Tracking System is to use the "reportbug" package and command of the same name. The reportbug program does a lot of automatic information-gathering that helps package maintainers to understand your system configuration, and also ensures that your message to the Debian Bug Tracking System is well-formed so that it is processed correctly by the automated tools that manage the reports. (If you've ever gotten a "bounce" message from the Debian Bug Tracking System that tells you your message couldn't be processed, you might appreciate this latter feature.) Therefore, I strongly urge you to give "reportbug" a try as your primary bug reporting tool for the Debian System in the future. If you *did* use reportbug to file your report, then you're receiving this message because the information we expected to see was not present. If you deliberately deleted this information from the report, please don't do that in the future, even if it seems like it makes the mail too large. 50 kB (kilobytes) of configuration and log data is typical. Only if the included information greatly exceeds this amount (more than 100 kB) should you consider omitting it; instead, put it up on the World Wide Web somewhere and provide URLs to it in your report, or in subsequent followup by mailing <[EMAIL PROTECTED]>. Thank you! -- G. Branden Robinson | When we call others dogmatic, what Debian GNU/Linux | we really object to is their [EMAIL PROTECTED] | holding dogmas that are different http://people.debian.org/~branden/ | from our own. -- Charles Issawi
signature.asc
Description: Digital signature
