Package Details: splashy-full c2c9cc2-1

Git Clone URL: https://aur.archlinux.org/splashy-full.git (read-only)
Package Base: splashy-full
Description: A boot splashing system
Upstream URL: http://anonscm.debian.org/gitweb/?p=splashy/splashy;a=summary
Licenses: GPL
Provides: splashy
Submitter: None
Maintainer: None
Last Packager: jorge_barroso
Votes: 115
Popularity: 0.000002
First Submitted: 2009-07-03 17:05
Last Updated: 2015-06-15 19:23

Required by (0)

Sources (8)

  • automake.patch
  • configure.ac.patch
  • initcpio_hook
  • initcpio_install
  • splash-initscripts
  • splash.conf
  • splashy-functions
  • splashy

Latest Comments

arkeiro commented on 2015-04-28 21:15

I can't compile splashy-full:

...
...
...
Makefile:611: recipe for target 'xml_parser.lo' failed
make[2]: *** [xml_parser.lo] Error 1
make[2]: Leaving directory '/tmp/yaourt-tmp-jribeiro/aur-splashy-full/src/splashy/src'
Makefile:528: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/tmp/yaourt-tmp-jribeiro/aur-splashy-full/src/splashy'
Makefile:409: recipe for target 'all' failed
make: *** [all] Error 2
==> ERRO: Uma falha ocorreu em build().
A cancelar...
==> ERROR: Makepkg was unable to build splashy-full.

arkeiro commented on 2015-04-26 22:00

I get this message: ***Error***: You must have automake >= 1.9 installed
But...
$ pacman -Q |grep omake
automake 1.15-1

15.1 > 9, is true

How can I fix this?

carstene1ns commented on 2014-03-21 01:11

As said the source url is wrong. Try my uploaded PKGBUILD instead.
(Or better: do not use splashy at all, it is not systemd-ready!)

kaede commented on 2014-02-17 11:42

Same like davidrapan.

Cloning into 'splashy'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed

carstene1ns commented on 2014-01-11 11:04

I have fixed the PKGBUILD so it compiles again, however please note that splashy requires SysV-Init and is not systemd-ready. It will likely not work!
https://gist.github.com/carstene1ns/c968774bb64ce4ac26d6

davidrapan commented on 2014-01-07 00:44

Hi guys!

Please can someone look at my error while compiling ?

Thread: https://bbs.archlinux.org/viewtopic.php?pid=1367882#p1367882

Problem:
[code]
==> Extracting sources...
==> Starting build()...
-> Cloning initial copy of splashy...
Cloning into 'splashy'...
fatal: The remote end hung up unexpectedly
fatal: early EOF
fatal: index-pack failed
==> ERROR: A failure occurred in build().
Aborting...
[/code]

ZHoob2004 commented on 2013-10-02 19:04

As a quick fix to the automake issue, I just installed automake1.10 from the aur and ran alias automake=automake1.10 before doing makepkg and it built with no issues. automake1.10 doesn't replace automake, so it could be configured as a dependency and the command changed in the PKGBUILD as a solution to this update headache.

But then it had trouble with directfb 1.7 vs 1.6 when I tried to run mkinitcpio, so I'm going to be trying to use plymouth instead since it's working fine so far.

ZHoob2004 commented on 2013-10-02 18:53

As a quick fix to the automake issue, I just installed automake1.10 from the aur and ran alias automake=automake1.10 before doing makepkg and it built with no issues. automake1.10 doesn't replace automake, so it could be configured as a dependency and the command changed in the PKGBUILD as a solution to this update headache.

denspirit commented on 2013-09-06 15:43

automake version seems to be hardcoded in autogen.sh script from sources.
automake1.10.patch was indended to fix these errors,but needs to be updated with each release of automake in repos.
I don't know how (have never written a PKGBUILD myself yet) , but maybe we can retrieve the version of automake present in system and give it to sed script,instead of patch.
ED: there is also similar stuff in initcpio_install, where we are forced to use 1.6-0 directfb version.

denspirit commented on 2013-09-06 15:04

automake version seems to be hardcoded in autogen.sh script from sources.
automake1.10.patch was indended to fix these errors,but needs to be updated with each release of automake in repos.
I don't know how (have never written a PKGBUILD myself yet) , but maybe we can retrieve the version of automake present in system and give it to sed script,instead of patch.

asdil12 commented on 2013-08-02 09:01

==> Starting build()...
-> Cloning initial copy of splashy...
Cloning into 'splashy'...
Checking connectivity... done
patching file ./autogen.sh
patching file ./configure.ac
checking for autoconf >= 2.59...
testing autoconf2.50... not found.
testing autoconf... found 2.69
checking for automake >= 1.13...
testing automake-1.13... not found.
***Error***: You must have automake >= 1.13 installed
to build Package. Download the appropriate package for
from your distribution or get the source tarball at
http://ftp.gnu.org/pub/gnu/automake/automake-1.13.tar.gz

checking for libtool >= 1.5...
testing libtoolize... found 2.4.2
checking for glib-gettext >= 2.2.0...
testing glib-gettextize... found 2.36.3
checking for pkg-config >= 0.14.0...
testing pkg-config... found 0.28
./autogen.sh: line 154: --print-ac-dir: command not found
Checking for required M4 macros...
libtool.m4 not found
glib-gettext.m4 not found
pkg.m4 not found
Checking for forbidden M4 macros...
***Error***: some autoconf macros required to build Package
were not found in your aclocal path, or some forbidden
macros were found. Perhaps you need to adjust your
ACLOCAL_FLAGS?

==> ERROR: A failure occurred in build().

maxdevaine commented on 2013-07-01 10:51

It is necessary modify automake1.10.patch with new automake-1.14 :

...
+ 1.10*) automake_progs="automake-1.10" ;;
+ 1.13*) automake_progs="automake-1.13 automake-1.14" ;;
...

and I muss add PATH to pod2man in to PKGBUILD :
export PATH=$PATH:/usr/bin/core_perl

thanks.
Max Devaine

hobarrera commented on 2013-04-16 00:40

The initscript should be removed, since initscripts have been deprecated and removed from the repositories.

jorge_barroso commented on 2013-03-02 19:34

automake1.10 wasn't a "base" dependency, it is in aur and the 'base' group one is in version 1.13. 1. Equally, I've adopted the package made two patches and it installs now using the up-to-date automake and m4 packages

Det commented on 2013-01-05 20:17

Nothing in 'base' is required to be listed.

fluxer commented on 2013-01-05 18:17

sysfsutils is in core/base and I doubt that someone will remove it, same goes for mkinitcpio. I will add them later for the sake of sanity.

paul.c commented on 2013-01-05 18:08

You should add sysfsutils as dependency, it's needed for initcpio hook

einseenai commented on 2012-11-16 08:18

Any additional things to do except for what is specified in the wiki page? I mean in regard of Arch has switched to systemd?

einseenai commented on 2012-11-16 08:18

Any additional things to do except for what is specified in the wiki page? I mean in regard of Arch has switched to systemd?

Anonymous comment on 2012-11-12 17:25

This package works for me with:

1. Download AUR automake1.10 and create package with "makepkg -i"
2. Download AUR splashy-full and create package with "makepkg -i"

Done.

Anonymous comment on 2012-11-02 19:47

@fredricj: Looking at the dependencies I guess the difference is that "splashy-full" comes with themes

Anonymous comment on 2012-05-17 22:29

whats the diff between this and the "splashy" aur package?

zonyitoo commented on 2012-05-17 10:58

make failed!. And the automake1.10 download failed

einseenai commented on 2012-05-05 12:36

Well, even if it was directfb 1.4-5, it didn't work too. with 1.4-5 only mkinitcpio -p linux worked.

