bug#4134: [Fwd: [Bug 593249] emacs and acroread don't work properly after upgrading to 2.17.9]

[David Ronis <ronis@ronispc.chem.mcgill.ca>]

[-- Attachment #1: Type: text/plain, Size: 119 bytes --]

Turns out the problem is in gtk+.  I've filed a bug report and this is
the last (relevant) comment on the bug.

David


[-- Attachment #2: Forwarded message - [Bug 593249] emacs and acroread don't work properly after upgrading to 2.17.9 --]
[-- Type: message/rfc822, Size: 4271 bytes --]

From: gtk+ (bugzilla.gnome.org) <bugzilla@gnome.org>
To: david.ronis@mcgill.ca
Subject: [Bug 593249] emacs and acroread don't work properly after upgrading to 2.17.9
Date: Thu, 27 Aug 2009 11:34:17 +0000 (UTC)
Message-ID: <20090827113417.E4CB46F3C2@bugzilla-web.gnome.org>

http://bugzilla.gnome.org/show_bug.cgi?id=593249



--- Comment #3 from Alexander Larsson <alexl@redhat.com> 2009-08-27 11:34:14 UTC ---
For the emacs thing, I can reproduce this here, but emacs does some pretty
weird things in its Gtk+ integration that can conflict quite a lot with the new
client-side window stuff in the later Gtk+.

Running with GDK_NATIVE_WINDOWS=1 in gtk+ >= 2.17.9 fixes this issue, although
setting that in emacs may not be a good idea as it will propagate to apps
launched by emacs. Instead I would recommend adding some code to emacs that
calls gdk_x11_drawable_get_xid() on all "toplevel" Gtk+ widgets they put in the
buffer window. This will ensure these windows get their own X window and should
be totally backwards compat and safe on older versions of Gtk+.

-- 
Configure bugmail: http://bugzilla.gnome.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You reported the bug.