> Package: xserver-xfree86
> Version: 4.3.0-7
> Severity: serious
>
> I've made the severity serious, since it appeared initially that X was
> completely unable to start. It turns out that the error is
> encountered upon loading /usr/X11R6/lib/modules/libxaa.a. After
> enabling NoAccel in my XF86Config-4, I got the server to start again.
>
> I would appreciate if someone (with similar hardware, if necessary)
> could attempt to reproduce this bug. There has been no change in my
> hardware or configuration (other than upgrading to the latest
> unstable) since X last functioned with hardware acceleration enabled.
Just FYI, you made a couple of poor decisions when filing this bug
report:
1) You set the severity to "serious". That's a decision for the package
maintainers to make.
As the bug tracking system documentation spells out:
serious
is a severe violation of Debian policy (that is, it violates a "must" or
"required" directive), or, in the package maintainer's opinion, makes the
package unsuitable for release.
You were not reporting a violation of Debian policy, nor are you one of
the package maintainers, so your usage of the "serious" severity was
inapposite.
This is not mere nitpicking, as xfree86 4.3.0-7 is scheduled to enter
"testing" today, and your report would have prevented that.
2) You included approximately 2 megabytes' worth of strace logs in your
bug report. Since the Debian packages of xfree86 are team-maintained,
a mailing list is used as the package maintainer address, and our
mailing list software rejected this ridiculously large message.
Consequently, few if any people saw your bug report as soon as it was
submitted.
Once your bug report begins to include large quantities (over 100kB or
so) of attachments, it's time to start thinking about putting the
information on a web page and simply providing URLs to it. Even a
gzipped attachment is preferable; this would have rendered your bug
report about 189kB in length, which is a big improvement on 2.2 MB.
Finally, it is worth noting that if this problem were widespread among
x86 users, it very likely would have been seen by many others long
before now (4.3.0-7 entered unstable for i386 about a week ago). I
suspect some subtle problem with your installation.
We'll be happy to work with you to resolve this problem, but if you have
expressed your frustration by filing an oversized bug report with an
inflated severity, I would suggest there are more productive ways to
request assistance.
Thanks for your report; we'll see what we can do. In the meantime, have
you tried using the debugging server instead?
# apt-get install xserver-xfree86-dbg
(You can use "aptitude" or your favorite package manager rather than
apt-get, if you like.)
[1] http://www.debian.org/Bugs/Developer#severities
--
G. Branden Robinson | The National Security Agency is
Debian GNU/Linux | working on the Fourth Amendment
branden@debian.org | thing.
http://people.debian.org/~branden/ | -- Phil Lago, Deputy XD, CIA
Attachment:
signature.asc
Description: Digital signature