You are not logged in.

#26 2008-05-23 01:38:50

angvp
Developer
From: Buenos Aires, Argentina
Registered: 2008-05-15
Posts: 32
Website

Re: Arch Linux and Splashy, a big update

Hi everyone!

lextid, nice work, you dedicate a lot researching about splashy, i was doing the same a few days before.

Now i will install and test your packages in another pc (i cannot test on the mine because i have to know if the AUR packages that actually are in, suddenly crash), but i have an idea.

We can do some splashy testing repo for testing in others machine (i can offer the repo, just for those splashy packages), i am very interested really.

Please write me an e-mail to be in contact angvp at archlinux.com.ve

Bye!

Offline

#27 2008-05-23 07:03:23

j.roszk
Member
From: Poznan/Poland
Registered: 2008-05-22
Posts: 29
Website

Re: Arch Linux and Splashy, a big update

About archlinux-burn - it's a bug in package. There are symlinks to files which don't exist.

/etc/splashy/themes $ ls -l archlinux-burn
razem 4
lrwxrwxrwx 1 root root   49 maj 23 08:54 background.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
lrwxrwxrwx 1 root root   49 maj 23 08:54 error.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
lrwxrwxrwx 1 root root   46 maj 23 08:54 FreeSans.ttf -> /usr/share/splashy/themes/default/FreeSans.ttf
lrwxrwxrwx 1 root root   49 maj 23 08:54 suspend.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
-rw-r--r-- 1 root root 3077 maj 23 08:54 theme.xm

Last edited by j.roszk (2008-05-23 07:03:47)

Offline

#28 2008-05-23 07:13:33

SiD
Member
From: Germany
Registered: 2006-09-21
Posts: 729

Re: Arch Linux and Splashy, a big update

Great wokrk!!

lexiw wrote:

A little note about splashy-themes: ideally we would have a theme for every wallpaper from archlinux-wallpaper plus other themes.
If you would like to submit a theme, send me a mail smile

I sent you an e-mail. wink

Offline

#29 2008-05-23 10:32:50

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

j.roszk wrote:

About archlinux-burn - it's a bug in package. There are symlinks to files which don't exist.

/etc/splashy/themes $ ls -l archlinux-burn
razem 4
lrwxrwxrwx 1 root root   49 maj 23 08:54 background.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
lrwxrwxrwx 1 root root   49 maj 23 08:54 error.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
lrwxrwxrwx 1 root root   46 maj 23 08:54 FreeSans.ttf -> /usr/share/splashy/themes/default/FreeSans.ttf
lrwxrwxrwx 1 root root   49 maj 23 08:54 suspend.jpg -> /usr/share/archlinux/wallpaper/archlinux-burn.png
-rw-r--r-- 1 root root 3077 maj 23 08:54 theme.xm

Thank you, i fixed it!

SiD wrote:

I sent you an e-mail.

The theme will be included as soon as possible. Just a question about the license, does it applies to the theme or just the background?

angvp wrote:

Hi everyone!

lextid, nice work, you dedicate a lot researching about splashy, i was doing the same a few days before.

Now i will install and test your packages in another pc (i cannot test on the mine because i have to know if the AUR packages that actually are in, suddenly crash), but i have an idea.

We can do some splashy testing repo for testing in others machine (i can offer the repo, just for those splashy packages), i am very interested really.

Please write me an e-mail to be in contact angvp at archlinux.com.ve

Bye!

I was about to write to you now that the project is almost complete. A repo would be a gret addition :)
If you want to collaborate to the project I'll be happy, just remember that i probably won't be online until tomorrow.

And now, the updated code in a single tarball, remember to remove the old packages and backup your important /etc/* files before update:
http://slexiw.netsons.org/files/splashy-stuff.tar.gz

Last edited by lexiw (2008-05-23 10:34:36)

Offline

#30 2008-05-23 12:05:28

SiD
Member
From: Germany
Registered: 2006-09-21
Posts: 729

Re: Arch Linux and Splashy, a big update

lexiw wrote:
SiD wrote:

I sent you an e-mail.

The theme will be included as soon as possible. Just a question about the license, does it applies to the theme or just the background?

Hmm, good question.
I've created the background with the images from the slim-darch theme by gleidson and used the same license he uses in the slim-theme-darch package in AUR.

I would say it applies to the complete theme. wink

edit:
Because I don't know much about all this license stuff, I used the same as gleidson for his slim theme. If it's ok I would change the license for the splashy theme to GPL.

Last edited by SiD (2008-05-23 12:13:54)

Offline

#31 2008-05-23 12:26:04

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

SiD wrote:
lexiw wrote:
SiD wrote:

I sent you an e-mail.

The theme will be included as soon as possible. Just a question about the license, does it applies to the theme or just the background?

Hmm, good question.
I've created the background with the images from the slim-darch theme by gleidson and used the same license he uses in the slim-theme-darch package in AUR.

I would say it applies to the complete theme. wink

edit:
Because I don't know much about all this license stuff, I used the same as gleidson for his slim theme. If it's ok I would change the license for the splashy theme to GPL.

The themes i created aren't under any license at all, they are just simple xml files. The backgrounds comes from archlinux-wallpaper (that uses a custom license) but they are just symlinked and the package itself is a dependency of splashy-themes.
We should probably contact the author of slim-darch theme because i'm not an expert in license stuff smile

Offline

#32 2008-05-23 18:52:19

schivmeister
Developer/TU
From: Singapore
Registered: 2007-05-17
Posts: 971
Website

Re: Arch Linux and Splashy, a big update

I actually like USplash but uhh..it doesn't matter. This is great work (as a praise for potential great work), but let me refrain from commenting before trying.


I need real, proper pen and paper for this.

Offline

#33 2008-05-23 23:35:18

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

It works. Freaking awesome. Throw the man a bone. I've been wanting this for months.
Thank you so much.

I still have this issue: http://bbs.archlinux.org/viewtopic.php?id=43829

Offline

#34 2008-05-23 23:47:40

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

SpookyET wrote:

It works. Freaking awesome. Throw the man a bone. I've been wanting this for months.
Thank you so much.

I still have this issue: http://bbs.archlinux.org/viewtopic.php?id=43829

The current (archlinux)version of splashy does not support any DM run as a daemon. The script lacks a way to check if gdm/xdm/kdm is starting to quit itself.
I believe that's your problem, correct me if I'm wrong. If you are running a DM as a daemon could you please try the inittab way to see if the problem is solved?
The current development version already support a "per-daemon check" and it should be easy to implement such check.

Offline

#35 2008-05-23 23:50:38

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

I don't know why uswsusp does not see splashy:

checking for LRMI_common_init in -lx86... yes
checking for lzo1x_1_compress in -llzo2... yes
checking for libgcrypt... found
checking for splashy_open in -lsplashy... no
configure: error: Required libsplashy was not found
make: *** No rule to make target `install'.  Stop.
==> ERROR: Build Failed.
    Aborting...

Offline

#36 2008-05-23 23:54:57

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

That might be needed. I know it's needed for uswsusp to work with FBSPlash. I explained this to the original PKGBUILD author.

# Remove unnecessary files
    rm -rf ${startdir}/pkg/usr/lib/*.la

Offline

#37 2008-05-23 23:56:51

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

Even with that removed, it still fails

==> Making package: uswsusp-splashy 0.8-1  (Fri May 23 19:56:06 EDT 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found suspend-0.8.tar.gz in build dir
  -> Found uresume-hook in build dir
  -> Found uresume-install in build dir
  -> Found whitelist.c.diff in build dir
==> WARNING: Integrity checks (md5) are missing or incomplete.
==> Extracting Sources...
  -> bsdtar -x -f suspend-0.8.tar.gz
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /bin/install -c
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gfortran option to produce PIC... -fPIC
checking if gfortran PIC flag -fPIC works... yes
checking if gfortran static flag -static works... yes
checking if gfortran supports -c -o file.o... yes
checking whether the gfortran linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for m4... m4
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for LIBPCI... no
checking for pci_init in -lpci... yes
checking for LRMI_common_init in -lx86... yes
checking for lzo1x_1_compress in -llzo2... yes
checking for libgcrypt... found
checking for splashy_open in -lsplashy... no
configure: error: Required libsplashy was not found
make: *** No rule to make target `install'.  Stop.
==> ERROR: Build Failed.
    Aborting...

Offline

#38 2008-05-23 23:59:15

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

lexiw wrote:
SpookyET wrote:

It works. Freaking awesome. Throw the man a bone. I've been wanting this for months.
Thank you so much.

I still have this issue: http://bbs.archlinux.org/viewtopic.php?id=43829

The current (archlinux)version of splashy does not support any DM run as a daemon. The script lacks a way to check if gdm/xdm/kdm is starting to quit itself.
I believe that's your problem, correct me if I'm wrong. If you are running a DM as a daemon could you please try the inittab way to see if the problem is solved?
The current development version already support a "per-daemon check" and it should be easy to implement such check.

I'm pretty sure it doesn't shut down. They do go away after a while. Though, I did not notice if the plack spots at the top of the screen went away after I did "splashy test" which fails by the way.

Offline

#39 2008-05-23 23:59:27

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

SpookyET wrote:

Even with that removed, it still fails

==> Making package: uswsusp-splashy 0.8-1  (Fri May 23 19:56:06 EDT 2008)
==> Checking Runtime Dependencies...
==> Checking Buildtime Dependencies...
==> Retrieving Sources...
  -> Found suspend-0.8.tar.gz in build dir
  -> Found uresume-hook in build dir
  -> Found uresume-install in build dir
  -> Found whitelist.c.diff in build dir
==> WARNING: Integrity checks (md5) are missing or incomplete.
==> Extracting Sources...
  -> bsdtar -x -f suspend-0.8.tar.gz
==> Removing existing pkg/ directory...
==> Entering fakeroot environment...
==> Starting build()...
checking for a BSD-compatible install... /bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables... 
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /bin/install -c
checking for a sed that does not truncate output... /bin/sed
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /bin/grep -E
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for /usr/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognize dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking for g++... g++
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking dependency style of g++... gcc3
checking how to run the C++ preprocessor... g++ -E
checking for g77... no
checking for xlf... no
checking for f77... no
checking for frt... no
checking for pgf77... no
checking for cf77... no
checking for fort77... no
checking for fl32... no
checking for af77... no
checking for xlf90... no
checking for f90... no
checking for pgf90... no
checking for pghpf... no
checking for epcf90... no
checking for gfortran... gfortran
checking whether we are using the GNU Fortran 77 compiler... yes
checking whether gfortran accepts -g... yes
checking the maximum length of command line arguments... 98304
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
appending configuration tag "CXX" to libtool
checking for ld used by g++... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC
checking if g++ PIC flag -fPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
appending configuration tag "F77" to libtool
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
checking for gfortran option to produce PIC... -fPIC
checking if gfortran PIC flag -fPIC works... yes
checking if gfortran static flag -static works... yes
checking if gfortran supports -c -o file.o... yes
checking whether the gfortran linker (/usr/bin/ld) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for pkg-config... /usr/bin/pkg-config
checking pkg-config is at least version 0.9.0... yes
checking for m4... m4
checking for special C compiler options needed for large files... no
checking for _FILE_OFFSET_BITS value needed for large files... 64
checking for LIBPCI... no
checking for pci_init in -lpci... yes
checking for LRMI_common_init in -lx86... yes
checking for lzo1x_1_compress in -llzo2... yes
checking for libgcrypt... found
checking for splashy_open in -lsplashy... no
configure: error: Required libsplashy was not found
make: *** No rule to make target `install'.  Stop.
==> ERROR: Build Failed.
    Aborting...

I will look into uswsusp as soon as the scripts are finished (i'm almost there btw).

Offline

#40 2008-05-24 00:02:38

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

SpookyET wrote:
lexiw wrote:
SpookyET wrote:

It works. Freaking awesome. Throw the man a bone. I've been wanting this for months.
Thank you so much.

I still have this issue: http://bbs.archlinux.org/viewtopic.php?id=43829

The current (archlinux)version of splashy does not support any DM run as a daemon. The script lacks a way to check if gdm/xdm/kdm is starting to quit itself.
I believe that's your problem, correct me if I'm wrong. If you are running a DM as a daemon could you please try the inittab way to see if the problem is solved?
The current development version already support a "per-daemon check" and it should be easy to implement such check.

I'm pretty sure it doesn't shut down. They do go away after a while. Though, I did not notice if the plack spots at the top of the screen went away after I did "splashy test" which fails by the way.

What DM are you using? Are you running it through the DAEMONS array in rc.conf?

Offline

#41 2008-05-24 03:30:21

lexiw
Member
Registered: 2008-04-29
Posts: 46

Re: Arch Linux and Splashy, a big update

Ok, another release for you: http://slexiw.netsons.org/files/splashy-stuff2.tar.gz
A big thanks to angvp for fixing splashy PKGBUILD and BIG thanks to #archlinux.it for helping me all the night smile
There's a new theme btw.

I opened a task in the bug tracker http://bugs.archlinux.org/task/10482, if the patch is accepted this will be the only patch needed to make any splash system works:

--- b/rc.shutdown    2008-05-23 21:52:57.000000000 +0200
+++ b/rc.shutdown    2008-05-23 21:58:57.000000000 +0200
@@ -41,12 +41,12 @@
 
 # Terminate all processes
 stat_busy "Sending SIGTERM To Processes"
-/sbin/killall5 -15 &> /dev/null
+/sbin/killall5 -15 $KILLALL5_OPTS &> /dev/null
 /bin/sleep 5
 stat_done
 
 stat_busy "Sending SIGKILL To Processes"
-/sbin/killall5 -9 &> /dev/null
+/sbin/killall5 -9 $KILLALL5_OPTS &> /dev/null
 /bin/sleep 1
 stat_done

Yes, initscripts-splash is almost unneeded.
I will concentrate on bug fixes now (there is only one bug reported, the DM one).

Enjoy!

Offline

#42 2008-05-24 03:58:46

angvp
Developer
From: Buenos Aires, Argentina
Registered: 2008-05-15
Posts: 32
Website

Re: Arch Linux and Splashy, a big update

I created a repository for those packages (just i686 for now if you have x86_64 feel free to contact me at angvp at archlinux.com.ve)

Add to your /etc/pacman.conf

[archlinuxve]
Server = http://repo.archlinux.com.ve/i686

pacman -S splashy

big_smile

Offline

#43 2008-05-24 05:33:40

Statix
Member
From: Hangzhou, China
Registered: 2008-02-16
Posts: 240

Re: Arch Linux and Splashy, a big update

angvp wrote:

I created a repository for those packages (just i686 for now if you have x86_64 feel free to contact me at angvp at archlinux.com.ve)

Add to your /etc/pacman.conf

[archlinuxve]
Server = http://repo.archlinux.com.ve/i686

pacman -S splashy

big_smile

I mailed ya the x86_64 packages.


Madly in love with Arch64, Openbox, DotA, and of course... penguins!
Happy to help if you're not a Help Vampire. Use your wonderful resources like ArchWiki, Google, and our wonderful search page.

Offline

#44 2008-05-24 07:45:25

luciferin
Member
Registered: 2007-05-10
Posts: 144

Re: Arch Linux and Splashy, a big update

Just got this up an running, great job on this.  I'm very happy with the results and hopefully we can get all of this incorporated to give arch this excellent splash solution.  I just want to tell you that I appreciate your excellent work and I'm very glad to have you in our community before I move on.

I'm having one small problem.  The scripts don't seem to support the inittab method of launching a display manager.  It works fine if I add GDM to my daemons array, but if I try to do this method (run level 5) Splashy just hangs on the last daemon launched and I have to ctrl+alt+del to restart.

Offline

#45 2008-05-24 09:08:00

angvp
Developer
From: Buenos Aires, Argentina
Registered: 2008-05-15
Posts: 32
Website

Re: Arch Linux and Splashy, a big update

luciferin wrote:

Just got this up an running, great job on this.  I'm very happy with the results and hopefully we can get all of this incorporated to give arch this excellent splash solution.  I just want to tell you that I appreciate your excellent work and I'm very glad to have you in our community before I move on.

I'm having one small problem.  The scripts don't seem to support the inittab method of launching a display manager.  It works fine if I add GDM to my daemons array, but if I try to do this method (run level 5) Splashy just hangs on the last daemon launched and I have to ctrl+alt+del to restart.

I awake thinking in do that test (change from 3 to 5) but i use SLiM let me try and i will tell you the story! bye

Offline

#46 2008-05-24 09:37:13

angvp
Developer
From: Buenos Aires, Argentina
Registered: 2008-05-15
Posts: 32
Website

Re: Arch Linux and Splashy, a big update

News:

Thanks to Statix we have an x86_64 packages now in the repo, so if you are using x86_64 add this:

[archlinuxve]
Server = http://repo.archlinux.com.ve/x86_64

Thanks

Offline

#47 2008-05-24 10:24:01

iphitus
Forum Fellow
From: Melbourne, Australia
Registered: 2004-10-09
Posts: 4,927

Re: Arch Linux and Splashy, a big update

Kudos on the good work!

Offline

#48 2008-05-24 12:41:35

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

lexiw wrote:
SpookyET wrote:
lexiw wrote:

The current (archlinux)version of splashy does not support any DM run as a daemon. The script lacks a way to check if gdm/xdm/kdm is starting to quit itself.
I believe that's your problem, correct me if I'm wrong. If you are running a DM as a daemon could you please try the inittab way to see if the problem is solved?
The current development version already support a "per-daemon check" and it should be easy to implement such check.

I'm pretty sure it doesn't shut down. They do go away after a while. Though, I did not notice if the plack spots at the top of the screen went away after I did "splashy test" which fails by the way.

What DM are you using? Are you running it through the DAEMONS array in rc.conf?

I'm using GDM in the daemons array.

Also, I'm having issues with themes. It falls back to default. It might show archlinux-simplyblack at shutdown for the first time when you enable it, but that's it. It falls back to default. It can also drop you in tty1 instead of tty7.

Offline

#49 2008-05-24 12:50:04

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

lexiw wrote:

Ok, another release for you: http://slexiw.netsons.org/files/splashy-stuff2.tar.gz
A big thanks to angvp for fixing splashy PKGBUILD and BIG thanks to #archlinux.it for helping me all the night smile
There's a new theme btw.

I opened a task in the bug tracker http://bugs.archlinux.org/task/10482, if the patch is accepted this will be the only patch needed to make any splash system works:

--- b/rc.shutdown    2008-05-23 21:52:57.000000000 +0200
+++ b/rc.shutdown    2008-05-23 21:58:57.000000000 +0200
@@ -41,12 +41,12 @@
 
 # Terminate all processes
 stat_busy "Sending SIGTERM To Processes"
-/sbin/killall5 -15 &> /dev/null
+/sbin/killall5 -15 $KILLALL5_OPTS &> /dev/null
 /bin/sleep 5
 stat_done
 
 stat_busy "Sending SIGKILL To Processes"
-/sbin/killall5 -9 &> /dev/null
+/sbin/killall5 -9 $KILLALL5_OPTS &> /dev/null
 /bin/sleep 1
 stat_done

Yes, initscripts-splash is almost unneeded.
I will concentrate on bug fixes now (there is only one bug reported, the DM one).

Enjoy!

I thought that they don't want initscripts patched. They want you to override functions and put them in functions.d.

Offline

#50 2008-05-24 13:03:50

SpookyET
Member
Registered: 2008-01-27
Posts: 410

Re: Arch Linux and Splashy, a big update

Is it possible to have a fancy progressbar like Ubuntu's? I know you can with fbsplash.

Offline

Board footer

Powered by FluxBB