[Splashy-devel] Bug#455685: Splashy makes GDM initscript fail (and hence, leaves system on VT1)

[Luis Mondesi]

On Dec 11, 2007 12:58 AM, Diego Escalante Urrelo <dieguito at gmail.com> wrote:

> After updating to splashy 0.3.7, GDM broke. It didn't start anymore. A
> quick visit to init 1 allowed me to see the output of GDM initscript,
> that took me to the culprit: splashy.
> The problem was a bad if [] in line 178 of /etc/lsb-base-loggin.sh,
> which is referenced as a fix for bug #400598.
>
> I couldn't catch the exact message, sorry. But you might want to
> double-check that line.
>

Hey Diego,

Can you purge the old Splashy package and re-install?

  # first, backup /etc/splashy (hint: tar cf /etc/splashy.tar /etc/splashy)
  dpkg -P splashy libsplashy1 libsplashy1-dev
  apt-get install splashy

If you still see this error, can you send me copies of your /etc/init.d/gdm
and /etc/lsb-base-logging.sh scripts?

You can join us in #splashy on irc.freenode.net to discuss this further.

Regards,

-- 
----)(-----
Luis Mondesi
Maestro Debiano

----- START ENCRYPTED BLOCK (Triple-ROT13) ------
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner
jbeyq.
----- END ENCRYPTED BLOCK (Triple-ROT13) ------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20071211/5afc28df/attachment.htm