Bug 702500

Summary: [abrt] desktop-effects-0.8.7-2.fc14: handle_error: Process /usr/bin/desktop-effects was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: pscottdv <scott>
Component: mesaAssignee: Adam Jackson <ajax>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: adel.gadllah, ajax, otaylor, sharon
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:2d55a42a4f0e27df5754c122aff94359635e812e
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-05-03 21:01:39 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description pscottdv 2011-05-05 21:05:00 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 19094 bytes
cmdline: desktop-effects
component: desktop-effects
Attached file: coredump, 2039808 bytes
crash_function: handle_error
executable: /usr/bin/desktop-effects
kernel: 2.6.35.10-74.fc14.x86_64
package: desktop-effects-0.8.7-2.fc14
rating: 4
reason: Process /usr/bin/desktop-effects was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1304629396
uid: 500

How to reproduce
-----
1. Using LTSP on Fedora 14
2. Start desktop-effects
3. desktop-effects crashes
Comment 1 pscottdv 2011-05-05 21:05:02 UTC 
Created attachment 497225 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:02:43 UTC 
Backtrace analysis of bugs across components suggests the actual bug is in component mesa instead of component desktop-effects, reassigning to mesa.

Bugs which were found to be similar to this bug: 
  celestia: bug #672864
  desktop-effects: bug #601773, bug #602036, bug #668232

This comment is automatically generated.
Comment 3 abrt-bot 2012-03-21 17:02:52 UTC 
*** Bug 668232 has been marked as a duplicate of this bug. ***
Comment 4 Adam Jackson 2012-05-03 21:01:39 UTC 
F14 is no longer supported.

BadRequest from DRI2Connect is a normal condition when GLX can't create a direct context because the server thinks the client is non-local.  It should be suppressed and simply handled internally, which is done as of:

http://cgit.freedesktop.org/mesa/mesa/commit/src/glx/dri2.c?id=fbc2fcf685d22ec9bc9465e1f731529979497eaa