On Wed, Jan 7, 2009 at 5:08 PM, wei sun wrote:
> I have the same problem with splashy.
> However, it works after I move "/etc/rcS.d/S03splashy" to
> "/etc/rcS.d/S04splashy".
> I guess the root cause is that there is another file "/etc/rcS.d/S03udev".
> splashy has to be
> started after udev.
Spla
I have the same problem with splashy.
However, it works after I move "/etc/rcS.d/S03splashy" to
"/etc/rcS.d/S04splashy".
I guess the root cause is that there is another file "/etc/rcS.d/S03udev".
splashy has to be
started after udev.
Hope this helps!
On Tue, Jan 6, 2009 at 1:25 AM, Tim Richardson wrote:
> As indicated already, please consider this patch for the next version of
> splashy. It replaces the sleep in the script, and only holds up init for
> the time necessary (certainly less than 0.5 s and perhaps only 0.1 s)
> (attached)
This has
Hi Tim,
> I think a delay of 1 second is probably five times too long even in
> worst cases, but if I didn't make mistakes in the code, it won't matter
> because a signal will arrive quickly.
Exactly, so it wouldn't hurt to increase it.
> Slower machines don't necessarily make the race condition
I think a delay of 1 second is probably five times too long even in
worst cases, but if I didn't make mistakes in the code, it won't matter
because a signal will arrive quickly.
Slower machines don't necessarily make the race condition more likely to
occur.
The "window of error" is only the exec
> /* some machines had a race condition causing splashy failure */
> +
> /* This fixes bug 505270 */
> +}
> +
You're messing up the indentation here, presumably b
;
}
+ else
+ {
+ /* send a SIGUSR2 signal to parent process. This signal lets the parent process exit so that init can continue */
+/* stalling init until this point is necessary to avoid the race condition causing bug 505270
:
>
> Package: splashy
> Version: 0.3.13-2
> Followup-For: Bug #505270
> found 505270 0.3.13-2
> thanks
>
> The sleep for 0.5 seconds in local-premount/splashy works, but not as
> currently patched. The last line of local-premount/splashy should read
> '/bin/sleep 0.5&#x
Package: splashy
Version: 0.3.13-2
Followup-For: Bug #505270
found 505270 0.3.13-2
thanks
The sleep for 0.5 seconds in local-premount/splashy works, but not as
currently patched. The last line of local-premount/splashy should read
'/bin/sleep 0.5' instead of 'sleep 0.5'
Cool. But for now we are closing this bug and revisiting your solution
later. Waiting half a second more for booting should not be a big deal
for most people. Fabo already uploaded the package and we'll need to
ask the debian release team to let it through Lenny.
On Mon, Jan 5, 2009 at 3:47 PM, Ti
I've made a version of splashy which uses a signal to exit rather than
wait a whole second in the local-premount script. I'll test it more
thoroughly tonight my time and then send patches.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe".
Awesome!
this is needed anyway for the fadein to work correctly. I'll apply
this and repackage for Sid. Hopefully we will be accepted for Lenny.
On Jan 5, 2009, at 6:32, Tim Richardson wrote:
I did a sleep 0.5
All three machines are fixed with this.
--
To UNSUBSCRIBE, email to
I did a sleep 0.5
All three machines are fixed with this.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
By the way, if you change the script in /usr/share/initramfs-tools/...
per my last comment,
you also need to do
update-initramfs -u
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Thanks to #splashy and Mattkijs Kooijman, we have a solution.
It's not a very good solution, but it proves we know what the problem
is:
The solution is to delay the init process for one or two seconds after
splashy boot
ie change /usr/share/initramfs-tools/scripts/local-premount/splashy
and add
Neil,
hi. I'm the original reporter, although by now I think it is clear that
many people see this bug. For me, it is 100% reproducible.
I only use stock Lenny i386 kernels, and I don't have /usr on a separate
partition. I certainly use initramfs, since I'm using a stock kernel.
I reproduce this
On Sun, 04 Jan 2009 19:28:10 +0100
Daniel Scharon wrote:
> Am Sonntag, den 04.01.2009, 17:46 + schrieb Neil Williams:
> >
> > This bug appears to only affect non-standard kernels not using
> > initramfs *and* using /usr on a different partition.
> >
>
> wrong.
Well, that at least helps c
I'm running Debian Sid, with stock kernel here:
[07:44:41]jsch...@jdh129:~$ uname -r
2.6.26-1-686
/usr is not on a separate partition either:
[07:45:05]jsch...@jdh129:~$ cat /etc/fstab
/dev/sda5 /boot ext2 defaults0 1
/dev/sda3 / reiserfsdefaults,relatime
Am Sonntag, den 04.01.2009, 17:46 + schrieb Neil Williams:
> Package: splashy
> tag 505270 + unreproducible
> tag 505270 + moreinfo
> thanks
>
> This bug appears to only affect non-standard kernels not using
> initramfs *and* using /usr on a different partition.
>
wrong.
My configuration:
Package: splashy
tag 505270 + unreproducible
tag 505270 + moreinfo
thanks
This bug appears to only affect non-standard kernels not using
initramfs *and* using /usr on a different partition.
I'm looking for confirmation that anyone can reproduce this bug with a
Debian stock kernel package (specify
I changed splashy_video.c to enable directFB debug and info messages to
console.
I see an error when init_font tries video.dfb->CreateFont
The first attempt at this always fails. It's the second attempt which
seems interesting.
the message from directFB is
(!) Direct/Interface Could not open int
Am Freitag, den 02.01.2009, 15:10 +1300 schrieb Jochen:
> I can confirm this bug on 2 of my systems. However for me
> the /etc/directfbrc does not fix the error.
>
> Cheers
> Jochen
>
>
>
>
I can confirm this bug as well, even with 0.3.13-1 the error persists.
The /etc/directfbrc hack doesn't
I forgot to mention in my previous post that splashy has always worked
upon shutdown, it's rebooting that's been the problem,
I tried moving /usr/share/splashy/themes to /etc/splashy, but it didn't
help much.
After changing themes splashy stopped working again, even with the
/etc/direcfbrc
Hi,
I still got problems with splashy 0.3.13-1 .
Running Debian Lenny:
j...@jupiter:~$ dpkg -l | grep splash
ii libsplashy1 0.3.13-1
Library to draw splash screen on boot, shutd
ii splashy 0.3.13-1A
complete user-spac
On Dec 30, 2008, at 4:42 AM, Tim Richardson wrote:
v 03.13 shows the same behaviour as 0.3.12. That is, splashy doesn't
work with the same error messages.
Also, the /tmp/directfbrc hack fixes it just the same.
I wonder why there was so much confidence that a fix was found. Have
the
develop
I can confirm this bug on 2 of my systems. However for me
the /etc/directfbrc does not fix the error.
Cheers
Jochen
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
v 03.13 shows the same behaviour as 0.3.12. That is, splashy doesn't
work with the same error messages.
Also, the /tmp/directfbrc hack fixes it just the same.
I wonder why there was so much confidence that a fix was found. Have the
developers managed to reproduce the bug yet on their own systems
Package: splashy
Version: 0.3.13-1
Followup-For: Bug #505270
I'm seeing this same bug with a freshly installed 0.3.13-1.
-- System Information:
Debian Release: 5.0
APT prefers unstable
APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64
tag 505270 patch
thanks
Luis Mondesi (23/12/2008):
> Now this makes sure we attempt to use our own font provided with the
> theme!
I didn't test the patch, but I'm tagging this bugreport according to
your subject and your claim that it fixes this bug. It could be tagged
“pending” too, I guess, b
I believe this is the end for this bug:
http://git.debian.org/?p=splashy/splashy.git;a=blobdiff;f=src/splashy_video.c;h=8de345edf07a889b101452a22c86d36e098a3c8e;hp=a1c0b07bfac4845870302c74aa59965b562b0570;hb=0d9697281009eb677c6fb75e192fb70a7a5188ba;hpb=43bd24eb8b7c6389f4fb7cd2904973b1ef81f938
It
Package: splashy
Version: 0.3.12-1
Followup-For: Bug #505270
Since the last kernel update (2.6.26-12) and initramfs-tools update (0.92m),
splashy doesn't work anymore (at boot and shutdown) => connection refused to
the server.
-- System Information:
Debian Release: 5.0
APT prefers
I forgot:
I needed /etc/directfbrc and early starting of splashy does not work
with the hard copied /usr/share/splashy/themes -> /etc/splashy/themes
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.
Hi,
I have /usr in it's own partition. So it would not work if splashy wants
to use files in /usr if it is not there at boot time.
I hard copied /usr/share/splashy/themes to /etc/splashy and edited the
themes path in /etc/splashy/config.xml back to /etc/splashy/themes and
it works again.
--
> re debian bug 505270
> does this help you:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=505270#27
>
> (my file /etc/directfbrc is attached)
>
> and after creating the /etc/directfbrc file, try this:
>
> sudo update-initramfs -u
>
Hi,
I confirm the prob
Package: splashy
Version: 0.3.12-1
Followup-For: Bug #505270
I've this bug too. But for me splashy has worked sometime and now it
doesn't worked anymore (error -10 during the boot).
My config used only one partition.
-- System Information:
Debian Release: lenny/sid
APT prefers tes
Package: splashy
Version: 0.3.12-1
Followup-For: Bug #505270
I precise that the error appears only during a cold boot. It works fine
during a reboot.
-- System Information:
Debian Release: lenny/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Ker
Thanks for sending me your initrd. I'm getting closer to fixing this
bug. It looks like the changes in the path for themes and default
theme has something to do with this and other crashes. We are now
using /usr to store themes and this is a separate partition for most
people. Also, the dir
Also, /boot/grub/menu.lst extract
## ## End Default Options ##
title Debian GNU/Linux, kernel 2.6.26-1-686
root(hd0,0)
kernel /boot/vmlinuz-2.6.26-1-686 root=/dev/hda1 ro quiet vga=791
splash
initrd /boot/initrd.img-2.6.26-1-686
--
To UNSUBSCRIBE, ema
Luis,
I sent the 4MB initrd image to your gmail account via yousentit
It's available for 7 days.
regards
Tim
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
> Tim,
>
> Is it possible that your problem is related to /etc/splashy/config.xml ?
>
> Try copying this file to /root/config.xml and purging Splashy 0.3.10
> (dpkg --purge splashy) (from Lenny) and installing the Sid version
> (0.3.12), then copy your config.xml back to /etc/splashy.
>
>
Lui
Tim,
Is it possible that your problem is related to /etc/splashy/config.xml ?
Try copying this file to /root/config.xml and purging Splashy 0.3.10
(dpkg --purge splashy) (from Lenny) and installing the Sid version
(0.3.12), then copy your config.xml back to /etc/splashy.
The new file calls the t
Installing splashy 0.3.10 works even when I leave all other packages at
the sid version, including libsplashy
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
hi,
As far as my knowledge goes i think u have not configured the
framebuffer. first compile the kernel and get the framebuffers support
and everything works fine. what flavor of linux do u go with.
bye
2008/11/28 Filippo Giunchedi <[EMAIL PROTECTED]>
> On Tue, Nov 11, 2008 at 09:27:19PM
> > Connection refused.
> > Couldn't splashy_start_splash. Error -10
>
> Reading the code a -10 error seems to indicate a problem with fonts. Are you
> using the default theme/font?
On all machines, only the default theme is used. The package with extra
themes is not installed.
>
> After booti
On Tue, Nov 11, 2008 at 09:27:19PM +1100, Tim Richardson wrote:
> Package: splashy
> Version: 0.3.12-1
> Severity: important
>
> With the upgrade to 0.3.12-1 I have a new problem.
> It occurs on two Intel-based laptops, but not on a non-intel desktop nor in
> virtual machines.
>
> The error occu
In the process of trying to debug this, I discovered that I can make it
boot properly if I create the file
/etc/directfbrc
and include this one line in the file
log-file=/tmp/directfb.log
I had no directfbrc file on my system.
An empty file doesn't help.
My attempt to make the log file was to
Purge and re-install unfortunately did not help me.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I was wrong when I said this bug doesn't occur on my non-intel desktop.
It uses a local repository and was slower to upgrade to the 0.3.12-1
Since splashy fails to start on all three machines on which I run sid, I
I will mark this as grave.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wit
Package: splashy
Version: 0.3.12-1
Followup-For: Bug #505270
I saw the same issue after the upgrade to 0.3.12-1. Purging the package
and reinstalling removes the error, but splashy no longer starts early
enough in the initramfs for me to enter the password for my encrypted
root partition
Package: splashy
Version: 0.3.12-1
Severity: important
With the upgrade to 0.3.12-1 I have a new problem.
It occurs on two Intel-based laptops, but not on a non-intel desktop nor in
virtual machines.
The error occurs at boot.
Connection refused.
Couldn't splashy_start_splash. Error -10
-- Sys
50 matches
Mail list logo