justforgetme commented on 2012-04-10 18:38

/lib/initcpio/install/splashy
Seems to have a lot of stuff hard coded into it.

I got errors about directfb 1.4-5 not being there (obvious since installed version is 1.5-0)
Also, on my system the if block determining architecture was failing since my $(arch) results in an error.

After fixing those two errors on my local copy the ramdisk is created without problems

einseenai commented on 2012-03-14 16:30

Guys, I've installed the package and done everything according to Arch's wiki. But it's still the same standard boot output. Any idea, why?

Det commented on 2012-02-24 09:38

I think we all know you were guessing there. You can try messing around with splashy.initcpio_hook and see, if it makes a difference.

Anonymous comment on 2012-02-24 08:16

I guessed on the second, still have problem getting it to work properly even after fixing the libpng15 issue(libvoodoo seems to be needed too). Now the splash only flashes before going back to textbased whereas it worked before

Det commented on 2012-02-23 22:57

Lol. That's actually it.

Not in 'installing' libpng14 but in trying to find it. This actually builds just fine with the latest libpng (1.5) after all but just looks for the older one for the hook.

I fixed the 'hook file' to only use symlinks so that this thing doesn't need to be updated every time one of those libraries gets updated (there was a lot of libraries not being included for this very reason).

I also updated the PKGBUILD. It's simpler and uses '--depth 1' for git (meaning the download's faster).

Anonymous comment on 2012-02-23 21:09

is the problem libpng15 per see or just that the hook tries to install libpng14 instead of libpng15?

Det commented on 2012-02-13 14:01

Ok :D. Wanna do a patch?

polylux commented on 2012-02-13 10:26

Don't have much time but... here I am.

Det commented on 2012-02-12 13:42

If you know someone who knows C, bring him here.

Anonymous comment on 2012-02-12 13:34

Ok, I see.
But since it is an orphan package, probably nobody would patch it...
Am I wrong? (I hope so).

Det commented on 2012-02-12 13:30

It's not a Debian issue. Arch is the only binary distribution currently using libpng15 (it would require a separate patch for the latest libpng):

https://alioth.debian.org/tracker/?atid=411690&group_id=30657&func=browse

Anonymous comment on 2012-02-12 12:38

Hello,
regarding the hook error mentioned by polylux, where can I find the bug submitted to the upstream?
Google did not find anything apart these comments, and I like to know how and when it will be fixed.
Now I cannot make this package work. My installation freeze after kernel boot.

polylux commented on 2012-02-08 14:57

Alright, got it. Thanks. Sorry for flagging it.

Det commented on 2012-02-08 14:38

You are. It's an upstream issue.

polylux commented on 2012-02-08 10:38

Splashy requires libpng14, whereas the current one in the repos is 1.5.
This renders errors when generating the linux image:

