Craig White wrote:
The address used for bugzilla could be different than the address used
for this list. I use another address for bug reports.
Anyway, I really responded to ask a question regarding finding
previously filed and resolved reports.
How would one find a bug report filed for an xorg-x11 problem relating
to an 865G video? I wanted to extract the xorg.conf file from the
previous report. I neglected to grab the xorg.conf file earlier, which
would be simpler than querying bugzilla.
I changed the query setup for jdow to my bug reporting address and it
only revealed 12 bugs that I commented on or submitted. For comparison,
the my bugs link on the bottom of the bugzilla report shows that I have
7 bugs active.
I anticipated that the xorg-x11 bug that was never consciously resolved
but accidentally resolved when the driver was revised to accommodate
i830 dual head and broke the i810 video cards would show up in that query.
----
are you talking about this one ?
http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=161242
That is not the bug that I was searching for. The bug above was pretty
bad but was caused by the compiler. The other one fixed by accident was
related to X crashing unpredictably. (The whole X server crashed but the
screen still showed information which was present at the crash)
The error stopped when the driver was changed to accommodate dual head
operation for the intel i830 which broke support for the intel 810/815
video cards.
I'll just grab the xorg.conf tomorrow for the Intel 865G system that I
have away from home.
Thanks!
Jim
you did use a different email address on that (netscape.com)
I'll try the advanced search feature to see if I can locate the bug for
the netscape mail addy. I was using the default search which showed
zarro bugs.
Craig
--
Art is either plagiarism or revolution.
-- Paul Gauguin
