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 116814 - Splash screen doesn't disappear
Splash screen doesn't disappear
Product: gnome-session
Classification: Core
Component: general
Other All
: Urgent major
: ---
Assigned To: Session Maintainers
Session Maintainers
: 91273 120921 147686 148662 169379 303423 (view as bug list)
Depends on:
Reported: 2003-07-06 11:26 UTC by Jan.Stocker
Modified: 2005-09-06 12:40 UTC
See Also:
GNOME target: 2.12.x
GNOME version: 2.7/2.8

Patch to make splash screen disappear after all client started (529 bytes, patch)
2004-02-25 02:28 UTC, Sirajuddin Maizir
needs-work Details | Review

Description Jan.Stocker 2003-07-06 11:26:08 UTC

If i've something other than the standard session , p.e. starting gaim and/
or evolution then the gnome session slash screen disappears only after
some minutes. In this time you cant logout. The splash screen is on top. If
you turn off splash screen the bahavior is the same. My last running
version was 2.3.3 (i think).
Comment 1 Joe Marcus Clarke 2003-08-07 19:38:36 UTC
If you edit ~/.gnome2/session, and remove the entry for gnome-session,
this problem goes away.  It looks like gnome-session may be trying to
spwan itself.
Comment 2 Jan.Stocker 2003-08-08 16:14:38 UTC
Removing entry doesn't help here
Comment 3 Mark McLoughlin 2003-08-08 17:56:05 UTC
I think this commit should fix it:

2003-08-08  Mark McLoughlin  <>
        * main.c: (main): make sure SM_CLIENT_ID gets set
        to a dummy id so that smproxy doesn't think we
        need to be session managed. Should fix bug 118063.
Comment 4 Jan.Stocker 2003-10-28 20:48:18 UTC
Problem still exists under a fresh installed system with
gnomesession-2.4.1 !  I'ven't a running version until today.
Comment 5 Uri David Akavia 2003-11-06 20:38:02 UTC
It happens in my GNOME 2.4 (gnome-session 2.4.1-2) also. Looking at my
gnome2/session file I do not see gnome-session at all. I tried
removing the entry for gnome-smproxy, but no luck.
Comment 6 Sirajuddin Maizir 2004-02-25 02:28:08 UTC
Created attachment 24744 [details] [review]
Patch to make splash screen disappear after all client started
Comment 7 Sirajuddin Maizir 2004-02-25 02:34:44 UTC
The attachment actually just a dirty hack. I just disable the code 
that I think prevent splash_stop() from being called. Because I find 
out that gnome-session enter the code section only when all client has 
been started. Actually I don't really understand the code, I just try 
to fix it, and it work, that's all.
Comment 8 Uri David Akavia 2004-03-07 21:45:37 UTC
More details - I'm running gnome-session 2.4.2. The problem only
appears when I add gkrellm as an application that runs as an
additional one (Startup Programs tab).
When I remove gkrellm, the splash screen disappears almost instantly.
(this is after erasing every file/directory that starts with . in my
home directory).
Comment 9 Kjartan Maraas 2004-04-28 23:40:46 UTC
Is this possibly a bug in gkrellm then? Is it the same with later gnome-session
and gkrellm releases?
Comment 10 Mark McLoughlin 2004-05-13 09:29:54 UTC
Well, yeah, gkrellm probably isn't implementing session management support
correctly and that causes the problem. We should still be more robust against
these problems, though.
Comment 11 Vincent Noel 2004-08-02 22:30:03 UTC
*** Bug 148662 has been marked as a duplicate of this bug. ***
Comment 12 Vincent Noel 2004-08-02 22:34:45 UTC
*** Bug 147686 has been marked as a duplicate of this bug. ***
Comment 13 Luis Villa 2004-08-04 15:51:40 UTC
We should be a lot more robust :/ This is one of the most frequently reported
bugs by Novell's internal GNOME users, for what it is worth, and vincent appears
to have found at least a half-dozen dups here.
Comment 14 Vincent Noel 2004-08-05 21:37:23 UTC
This bug is also a part of bug 145179.
Comment 15 Vincent Noel 2004-08-06 15:33:05 UTC
And should be related to bug 91273 somehow...
Comment 16 Vincent Noel 2004-08-06 15:36:42 UTC
*** Bug 91273 has been marked as a duplicate of this bug. ***
Comment 17 Vincent Noel 2004-08-06 15:50:29 UTC
*** Bug 120921 has been marked as a duplicate of this bug. ***
Comment 18 Vincent Noel 2004-08-06 15:51:38 UTC
Bug 120921 also have a (much longer) patch.
Comment 19 Elijah Newren 2004-08-06 16:12:44 UTC
Due to Luis' comment and the sheer number of dups, I'm bumping up the priority.
 Also due to his comment, I'm setting the version to 2.7.x.

