On Sat, 27 Sep 2003, Branden Robinson wrote: > On Fri, May 09, 2003 at 04:24:04AM -0700, Black Raven wrote: > > First, it doesn't display an error message, per se. Well, example one, > > is: www.tentacle.net/~awk/snapshot1.jpg It's lost some quality do to how > > much I compressed it. www.tentacle.net/~awk/snapshot1.png is the original > > png. > > > > Using aptitude, I upgraded xserver-xfree86 from the version in stable > > (4.1.0-16) to the version in unstable (4.2.1-6), that's when the problem > > showed up. > > You did not provide sufficient information with your initial report for > me to handle this bug. > > The XF86Config(7) manual page says: > > When reporting bugs to the Debian Bug Tracking System in > xserver-xfree86, be sure to include a copy of your > /etc/X11/XF86Config-4 and /var/log/XFree86.0.log (or > whichever log file the X server used - see XFree86(1x)) files > in the bug report. Many problems with the X server are the > result of poor configuration. Furthermore, this information > aids the Debian Developers in determining your hardware sce??? > nario. > > If you use the "reportbug" package and command, the above files will be > included automatically if they exist. > > Also, are you still experiencing this problem with xserver-xfree86 > 4.2.1-11?
The bug vanished with the newer version of the xserver-xfree86. (The older version also worked.) (And, as far as I know, it doesn't exist with 4.2.1-11.) Sorry I couldn't have been more of a help, but I'm not exactly familiar with the bug reporting procedure. I'll try to remember to include the config files, in any future bug reports. -awk
