Bug 8748 - Twinview/Xinerama doesn't work as before in metacity
: Twinview/Xinerama doesn't work as before in metacity
Status: VERIFIED FIXED
Product: gnome
window-manager
: dev_117
: ANY/Generic All
: P2 major
: dev_116
Assigned To: Erwann Chénedé
: QA alias for GNOME > Window Manager
:
:
:
:
:
  Show dependency treegraph
 
Reported: 2009-05-07 08:10 UTC by Erwann Chénedé
Modified: 2009-07-15 00:33 UTC (History)
9 users (show)

See Also:


Attachments
patch removing Xsun xinerama support (5.50 KB, patch)
2009-05-07 09:49 UTC, Erwann Chénedé
no flags Details | Diff


Note

You need to log in before you can comment on or make changes to this bug.


Description Erwann Chénedé 2009-05-07 08:10:00 UTC
Metacity is hitting the same problem as gtk see 7783
Comment 1 Erwann Chénedé 2009-05-07 09:49:08 UTC
Created an attachment (id=1892) [details]
patch removing Xsun xinerama support 

I've added the fix to spec-files trunk
Comment 2 Erwann Chénedé 2009-05-07 09:50:15 UTC
Fix for this issue will be available in build 116
Comment 3 Brian Cameron 2009-05-07 12:33:04 UTC
A patch that removes the Sun Xinerama support isn't really ideal since I'd
think we would want people to build the upstream source and have it work.  We
also want to continue supporting the Sun extensions if people build metacity on
older Sun platforms where only the Sun extensions are available.

For GDM and GTK+, I modified the configure script so that it first checks for
Xfree and uses that if found, and falls back to the Sun extensions otherwise.
I think this is a better approach than just removing the Sun extensions code,
and could get accepted upstream.

Looking at the new mutter code, it has the same issue.  So we'd probably want
to get a fix like this into both metacity and mutter.  Otherwise we'll need to
make the same change again into mutter when we start using it.
Comment 4 Praveen Kumar 2009-05-14 10:50:21 UTC
Is it possible to workaround this issue in older builds (111 to 115)? I have a
dual screen setup and I had to rollback to build 110 because of this issue. Is
there a plan to rebuild any of older builds? It is unfortunate that I won't be
able to run any builds between 110 to 116 because of this issue.
Comment 5 Brian Cameron 2009-05-14 13:32:23 UTC
Unfortunately I believe the only "workaround" is to rebuild metacity and ensure
that configure picks up the Xorg Xinerama interfaces.
Comment 6 Erwann Chénedé 2009-05-15 01:49:53 UTC
For convenience, I've build a gnome 2.24 version of metacity with the fix
included
both the metacity binary and the full set of package can be found here :
http://www.gnome.org/~erwannc/bugs/8748/
Comment 7 Erwann Chénedé 2009-05-15 02:56:27 UTC
Brian, I've modified the patch metacity-07-xfree-xinerama.diff so that it now 
check XFree implementation first if it's not available it will default to 
XSun's on Solaris system if it's present.
Comment 8 Erwann Chénedé 2009-05-20 07:08:27 UTC
*WORKAROUND*  (See comment #6 for details)

1) download : http://www.gnome.org/~erwannc/bugs/8748/metacity
2) replace /usr/bin/metacity by the downloaded binary
3) In a terminal run : metacity --replace
Comment 9 David 2009-06-01 08:52:07 UTC
The updated binary fixes my workstation.  Is there anyway for fixes like this
to show up as an update in the release repository?

I think this could put a lot of potential users off of 2009.06.  A
malfunctioning windowing system is serious deal-breaker for most.
Comment 10 Justin Ellison 2009-06-16 11:23:50 UTC
Just to back up what Dave said, I was about 10 minutes of head-banging away
from waiting for 2009.12 and switching back to Linux on my main workstation. 
The binary referenced above worked great for me as well. New windows launch in
the proper screen, and maximizing windows fills only the screen they are in.
Comment 11 Pablo Méndez Hernández 2009-06-25 09:33:40 UTC
I'm seeing again the same problem in snv_117. It also happened in snv_116, but
at least there the patched binary worked, which is not the case anymore.
Comment 12 Oscar del Rio 2009-06-26 11:16:03 UTC
(In reply to comment #11)
> I'm seeing again the same problem in snv_117. It also happened in snv_116, but
> at least there the patched binary worked, which is not the case anymore.

Confirming the problem in snv_117.  This time, replacing the metacity binary
does not seem to fix the problem (it worked on snv_111b).
Comment 13 Oscar del Rio 2009-06-27 09:18:47 UTC
(In reply to comment #12)
> (In reply to comment #11)
> > I'm seeing again the same problem in snv_117. It also happened in snv_116, but
> > at least there the patched binary worked, which is not the case anymore.
> 
> Confirming the problem in snv_117.  This time, replacing the metacity binary
> does not seem to fix the problem (it worked on snv_111b).

New bug 9719 opened for this issue since it is a reoccurrance of a previoulsy
fixed problem.
Comment 14 XuJin 2009-07-15 00:33:42 UTC
This bug is verified in snv_118+nevada_119.