Bug 3513 - Xnest "unhandled event" warning spew with -parent
Summary: Xnest "unhandled event" warning spew with -parent
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xnest (show other bugs)
Version: git
Hardware: x86 (IA32) Linux (All)
: high minor
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-06-10 09:21 UTC by Mark McLoughlin
Modified: 2011-10-15 15:33 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Mark McLoughlin 2005-06-10 09:21:56 UTC 
When you run Xnest with -parent, Xnest selects StructureNotifyMask on the parent
window in order to get DestroyNotify so it knows when to exit.

However, that causes it to get a bunch of other event types which it doesn't
explicitly handle causing lots of warning spew:

xnest warning: unhandled event
xnest warning: unhandled event
xnest warning: unhandled event

Attaching trivial patch
Comment 1 Mark McLoughlin 2005-06-10 09:23:03 UTC 
Created attachment 2868 [details] [review]
Proposed patch for cairo-0.9.2 dealing with vendor string change
Comment 2 Adam Jackson 2005-06-12 17:09:35 UTC 
applied, thanks!
Comment 3 Adam Jackson 2005-06-14 12:32:48 UTC 
uh, and let's close it this time...
Comment 4 Mark McLoughlin 2005-07-11 22:22:47 UTC 
Nominating for the 6.8.x branch

Extremely trivial fix for a bug which causes lots of annoying debugging spew
with Sabayon (http://www.gnome.org/projects/sabayon)
Comment 5 Daniel Stone 2007-02-27 01:27:01 UTC 
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 6 Jesse Adkins 2010-11-28 22:38:24 UTC 
> Nominating for the 6.8.x branch
> 
> Extremely trivial fix for a bug which causes lots of annoying debugging spew
> with Sabayon (http://www.gnome.org/projects/sabayon)

6.8 is long past. Closing.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.