You are not logged in.
I had created a PKGBUILD for xsplash-bzr (and then uploaded on AUR), when I learned that it existed, but I supposed that there might be something like a README, somewhere, but there is no documentation. The Ubuntu packages are cryptic, I can't find a way to make it work.
Can someone help me improve the PKGBUILD I've uploaded on AUR ? ![]()
Offline
Maybe we can get some infos from here: http://ubuntuforums.org/showthread.php?p=7888736
Documentation is on the todo list from the project...
Think we need a modded gdm to get this to work properly.... maybe its not worth the work at the moment... I thought it was a boot splash like plymouth, but seems jus to replace the gdm splash....
Last edited by Solid1986Snake (2009-09-21 06:04:48)
Offline
Well just managed to find out that this would not e very useful for arch in the current state!
Why? I'll try to make it clear on the difference between plymouth and xsplash.
Playmouth initializes an xserver at very early boot stage and kills that before login.
Xsplash is intended to start a full xserver in a very early boot stage. To get this behaviour we would need to mod the initscripts very hard, because gdm is NEVER started before init:3 ....
Maybe we have chances to mod the quick-init or finit-arc packages to get splash to work.... But its too much of work I think....
Offline
Oh my .... :-/ I think we are gonna wait for gdm 2.28 to end up in [extra], and then... check out for new initscripts (and that's definitelly a difficult task)
Offline
If you have some free time you could try to compile the modded gdm from Ubuntu under Archlinux...
This could be a first begining to get xsplash started.....
Offline
Οh, I've tried (I once wanted to see why these Ubuntu devs want to patch EVERYTHING), it could be compiled, but it wouldn't start (arghhhh).
Offline
Well than lets really wait for a documentet Version, it seems not worth to try it really harder at the moment...
Offline
Ubuntu and Debian tend to have their packaging process really cryptic and undocumented, unfortunatelly ...
unlike RHEL/Fedora (spec files), Gentoo (.ebuild), Slack (.Slackbuild), Arch (PKGBUILD).
Offline
Playmouth initializes an xserver at very early boot stage and kills that before login.
Wrong. Plymouth paints straight on the framebuffer, and is able to show fancy graphics only if KMS is enabled and working, otherwise it falls back to a text-based mode. XSplash really looks crap, they could have simply relied on Plymouth, but I bet they don't want to show a text-based bootsplash to nVidia and recent ATI cards owners.
Offline
Solid1986Snake wrote:Playmouth initializes an xserver at very early boot stage and kills that before login.
Wrong. Plymouth paints straight on the framebuffer, and is able to show fancy graphics only if KMS is enabled and working, otherwise it falls back to a text-based mode. XSplash really looks crap, they could have simply relied on Plymouth, but I bet they don't want to show a text-based bootsplash to nVidia and recent ATI cards owners.
Thanks for the info drf........ i really find that it is very hard to find information about these softwares.......
Offline
Well i copmiled gdm today.... it wasnÄt scuh a problem.... maybe we can go a little bit further now?
# Maintainer: Patrick Schwalm <patrick schwalm googlemail com
pkgname=gdm-ubuntu
_realname=gdm
pkgver=2.20.10
pkgrel=1
pkgdesc="Gnome Display Manager (a reimplementation of xdm) with Ubuntu patches"
arch=(i686 x86_64)
license=('GPL')
depends=('pam>=1.0.2' 'libdmx' 'tcp_wrappers>=7.6' 'libgnomecanvas>=2.26.0' 'librsvg>=2.26.0' 'gksu>=2.0.0' 'dbus-glib>=0.80' 'consolekit' 'zenity>=2.26.0')
makedepends=('intltool' 'gnome-doc-utils>=0.16.0' 'pkgconfig' 'xorg-server')
install=gdm.install
url="http://www.gnome.org"
groups=()
provides=(gdm)
replaces=(gdm)
backup=('etc/gdm/custom.conf' 'etc/pam.d/gdm' 'etc/pam.d/gdm-autologin')
options=('!libtool')
source=(http://archive.ubuntu.com/ubuntu/pool/universe/g/gdm-2.20/gdm-2.20_2.20.10.orig.tar.gz
gdm
defaults.conf
gdm.pam
gdm-autologin.pam)
build() {
cd "${srcdir}/${_realname}-${pkgver}"
./configure --prefix=/usr --sysconfdir=/etc \
--libexecdir=/usr/lib/gdm \
--localstatedir=/var/lib --disable-static \
--with-xevie=yes --disable-scrollkeeper \
--enable-secureremote || return 1
sed -i -e 's|${prefix}|/usr|' config.h || return 1
make || return 1
make DESTDIR="${pkgdir}" install || return 1
#PAM, we use our own, not Redhat stuff
install -m644 "${srcdir}/gdm-autologin.pam" "${pkgdir}/etc/pam.d/gdm-autologin" || return 1
install -m644 "${srcdir}/gdm.pam" "${pkgdir}/etc/pam.d/gdm" || return 1
#init script and configuration
install -m755 -d "${pkgdir}/etc/rc.d"
install -m755 "${srcdir}/gdm" "${pkgdir}/etc/rc.d/" || return 1
install -m444 "${srcdir}/defaults.conf" "${pkgdir}/usr/share/gdm/" || return 1
rm -f ${pkgdir}/usr/share/xsessions/gnome.desktop
# fix gdmsetup
sed -i -e 's|^Exec=|Exec=gksu |' "${pkgdir}/usr/share/gdm/applications/gdmsetup.desktop" || return 1
}
md5sums=('67919a56f5b31ccbf051cd611f6a294f'
'2fdb6d6fd7fd8124b1e00621b3d238f9'
'fa61d885f0368756a7d8e7f7abdb11d9'
'2e52f326dccc833e9c135f8df8297b12'
'157f32e089a7aab50732dc122e592b35')Offline
Solid1986Snake wrote:Playmouth initializes an xserver at very early boot stage and kills that before login.
Wrong. Plymouth paints straight on the framebuffer, and is able to show fancy graphics only if KMS is enabled and working, otherwise it falls back to a text-based mode. XSplash really looks crap, they could have simply relied on Plymouth, but I bet they don't want to show a text-based bootsplash to nVidia and recent ATI cards owners.
Well, if you add a vga= parameter, that would allow graphics at least up until Fedora 11, it worked fine on my nvidia based computer.
Of course you wouldn't get KMS awesomeness, but at least it would be a nice bootup.
XSplash is (IMO) utterly useless
Offline
Doesn't playmouth fall back to text mode? I think so...
Offline
but can we make it work now? plymouth seems like eye-candy of the good kind, while xsplash is just meant to distract you from the fact that the booting process is slow:rolleyes:
Offline
Plymouth demands KMS, and not all cards (and drivers) support it now. Xsplash can't distract you from a slow boot, since boot on Arch is speedy ![]()
Offline
Plymouth demands KMS, and not all cards (and drivers) support it now. Xsplash can't distract you from a slow boot, since boot on Arch is speedy
hehe yeah I was thinking about Ubuntu I guess
humm I use Intel and KMS works like a cool summer breeze
the last time I tried plym it wasn't very stable.. guess I'll try it again
Offline
I think Scott James does a good job of explaining the difference between Plymount and Xsplash. There is a distinct different.
Offline
to build this you need to apply a pacth with this function:
--- a/src/xsplash.c 2009-10-22 21:54:02.000000000 +0300
+++ b/src/xsplash.c 2010-08-02 17:33:58.000000000 +0300
@@ -468,7 +468,7 @@
is_composited = gdk_screen_is_composited (screen);
- if (GTK_WIDGET_REALIZED (priv->window))
+ if (gtk_widget_get_realized (priv->window))
{
if (is_composited)
{found it on http://bugs.gentoo.org/show_bug.cgi?id=300889
Offline