Bug#522104: splashy: The bug is still there
please purge and re-installed. sudo apt-get --purge remove splashy sudo apt-get install splashy That will remove /etc/lsb-base-logging.sh and install a newer copy. On Mon, Apr 20, 2009 at 9:36 AM, Jaime Alberto Silva < jaimealbertosi...@gmail.com> wrote: > Package: splashy > Version: 0.3.13-5 > Severity: normal > > > I downgraded recently from "unstable" to "testing", however when I > received your e-mail I installed the unstable version of splashy, > splahsy-themes and libsplashy1 but the same problem is still there. > > -- System Information: > Debian Release: squeeze/sid > APT prefers testing > APT policy: (500, 'testing'), (102, 'unstable'), (101, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.26-2-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages splashy depends on: > ii initramfs-tools0.93.2tools for generating an > initramfs > ii libc6 2.9-4 GNU C Library: Shared > libraries > ii libdirectfb-1.2-0 1.2.7-2 direct frame buffer graphics - > sha > ii libgcc11:4.3.3-3 GCC support library > ii libglib2.0-0 2.20.0-2 The GLib library of C routines > ii libmagic1 5.00-1File type determination > library us > ii libsplashy10.3.13-5 Library to draw splash screen > on b > ii lsb-base 3.2-22Linux Standard Base 3.2 init > scrip > ii zlib1g 1:1.2.3.3.dfsg-13 compression library - runtime > > splashy recommends no packages. > > Versions of packages splashy suggests: > ii console-common0.7.80 basic infrastructure for text > cons > ii splashy-themes0.4.1 A complete user-space boot > splash > pn upstart(no description available) > > -- no debconf information > > > > Jaime Alberto Silva > Socio / Representante Legal > SG Automatización Ltda. > Pereira \ Risaralda \ Colombia > > > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#523187: [Pkg-utopia-maintainers] Bug#523187: Same issue for me
We updated Splashy's /etc/lsb-base-logging.sh to avoid some of these issues (especially when the package is removed.) What's the version being used? On Thu, Apr 9, 2009 at 2:26 AM, Thomas Renard wrote: >> >> Looks like a splashy related problem >> Thomas, do you also have splashy installed, ie. do you have a file >> /etc/lsb-base-logging.sh ? >> > > I have :-( > > So, then I tried your trick with renaming lsb-base-loging.sh and then the > update works with no problem. > Looks like uninstalling splashy for now... > > (do you still need the sh -x output?) > > Thomas > > > > > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#522104: do you use uswsusp?
What are you using to suspend/resume? Can you install uswsusp? Splashy and uswsusp work very well together. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#519711: splashy: hard-coded dependency on libdirectfb-1.0-0
Splashy has not been tested against newer version of libdirectfb. I know for sure that libdirectfb 1.2 makes it segfault. We will need to work on the transition anyway. I just have not have time lately to work on this. Maybe this summer. On Mon, Mar 16, 2009 at 9:53 AM, Adeodato Simó wrote: > > This is a bit complicated. We will work on it. > > I’m curious. Why is it complicated? > > Thanks, > > -- > - Are you sure we're good? > - Always. >-- Rory and Lorelai > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#519711: splashy: hard-coded dependency on libdirectfb-1.0-0
This is a bit complicated. We will work on it. On Sat, Mar 14, 2009 at 11:12 AM, Adeodato Simó wrote: > Package: splashy > Version: 0.3.13-3 > Severity: serious > > I guess it’s time to drop the hard coded dependency on libdirectfb-1.0-0. > > Thanks, > > -- > - Are you sure we're good? > - Always. >-- Rory and Lorelai > > > > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#505270: splashy: Don't use sh builtin sleep
we noted this and released 0.3.13-3 quickly. sleep 1 that way it would work with any and we will include a proper fix in a future version for Splashy. adding one second to the boot process should not even be noticeable for most users. On Mon, Jan 5, 2009 at 7:44 PM, Byron Clark wrote: > > 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'. Without the /bin/ prefix, the > sleep builtin of the busybox shell is used and it only understands > integer arguments. Adding /bin/ forces the full version of sleep in the > initramfs to be used. > > > -- System Information: > Debian Release: 5.0 > APT prefers unstable > APT policy: (500, 'unstable'), (1, 'experimental') > Architecture: amd64 (x86_64) > > Kernel: Linux 2.6.26-1-amd64 (SMP w/2 CPU cores) > Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) > Shell: /bin/sh linked to /bin/bash > > Versions of packages splashy depends on: > ii initramfs-tools0.92n tools for generating an initramfs > ii libc6 2.7-18GNU C Library: Shared libraries > ii libdirectfb-1.0-0 1.0.1-11 direct frame buffer graphics - > sha > ii libgcc11:4.3.2-1.1 GCC support library > ii libglib2.0-0 2.16.6-1 The GLib library of C routines > ii libmagic1 4.26-2File type determination library > us > ii libsplashy10.3.13-2 Library to draw splash screen on > b > ii lsb-base 3.2-20Linux Standard Base 3.2 init > scrip > ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime > > splashy recommends no packages. > > Versions of packages splashy suggests: > ii console-common0.7.80 basic infrastructure for text > cons > ii splashy-themes0.4.1 A complete user-space boot splash > pn upstart(no description available) > > -- no debconf information > > -- > Byron Clark > > > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505270: a better solution
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, Tim Richardson wrote: > 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. > > > > > > > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505270:
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 developers managed to reproduce the bug yet on their own systems? Unfortunately, I can't get a virtual machine to show this bug, only my three real machines. I'd be more than happy to test any proposed fixes before they are packaged. I'm trying to follow development via the mailing list, now I will try to learn IRC. If the Lenny deep freeze is just around the corner, I suggest using my mysterious fix (the /tmp/directfbfc fix documented earlier in this bug report) while we work out what is really happening because at least then this bug could be closed. Hey Tim, did you try purging Splashy and possible re-installing libdirectfb directly from Lenny? The problem is this: when splashy launches it tries to open a font file that's shipped with splashy itself and it's copied to initramfs under /usr/share/splashy/ themes/default/... (or whatever theme you use) the C function for splashy that loads the fonts attempts to first load this font and if it fails, it falls back to NULL which tells directfb to use whatever default font. this worked well for as long as I can remember but for some reason it broke in Lenny. so, I fixed the splashy portion of the code so it always finds the theme supplied font, and if it does not for whatever reason, it should fall back to NULL. the C portion of splashy was broken when we switched paths from /etc/splashy/themes to the new one under /usr. this is not a problem for people using splashy from initramfs (most users). only those not using initramfs and using a different partition for /usr would see an issue (and there is nothing we can do about this. the end-user would need to resolve this manually in a number of ways, like changing /etc/splashy/config.xml to point to a partition that's mounted early enough). installing Lenny on a fresh VM works well. using splashy on all my systems also work correctly. I wish somebody else could confirm that they also have this problem when using 0.3.13. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505270: patched!
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 looks like this used to work before because directfb would just ignore the font and create the font object with whatever built-in font they had. Now this makes sure we attempt to use our own font provided with the theme! We'll release this together with other bug fixes. -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#505270: splashy fails at boot: Couldn't splashy_start_splash error -10
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 themes from /usr/share/splashy/themes/. I just want to rule out that this is not the cause of your problem. Can you send a copy of your initrd (/boot/initrd.img-`uname -r`) and /etc/fstab to my email? I'd like to know more about this issue. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: splashy does or doesn't work with hibernation ??
On Sun, 2008-10-26 at 21:50 -0400, Eric Doviak wrote: > Hi Luis, Tim and Yves-Alexis, [snip] > Because I'm curious ... What change was made that corrected Splashy's > behavior? Tim changed the order at which Splashy is executed during resume to allow uswsusp to start first. We will release 0.3.11 which is a complete fix for this issue. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: [Splashy-devel] Bug#486400: Bug#486400: Splashy works with hibernation, but ...
On Mon, Oct 13, 2008 at 6:13 AM, Tim Dijkstra <[EMAIL PROTECTED]> wrote: > Luis, > > Unfortunately I haven't looked at splashy (or any other FOSS project for > that matter) for a while, but I noticed this bug is RC. The bug log shows > you've been commenting on it, do you know the status? > Hey Tim, We tried to fix this in various ways from Splashy's end but we were not successful. It looks like uswsusp starts (dfb init) the framebuffer again when resuming at boot. Meaning, /sbin/splashy starts from initramfs and later uswsusp starts libsplashy again. We weren't sure how to go about making both of them work. If you can point me in the right direction I can implement a fix. (Not sure about uswsusp as I have never seen the source code for it -- yet.) -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: Still in 0.3.11
On Wed, Aug 6, 2008 at 1:36 PM, Fabio Pugliese Ornellas <[EMAIL PROTECTED]> wrote: > Since you already know exactly what the problem is, please let me know where > it is, so I won't waste time on something already known. Please drop me an > email with it, and we keep in touch. > Ok, I'll send you the information on a private email to keep the noise from hitting this bug report. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: Still in 0.3.11
This is a very important bug; if you can get a fix for it, got for it. I have not been able to do any FOSS work these last weekends. I guess we will just miss Lenny... On Fri, Aug 1, 2008 at 2:35 PM, Fabio Pugliese Ornellas <[EMAIL PROTECTED]> wrote: > If by any means I can help, please let me know. I was about to start > debugging it today... -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: Still in 0.3.11
On Aug 1, 2008, at 11:55 AM, "Fabio Pugliese Ornellas" <[EMAIL PROTECTED] > wrote: I had a look at uswsusp suspend command (called from within initrd) and saw that it do interact with the framebuffer and makes some splash-related initialization. Would'nt that be messing up with splashy? Shouldn't its code get reviewed? Or you are sure the issue is splashy related only? Yes. We know exactly what the problem is. We are working on a solution for it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: Still in 0.3.11
On Aug 1, 2008, at 12:47 AM, "Fabio Pugliese Ornellas" <[EMAIL PROTECTED] > wrote: Hello, I have just tested the newer 0.3.11 version asn my Asus EEE PC 900 still "freezes" if I use uswsusp + splashy, the bug still exists. If I find time on the following days, I'll post here my findings on the topic. Yeah we are working on a quick release of 0.3.12 to address this and other pesky bugs. Sit tight. So far it looks like removing chvt 8 from initramfs and Splashy fixes a few of this issues. Exiting when $resume is set proved not to be the right solution. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#486400: [Splashy-devel] Bug#486400: Grave bug
This is fixed in Git and it will be released as 0.3.11 shortly. The debian package for it will follow shortly after that. On Fri, Jul 25, 2008 at 9:43 AM, Tim Richardson <[EMAIL PROTECTED]> wrote: > Laptop top users can't really use splashy because of this bug; I'm > surprised this is not an RC bug. I wouldn't want this to be in a stable > release because I'm a Debian enthusiast. > > > > > ___ > Splashy-devel mailing list > [EMAIL PROTECTED] > http://lists.alioth.debian.org/mailman/listinfo/splashy-devel > -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455872: [Splashy-devel] Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Jan 6, 2008 11:10 AM, Luca Capello <[EMAIL PROTECTED]> wrote: > clone 455872 -1 > submitter -1 Luca Capello <[EMAIL PROTECTED]> > retitle -1 should start after udev > found -1 0.3.7-1 > severity -1 important > thanks > > Hello! > > IMHO this bug was a mix of two: the one related to the libdirectfb > version and the other one related to udev. While the first one is > closed, the second one remains, thus the cloning (-1). > > BTW, I cc:ed all the people involved in the bug, but setting myself as > the new submitter. > > On Tue, 18 Dec 2007 04:47:11 +0100, Luis Mondesi wrote: > > On Dec 12, 2007 3:13 AM, Georg Wittenburg <[EMAIL PROTECTED]> wrote: > >> After upgrading to splashy 0.3.7, splashy fails to start with error code > >> -3 from splashy_start_splashy(). > >> > >> What is worse, several unrelated other modules fail to load afterwards, > >> e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This > >> effectively breaks sound and networking on my system. > > I can reproduce it (but with error code -2) booting with just "splash" > (so no fb) on my sid-amd64. Various unrelated modules are messed up, > e.g. X cannot start because /dev/agpgart doesn't exist (and manually > loading the intel-agp module doesn't change anything). > > > This looks like udev is not starting properly. > > Indeed udev has some problems with splashy, here the output I recorded > on my MiniDV: > = > Starting the hotplug event dispatcher: udevdSplashy ERROR: Connection refused > Splashy ERROR: Coudln't splashy_start_splashy(). Error -2 > > splashy[1588]: segfault at 0018 rip 2611de7774c7 rsp > 7fffce751248 error 4 > = > > > Can you move /usr/share/initramfs-tools/scripts/init-top/splashy to > > /usr/share/initramfs-tools/scripts/init-bottom/z_splashy > > > > and redo your initrd? > > > > update-initramfs -u > > > > That should allow udev to start first and it should fix your problem. > > This works only when splashy is inside the initramfs. For the other > case, you need to move the splashy rc script after udev, something like > > $ mv /etc/rcS.d/03splashy /etc/rcS.d/z_splashy > > This fixes the problem and splashy nicely starts :-D I'm guessing then that Splashy should always be used from initramfs or after udev when not from initramfs? Perhaps there is another way of doing this. Is there something we can do to work with udev? I know I did a test that splashy was started after udev in initramfs and that just didn't work as expected. I dunno outside of initramfs. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#455685: Splashy makes GDM initscript fail (and hence, leaves system on VT1)
On Dec 22, 2007 12:11 PM, Steve Fosdick <[EMAIL PROTECTED]> wrote: > I have had the same issue with gdm not starting when splashy is installed. > > I have checked line 178 of /etc/lsb-base-logging.sh but in the version > installed on my system this line is a comment so I can not see how, in my > case, that line could be causing the error. > > The failure mechanism seems to be that /etc/init.d/gdm has performed 'set > -e' so that any command that fails, even if there is no error message or the > message is surpressed by re-directing to /dev/null, will cause > /etc/init.d/gdm to stop executing at that point. With splashy installed and > its corresponding /etc/lsb-base-logging.sh the log_daemon_msg subroutine > is failing and thus aborting /etc/init.d/gdm. > > I haven't had a chance to work through all the commands splashy is running > but perhaps there are some assumptions there that don't hold true. For > example, in my case, splashy was installed because it was recommended by > uswsusp and is therefore used for the suspend/resume progress screen but I > have not yet got around to setting it up for normal startup/shutdown. > > Anyway, for now, I have been able to work around this patching /etc/lsb- > base-logging.sh as follows: > > diff -u lsb-base-logging-orig.sh lsb-base-logging.sh > --- lsb-base-logging-orig.sh2007-12-22 17:09:34.0 + > +++ lsb-base-logging.sh 2007-12-22 17:03:52.0 + > @@ -118,7 +118,7 @@ > > # Stop splashy on *dm > case $2 in > - ?dm) stop_splashy;; > + ?dm) stop_splashy || return 0 ;; > esac > } > > So even if attempting to stop splashy fails gdm still starts. > Hello Steve, Thanks for suggesting this fix. We included this in our latest script [1]. This will be released as Splashy 0.3.9. Please note that Splashy 0.3.8 included code that prevented this from happening by doing the right thing when stop_splashy is called: - only run keymap.sh if splashy prevented it from starting. do the same for console-screen.sh - only umount Splashy's steps dir if it's mounted However, it doesn't hurt to have "|| return 0" in the log_daemon_msg() call as well. Splashy 0.3.8 will be added to the debian archives soon. It has not been added yet because we are all in "holidays" mode and the whole release/bug-fix cycle has been reduced in speed ;-) If you are reading this bug and you are having problems with gdm or any other script, please just grab a copy of lsb-base-logging.sh and replace your /etc/lsb-base-logging.sh copy with this [1]. Notes: 1. http://git.debian.org/?p=splashy/splashy.git;a=blob_plain;f=scripts/lsb-base-logging.sh;hb=HEAD -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 20, 2007 2:45 AM, Georg Wittenburg <[EMAIL PROTECTED]> wrote: > Hi, > > with regard to the screen corruption I mentioned in my previous, have a > look > at the attached screenshot. > > Regards, >Georg > Yeah I've seen that myself. And in fact, the directfb devels know about this [1]. I'm trying to address that problem for 0.3.9. 0.3.8 is out and it should fix most of the current bugs. Sit tight as we are now in "holiday mode" and everybody is away from their keyboards ;-) Notes: 1. http://mail.directfb.org/pipermail/directfb-dev/2007-December/003775.html -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#455872: splashy: Fails to initialize, messes up loading other modules
If you have libdirectfb-0.9.25-x installed, can you please remove it? It seems that even though Splashy links against libdirectfb-1.0.x (from Sid), the binary tries to access the older version of the lib causing the -3 errors. Please report back ASAP as we are getting ready to do a bug fix release.
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 12, 2007 3:13 AM, Georg Wittenburg <[EMAIL PROTECTED]> wrote: > Package: splashy > Version: 0.3.7-1 > Severity: critical > Justification: breaks the whole system > > > Hi! > > After upgrading to splashy 0.3.7, splashy fails to start with error code > -3 from splashy_start_splashy(). > > What is worse, several unrelated other modules fail to load afterwards, > e.g. all sound drivers (snd_*) and the WLAN driver iwl4965. This > effectively breaks sound and networking on my system. > > I haven't seen any suspicios messages in dmesg or syslog that would > point to what exactly the problem is, but I could provide the output if > necessary. As a workaround I removed "splash" from the kernel command > line and the system works fine. > > Regards, > > Georg > This looks like udev is not starting properly. Can you move /usr/share/initramfs-tools/scripts/init-top/splashy to /usr/share/initramfs-tools/scripts/init-bottom/z_splashy and redo your initrd? update-initramfs -u That should allow udev to start first and it should fix your problem. We will do a minor (bug fix) release shortly. If you can send us the result of this test it will be greatly appreciated. Regards, -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#455685: splashy: scripting problems
On Dec 15, 2007 2:25 PM, Witold Baryluk <[EMAIL PROTECTED]> wrote:
> Package: splashy
> Followup-For: Bug #455685
>
> It also assumes that splashy is started.
>
> Error is in function log_daemon_msg in /etc/lsb-base-logging.sh
> ("pidof splashy ..." line, and call to stop_splashy in "case ...")
>
> Please fix this problem quickly, becouse it is quite hard
> to track down this script error. (And it seems like
> gdm error, when it's not).
>
> Thanks.
Will do. Thanks for the report.
--
)(-
Luis Mondesi
Maestro Debiano
- START ENCRYPTED BLOCK (Triple-ROT13) --
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner
jbeyq.
- END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#455259: stop_splashy() from /etc/lsb-base-logging.sh does not check umount's exit value
Thanks for reporting this bug. Attached is a copy of lsb-base-logging.sh that fixes this and other bugs. We will be doing a minor (bug fixes) release shortly. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- etc_lsb-base-logging.sh Description: Bourne shell script
Bug#455872: splashy: Fails to initialize, messes up loading other modules
On Dec 15, 2007 12:05 PM, Alessio Gaeta <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > I can confirm this bug, it happens on my machine too. The problem shows > itself only when the parameter "splashy" is passed to the kernel. If I > remove it, the system boots normally, but for the bug #455685 (Splashy > makes GDM initscript fail. > > Symptoms are the same: splashy fails to start with error code > - -3 from splashy_start_splashy(), no sound, no usbhid, no networking... > Hotplugging doesn't work at all, modules aren't automatically loaded and > modprobe rules aren't satisfied (i.e. I have a rule to load usbnet whith > cdc_subset, but when I plug my Linux Ipaq in the cradle the module > cdc_subset isn't loaded; if I probe the module manually the module > usbnet isn't automatically loaded. > > I noted that when starting without the parameter "splashy" i can see the > log line > > Waiting for /dev to be fully populated...done. > > but with splashy activated that line doesn't appear. So I guess it is a > udev (odd-)interaction problem (or maybe a more complicated > splashy/udev/initramfs-tool, seen problems of update-initramfs with > udev...). > > Moreover, it happens that if I reboot and temporary delete the initrd > line from GRUB (my kernel can boot without initrd, but I need it for > uswsuspend), boot fails because /dev is completely screwed up. > > Hello, Sorry for taking so long to reply (holidays are almost here!) Can you do a test for me? As root, run the following on your system: mv /usr/share/initramfs-tools/scripts/init-top/splashy /usr/share/initramfs-tools/scripts/init-bottom/z_splashy update-initramfs -u make sure that you put back "splash vga=791" to your kernel boot parameters. Note that it's not "splashy" but "splash". Also, I have attached 2 scripts to this email. /etc/lsb-base-logging.sh and /etc/console-tools/config.d/splashy. Please use this scripts to replace the ones that you have. These come straight from our Git repository (See more here http://splashy.alioth.debian.org/wiki/developers). Please report back your experience. If this is too much for you to do, then you can hold on for the next Splashy revision (which should come out pretty quickly). Regards, -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) -- console-tools_config.d_splashy Description: Binary data etc_lsb-base-logging.sh Description: Bourne shell script
Bug#455685: Splashy makes GDM initscript fail (and hence, leaves system on VT1)
On Dec 14, 2007 4:36 AM, Raphael Hertzog <[EMAIL PROTECTED]> wrote: > On Tue, 11 Dec 2007, Luis Mondesi wrote: > > If you still see this error, can you send me copies of your > /etc/init.d/gdm > > and /etc/lsb-base-logging.sh scripts? > > I also got the problem and I didn't touch to any of those files. So you > should be able to duplicate easily by installing gdm and splashy in the > same chroot/virtual machine. > > Here's the output of "sh -x /etc/init.d/gdm" when I had the problem. > Removing the package was not enough to solve the problem, I had to purge > it so it proves that the propblem comes from /etc/lsb-base-logging.sh. > [snip] > + '[' 2 -gt 1 -a 2 -lt 6 ']' > + '[' -x /etc/init.d/keymap.sh ']' > + '[' x0 '!=' x0 ']' > + /etc/init.d/keymap.sh start > + '[' -x /etc/init.d/console-screen.sh ']' > + '[' x0 '!=' x0 ']' > + '[' x0 = x0 ']' > + umount /lib/init/rw/splashy > Thank you very much for this information! I can see a few things wrong with this. Splashy lsb-base-logging.sh is assuming that gdm will be started once and stop once. And it also assumes that this happens at boot. I'll modify the script and do a quick release to fix these issues. -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#455685: Splashy makes GDM initscript fail (and hence, leaves system on VT1)
On Dec 11, 2007 12:58 AM, Diego Escalante Urrelo <[EMAIL PROTECTED]> wrote: > After updating to splashy 0.3.7, GDM broke. It didn't start anymore. A > quick visit to init 1 allowed me to see the output of GDM initscript, > that took me to the culprit: splashy. > The problem was a bad if [] in line 178 of /etc/lsb-base-loggin.sh, > which is referenced as a fix for bug #400598. > > I couldn't catch the exact message, sorry. But you might want to > double-check that line. > Hey Diego, Can you purge the old Splashy package and re-install? # first, backup /etc/splashy (hint: tar cf /etc/splashy.tar /etc/splashy) dpkg -P splashy libsplashy1 libsplashy1-dev apt-get install splashy If you still see this error, can you send me copies of your /etc/init.d/gdm and /etc/lsb-base-logging.sh scripts? You can join us in #splashy on irc.freenode.net to discuss this further. Regards, -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
Bug#453349: Information about splashy FTBFS
On Nov 28, 2007 8:10 PM, brian m. carlson <[EMAIL PROTECTED]> wrote: > __vdso_clock_gettime is a fast version of clock_gettime that lives in > the Linux VDSO (linux-vdso.so.1 on amd64), which is a dummy library that > is part of the kernel (and mapped by the kernel into every process's > address space). Thus, ld will never be able to look it up, since it > doesn't exist outside of the kernel binary. > > This bug will only manifest itself on architectures that have the VDSO, > which (TTBOMK) are i386 and amd64. > > There are two ways around this: either don't link statically, [snip] Splashy 0.3.7 won't be linked statically anymore. This version is in active development and it will be released very soon. Regards, -- )(- Luis Mondesi Maestro Debiano - START ENCRYPTED BLOCK (Triple-ROT13) -- Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq. - END ENCRYPTED BLOCK (Triple-ROT13) --
