dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 29393] R600: libGL crashes using Lwjgl
Date: Tue,  3 Aug 2010 19:26:51 -0700 (PDT)	[thread overview]
Message-ID: <20100804022651.BAC51130114@annarchy.freedesktop.org> (raw)
In-Reply-To: <bug-29393-502@http.bugs.freedesktop.org/>

https://bugs.freedesktop.org/show_bug.cgi?id=29393

--- Comment #3 from Casey Jones <jonescaseyb@gmail.com> 2010-08-03 19:26:51 PDT ---
This is what I got.

f8d81c31cee30821da3aab331a57f484f6a07a5d is the first bad commit
commit f8d81c31cee30821da3aab331a57f484f6a07a5d
Author: Nick Bowler <nbowler@draconx.ca>
Date:   Wed Jul 14 12:01:49 2010 -0400

    dri2: Track event mask in client code.

    When direct rendering is being used, DRI2 BufferSwapComplete events are
    sent unconditionally to clients, even if they haven't been requested.
    This causes error messages to be printed by every freeglut application
    of the form

      freeglut (./gears): Unknown X event type: 104

    and might confuse other clients.

    This is a fixed up version of the patch by Jesse Barnes, which drops
    BufferSwapComplete events if they are not requested by clients.

    Fixes fdo bug 27962.

    Signed-off-by: Nick Bowler <nbowler@draconx.ca>
    Signed-off-by: Jesse Barnes <jbarnes@virtuousgeek.org>

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2010-08-04  2:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-04  0:48 [Bug 29393] New: R600: libGL crashes using Lwjgl bugzilla-daemon
2010-08-04  1:07 ` [Bug 29393] " bugzilla-daemon
2010-08-04  1:17 ` bugzilla-daemon
2010-08-04  2:26 ` bugzilla-daemon [this message]
2010-08-04  4:21 ` bugzilla-daemon

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=20100804022651.BAC51130114@annarchy.freedesktop.org \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox