John Pettigrew
In a previous message, expatriate
wrote: When I [snip] become root, seem that the superuser cannot find the same program, and if I type all the path /opt/.../gedit by example refuse to find the X display. Any hint to set the su to "work fine" as my user?
Type "echo $PATH" in each environment to see what they are.
I have a similar problem - I can run apps OK from su, not using sux or gnomesu. This is a pain.
Which file do I need to alter to get the paths right for sux/gnomesu (given that su is already OK)?
TiA
John --
John, you say that "su is already OK", do I am not sure what your problem is, but when i change to "root", i usually do "sux -" which using expatriate's "echo $PATH" puts some 16 directories in my path, versus only 5 when I do "su". YMMV. HTH, Gar -- In the Beginning was the Command Line ---Neal Stephenson -- __________________________________________________________________ New! Unlimited Netscape Internet Service. Only $9.95 a month -- Sign up today at http://isp.netscape.com/register Act now to get a personalized email address! Netscape. Just the Net You Need.
On Thursday 15 January 2004 09:36, GarUlbricht7@netscape.net wrote:
John, you say that "su is already OK", do I am not sure what your problem is, but when i change to "root", i usually do "sux -" which using expatriate's "echo $PATH" puts some 16 directories in my path, versus only 5 when I do "su". YMMV.
Most problems with sux or (gnome|kde)su are because of $HOME/.Xauthority, either the user's or root's. Deleting them and logging in again usually solves the problem.
In a previous message, Anders Johansson
Most problems with sux or (gnome|kde)su are because of $HOME/.Xauthority, either the user's or root's. Deleting them and logging in again usually solves the problem.
Bingo - that was it! Deleting root's ~/.Xauthority means my gnomesu now works again :-) Any idea what messes this up? John -- John Pettigrew Headstrong Games john@headstrong-games.co.uk Fun : Strategy : Price http://www.headstrong-games.co.uk/ Board games that won't break the bank Fields of Valour: 2 Norse clans battle on one of 3 different boards
On Thursday 15 January 2004 12:04, John Pettigrew wrote:
In a previous message, Anders Johansson
wrote: Most problems with sux or (gnome|kde)su are because of $HOME/.Xauthority, either the user's or root's. Deleting them and logging in again usually solves the problem.
Bingo - that was it! Deleting root's ~/.Xauthority means my gnomesu now works again :-)
Any idea what messes this up?
I don't know if there are other causes, but in my case it's usually because I switch between logging in with kdm and using startx from a command line. kdm and startx use different types of X authentication cookies, and suse's sux script doesn't parse the cookie list correctly when it decides which cookie to transfer to the other user
participants (3)
-
Anders Johansson
-
GarUlbricht7@netscape.net
-
John Pettigrew