[Splashy-devel] Bug#473112: splashy: Fails to initialize, messes up loading other modules

[Matthijs Kooijman]

Hi,

I've been seeing this problem as well, but I don't think switching udev and
splash is the solution here (will solve udev's problems but might just cause
others to show problems).

Anyway, it seems to problem is that splashy starts but needs a small amount of
time to get its networking up and running. Any init script that runs directly
after splashy will see splashy running, but might get connection refused (It
seems this particularly happens on log_end_msg, thus after starting udevd but
before synthesising events). This kills off the udev init script leaving
things broken.

The proper way to fix this is already discussed here and in some other
reports: Never let splashy's lsb-base-logging functions exit with an error.
The || true to arrange this are already added upstream.

I can confirm that this problem does not occur for me using the
lsb-base-logging.sh from git, from both the master branch and the 0.3.9 tag.
So, packaging 0.3.9 should close this report.

Gr.

Matthijs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20080526/26b22474/attachment.pgp