freezes for 15 seconds with "throbber started" before timing out

Bug #504403 reported by bcrowell on 2010-01-07
This bug affects 3 people
Affects Status Importance Assigned to Milestone
xsplash (Ubuntu)
Declined for Karmic by Sebastien Bacher
Declined for Lucid by Sebastien Bacher

Bug Description

Binary package hint: xsplash

After upgrading to karmic, I found that logging in took 15 seconds longer than it previously had. The 15-second delay does not depend on the choice of desktop session. E.g., it takes the extra 15 seconds even if you're logging in to an xterm failsafe session. By careful comparison against wall-clock time, I was able to find that the 15-second delay coincides with the following in /var/log/gdm/xsplash-user.log :

[09:52:35:-1262886754414120 - MSG] throbber started (50 frames)
[09:52:50:-1262886769000640 - MSG] ** timeout **

The "throbber started" message occurs at the beginning of the delay, and the "timeout" message at the end.

This appears to be related to, but not the same as, these bugs:

I'm not sure, but my guess is that xsplash expects to receive a signal from Gnome telling it that it's started up. I'm guessing that other desktops besides Gnome (e.g., fluxbox or the xterm failsafe session) do not provide such a signal, so xsplash hangs up the login process for 15 seconds waiting for the signal.

$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 9.10
Release: 9.10
Codename: karmic
$ uname -a
Linux rintintin 2.6.31-17-generic #54-Ubuntu SMP Thu Dec 10 17:01:44 UTC 2009 x86_64 GNU/Linux
$ apt-cache policy xsplash
  Installed: 0.8.5-0ubuntu1
  Candidate: 0.8.5-0ubuntu1
  Version table:
 *** 0.8.5-0ubuntu1 0
        500 karmic-updates/main Packages
        100 /var/lib/dpkg/status
     0.8.4-0ubuntu1 0
        500 karmic/main Packages

bcrowell (launchpadcrowell07) wrote :

I located the place in the source where this is happening. There is a function in xsplash.c called "temporary_hack_for_initial_fade." Well, I guess the name of the function says it all. The callback to temporary_hack_for_initial_fade is set in main(). Note that the 15 is hardcoded in two different places:

static guint timeout = 15;

"Timeout (in seconds - 15s by default) ", NULL

bcrowell (launchpadcrowell07) wrote :

I changed the 15 to 1, recompiled, and verified that this actually does fix the problem. Since setting it to 15 rather than 1 is causing unnecessary delays for people who use WMs that don't take 15 seconds to load, and since the whole thing is labeled "temporary_hack...", I would really just suggest changing the 15 to 1 for everybody until a permanent fix for the temporary hack can be produced.

Phillip Susi (psusi) wrote :

This package has been removed from Ubuntu. Closing all related bugs.

Changed in xsplash (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers