Red Hat Bugzilla – Bug 416361
Gnome session save regression for multiple xterm instances
Last modified: 2007-12-17 10:58:17 EST
Description of problem:
After saving a session with multiple xterms at different positions and sizes,
a new session momentarily shows the xterms at their correct places and then
rapidly smashes them into one position (on top of each other). It does this
identically for each virtual desktop, re-positioning the instances that were
initially correctly placed on that desktop, as if using relative coordinates
within the virtual desktop.
Version-Release number of selected component (if applicable):
Nearly always. I have seen some odd behaviors where a login does not do this
extra smashing of positions and xterms remain where they belong, but this has
only happened coincidentally with other strange behaviors such as a
System->Logout->Logout request failing to have any effect. I am left with the
impression that there are some race-conditions in the session handling.
I see this consistently on a single processor laptop install. I am not positive,
but I think it seems more "random" on a 4-core workstation. But, I have not
done enough logout/login cycles to really have statistically meaningful
Steps to Reproduce:
1. Login to a new session with no applications
2. Open several xterm processes and position them
3. Do a gnome-session-save
Xterm windows misplaced.
All xterm windows at same places where they were when session was saved.
This is a regression. There have been many problems in past Fedora releases but
this behavior was fixed in Fedora 7 and lulled me into using Gnome again instead
of XFCE (where xterms are handled correctly). It is unfortunate that there are
not regression tests to notice this recurring problem before changes are
released... I'm not enough of an X hacker to suggest how to write an automated
test to validate geometry of windows in saved sessions, but I think it would be
wise to try, given the recurring nature of this problem...
Since reporting this, I've seen sessions come back properly. I am not sure
whether an update was installed that fixed it, or whether perhaps the original
problem had to do with home directory settings saved from F7 and then loaded
under F8... I cannot seem to reproduce the failure now.
excellent. Since you've been the only reporter, I'm going to close this out,
but please reopen if it happens again.