On Wed, Jan 28, 2009 at 04:15:15PM +0200, Agathoklis D. Hatzimanikas wrote: > Hi, > > On a recent Lfs build (a copy of a middle December) I've installed > (with no problems) the latest Xorg release 7.4 by following book > instructions. > > But when I've tried to log in X, I've faced some problems: > > The first error was about that "RgbPath" wasn't not a valid keyword. > By commenting out the relevant line I was able to continue. > agreed
> The second one was about the "record" module, I did the same as before > and I was able to continue. > I don't remember having to do anything, but 'record' rings a vague bell with me. [checks...] - I've still got 'Load "record"' and I get a warning and error in the log, same as xtrap and type1 which I also stopped building at some point. > The third one was the famous error "couldn't find default font fixed", > and although I've done all the usual steps, I wasn't able to fix this, > so I just cheated and by blatantly copied the fonts from an old working > system I was able to continue. I don't know exactly the reason for this > failure, both the "font-alias" and "bdftopcf" packages was installed > properly with no error. You haven't gone for --enable-builtin-fonts in xorg-server. Admittedly, there may be problems with that on old apps, e.g. xcalc's keys for square-root and divide show gibberish instead of the expected symbols, but the '/' key works as normal -I'm trying to move to gcalctool on completed systems, but obviously I can't build that until much later. It's possible other old apps will show worse behaviour. > > The fourth is basically the reason for this email, so the solution can be > archived for reference to people with the same problem. > > > Now, when I've tried to log in X, my computer just locked. I couldn't > use the mouse, I couldn't use the keyboard to switch to virtual consoles, > so basically it left nothing else other than a hard reset (after years > without one, that was an unpleasant experience). > > I've looked to the Xorg log but I couldn't find an obvious reason for > this, so and because I wanted to be sure first (before to start > reporting) I fall back to the know good versions of Xorg to see if they > are working on the same exact system and apparently they did. > I've then tried to build Xorg without Mesa, but I've had the same hard lock. > > So, I've started to look in the Xorg lists and I've found two similar > problems within the last days. The solution was pretty easy, I just wanted > to put to the "ServerFlags" section the following line: > > Option "AllowEmptyInput" "false" > Yeah, the hardest part is trying to search for the solution from a text-mode browser ;-) I commented about this in #2642 (evdev) a little while ago, but it's probably better to record it here where google can find it. I've got a suspicion that it might only affect people using usb connections - I'm actually on a kvm switch with PS/2 connectors, but that might exercise different code than straight PS/2 connectors plugged directly to the machine. If you are using PS/2 keyboard and mouse plugged in directly, I'll drop this thought. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
