unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: emacs-devel@gnu.org
Subject: Re: Possible new display bug
Date: Tue, 20 Sep 2011 14:10:59 +0200	[thread overview]
Message-ID: <m3vcsn9zxo.fsf@chopper.vpn.verona.se> (raw)
In-Reply-To: <m339fs4bxi.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 19 Sep 2011 20:36:09 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I'm not filing a bug report, because I don't have a test case.
>
> But recently -- the last day or so -- I'm sometimes seeing windows not
> being updated, especially if they have images in them.  The symptoms are
> that if you have a buffer that is a window-and-a-half long, and you're
> looking at the first window-full, and then `down' to scroll down, the
> portion of the window that's after the end of the buffer doesn't get
> updated at all.  The pixels just remain the same.
>
> I'm not able to reproduce it reliably, but it's happened like ten
> times. 

I had some very similar issues. I had juggled some settings on the Intel
DRI graphics driver and later forgot about it. Emacs showed the symptoms
you describe but oddly enough no other application. Have you recently
begun using GNOME3 or something?

-- 
Joakim Verona



  parent reply	other threads:[~2011-09-20 12:10 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-19 18:36 Possible new display bug Lars Magne Ingebrigtsen
2011-09-19 19:56 ` Eli Zaretskii
2011-09-20 12:10   ` Lars Magne Ingebrigtsen
2011-10-01 16:36     ` Lars Magne Ingebrigtsen
2011-10-01 17:53       ` Eli Zaretskii
2011-10-06 19:23         ` Lars Magne Ingebrigtsen
2011-10-06 19:54           ` Eli Zaretskii
2011-10-06 20:06             ` Lars Magne Ingebrigtsen
2011-09-20 12:10 ` joakim [this message]
2011-09-20 12:10   ` Lars Magne Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=m3vcsn9zxo.fsf@chopper.vpn.verona.se \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).