severity 261522 important retitle 261522 xserver-xfree86: [sis] SEGV on 86C326 5598/6326 rev 11 tag 261522 + upstream moreinfo thanks
On Mon, Jul 26, 2004 at 04:47:11PM +0200, Thibault TAILLANDIER wrote: > Package: xserver-xfree86 > Version: 4.3.0.dfsg.1-4 > Severity: grave Why did you set this bug's severity to "grave"? Is it your contention that Debian should not ship the XFree86 X server for any of our users unless we can get it working on your hardware? > Hi, > > Here is some other informations you can use : > $ uname -a > Linux thib 2.4.26 #1 Fri Apr 16 10:48:55 CEST 2004 i686 GNU/Linux > $ dpkg -s libc6 | grep ^Version > Version: 2.3.2.ds1-13 > > I'm using testing/sarge distribution. > > My x-server crashed due to a Fatal server error, it drove me back to > console. > I got a message that told me how to report the bug, so here is the > backtrace of the crash. > (See the attached file) > > I cant really explain more about the crash, and i dont really know what > would help you more on this ... but i'm available to give more > informations i have ... > > Thx for your work. Using reportbug would be a big help in the future. Please see 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 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#261522" [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 | The software said it required Debian GNU/Linux | Windows 3.1 or better, so I [EMAIL PROTECTED] | installed Linux. http://people.debian.org/~branden/ |
signature.asc
Description: Digital signature
