All of lore.kernel.org
 help / color / mirror / Atom feed
From: Didier Spaier <didier.spaier-GqzDj6/B2j8@public.gmane.org>
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: Re: [Bug 33977] X core font rendering is "laggy"
Date: Mon, 07 Feb 2011 10:31:58 +0100	[thread overview]
Message-ID: <4D4FBC0E.2090504@epsm.fr> (raw)
In-Reply-To: <20110207091543.AA74D13004F-4GnqB8vgsbnwRzGw0Gvu8Q/tdpCO6/zZ@public.gmane.org>

Le 07/02/2011 10:15, bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org a écrit :
> https://bugs.freedesktop.org/show_bug.cgi?id=33977
>
> --- Comment #3 from Maarten Maathuis<madman2003-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>  2011-02-07 01:15:43 PST ---
> This is an xserver issue which i recently fixed.
>
> http://cgit.freedesktop.org/xorg/xserver/commit/?id=541b25038a5de74411a094570b407c5ae018c2ba
>
> I have asked for it to be also put in the next 1.9 release, will have to wait
> how this goes.
>

The bug is tagged as x86-64 (AMD64) Linux (All) but it occurs here as well (i686).

And during a few seconds sometimes I see only half of the last row of text displayed (vertically cut).

  parent reply	other threads:[~2011-02-07  9:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-07  3:31 [Bug 33977] New: X core font rendering is "laggy" bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-33977-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2011-02-07  3:31   ` [Bug 33977] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  3:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  4:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07  9:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found]     ` <20110207091543.AA74D13004F-4GnqB8vgsbnwRzGw0Gvu8Q/tdpCO6/zZ@public.gmane.org>
2011-02-07  9:31       ` Didier Spaier [this message]
2011-02-07 16:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 17:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-07 18:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09  9:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 11:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 20:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 20:28   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-09 20:29   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2011-02-10  6:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 16:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 17:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-19 17:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4D4FBC0E.2090504@epsm.fr \
    --to=didier.spaier-gqzdj6/b2j8@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.