retitle 280146 xlibmesa-dri: [radeon_dri] locks up when using scorched3d on ATI Radeon Mobility M6 LY tag 280146 + upstream moreinfo # Hardware-specific crashes/lockups are not release-critical. It is each X # client's responsibility to gracefully handle losing its connection to the # X server. If it does not, and loses data as a result, that is a bug in # the X client. severity 280146 important thanks [The following is a form letter.] Dear bug submitter, The DRI-enabled Mesa implementation of OpenGL is a complex piece of software, which often has bugs specific to particular hardware drivers, or even particular models of display adapter. Consequently, 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/xlibmesa-dri >/tmp/output 3>&1 $ mailx -s "Re: Bug#280146 followup" 280146@bugs.debian.org </tmp/output (Do not type the "$" at the beginning of the above lines; they are there simply to indicate the shell prompt.) If you do not have a "mailx" command on your system, you can get it 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 <280146@bugs.debian.org>. Thank you! -- G. Branden Robinson | What influenced me to atheism was Debian GNU/Linux | reading the Bible cover to cover. branden@debian.org | Twice. http://people.debian.org/~branden/ | -- J. Michael Straczynski
Attachment:
signature.asc
Description: Digital signature