apt-get dist-upgrade, and X issues

[Leonard]

Stan please don't copy me.  I get the list mail and don't need an extra 
copy.
Perhaps review the ubuntu code of conduct.

stan wrote:
> On Sat, Dec 05, 2009 at 10:46:08AM -0800, Leonard Chatagnier wrote:
>    
>> --- On Sat, 12/5/09, stan<stanb at panix.com>  wrote:
>>
>>      
>>> From: stan<stanb at panix.com>
>>> Subject: apt-get dist-upgrade, and X issues
>>> To: "Ubuntu Linux List"<ubuntu-users at lists.ubuntu.com>
>>> Date: Saturday, December 5, 2009, 12:21 PM
>>> I just did an apt-get dist-upgrade on
>>> a 9.10 box, and when I rebooted. I
>>> get a message about running in low-res mode. It says
>>> "(EE)XKB: no
>>> components provided for virtual cire keyboard.
>>>
>>> This machine has a Nvidia graphics card, and the Xorg.0.log
>>> file seems to
>>> indicate that the nvidia module was laoded corectly:
>>>
>>> This seems to e the root cause of the problem:
>>>
>>> (EE) XKB: No components provided for device Virtual core
>>> keyboard
>>> (WW) Couldn't load XKB keymap, falling back to pre-XKB
>>> keymap
>>> [config/dbus] couldn't take over org.x.config:
>>> org.freedesktop.DBus.Error.Disconnected (Connection was
>>> disconnected before
>>> a reply was received)
>>> [config/hal] couldn't add match rule:
>>> org.freedesktop.DBus.Error.Disconnected (Connection is
>>> closed)
>>> [config/hal] cannot detect a HAL startup.
>>>
>>> What can I do to fix this?
>>>
>>>        
>> Welcome to the club and I don't know know a permanent fix as I've been suffering from a low res issue for a few weeks now on my 64 bit Karmic with kubuntu-desktop.  Do you have an /etc/X11/xorg.conf file? If so, copy and pasted it to your reply.
>>      
> # xorg.conf (xorg X Window System server configuration file)
> #
> # This file was generated by dexconf, the Debian X Configuration tool, using
> # values from the debconf database.
> #
>    
This above seem to indicate that you upgraded from an earlier version of 
Ubuntu and I assumed
you did a dist-upgrade from an already installed Karmic.  Exactly what 
did you do to upgrade
to Karmic?
> # Edit this file with caution, and see the xorg.conf manual page.
> # (Type "man xorg.conf" at the shell prompt.)
> #
> # This file is automatically updated on xserver-xorg package upgrades *only*
> # if it has not been modified since the last upgrade of the xserver-xorg
> # package.
> #
> # If you have edited this file but would like it to be automatically updated
> # again, run the following command:
> #   sudo dpkg-reconfigure -phigh xserver-xorg
>    
I hAVEN'T SEEN THIS ON MY kARMIC FRESH INSTALL; iT'S FROM AN EARLIER VERSION

> Section "Files"
> EndSection
>
> # commented out by update-manager, HAL is now used
> #Section "InputDevice"
> #	Identifier	"Generic Keyboard"
> #	Driver		"kbd"
> #	Option		"CoreKeyboard"
> #	Option		"XkbRules"	"xorg"
> #	Option		"XkbModel"	"pc105"
> #	Option		"XkbLayout"	"us"
> #EndSection
>
> # commented out by update-manager, HAL is now used
> #Section "InputDevice"
> #	Identifier	"Configured Mouse"
> #	Driver		"mouse"
> #	Option		"CorePointer"
> #	Option		"Device"	"/dev/input/mice"
> #	Option		"Protocol"	"ImPS/2"
> #	Option		"ZAxisMapping"	"4 5"
> #	Option		"Emulate3Buttons"	"true"
> #EndSection
>
> # commented out by update-manager, HAL is now used
> #Section "InputDevice"
> #	Driver		"wacom"
> #	Identifier	"stylus"
> #	Option		"Device"	"/dev/input/wacom"
> #	Option		"Type"	"stylus"
> #	Option		"ForceDevice"	"ISDV4"# Tablet PC ONLY
> #EndSection
>
> # commented out by update-manager, HAL is now used
> #Section "InputDevice"
> #	Driver		"wacom"
> #	Identifier	"eraser"
> #	Option		"Device"	"/dev/input/wacom"
> #	Option		"Type"	"eraser"
> #	Option		"ForceDevice"	"ISDV4"# Tablet PC ONLY
> #EndSection
>
> # commented out by update-manager, HAL is now used
> #Section "InputDevice"
> #	Driver		"wacom"
> #	Identifier	"cursor"
> #	Option		"Device"	"/dev/input/wacom"
> #	Option		"Type"	"cursor"
> #	Option		"ForceDevice"	"ISDV4"# Tablet PC ONLY
> #EndSection
>
> Section "Device"
> 	Identifier	"nVidia Corporation NV34 [GeForce FX 5200]"
> 	Driver		"nvidia"
> 	Busid		"PCI:1:0:0"
> 	Option		"AddARGBVisuals"	"True"
> 	Option		"AddARGBGLXVisuals"	"True"
> 	Option		"NoLogo"	"True"
> EndSection
>
> Section "Monitor"
> 	Identifier	"Generic Monitor"
> 	Option		"DPMS"
> 	Horizsync	30-70
> 	Vertrefresh	50-160
> EndSection
>
> Section "Screen"
> 	Identifier	"Default Screen"
> 	Device		"nVidia Corporation NV34 [GeForce FX 5200]"
> 	Monitor		"Generic Monitor"
> 	Defaultdepth	24
> EndSection
>
> Section "ServerLayout"
> 	Identifier	"Default Layout"
>    screen "Default Screen"
> # commented out by update-manager, HAL is now used
> #	Inputdevice	"Generic Keyboard"
> # commented out by update-manager, HAL is now used
> #	Inputdevice	"Configured Mouse"
> 	
> 	# Uncomment if you have a wacom tablet
> 	#	InputDevice     "stylus"	"SendCoreEvents"
> 	#	InputDevice     "cursor"	"SendCoreEvents"
> 	#	InputDevice     "eraser"	"SendCoreEvents"
> EndSection
> Section "Module"
> 	Load		"glx"
> EndSection
>
>    
>> After you close out the startup low res error message, did you try any of the suggestions to fix or read the log file, etc?  What did the X logs say?
>>      
> Yes.
>    

So, what did /var/log/Xorg.0.log say. That's the important thing.  
Especially anything about xkb.

>> If you can't get into X windows from the command tty using startx, you might try:
>>      
> I think the relevant part of it was in the original post. If needed I can
> send the whole thing.
>    
I thought I replied to your original post as I saw no replies on it.  If 
you do have an original post please send it to me
directly as the list should already have it.
>    
>> sudo restart dbus
>>      
> This works.
>
>    
>> sudo restart hal
>>      
> This fails:
>
> root at boo-boo:/etc/X11# restart hal
> restart: Unknown instance:
>    
This could be an issue with hal as I didn't have it when I ran it.  BTW, 
Ubuntu recommends that you use sudo instead
of a root terminal.  A root terminal can cause you untold misery if not 
used correctly.
>
>    
>> sudo /etc/init.d/gdm(or kdm, whichever you use) restart(all one line)
>>      
> Well this gets interesting:
>
> root at boo-boo:/etc/init.d# ./kdm start
>    
Interesting, I've never had any luck without putting the entire path for 
/etc/ionit.d in the
command line.  Maybe it's the ./ before the kdm that does it.
> Rather than invoking init scripts through /etc/init.d, use the service(8)
> utility, e.g. service kdm start
>
> Since the script you are attempting to invoke has been converted to an
> Upstart job, you may also use the start(8) utility, e.g. start kdm
>
>
> Having foudn this, I was able to do "stop kdm" followed by "start kdm" as
> root. This got the graphical login up, but neither the mouse, nor the
> kayboard work, at this point.
>    
What does the xorg.log.0 say about the mouse and keyboard.  I think you 
have a hal issue
but the xorg log info is needed including anything about hal.

Leonard
lenc5570 at sbcglobal.net
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lenc5570.vcf
Type: text/x-vcard
Size: 95 bytes
Desc: not available
URL: <https://lists.ubuntu.com/archives/ubuntu-users/attachments/20091205/8e79ba8d/attachment.vcf>