On Sun, Feb 09, 2003 at 11:31:20AM -0500, Fraser Campbell wrote:
I don't know the security implications of what I did so if you have a
multi-user system I'd suggest figuring that out first. A better alternative
may be to use gnome-sudo instead of su, like this:
gnome-sudo gnome-apt
On Sun, Feb 09, 2003 at 01:53:10AM +0200, Johan Ehnberg wrote:
Yeah, I got annoyed because of this too. Anyway it's not a big problem.
What happens when you 'su' is that your env.vars. are changed to root's.
Thus, apps don't know where the user's X session is. What you can do is
use the -p
Andrej Prsa wrote:
I have a very-difficult-to-reproduce-but-pertaining problem with
accessing X applications (such as nedit) when gaining access via
su from some other user's X session. If I log in as root to X,
such problem never occurs. But as I don't want to take the name
of root in vain,
Hello List,
I have a very-difficult-to-reproduce-but-pertaining problem with
accessing X applications (such as nedit) when gaining access via
su from some other user's X session. If I log in as root to X,
such problem never occurs. But as I don't want to take the name
of root in vain, I got used
Yeah, I got annoyed because of this too. Anyway it's not a big problem.
What happens when you 'su' is that your env.vars. are changed to root's.
Thus, apps don't know where the user's X session is. What you can do is
use the -p flag for su. 'su -p' will preserve the user's env.vars. for
the
Hello List,
I have a very-difficult-to-reproduce-but-pertaining problem with
accessing X applications (such as nedit) when gaining access via
su from some other user's X session. If I log in as root to X,
such problem never occurs. But as I don't want to take the name
of root in vain, I got
6 matches
Mail list logo
