Bug#575431: Update: Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-04-10 Thread Christian Meyer
Hello again, with plymouth 0.8.1-1 (amd64, from maintainers site) the behaviour has changed: Boot process no longer hangs as described in the initial bug report. BUT it has become more strange: With console-setup active in rcS.d, plymouth exits AFTER rcS.d (not exactly during or after invocation

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Daniel Baumann
On 03/27/2010 09:59 PM, Steve Langasek wrote: (OTOH, I'm not sure we ever saw the described hang in Ubuntu - my understanding is the fonts would simply fail to be set. Perhaps this is actually caused by the version of plymouth in experimental being significantly out of date.) ftr, 0.8.0 was up

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Steve Langasek
On Sat, Mar 27, 2010 at 11:49:34AM +0200, Anton Zinoviev wrote: > On Sat, Mar 27, 2010 at 08:48:17AM +0100, Daniel Baumann wrote: > > reassigning, hopefully the initscript can be fixed/updated/changed > > in keyboard-configuration. > There is nothing wrong in the script. It does what it is suppo

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Anton Zinoviev
On Sat, Mar 27, 2010 at 10:00:49AM -0300, Otavio Salvador wrote: > > splashy and usplash uses /etc/console-tools/config.d/ for it. > > I think it ought to keep using it too. There is also /etc/kbd/config.d/. But since there is no policy regulating the effects of the scripts in these directorie

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Otavio Salvador
Hello, On Sat, Mar 27, 2010 at 8:48 AM, Anton Zinoviev wrote: > On Sat, Mar 27, 2010 at 11:35:53AM +0100, Daniel Baumann wrote: >> >> >What I am going to do about this is to provide some method that packages >> >such as plymouth, splashy and usplash can use in order to disable >> >console-setup.

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Anton Zinoviev
On Sat, Mar 27, 2010 at 11:35:53AM +0100, Daniel Baumann wrote: > > >What I am going to do about this is to provide some method that packages > >such as plymouth, splashy and usplash can use in order to disable > >console-setup. > > great, thanks. Or maybe there will be a simpler solution if you

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Daniel Baumann
On 03/27/2010 10:49 AM, Anton Zinoviev wrote: reassigning, hopefully the initscript can be fixed/updated/changed in keyboard-configuration. There is nothing wrong in the script. by 'fixed/updated/changed' i didn't mean to imply it's the fault of keyboard-configuration, just that the workarou

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Anton Zinoviev
On Sat, Mar 27, 2010 at 08:48:17AM +0100, Daniel Baumann wrote: > > reassigning, hopefully the initscript can be fixed/updated/changed > in keyboard-configuration. There is nothing wrong in the script. It does what it is supposed to do - it sets the console. Apparently loading a font on the co

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-27 Thread Daniel Baumann
reassign 575431 keyboard-configuration retitle 575431 initscript breaks plymouth thanks reassigning, hopefully the initscript can be fixed/updated/changed in keyboard-configuration. -- Address:Daniel Baumann, Burgunderstrasse 3, CH-4562 Biberist Email: daniel.baum...@panthera-

Bug#575431: plymouth: Plymouth seems to hang when console-setup is called during boot

2010-03-25 Thread Christian Meyer
Package: plymouth Version: 0.7.2-4 Severity: normal The Computer seems to boot up endlessly. The (animated) plymouth screen 'never' finishes while there is no activity on the harddisk (I waited up to 15 minutes). Pressing Esc, then Ctrl-Alt-F3, then Ctrl-Alt-F2 lets the bootsequence continue immed