all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Darren Hoo <darren.hoo@gmail.com>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel <emacs-devel@gnu.org>
Subject: Re: Problems with compositing-enabled metacity in gnome enviroment
Date: Fri, 11 Feb 2011 22:53:19 +0800	[thread overview]
Message-ID: <AANLkTinkspSqZ65wfAW402ZJx=PH3j8x0Cd_pKroMmpi@mail.gmail.com> (raw)
In-Reply-To: <4D553F00.2070609@swipnet.se>

Hi Jan

On Fri, Feb 11, 2011 at 9:52 PM, Jan Djärv <jan.h.d@swipnet.se> wrote:
> Hello.
>
> I can easily reproduce this bug.  Emacs does get restored, but metacity is
> buggy, and doesn't draw the window correctly.  Other apps also don't redraw
> correctly with metacity and compositing_manager true.  For example, Chromium
> menus don't pop down and are left on the screen, the Gnome panel sometimes
> vanishes, and so on.  If you wan't compositing_manager use compiz, it is
> nowhere near as buggy as metacity.  Emacs (and other apps) works fine with
> it.

The version of  metacity I am using is 2.30.1-3 in Debian Unstable. Is
there any related
bug report of metacity that I can refer to?

I had experienced the varnishes of  Gnome panel a long time ago, But
since then I
never experience it for at least half a year, aslo with  Chromium I
never encounter
such  symptoms as you mentioned.

The only thing I want with compositing is the fancy tranparency of
Emacs, switching to
compiz seems not to be a choice for me, compiz is somewhat over-bloated to me.

>
> BTW, you probably meant (set-frame-parameter nil 'alpha 94).  Also, please
> use report-emacs-bug for bugs like these.
Got it

> I reverted to the version before this commit, but the bug in metacity remains.  It is
> probably a fluke that your meatcity works with > that version.

just FYI,  it is this specific hunk of the commit that triggers the
(possible) bug of metacity
Just revert this hunk of the commit Emacs works as expected at least for me.

src/xterm.c:

@@ -489,14 +489,14 @@ x_set_frame_alpha (struct frame *f)
 			     &data);

     if (rc == Success && actual != None)
-      if (*(unsigned long *)data == opac)
-	{
-	  XFree ((void *) data);
-	  x_uncatch_errors ();
-	  return;
-	}
-      else
+      {
 	XFree ((void *) data);
+	if (*(unsigned long *)data == opac)
+	  {
+	    x_uncatch_errors ();
+	    return;
+	  }
+      }
     x_uncatch_errors ();
   }



Thanks,

Darren.



  reply	other threads:[~2011-02-11 14:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-10 18:29 Problems with compositing-enabled metacity in gnome enviroment Darren Hoo
2011-02-11 13:52 ` Jan Djärv
2011-02-11 14:53   ` Darren Hoo [this message]
2011-02-11 16:02     ` Jan Djärv
2011-02-11 16:15       ` Darren Hoo

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='AANLkTinkspSqZ65wfAW402ZJx=PH3j8x0Cd_pKroMmpi@mail.gmail.com' \
    --to=darren.hoo@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.