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 libdirect
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 s
Processing commands for [EMAIL PROTECTED]:
> clone 455872 -1
Bug#455872: splashy: Fails to initialize, messes up loading other modules
Bug 455872 cloned as bug 459447.
> submitter -1 Luca Capello <[EMAIL PROTECTED]>
Bug#459447: splashy: Fails to initialize, messes up loading o
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the delay, I forgot to subscribe the bug...
> 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
udev is still scre
On Tuesday 18 December 2007 16:31:09 Luis Mondesi wrote:
> 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.
>
> P
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 releas
On Tuesday 18 December 2007 04:47:11 Luis Mondesi wrote:
> 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, splas
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().
>
> Wha
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 no
-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 a
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 driver
12 matches
Mail list logo