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 120921 - starting script from session-manual prevent splash to disappear quickly
starting script from session-manual prevent splash to disappear quickly
Status: RESOLVED DUPLICATE of bug 116814
Product: gnome-session
Classification: Core
Component: general
2.3.x
Other Linux
: Normal normal
: ---
Assigned To: Session Maintainers
Session Maintainers
: 120926 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2003-08-28 16:33 UTC by Frederic Crozat
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.3/2.4

Attachments
patch to revert the new splash screen for testing (18.03 KB, patch)
2003-09-22 09:58 UTC, Mark McLoughlin 		needs-work Details | Review

Description Frederic Crozat 2003-08-28 16:33:25 UTC 
Create a file called foobar :
cat << EOF > foobar
#!/bin/sh
EOF

chmod +x foobar

add foobar to your ~/.gnome2/session-manual using
gnome-session-properties/Startup programs

logout
login
splash will wait for foobar to issue some SM communication, which it won't
do and splash will only disappear after 1/2 minutes..
Comment 1 Robert Pollak 2003-09-02 11:31:11 UTC 
Related to http://qa.mandrakesoft.com/show_bug.cgi?id=4505 .

Is this a duplicate of bug 118063?
Comment 2 Malcolm Tredinnick 2003-09-06 01:15:29 UTC 
I just poked through the source code to confirm what I thought was
going on here: all the programs from the startup programs capplet are
currently expected to register themselves with the session manager
correctly (they are treated like all other programs in
save.c:read_session() ). Shell scripts (and numerous other programs)
obviously do not.

Mark: is the correct solution here to write a wrapper program which
does register itself with the session manager and is responsible for
starting these startup programs? After all, if the startup programs
could do session management, you could just save them as part of a
normal session and they would not need to go into this dialog box at all.

It kind of seems wrong to just have the session manager fork/exec
these programs (in fact, it may be just broken for remote sessions),
hence the idea of farming it out to a wrapper, so that we can keep the
code separate.
Comment 3 Malcolm Tredinnick 2003-09-22 01:05:58 UTC 
*** Bug 120926 has been marked as a duplicate of this bug. ***
Comment 4 Mark McLoughlin 2003-09-22 09:57:05 UTC 
It shouldn't be required for session-manual entries to connect to the
session manager.

So, I've found out what introduced these problems. It was the splash
screen re-write that Michael did over a year ago now. I'll attach a
patch on how to revert it to help anyone who wants to debug the
problem ....
Comment 5 Mark McLoughlin 2003-09-22 09:58:35 UTC 
Created attachment 20180 [details] [review]
patch to revert the new splash screen for testing
Comment 6 Vincent Noel 2004-08-06 15:50:27 UTC 

*** This bug has been marked as a duplicate of 116814 ***