-> Parsing hook: [splashy]
==> ERROR: file not found: `/usr/lib/libpng14.so.14'

If I'm not wrong, I should set this to outdated.

Anonymous comment on 2011-09-09 15:56

I added
add_file "/lib/libbz2.so.1.0"
to
"splashy.initcpio_install" and rebuilt, now my splashscreen works fine.

Anonymous comment on 2011-08-29 18:09

Rebuilt with automake1.10. Installed, rebuilt initrd for splashy. same problem at boot. There's a post about it on the forums already: https://bbs.archlinux.org/viewtopic.php?id=124966

Det commented on 2011-08-29 09:22

No idea what's causing that then. Still builds fine here.

Are you sure you get those errors even after installing 'automake1.10'?

Anonymous comment on 2011-08-29 05:09

Only touched autogen.sh . It compiled, but I'm getting a segfault in dmesg when it's run at boot time now.

Det commented on 2011-08-28 19:09

You didn't happen to "chop" the 'automake1.10' make dependency too?

Anonymous comment on 2011-08-28 18:28

When I installed, autogen.sh didn't seem to like automake-1.11 . Had to chop the script up a little to get it to continue.

Det commented on 2011-08-20 13:06

Might want to concider doing that yourself in the future. It wasn't a big thing.

Anonymous comment on 2011-08-20 05:48

might want to update the deps to include git since its added now.

Det commented on 2011-08-12 08:25

Ok, I've now updated this thing to use the Git repo rather than the latest release tarball that's over 2 and half years old.

For some reason though, I just couldn't get this to work for myself anymore. It might be because of the 3.0 kernel, I'm not sure.

Det commented on 2011-08-11 12:44

Btw. I've now updated the Wiki for this thing too.

Det commented on 2011-07-29 20:08

Ok, in addition to the '-Werror' trick thesofty mentioned I just installed the "automake1.10" package and replaced the 'configure' with 'autogen.sh' in the PKGBUILD and I was able to make the git version to work.

Det commented on 2011-07-29 18:58

Ok, in addition to the '-Werror' trick thesofty mentioned I just installed the "automake1.10" package and I was able to make the git version to work.

Det commented on 2011-07-27 10:54

@thesofty, yeah it actually builds that way. Though, would've been enough to just 1) cd to the build path, 2) uncomment the 'patch' line from the PKGBUILD and 3) build with 'makepkg -ei'.

But I'm not sure whether this tarball should really be used since it was packaged over 2,5 years ago. Even before _this_ package was created.

The project seems otherwise (somewhat) active with last commit(s) done just 11 days ago (3 of 'em): http://anonscm.debian.org/gitweb/?p=splashy/splashy.git;a=summary

I actually pulled the current head (git clone git://anonscm.debian.org/git/splashy/splashy.git [path]) and tried to build it but got so many errors that I thought "oh, forget it": http://pastebin.com/Rt3g8Cfd

thesofty commented on 2011-07-24 09:03

I also cannot compile splashy-full. The problems are some minor warnings (variable initialized but not used) and the Werror compiler setting. I did a workaround by unpacking the splashy-0.3.13 tar file and removing the '-Werror' flag in the configure file. Afterwards I packed the splashy-0.3.13 diretory again, changed the md5 checksum, and compiled it by using makepkg.

Anonymous comment on 2011-07-23 16:30

Splashy build fails. pod2man is a dependency:

/bin/sh: pod2man: Command not found.

Greets

Anonymous comment on 2011-07-22 10:03

I found the culprit in the mkinicpio package, in the file "init":
At version 0.6.8 it had the code:

read CMDLINE </proc/cmdline
export CMDLINE

Which is gone in version 0.6.11.

Anonymous comment on 2011-07-21 23:10

I had the problem described by iansison and just "fixed" it by adding this to this beginning of /etc/rc.d/functions.d/splash:

if [ -z "$CMDLINE" ]; then
export CMDLINE=`cat /proc/cmdline`
fi

Turning on SPLASH_DEBUG showed that the script didn't get past "splash_enabled_cmdline", I guess CMDLINE is no longer defined for some reason, but this may not be a proper fix.

Anonymous comment on 2011-07-05 04:05

Package is not out of date, so I have updated the flag to reflect this fact.

====================
$ pkgfile libgcc_s.so.1

multilib/dwarffortress
multilib/gcc-libs-multilib
multilib/lib32-gcc-libs
core/gcc-libs
====================

Check to see if any of those packages resolve your error with libgcc_s.so.1 and report back please. I can't get splashy to work at all, so cannot verify that the multilib gcc package helps any, but it's worth a go.

leifurhauks commented on 2011-06-24 13:35

Why was this marked out of date? According to the project page (http://alioth.debian.org/projects/splashy/), 0.3.13 is the latest release.

Anonymous comment on 2011-05-25 01:30

Ughh.. have these issues been fixed? It would seem all versions of splashy here in the AUR are 'out of date'

Anonymous comment on 2011-05-04 15:30

splashy-full 0.3.13-7 worked for me until an update of mkinitcpio (0.6.8-2 -> 0.6.11-1) arrived. The resultant problem after the update is the boot graphic appearing with no progress bar activity. You need to press 'Ctrl-Alt-F7' to get out of the graphic and proceed with the bootup. Downgrading mkinitcpio to 0.6.8 fixes the problem. The question is how long will I need to pin the mkinitcpio package just because it breaks splashy... :(

Anonymous comment on 2011-04-28 10:49

easy to solve the problem, add the following to the PKGBUILD:
#------------------------------------------------------
sed -e 's| -Werror||g' \
-i "${srcdir}/splashy-${pkgver}/Makefile" \
-i "${srcdir}/splashy-${pkgver}/configure" \
-i "${srcdir}/splashy-${pkgver}/configure.ac"
#------------------------------------------------------
add it to the build() function,
just before 'make'

Anonymous comment on 2011-04-28 10:22

check this problem when building: http://pastebin.com/XMDmERyC
looks like xml_parser.c has 2 errors...

another user found this error: https://bbs.archlinux.org/viewtopic.php?id=117537

Anonymous comment on 2011-04-19 02:40

I have the same problem here with the libgcc_s.so nonsense. Can someone point me to a tutorial for removing splashy from my machine until this issue is resolved?

Georgios commented on 2011-04-17 09:58

adding libgcc_s.so.1 didnt help in my case.

BlackIkeEagle commented on 2011-04-11 08:26

@aivs

could you try to add libgcc_s.so.1 to your initramfs and check if the problem stays ?


if not you could post a patch here, thx + then gcc-libs becomes a dependency too

Anonymous comment on 2011-04-11 07:29

I have some problem when i booting (Atom 330)
libgcc_s.so.1 must be installed for pthread_cancel to work
This problem is solved?

Anderson commented on 2011-01-09 21:31

If you get "pod2man: command not found" during installing, just link
/usr/lib/perl5/core_perl/bin/pod2man
to
/usr/bin/pod2man

Anonymous comment on 2010-12-25 17:32

Add pkg-config to the make-depends

zebulon commented on 2010-12-02 07:23

@pennega: the problem is that after mkinitcpio I lost the written messages (but strangely, only when booting, not shutting down), that is weird.

Anonymous comment on 2010-11-30 19:59

i have simply commented the line #add_file "/usr/lib/directfb-1.4-5/interfaces/IDirectFBFont/libidirectfbfont_default.so" in the /lib/initcpio/install/splashy and it work perfect (at least it seems :D)

zebulon commented on 2010-11-30 18:45

I flagged this out of date, because this file:
ERROR: file '/usr/lib/directfb-1.4-5/interfaces/IDirectFBFont/libidirectfbfont_default.so' does not exist anymore (listed in splashy.initcpio_install).
Should this file be replaced?

zebulon commented on 2010-11-30 18:37

I flagged it out-of-date because this file:
/usr/lib/directfb-1.4-5/wm/libdirectfbwm_default.so
is not available anymore in directfb package. What is the alternative?

zebulon commented on 2010-11-30 18:31

I flagged it out-of-date because this file:
/usr/lib/directfb-1.4-5/wm/libdirectfbwm_default.so
is not available anymore in directfb package. What is the alternative?

Anonymous comment on 2010-11-13 22:01

Hello! It seems that jpeg-based themes (for example, archlinux-burn) taken from splashy-themes do not work. When the system is loading
I see an empty screen (no background/progress bars, just a single color screen). However, png-based themes (for example, darch-white) work good.

Also, when I use jpeg-based theme, after my desktop environment is loaded (I use XFCE), I see strange black horizontal lines in the top-left corner of the screen.
They disappear if I switch from 7th virtual terminal to 1st and then back to 7th. However, I'm not sure that it is related to the type of the theme (jpeg or png),
but after I had switched from archlinux-burn to darch-white, the problem disappeared.

BlackIkeEagle commented on 2010-11-02 05:47

could you rebuild splashy without the splashy_video.c.patch ?

and check if the patch has not caused the yellow flash ?

if so, you could rebuild without the patch, but then there will be no progress bar.

lagagnon commented on 2010-11-01 23:20

I can confirm since my upgrade yesterday (after 3 months) splashy now causes a pale yellow screen flashing just before splashy starts up and that the fonts in the archlinux-simplyblack theme are now way too large and unreadable. Changing the theme to archpaint2 solved the fonts problem (as there is no text scrolling in that theme) but the yellow screen flash is still there.

Anonymous comment on 2010-10-23 11:55

googling showed this links:
http://forum.teamspeak.com/showthread.php?t=40875
https://bugs.launchpad.net/ubuntu/+source/gcc-3.3/+bug/40285

You're not alone and your problem may be no concerned with splashy

Anonymous comment on 2010-10-11 04:16

I have a problem:
AMD64, using vesafb on nvidia

Splashy works fine, but after booting, I get a black screen. Any keypress wakes up the console, but then there is an error:
login: libgcc_s.so.1 must be installed for pthread_cancel to work
Splashy caught signal number 6. Exiting...Splashy caught signal number 6. Exiting...

I don't know whether this error is responsible for the black screen.

Any ideas?

Output of:
└───#» locate libgcc_s
/usr/lib/libgcc_s.so
/usr/lib/libgcc_s.so.1
/usr/lib32/libgcc_s.so
/usr/lib32/libgcc_s.so.1

Anonymous comment on 2010-09-21 07:22

fyi: working almost flawlessly with intel gma 945 kms mode, big fonts with darch-white, but edited the theme not to show it=) thanks@blackeagle for the patch^^

Anonymous comment on 2010-09-19 19:30

@BlackEagle

Sorry, that wasn't my intention. In fact, I didn't even know that you are notified about comment changes.

About the yellow screen, I recorded a video to show you when it happens, its fast and just before splashy (and its theme independent, now i'm using archpaint2). I tried a lot of configs, but none solved this issue.

Yout can see it here: http://www.youtube.com/watch?v=vS7eMwvwm8E


Thanks :)

BlackIkeEagle commented on 2010-09-19 18:54

@estevao

could you please stop changing your comment, we already know you are using archlinux-simplyblack

Anonymous comment on 2010-09-19 18:47

@sherlock

I'm using archlinux-simplyblack. Thanks.

Anonymous comment on 2010-09-19 03:18

What theme are you using? I'm using archpaint2 without messages and everything is fine.
I think you can change font height in /usr/share/splashy/themes/<theme>/theme.xml in /splashy/textbox/text/font/height

Anonymous comment on 2010-09-18 22:26

Some problems with new version here. Textbox fonts are too big and theme background color is changing to yellow during boot and shutdown.

BlackIkeEagle commented on 2010-09-02 18:20

http://github.com/BlackIkeEagle/herecura/tree/master/herecura-stable/splashy/

fixed the progressbar failure

Anonymous comment on 2010-08-31 17:05

progressbar doesn't work over here with patch, but better than nothing=)

Feanor12 commented on 2010-08-30 22:35

i created a patch http://pastebin.com/uazapTzY for /lib/initcpio/install/splashy

Anonymous comment on 2010-08-29 23:22

The file /lib/initcpio/install/splashy must point to the new lib directories created by directfb-1.4.5-1 package. Thanks.

Anonymous comment on 2010-05-14 18:08

Please add pkgconfig to dependance :
checking for pkg-config... no
checking for splashy... configure: error: The pkg-config script could not be found or is too old. Make sure it
is in your PATH or set the PKG_CONFIG environment variable to the full
path to pkg-config.