DRI2 will throw BadRequest for this when the client is not local, but
DRI2 is an implementation detail and not something callers should have
to know about. Silently swallow errors in this case, and just propagate
the failure through DRI2Connect's return code.
Bugzilla:
On Thu, Jun 9, 2011 at 18:57:54 +1000, Christopher James Halse Rogers wrote:
DRI2 will throw BadRequest for this when the client is not local, but
DRI2 is an implementation detail and not something callers should have
to know about. Silently swallow errors in this case, and just propagate
On Tue, May 24, 2011 at 6:10 PM, Adam Jackson a...@redhat.com wrote:
DRI2 will throw BadRequest for this when the client is not local, but
DRI2 is an implementation detail and not something callers should have
to know about. Silently swallow errors in this case, and just propagate
the failure
On Thu, 2011-05-26 at 17:39 -0400, Kristian Høgsberg wrote:
On Tue, May 24, 2011 at 6:10 PM, Adam Jackson a...@redhat.com wrote:
DRI2 will throw BadRequest for this when the client is not local, but
DRI2 is an implementation detail and not something callers should have
to know about.
DRI2 will throw BadRequest for this when the client is not local, but
DRI2 is an implementation detail and not something callers should have
to know about. Silently swallow errors in this case, and just propagate
the failure through DRI2Connect's return code.
Signed-off-by: Adam Jackson
