On Dec 22, 2007 12:11 PM, Steve Fosdick <<a href="mailto:dbugs@pelvoux.nildram.co.uk">dbugs@pelvoux.nildram.co.uk</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have had the same issue with gdm not starting when splashy is installed.<br><br>I have checked line 178 of /etc/lsb-base-logging.sh but in the version installed on my system this line is a comment so I can not see how, in my case, that line could be causing the error.
<br><br>The failure mechanism seems to be that /etc/init.d/gdm has performed 'set -e' so that any command that fails, even if there is no error message or the message is surpressed by re-directing to /dev/null, will cause /etc/init.d/gdm to stop executing at that point. With splashy installed and its corresponding /etc/lsb-
base-logging.sh the log_daemon_msg subroutine is failing and thus aborting /etc/init.d/gdm.<br><br>I haven't had a chance to work through all the commands splashy is running but perhaps there are some assumptions there that don't hold true. For example, in my case, splashy was installed because it was recommended by uswsusp and is therefore used for the suspend/resume progress screen but I have not yet got around to setting it up for normal startup/shutdown.
<br><br>Anyway, for now, I have been able to work around this patching /etc/lsb-base-logging.sh as follows:<br><br>diff -u lsb-base-logging-orig.sh lsb-base-logging.sh<br>--- lsb-base-logging-orig.sh 2007-12-22 17:09:34.000000000
+0000<br>+++ lsb-base-logging.sh 2007-12-22 17:03:52.000000000 +0000<br>@@ -118,7 +118,7 @@<br><br> # Stop splashy on *dm<br> case $2 in<br>- ?dm) stop_splashy;;<br>+ ?dm) stop_splashy || return 0 ;;<br>
esac<br> }<br><br>So even if attempting to stop splashy fails gdm still starts.<br></blockquote><div><br>Hello Steve,<br><br>Thanks for suggesting this fix. We included this in our latest script [1].<br>This will be released as Splashy
0.3.9.<br><br>Please note that Splashy 0.3.8 included code that prevented this from happening by doing the right thing when stop_splashy is called:<br>- only run keymap.sh if splashy prevented it from starting. do the same for
console-screen.sh<br>- only umount Splashy's steps dir if it's mounted<br><br>However, it doesn't hurt to have "|| return 0" in the log_daemon_msg() call as well.<br><br>Splashy 0.3.8 will be added to the debian archives soon. It has not been added yet because we are all in "holidays" mode and the whole release/bug-fix cycle has been reduced in speed ;-)
<br></div></div><br>If you are reading this bug and you are having problems with gdm or any other script, please just grab a copy of lsb-base-logging.sh and replace your /etc/lsb-base-logging.sh copy with this [1].<br><br>
Notes:<br>1. <a href="http://git.debian.org/?p=splashy/splashy.git;a=blob_plain;f=scripts/lsb-base-logging.sh;hb=HEAD">http://git.debian.org/?p=splashy/splashy.git;a=blob_plain;f=scripts/lsb-base-logging.sh;hb=HEAD</a> <br>
<br>-- <br>----)(----- <br>Luis Mondesi<br>Maestro Debiano<br><br>----- START ENCRYPTED BLOCK (Triple-ROT13) ------<br>Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq.<br>----- END ENCRYPTED BLOCK (Triple-ROT13) ------