Hi Lucas Moulin,
> I've upgraded my system yesterday, and I've seen the problem you're
> talking about. Actually, I don't see any boot messages after "Setting up
> ICE socket...", but I see wdm starting, and I got the login prompt right
> after. That makes me think this is bootlogd related.
It is
In article <[EMAIL PROTECTED]>,
Adam Warner <[EMAIL PROTECTED]> wrote:
>Since upgrading to the latest unstable I have discovered that after my
>startup reaches "Setting up X socket server directory ..." that I get no
>further output at the terminal. I have confirmed this on two different
>computer
On mar, jui 22 09:17
Adam Warner <[EMAIL PROTECTED]> wrote :
[...]
> This could explain how you were still able to see the login. I suspect if
> you look harder at your terminal output you will see some of it is
> missing. You could be fortunate that a kernel message restarted the
> terminal out
On Tue, Jul 22, 2003 at 07:17:50PM +1200, Adam Warner wrote:
> Hi Geordie Birch,
>
> > FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc
> > installed and am not having any problems re. terminal output.
>
> Upon standard bootup into a terminal it appears that output ceases before
On Tue, Jul 22, 2003 at 06:45:26PM +1200, Adam Warner wrote:
> Hi Geordie Birch,
>
> > On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote:
> >> I wrote:
> >>
> >> I have confirmed that downgrading to initscripts_2.85-4.1_all.deb
> >> sysv-rc_2.85-4.1_all.deb and sysvinit_2.85-4.1_i386.d
Hi Geordie Birch,
> FWIW, I have version 2.85-5 of initscripts, sysvinit, and sysv-rc
> installed and am not having any problems re. terminal output.
Upon standard bootup into a terminal it appears that output ceases before
the INIT: Entering Runlevel : 2 message but will start up again if the
ke
Hi Geordie Birch,
>> > The bug is most likely caused by initscripts, sysvinit or sysv-rc. If
>> > you have upgraded you may wish to downgrade/wait for a fix before
>> > rebooting, especially if your computer doesn't automatically boot into
>> > X.
>>
>> I have confirmed that downgrading to initsc
Hi Geordie Birch,
> On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote:
>> I wrote:
>>
>> > The bug is most likely caused by initscripts, sysvinit or sysv-rc. If
>> > you have upgraded you may wish to downgrade/wait for a fix before
>> > rebooting, especially if your computer doesn't aut
On Tue, Jul 22, 2003 at 06:14:01PM +1200, Adam Warner wrote:
> I wrote:
>
> > The bug is most likely caused by initscripts, sysvinit or sysv-rc. If
> > you have upgraded you may wish to downgrade/wait for a fix before
> > rebooting, especially if your computer doesn't automatically boot into
> > X
I wrote:
> The bug is most likely caused by initscripts, sysvinit or sysv-rc. If
> you have upgraded you may wish to downgrade/wait for a fix before
> rebooting, especially if your computer doesn't automatically boot into
> X.
I have confirmed that downgrading to initscripts_2.85-4.1_all.deb
sys
Hi all,
Since upgrading to the latest unstable I have discovered that after my
startup reaches "Setting up X socket server directory ..." that I get no
further output at the terminal. I have confirmed this on two different
computers.
Neither the computers nor keyboards are locked up. I am able to
11 matches
Mail list logo
