It also seems that we are unnecessarily waiting for the nautilus signal in UNR, 
when we could begin_fade after receiving the netbook-launcher signal.  FWIW, I 
rewrote line 1028 in xsplash.c to check for NULL or netbook-launcher, and it 
seemed to work better:
  
  if (signal_list ==  NULL || strcmp((gchar*)l->data,"netbook-launcher"))

I originally tried raising the timeout to 45sec (the default of 15 was
timing out even before netbook-launcher sent its' signal), but the
system still timed out waiting for nautilus...and IMHO we really don't
need that up to begin use in UNR.

-- 
xsplash taking 100% CPU with UNR installations
https://bugs.launchpad.net/bugs/438458
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to