Just to follow up, it appears that I was indeed rather premature with
this report (but you all knew that anyway). I acted too hastily. I had
just upgraded the xfree86 packages, and went to restart my x session and
X crashed. After a little bit of debugging, and seeing a similar report
on Alpha, I added another bug. I assumed that since the package simply
did not start, that it qualified as a serious bug (I believe that a
package that does not start in its default configuration is a serious
violation of policy, but I can't find the reference now).
In hindsight, I should have been more thoughtful. The package was,
first of all, not in its default configuration, obviously, since I have
spent time customizing my XF86Config-4 file. Secondly, I didn't check
to see how long the package had been out before filing the report.
Anyway, I downloaded xserver-xfree86-dbg in the hopes of finding out
more information, and it started just fine. I redownloaded the standard
4.3.0-7 package, and it too worked just fine. I'm not sure exactly what
the problem was on my system that day, but the very same package is
working fine now.
So, now that I'm sufficiently embarrassed, I'm going to recommend that
this bug be closed, and start a thorough reading of the Debian Policy
Manual, as well as promise to behave more sensibly in the future.
Anthony W. Juckel
ps. Perhaps I should have just sat back and got a nice warm cup of shut
the f**k up :-) At least until I had verified it with a couple other
users...
Branden Robinson wrote:
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.
