[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#285943: Font antialiasing looks bad (looks like an mga driver related problem)



retitle 285943 xserver-xfree86: [mga] antialiased fonts get colored outlines (problem goes away when fbdev driver used) on MGA G550 AGP rev 1
tag 285943 + upstream moreinfo
thanks

On Thu, Dec 16, 2004 at 04:31:00PM +0100, Hársfalvi Levente wrote:
> When I configure X to use the mga driver, X font aliasing looks ugly 
> (see attached screenshot). The fonts get a colored outline in result of 
> the antialiasing filter. Looks like there's some problem in the 2d 
> filtering routine. If I make a switch to the fbdev driver (reconfigure X 
> to use fbdev), everything goes well (see second screenshot).
> 
> I downloaded the latest mga driver from Matrox and gave it a try, with 
> the same results.
> 
> My videocard is a G550 ( Matrox Graphics, Inc. MGA G550 AGP rev 1 ). The 
> Display is a Sony SDMX-82 18" TFT, DVI cable, I'm using it in 1280x1024 
> 24bit.
> 
> I'm using Debian GNU/Linux Sid with a self-compiled 2.6.8 kernel and 
> libc6 2.3.2.ds1-19.
> 
> (Attached: config files and screenshots for both mga and fbdev 
> configuration.)

Thanks for your report.  We need a little more information, which is
described below.

[The following is a form letter.]

Dear bug submitter,

Since the XFree86 X server is a large and complex piece of software, 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/xserver-xfree86 >/tmp/output 3>&1

[ If you're using xserver-xfree86 4.3.0.dfsg.1-11 or later, the above
  command should be:

  $ /usr/share/bug/xserver-xfree86/presubj >/tmp/output 3>&1

  instead. ]

$ mailx -s "Re: Bug#285943 followup" 285943@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 <285943@bugs.debian.org>.

Thank you!

-- 
G. Branden Robinson                |     The last time the Republican Party
Debian GNU/Linux                   |     was on the right side of a social
branden@debian.org                 |     issue, Abe Lincoln was president.
http://people.debian.org/~branden/ |     -- Kirk Tofte

Attachment: signature.asc
Description: Digital signature


Reply to: