[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#575431: marked as done (initscript breaks plymouth)

Your message dated Mon, 30 Aug 2010 06:34:16 +0200
with message-id <20100830043416.GQ3336@mykerinos.kheops.frmug.org>
and subject line Re: Bug#575431: Please close 575431
has caused the Debian Bug report #575431,
regarding initscript breaks plymouth
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
575431: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=575431
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
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 immediately (without plymouth).

I found that 'S21console-setup' in /etc/rcS.d (from packet 'keyboard-
configuration') caused the problem. When renaming it to 'K21console-setup' boot
process continues normally.
I saw that console-setup processes 'readlink /proc/self/fd/2' and think that this
causes the problem. Maybe the bug belongs to packet 'keyboard-configuration'.
I also saw Debian bugs belonging to splashy (a different boot splash program)
related to console-setup which had been fixed in splashy.

Christian Meyer


-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages plymouth depends on:
ii  initramfs-tools         0.93.4           tools for generating an initramfs
ii  libatk1.0-0             1.28.0-1         The ATK accessibility toolkit
ii  libc6                   2.10.2-6         Embedded GNU C Library: Shared lib
ii  libcairo2               1.8.10-2         The Cairo 2D vector graphics libra
ii  libfontconfig1          2.8.0-2          generic font configuration library
ii  libfreetype6            2.3.11-1         FreeType 2 font engine, shared lib
ii  libglib2.0-0            2.22.4-1         The GLib library of C routines
ii  libgtk2.0-0             2.18.6-1         The GTK+ graphical user interface 
ii  libpango1.0-0           1.26.2-1         Layout and rendering of internatio
ii  libpng12-0              1.2.43-1         PNG library - runtime
ii  plymouth-plugins-all    0.7.2-4          Graphical Boot Animation and Logge
ii  plymouth-plugins-fade-i 0.7.2-4          Graphical Boot Animation and Logge
ii  plymouth-plugins-label  0.7.2-4          Graphical Boot Animation and Logge
ii  plymouth-plugins-solar  0.7.2-4          Graphical Boot Animation and Logge
ii  plymouth-plugins-spinfi 0.7.2-4          Graphical Boot Animation and Logge
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

plymouth recommends no packages.

Versions of packages plymouth suggests:
ii  gdm                           2.20.10-1  GNOME Display Manager

-- no debconf information

--- End Message ---
--- Begin Message --- 
Quoting Christian Meyer (c2h5oh@web.de):
> Hello again,
> 
> I can not remember what happend exactly but I can't reproduce 575431 any
> more. Plymouth changed its 'INIT INFO' headers to properly support
> dependency based boot, keyboard-configuration is a newer version (1.55),
> maybe that is the cause.
> I still start console-setup in rcS.d but everything is fine.
> 
> Please feel free to close 575431.


Doing so with this mail. You can actually do it by using the same
method: this is a perfectly accepted action.

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: