I didn't respond to the initial message in this thread because the issue
that is being discussed here confused me.
One usually needs "xhost+" (or one of its more secure cousins - this
"solution" is really just for a quick test, not a long-term answer) only
when running X clients from a remote host -- they need explicit permission
to write to the X display on your workstation.
If the app that is causing the problem is running on the same workstation as
the X server, and if you are starting it in an xterm ... well, have you
possibly su'd to a diferent userid in the xterm? (Not root; some other
userid.) That *might* generate a permissions problem of the sort you described.
At 12:09 PM 2/11/00 +0530, [EMAIL PROTECTED] wrote:
>well, the error message that u got comes when the client is not able to
>connect to the server... "xhost+" command allows any client to connect to
>the xserver. so, it can solve the problem, though my knowledge isnt good
>enough to tell u why it is occuring inthe first place... maybe other
>listers can tell u...
>----------
>> From: Karthik Vishwanath <[EMAIL PROTECTED]>
>> To: R.S.Ramakrishnan <[EMAIL PROTECTED]>
>> Cc: [EMAIL PROTECTED]
>> Subject: Re: Problems with X
>> Date: Friday, February 11, 2000 11:33 AM
>>
>> You mean that I am to xhost my own machine??! I can start X and run apps.
[rest and html duplicate deleted]
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
