GNOME Bugzilla – Bug 343701
gnome-session doesn't allow for multiply starting up a program of the same name (even with different parameters)
Last modified: 2006-07-13 02:31:49 UTC
Distribution: Gentoo Base System version 1.12.0 Package: gnome-session Severity: Normal Version: GNOME2.14.1 2.14.x Gnome-Distributor: Gentoo Synopsis: gnome-session doesn't allow for multiply starting up a program of the same name (even with different parameters) Bugzilla-Product: gnome-session Bugzilla-Component: gnome-session Bugzilla-Version: 2.14.x Description: Description of Problem: gnome-session fails to start multiple instances of the same program from the "Startup Programs" list, even if I give different parameters. I'd like to do that to start two digital xclocks at login, one showing the time, another showing the date. Steps to reproduce the problem: 1. Run the sessions capplet. 2. Add two entries to "Startup Programs", say "xclock" and "xclock -digital" 3. Close the sessions capplet. 4. Log out and back in. Actual Results: Only one of the xclocks appears. Expected Results: I'd expect to see both xclocks. How often does this happen? always :-) Additional Information: I think the problem is caused by the compare_restart_command implementation in save.c which is called by remove_duplicated_clients. I don't know what's the point of trying to remove duplicate startup commands, so I don't know what would be the correct fix. Perhaps the compare_restart_command function should do more thorough comparing, i.e. also look at the program arguments. ------- Bug created by bug-buddy at 2006-06-02 18:17 -------
The problem you are seeing may have the same cause as bug 341286. The thread at http://www.redhat.com/archives/rhl-devel-list/2006-February/msg01194.html also talks about GNOME sessions not being restored properly. Whatever happened to the "Save changes" checkbox in the logout dialog? That was useful to have. Have you tried calling "gnome-session-save" from the command line after modifying your "Startup Programs" list, but before logging out? It didn't help me, but let's confirm that it doesn't help in your case either.
Actually, I checked whether the .desktop files that the capplet generates in ~/.config/autostart are correct. And they are. Furthermore, if I invoke one of the xclocks as 'xclock' and the other one as '/usr/bin/xclock', both get started just as they should. So I think this problem is not a matter of saving but of starting the session properly. Btw: You can still have the 'save session' checkbox by selecting the 'ask on logout' checkbox in the 'session options' pane of the sessions capplet. At least this is the case with my gnome-session installation as of version 2.14.1.
(In reply to comment #2) > So I think this problem is not a matter of saving but of starting the session > properly. I agree. My session files look fine, too, they just aren't processed correctly. > Btw: You can still have the 'save session' checkbox by selecting the 'ask on > logout' checkbox in the 'session options' pane of the sessions capplet. At > least this is the case with my gnome-session installation as of version 2.14.1. I have the "Ask on logout" checkbox on, but I don't get the "Save current setup" checkbox on logout anymore (FC4 had it, now I'm running FC5; I tried both gnome-session 2.14.1 and 2.15.1). I think "Ask on logout" refers to whether to display a logout confirmation dialog at all. I'm running FC5, you are running Gentoo - maybe there are differences between the distros.
*** This bug has been marked as a duplicate of 341286 ***