On Monday 03 July 2006 00:46, Iain Buchanan wrote: > On Sun, 2006-07-02 at 13:50 +0100, Dave S wrote: > > On Sunday 02 July 2006 12:40, Bo Ørsted Andresen wrote: > > > On Sunday 02 July 2006 09:09, Dave S wrote: > > > > < HOME = /root > > > > --- > > > > > > > > > HOME = /home/vanda > > > > > > This is only a theory but could it be that one reads config files in > > > /root and the other in /home/vanda? > > > > The only related config I can find is for /etc/gksu.conf and thats not > > user dependent. I cant find any config relevent in /root or /home/vanda > > you'll probably find its a gnome (or kde) theme that is causing the > issue, and the gnome (or kde) themes are stored in $HOME. Since you > usually don't log in graphically as root (which is usually good) you > don't have theme folders set up in root's home... am I making sense?! > You sure are :)
> try running `visudo` and commenting out the line: > Defaults env_reset > > I don't know if gksudo uses this file, but if it does, your problem > should go away... If it does go away, then uncomment the line and do > something better like: > > Defaults:yourname env_keep-=TERMCAP Unfortunately my /etc/gksudo is pretty sparse - it consists of ... [EMAIL PROTECTED]:/etc# cat sudoers # /etc/sudoers # # This file MUST be edited with the 'visudo' command as root. # # See the man page for details on how to write a sudoers file. # # Host alias specification # User alias specification # Cmnd alias specification # Defaults Defaults !lecture,tty_tickets,!fqdn # User privilege specification root ALL=(ALL) ALL # Members of the admin group may gain root privileges %admin ALL=(ALL) ALL [EMAIL PROTECTED]:/etc# > > HTH, > -- > Iain Buchanan <iaindb at netspace dot net dot au> > > It's not reality that's important, but how you perceive things. -- [email protected] mailing list
