also sprach Petter Reinholdtsen <[EMAIL PROTECTED]> [2008.02.01.1717 +1100]:
> First of all, how did xdm end up that early in the boot sequence?
I put it there. I have had it there for *years*.
> Do you have usplash or splashy installed and activated?
Never! :)
> Moving xdm a bit later in the
also sprach Petter Reinholdtsen <[EMAIL PROTECTED]> [2008.02.01.1728 +1100]:
> Can you test this patch?
That seems to solve it.
--
.''`. martin f. krafft <[EMAIL PROTECTED]>
: :' : proud Debian developer, author, administrator, and user
`. `'` http://people.debian.org/~madduck - http://de
[Petter Reinholdtsen]
> This is a problem with sysv-rc, all right. It should not break down
> even if there are no progress bar steps to count because xdm (or kdm
> and gdm) is the first entry in the runlevel. Will have a look at
> the logic to fix it.
Can you test this patch?
Index: debian/sys
[Martin F Krafft]
> I start xdm first:
>
> lapse:~> ls /etc/rc2.d/S* | head -1
> /etc/rc2.d/S01xdm
First of all, how did xdm end up that early in the boot sequence? Do
you have usplash or splashy installed and activated? I know usplash
need to stop before xdm, so it is very surprising to see th
Package: sysv-rc
Version: 2.86.ds1-52
Severity: grave
I start xdm first:
lapse:~> ls /etc/rc2.d/S* | head -1
/etc/rc2.d/S01xdm
This causes the num_steps loop on line 257 of /etc/init.d/rc to
break during the first iteration, which in turn causes a division by
zero in the startup_process() functi
5 matches
Mail list logo
