After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 96725 - [Solaris Xinerama] Ghex placed in a wrong position after changing from xinerama to single head
[Solaris Xinerama] Ghex placed in a wrong position after changing from xinera...
Status: RESOLVED NOTABUG
Product: metacity
Classification: Other
Component: general
unspecified
Other Solaris
: Normal normal
: ---
Assigned To: Metacity maintainers list
Metacity maintainers list
Depends on:
Blocks: 107063
 
 
Reported: 2002-10-24 17:20 UTC by Mamatha
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Mamatha 2002-10-24 17:20:11 UTC
I am running Sun's stable build 12 - (CVS snapshot date 'Tue Oct 15
15:00:00 BST 2002').

Not too sure if this bug belongs to here or not. Please move to the 
appropriate component, if this is not to be filed under this product.

Steps to reproduce:
1. Configure a Xinerama server with two screens on left (scr0) and 
right (scr1). 
2. Invoke both ghex and gnome-calculator in scr0, and drag 'ghex2' to src1.
3. Turn off xinerama mode, and configure as a single head system. As super 
user, edit /usr/dt/config/Xservers file replace the Xsun startup info 
with ":0 Local local_uid@console root /usr/openwin/bin/Xsun :0 -nobanner" 
4. Select Logout from the 'Actions' drop down menu and enable 'Save 
session' check box then click on OK and then login back.
5. The 'Calculator' comes up properly  on the screen (as expected), 
but 'ghex' comes at the edge of the screen.

I'll attach two screenshots to explain the bug scenario.
Comment 1 Glynn Foster 2002-11-28 14:24:32 UTC
you didn't attach the screenshots ;)
Comment 2 Rob Adams 2003-02-26 04:06:54 UTC
The session has ghex at a position outside the screen area when
reloading the session when logging back in.  Metacity's constraints
force it back into the now available area, but leave it as close as
possible to the old position.  Sounds to me like metacity is behaving
exactly as it should here, unless I'm misunderstanding somehow.