[Splashy-users] [splashy] WORKS: 0.3.10+git20080510-1 with patched /etc/init.d/keymap.sh and /etc/splashy/config.xml

[Niko Cavallini Araya]

> After several tests I rely on the debianblue theme which will be in
> the upcoming splashy-theme v0.4.1 [6].
>
> The frustrating problem was the F2-disaster and (consequently?) a
> non-animated progress-bar [7].
> NO, it was a standstill!
> By pressing any key splashy was reanimated.

I am using debian-moreblue from splashy-themes v0.4 and my bar is animated.
Am I missing something here?

>
> In the end I eliminated two effects:
>   Patch #1: /etc/init.d/keymap.sh   <--- standstill
>   Patch #2: /etc/splashy/config.xml <--- progress-bar
>
> [P1] PATCHING /etc/init.d/keymap.sh
> OK, I overread the section "Sorting out bugs" in the WIKI.
> There, it is explained that init-scripts using unicode_start_stop()
> function causes problems with splashy.
>
> After patching /etc/init.d/keymap.sh splashy worked nearly perfect.
> Niko Cavallini Araya [8] is reporting the additional need of patching
> console-screen.sh.
> Please, check this for your system.

I just disd as directed by the FAQ at the end this just got updated
before i pached them, still changing console-screen.sh might not be
needed, I didn't test.

> W1: AUTOVERBOSE BOOT-PROMPT-PARAMETER
> What about an "autoverbose=on" as a boot-prompt option (not-only in
> case of errors!)?
>
> [splashy-0.3.10+git20080510/doc/splashy_config.pod] says:
> [...]
> =item B<--autoverbose> yes|no
>
> Set if Splashy turn into verbose mode when an error appears at boot
> [...]

Luis said he had to look into this part of the code. :)

-- 
Saludos
 Niko