/me wonders why he wasn't added to the cc list when bug 91273 was marked as a
duplicate of this bug
Comment 20 Federico Mena Quintero 2004-09-02 01:21:54 UTC
Retitling for clarity.
Comment 21 Federico Mena Quintero 2004-09-02 01:27:05 UTC
See the patch in bug #147686; is this fix correct?
Comment 22 Federico Mena Quintero 2004-09-02 02:19:57 UTC
We have that patch in the Novell package for gnome-session, BTW.  For reference,
it is attachment #29570 [details].
Comment 23 Elijah Newren 2004-09-03 21:34:43 UTC
I'm going to mark this bug with the 2.8.0 milestone; however, the fact that
we've already put up with this bug through several releases anyway might meant
that we should punt this until 2.8.x (with x >= 1).
Comment 24 Frederic Crozat 2004-09-15 17:12:25 UTC
Hmm, patch from bug #147686 doesn't fix the testcase I gave in bug 147686 :(
Comment 25 Frederic Crozat 2004-09-15 17:14:24 UTC
I was speaking of attachment #29570 [details], of course (sorry for the spam)
Comment 26 Elijah Newren 2004-09-15 17:15:58 UTC
Frederic: Um, you didn't comment in bug 147686 at all; did you mean the testcase
you gave in bug 120921?
Comment 27 Frederic Crozat 2004-09-15 17:19:56 UTC
Yeah, I mixed bug containing patch and bug containing testcase :)

Let's rehash :

Patch from bug 147686 doesn't fix testcase from bug 120921 

Comment 28 Kjartan Maraas 2004-10-14 22:36:25 UTC
I'm seeing this too with the latest 2.8.x stuff and I think it was caused by
adding gaim to my session.
Comment 29 Ray Strode [halfline] 2004-10-14 22:38:41 UTC
Kjartan you are more likely seeing this:
Comment 30 Josselin Mouette 2004-12-05 18:28:28 UTC
I also often get bug reports caused by gaim. There is also a broken session
handling in gdesklets.

I can confirm the patch from bug 147686 doesn't work, it even makes things worse
by triggering the problem with some valid setups where the current code works.
Comment 31 Kjartan Maraas 2005-01-03 16:34:45 UTC
Is anyone seeing this in 2.9.x? Is it caused by problems in gnome-session or by
badly managed apps?
Comment 32 Sebastien Bacher 2005-01-03 16:51:42 UTC
it's caused by apps with a broken session management afaik and still here with
2.9 (according to the ChangeLog there is almost no code change since 2.5)
Comment 33 Luis Villa 2005-01-24 16:14:03 UTC
Well, it is caused by poorly managed apps, but g-s-m's behavior in the face of
poorly managed apps is terrible. (And yes, it is still in 2.9.) The timeout for
the display of the splash screen should be much shorter.
Comment 34 Lee Aylward 2005-02-28 17:27:49 UTC
I am currently working on an app ( that causes this
behavior. Is there anything in particular I should be looking for to fix it?
Right now I am just calling Gnome2::Program->init when the program is started.
Is there anything else that I should be worrying about?
Comment 35 Baptiste Mille-Mathias 2005-03-06 14:39:54 UTC
*** Bug 169379 has been marked as a duplicate of this bug. ***
Comment 36 Sébastien Chenevotot 2005-03-20 11:43:42 UTC
I have the same problem with my gnome 2.8. I've read the topic but I didn't
understand how to fix that. 
Comment 37 Jack Stewart 2005-05-10 02:28:56 UTC
I have the same problem with Gnome 2.10 (of course it is mentioned in the 
release notes).  My problem extends to logout as well.  Th culprit in my case 
seems to be esd which is taking a long time to start up for some reason.  If I 
disable the sound server there is no problem but the hang is still evident at 
log out (not sure whether that is an esd issue)
IMHO gnome-session should not wait for apps that are not part of the default 
Comment 38 Teppo Turtiainen 2005-07-23 10:37:33 UTC
*** Bug 303423 has been marked as a duplicate of this bug. ***
Comment 39 Mark McLoughlin 2005-09-06 12:40:26 UTC
In practice, I think most cases of this problem were caused by gnome-smproxy.

We've removed gnome-smproxy in GNOME 2.12. See:

So, if anyone sees this issue, please do the following:

  - Remove ~/.gnome2/session, log back in and try and reproduce the bug

  - Once you've reproduced it, verify that gnome-smproxy isn't running

  - If its not running, log a new bug (maybe mention this bug number) and
    attach your ~/.gnome2/session

I've filed a new bug (bug #315350) about how we should better handle non-XSMP
aware in apps in the session. However, if a non-XSMP app appears in the session,
then that is a bug in itself which needs to be fixed separately from bug #315350