Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
From what I can see there:
Your running as root; did you su to root? If so, that will not work as the screen is owned by the user that logged in.
So either login in GUI as root (not always permitted) or use xhost +; I saw that command somewhere related to a similar question; never used it however so not sure how to use it.
Unless you've given blanket permission to a host (with xhost +hostname),
the X server refuses access to processes that can't provide the secret
credentials. For a normal user, the name of the file with the secret
credentials is held in the XAUTHORITY environment variable, which usually
looks something like this:
In Fedora 7, the XAUTHORITY environment variable is not normally
preserved by sudo(1), so commands run under sudo don't know where to find the credentials. You can use visudo(8) to edit /etc/sudoers to pass the XAUTHORITY environment variable to the commands it runs. Look for the
Defaults env_keep = .......
Normally only the original user and root can read the $XAUTHORITY file; if
you're trying to do so from some other account, or the file is on a
root_squash NFS file system, you'll have to take other measure to allow
access to the file contents.