[UPDATE] Re: Update this morning killed local login.
Ok, I reconfigured my keyboard as suggested by a couple of people, and that
fixed the login problem, but X was still failing to load on boot. On checking
the /init.d/kdm file I noticed that it was failing because it was looking for a
command parse-xf86config which was apparently removed when the new
version of Xfree was installed with this mornings update. I commented out
the offending lines in the kdm file and now the system boots and runs X as
expected, however this is only a stop gap method. Looks like it will be up
to the KDE developers to fix this one...
Regards,
And many thanks to all those that helped,
Todd
On Thu, 02 Mar 2000, kmself@ix.netcom.com wrote:
> On Thu, Mar 02, 2000 at 06:08:01PM +0100, Grendel wrote:
> > ** On Mar 02, Todd Suess scribbled:
> > >
> > > Greets ppl,
> > >
> > > I did an apt-get dist-upgrade this morning, and after that I can no longer
> > > log in to the console. I had just rebooted after the update, and was watching
> > > the kernel boot messages, when I saw something strange pop up. It was similar
> > > to the following (going from memory)
> > >
> > > Checking for valid XFree86 configuration file.....unable to check!
> > > Not starting KDM Windows Manager
> > >
> > > I then got a normal non X login console screen, but no matter what
> > I got that several times as well. It turned out that the keyboard was
> > initialized in a way that some keys (apparently at random) were swapped -
> > e.g. q/a, y/z. At first I thought the problem was that I selected a Polish
> > keyboard (Poland has two keyboard layouts - one "official" and practically
> > not used :), and the other one "programmers". The official one uses the
> > qwertz layout while the other the standard US one), but the keys were
> > swapped each time differently. It was enough for me to login remotely, su to
> > root and reinitialize the keyboard. To see whether it is your problem - just
> > type the password as a login name and see whether all characters are
> > correct. I failed to find where the problem lied since the keyboard layout
> > initialized by console-tools worked OK when the keyboard was reinitialized.
>
> I once had my usual "qwerty" keymap replaced with "azerty" following an
> update. That took a while to diagnose.... <g>
>
> --
> Karsten M. Self (kmself@ix.netcom.com)
> What part of "Gestalt" don't you understand?
>
> Scope out Scoop: http://scoop.kuro5hin.org/
> Nothin' rusty about Kuro5hin: http://www.kuro5hin.org/
>
>
> --
> Unsubscribe? mail -s unsubscribe debian-user-request@lists.debian.org < /dev/null
--
-----BEGIN GEEK CODE BLOCK-----
Version: 3.12
GAT d- s:++ a C++++ UL++++ P+ L++ E---- W++ N++ o-- K- w
O- M-- V-- PS+ PE Y++ PGP 5++ X++ R* tv+ b+ DI++ D++
G e h--- r+++ y+++
------END GEEK CODE BLOCK------
Reply to: