Welcome to Linux Forums! With a comprehensive Linux Forum, information on various types of Linux software and many Linux Reviews articles, we have all the knowledge you need a click away, or accessible via our knowledgeable members.
Find the answer to your Linux question:
New to Linux Forums? Register here for free!
    Linux Forums > Your Distro > Ubuntu Help > X Display Errors

Forgot Password?
 Ubuntu Help   Discussion and help about Ubuntu, Kubuntu, Xubuntu, and all the Ubuntu family

Site Navigation
Linux Articles
Linux Forums
Linux Downloads
Linux Hosting
Free Magazines
Job Board
IRC Chat
RSS Feeds


Linux Forum Topics
Linux Forums
Your Distro
Linux Resources
GNU Linux Zone
The Community
Reply
 
Thread Tools Display Modes
Old 09-23-2006   #1 (permalink)
Just Joined!
 
phoch00's Avatar
 
Join Date: Sep 2006
Location: Dallas, TX
Posts: 32
X Display Errors

I've noticed that I get display error messages like:

Code:
Xlib: connection to ":0.0" refused by server
Xlib: No protocol specified

dpkg-preconfigure: cannot connect to X server :0.0
debconf: unable to initialize frontend: Kde
debconf: (DISPLAY problem?)
debconf: falling back to frontend: Dialog
This was during an Adept Update. I also get similar messages when starting some programs from the command line. Other than the occasional error message I don't have any other symptoms or concerns. Any thoughts on this? I would guess it started after using Automatix to install the nVidia drivers.

Here's a message from the command line when starting a gui program:
Code:
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 166
  Major opcode:  146
  Minor opcode:  3
  Resource id:  0x0
Failed to open device
phoch00 is offline  


Reply With Quote
Old 09-24-2006   #2 (permalink)
Just Joined!
 
phoch00's Avatar
 
Join Date: Sep 2006
Location: Dallas, TX
Posts: 32
Answering my own question

A little digging around with Google and I found the solution.

Apparently the default xorg.conf includes support for Wacom tablets which I'm not using and commenting out those lines in the xorg.conf resolved the situation. If anyone else has the issue, edit your xorg.conf as follows:

First, make a backup of it in case you screw up! If you don't do that your X session might not start and then you'll be at the command line to fix it. So, first:

Code:
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.bak
This way if X doesn't start you can just get your old conf file back in place by typing:

Code:
sudo mv /etc/X11/xorg.conf.bak /etc/X11/xorg.conf
Now that there is a backup, edit the following:

Code:
Section "ServerLayout"
    Identifier     "Default Layout"
    Screen         "Default Screen" 0 0
    InputDevice    "Generic Keyboard"
    InputDevice    "Configured Mouse"
#    InputDevice    "stylus" "SendCoreEvents"
#    InputDevice    "cursor" "SendCoreEvents"
#    InputDevice    "eraser" "SendCoreEvents"
EndSection
This comments out the stylus, cursor, and eraser in the ServerLayout section.

Next, comment out the following sections as follows:

Code:
# Section "InputDevice"
#
#                                                      # /dev/input/event
#                                                      # for USB
#    Identifier     "stylus"
#    Driver         "wacom"
#    Option         "Device" "/dev/wacom"          # Change to 
#    Option         "Type" "stylus"
#    Option         "ForceDevice" "ISDV4"               # Tablet PC ONLY
# EndSection

# Section "InputDevice"
#
#                                                      # /dev/input/event
#                                                      # for USB
#    Identifier     "eraser"
#    Driver         "wacom"
#    Option         "Device" "/dev/wacom"          # Change to 
#    Option         "Type" "eraser"
#    Option         "ForceDevice" "ISDV4"               # Tablet PC ONLY
# EndSection

# Section "InputDevice"
#
#                                                      # /dev/input/event
#                                                      # for USB
#    Identifier     "cursor"
#    Driver         "wacom"
#    Option         "Device" "/dev/wacom"          # Change to 
#    Option         "Type" "cursor"
#    Option         "ForceDevice" "ISDV4"               # Tablet PC ONLY
# EndSection
That does the trick for me! Restart X and you are good.
phoch00 is offline   Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 
Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are Off
Pingbacks are Off
Refbacks are Off

Free Magazines
Run Your Own Web Server Using Linux & Apache - Free 191 Page Preview
Learn about everything you'll need to build and maintain your Linux servers, and to deploy Web applications to them.
subscribe
Open Source Security Myths Dispelled
Dispel the five major myths surrounding Open Source Security and gain the tools necessary to make a truly informed decision for your IT organization
subscribe
InformationWeek
InformationWeek is the only newsweekly you'll need to stay on top of the latest developments in information technology.
subscribe



All times are GMT. The time now is 08:27 AM.






© 2000 - 2009 - All Rights Reserved - Property of  MAS Media

Content Relevant URLs by vBSEO 3.3.0 RC2