tag 245249 + moreinfo upstream thanks On Wed, Apr 21, 2004 at 11:28:41PM -0700, CE wrote: > Subject: xserver-xfree86: [sis] screen "melt" with SiS 630ST and 4.3.0-7 > Package: xserver-xfree86 > Version: 4.3.0-7 > Severity: important > > The recently updated package renders X unusable with the SiS > 630ST. The screen will "melt" (going from black to white then > fading) upon starting X. The effect is rather pretty but > renders X unusable. X is able to be killed but no useful > entries are left in /var/log/XFree86.0.log. The problem started > with upgrading from 4.3.0-0ds4. X works fine with that release > but newer packages seem to reintroduce a variant of a problem > that Thomas Winischhofer > http://www.winischhofer.net/linuxsisvga.shtml had fixed in the > drivers. I can provide additional details if needed. Yes, please do, per the instructions below. [The following is a form letter.] Dear bug submitter, Since the XFree86 X server is a large and complex piece of software, some more informtion 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#245249" 245249@bugs.debian.org < /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'r 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 <245249@bugs.debian.org>. Thank you! -- G. Branden Robinson | Debian GNU/Linux | kernel panic -- causal failure branden@debian.org | universe will now reboot http://people.debian.org/~branden/ |
Attachment:
signature.asc
Description: Digital signature