Bug 63586 - gnome-terminal placements improperly restored at next login
Summary: gnome-terminal placements improperly restored at next login
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Public Beta
Classification: Retired
Component: gnome-core
Version: skipjack-beta2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Havoc Pennington
QA Contact: Aaron Brown
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-04-15 23:53 UTC by David Paschal
Modified: 2007-04-18 16:42 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2002-04-15 23:54:11 UTC
Embargoed:


Attachments (Terms of Use)

Description David Paschal 2002-04-15 23:53:45 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.2.18-dsp1 i686)

Description of problem:
When I log out of Gnome and choose "Save current setup", the gnome-terminal
windows arrangements I had before aren't properly restored on the next login. 
For example, if I previously had some windows placed on several of the desktops,
they all get restored on desktop 1 with the correct sizes but incorrect
positions.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Log into Gnome.
2. Open several gnome-terminal windows on several desktops, and drag them to the
desired positions and sizes.
3. Log out of Gnome, and check the "Save current setup" option.
4. Log back into Gnome.

Actual Results:  All gnome-terminal windows come back up with the correct sizes,
but they are strewn all over desktop 1, regardless of which desktop they
previously were on and what position they had on their original desktop.

Expected Results:  The gnome-terminal windows should have been restored to
exactly the same desktop and position they originally were in.

Additional info:

Comment 1 Havoc Pennington 2002-04-16 00:50:51 UTC
This is partly gnome-terminal's fault and partly Sawfish's fault. It's a lot of
engineering to fix; I've done most of the work already, but only 
for GNOME 2. It should be fixed when we move to GNOME 2. The last 
GNOME 1.x drop date is already passed, so closing the bug; it's too late to 
fix for 1.x.



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