Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled

2008-06-21 Thread Marc Haber
On Sat, Mar 01, 2008 at 09:22:22AM -0500, Luis Mondesi wrote: ok, those two logs look perfect. Not a single Splashy related string or executing in them. can you try to edit /etc/default/splashy and change CHVT_TTY to 7 ? On my system with splashy 0.3.10-2, it works even with CHVT_TTY=auto.

Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled

2008-03-03 Thread Michal Sojka
On Saturday 01 of March 2008 15:22:22 you wrote: ok, those two logs look perfect. Not a single Splashy related string or executing in them. can you try to edit /etc/default/splashy and change CHVT_TTY to 7 ? Great, this helped. Now, kdm starts properly. Thanks Michal -- To UNSUBSCRIBE,

Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled

2008-03-01 Thread Luis Mondesi
ok, those two logs look perfect. Not a single Splashy related string or executing in them. can you try to edit /etc/default/splashy and change CHVT_TTY to 7 ? This will tell Splashy that when it's finished booting, it should chvt to tty7 where X should be. Splashy uses tty8 and stays in tty8

Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled

2008-02-29 Thread Michal Sojka
On Wednesday 27 of February 2008 04:04:32 Luis Mondesi wrote: Can you change the first line of /etc/init.d/kdm and send us the output? The line should read: !#/bin/sh -x The output is in attachment. Please note that a new version of Splashy was released and /etc/lsb-base-logging.sh

Bug#465729: [Splashy-devel] Bug#465729: KDM doesn'd display login screen when splashy is enabled

2008-02-26 Thread Luis Mondesi
Can you change the first line of /etc/init.d/kdm and send us the output? The line should read: !#/bin/sh -x We need the output of: /etc/init.d/kdm stop /etc/init.d/kdm start Please note that a new version of Splashy was released and /etc/lsb-base-logging.sh included here will address this