Multi-head session management



Title: Message
Hi,
 
The behavior of save session in a multi-head setup is illustrated in this mail.
 
The following 2 changes are made to Client and Manager respectively
 
1. Change to Libgnomeui client :
 
In libgnomeui/libgnomeui/gnome-client.c (client_save_yourself_callback) added the line
gnome_client_set_environment (client, "DISPLAY", DisplayString (GDK_DISPLAY ( )));
 
2. Change to gnome-session :
 
In gnome-session/gnome-session/manager.c
added a function that will find whether the screen is available at the time of next login
and if not, open the application on the default screen
 
Case 1:
* Machine with 2 screens, each screen having four workspaces and one application is started in
each  of the workspaces on both the screens. (Total 8 Applications)
* Log out after saving session and log back in.
* All applications get restored properly on both the screens in the proper Workspace
 
Case 2:
* Remove one screen from the above setup (by changing /usr/dt/config/Xservers)
* Log out and log back in.
* All applications get restored on the first screen  (Total 8 Applications)
 
Case 3:
* Without saving the session last started in Case 2, log out and log in after restoring the
second screen.
* All applications get restored properly on both the screens in the proper Workspace.
 
Case 4:
* Remove the second screen and log out and log in without saving session.
* All applications get restored properly on the first screen.
* Log out and log in after saving the session and restoring the second screen.
* All applications get restored on the first screen.
 
Case 5: Check the behavior if the application explicitly sets the DISPLAY variable.
* Modified gnome-calculator to set the DISPLAY explicitly.
* Log out, log in after saving the session.
* gnome-calculator gets restored properly on the correct screen.
 
Following case describes a case where gnome-session is started on
a remote host.
 
Case 6:
* From Machine A in failsafe mode start gnome-session on Machine B.
* Invoke some applications from the started session on Machine B .
* Log out after saving the session.
* From Machine A, restart gnome-session on Machine B.
* Session gets started on Machine B and applications get restored properly.
 
* Log out of the session on Machine B.
* Log out of the failsafe mode in Machine A.
* Log in the console of Machine A with GNOME Desktop Environment.
* All saved applications and panel get restored on Machine B .
 
What is the expected behavior in this scenario?
 
Another open issue in case 6 is :
Even after Changing the DISPLAY variable in the session file to that
of Machine A, sawfish frames windows on the Machine B.
 
Please add your comments and suggestions.
 
 


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]