Re: [arch-general] new xorg go-openoffice are fighting - fatal user interface language cannot be determined [SOLVED]

2009-11-09 Thread Alessandro Doro
On Mon, Nov 09, 2009 at 05:04:53PM -0600, David C. Rankin wrote:
 Ah hah! sudo chown -R david:david ./config/.openoffice.org and all is well. 
 For some reason starting as root while su root caused the 
 ./config/.openoffice.org directory to be created under root UID  GID. 
 Doesn't 
 seem like it should have done that. Usually even if using su or kdesu the 
 configs still go under /root not the current user. Strange ...

If you need a real root shell you must give the -l option to su.
Try this:
$ su
Password:
and then look at the $USER environment variable: surprised?

Anyway it isn't a good idea to run graphical applications as root.

bye


Re: [arch-general] new xorg go-openoffice are fighting - fatal user interface language cannot be determined [SOLVED]

2009-11-09 Thread David C. Rankin
On Monday 09 November 2009 17:18:28 and regarding:
 and then look at the $USER environment variable: surprised?
 

Well it's me!

 Anyway it isn't a good idea to run graphical applications as root.
 

Good words of wisdom to live by :-)

-- 
David C. Rankin, J.D.,P.E.
Rankin Law Firm, PLLC
510 Ochiltree Street
Nacogdoches, Texas 75961
Telephone: (936) 715-9333
Facsimile: (936) 715-9339
www.rankinlawfirm.com


Re: [arch-general] new xorg go-openoffice are fighting - fatal user interface language cannot be determined [SOLVED]

2009-11-09 Thread Alessandro Doro
On Mon, Nov 09, 2009 at 05:57:38PM -0600, David C. Rankin wrote:
 On Monday 09 November 2009 17:18:28 and regarding:
  and then look at the $USER environment variable: surprised?
  
 
 Well it's me!
Yes, you are half root, half david; kde will create its directories in
/tmp/ksocket-david, /tmp/kde-david, /var/tmp/kdecache-david but owned
by root. Boom.

  Anyway it isn't a good idea to run graphical applications as root.
  
 
 Good words of wisdom to live by :-)
And not only for security reasons; If you have time have a look at
http://bugs.archlinux.org/task/14926
in that case the permission problems affected the system directories.

And times ago there where permission (umask) issues with users calling
pacman with sudo.