Hello. My reply follows: Mike On Jul 5, 2004, at 1:17 PM, peter Nikolic wrote:
Hello.
From a remote location, via SSH without an X Window session, I used the text version of yast from a shell to update one of our SuSE boxes to the new -95 kernel. Upon a return to office today I noticed that the updated SuSE box no longer:
*boots to an XWindow login screen (we use KDE 3.2(1?)/whatever KDE rev is included in the SuSE 9.1 distribution) *provides a method for multiuser login from the KDE Desktop
In addition, Konqueror as a viewer for the file system has a heck of a time opening the root directory.
The necessary KDE SuSE files are properly installed in the system.
However, I cannot X over to the system. I just tried to load konqueror and received the following error message:
Xlib: extension "XInputExtension" missing on display "localhost:10.0". Failed to get list of devices
Has anyone hit these problems? I would appreciate some insight.
Thanks
Mike
On Monday 05 Jul 2004 17:22, Mike Blonder wrote: there is a patch for KDE also available via YOU install that and you will find all is OK
For the record, The KDE update(s) are not described as patches for the -95 kernel. They are described as Security Patches. There is also a note that comes up before the user loads any of the kernel patches. This note directs the user to reboot the system immediately after installing the kernel patch(es) so that additional updates can be effected, presumably to the kernel; however, despite rebooting several times and reloading the patches several times the system neither: *returned to YaST2 to finish any updating of anything *nor booted to an X Login screen *nor permitted multiuser login after loading X I solved the problem by loading XDM with runlevel 5 functionality with the Runlevel Editor (set to Expert Mode) within YaST2. It is worth noting that the first several attempts to load XDM failed. The failures were particularly vexing as the system simply hung and never returned to a known state. I had to kill processes to get the machine back. The solution was to load XDM at the shell prompt at the initial login subsequent to a reboot of the system but before <startx> or <startkde>. Once X came up, a return to YaST2 Runlevel Editor indicated that XDM was NOT running. A refresh revealed that KDM was missing. I loaded KDM from Konsole, could then enable XDM from the Runlevel Editor. I then rebooted the system which came back up to an KDE login screen :) I hope that this may help someone else facing this type of problem. Mike
if not better than it was prior to the kernel update not shure what the tie up is but ther we go no doubt there will be flamers out there but what the hell IT WORKS ..
-- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan PGN
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com