[arch-general] new xorg & go-openoffice are fighting -> fatal user interface language cannot be determined
Guys, I thought I would try go-openoffice to see if there was a difference that I could tell from the way I use it. In short, installed go-oo and the dependencies. go-oo WILL start for root, but WILL NOT start for normal users. The error dialog received at the same time the splash appears says Fatal Error: "The application cannot be started. The user interface language cannot be determined." Launching it from the command line results in the following error: 15:26 alchemy:~> soffice [Java framework] Error in function createSettingsDocument (elements.cxx). javaldx failed! OK, that doesn't jive with the dialog reported error, but I'm sure they are related. I have googled it and the only thing I ran across was the suggestion to check /etc/locale.gen to determine if the correct language was uncommented. I believe it is: 15:32 alchemy:~> noc /etc/locale.gen en_US.UTF-8 UTF-8 en_US ISO-8859-1 The strange part is the fact it starts for root, but not a regular user (that normally sounds like a permissions problem). Java runtime permissions?? Where? Let me know what to check and whether you want me to file it as a bug and I'll be happy to. -- 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
On Monday 09 November 2009 15:43:16 and regarding:
Guys,
I thought I would try go-openoffice to see if there was a difference that I could tell from the way I use it. In short, installed go-oo and the dependencies. go-oo WILL start for root, but WILL NOT start for normal users. The error dialog received at the same time the splash appears says
Fatal Error:
"The application cannot be started. The user interface language cannot be determined."
Launching it from the command line results in the following error:
15:26 alchemy:~> soffice [Java framework] Error in function createSettingsDocument (elements.cxx). javaldx failed!
OK, that doesn't jive with the dialog reported error, but I'm sure they are related. I have googled it and the only thing I ran across was the suggestion to check /etc/locale.gen to determine if the correct language was uncommented. I believe it is:
15:32 alchemy:~> noc /etc/locale.gen en_US.UTF-8 UTF-8 en_US ISO-8859-1
The strange part is the fact it starts for root, but not a regular user (that normally sounds like a permissions problem). Java runtime permissions?? Where?
Let me know what to check and whether you want me to file it as a bug and I'll be happy to.
I think I know what happened. I installed from the command line su to root and I started openoffice for the first time from konsole that was su to root. When I tried to start as a user oo crashed. Picking around in ~/.config I found the following: 16:59 alchemy:~> cat cnf/oobug-inst.txt drwxr-xr-x 18 david david 4096 2009-11-09 15:16 . drwx------ 61 david david 4096 2009-11-09 16:44 .. drwxr-xr-x 2 david david 4096 2009-11-05 02:25 akonadi drwxr-xr-x 2 david david 4096 2009-11-04 14:32 autostart drwxr-xr-x 3 david david 4096 2008-10-07 00:29 compiz drwxr--r-- 2 david david 4096 2009-11-06 21:12 gpicview drwx------ 2 david david 4096 2009-11-09 14:09 gtk-2.0 drwxr-xr-x 2 david david 4096 2009-09-30 11:22 gtk-qt-engine drwxr-xr-x 2 david david 4096 2009-11-06 23:16 kde.org drwxr-xr-x 2 david david 4096 2009-11-04 09:45 keepassx drwxr-xr-x 2 david david 4096 2009-11-04 09:35 lxde drwx------ 3 david david 4096 2009-11-04 09:33 lxpanel drwx------ 2 david david 4096 2009-11-07 17:08 openbox drwxr-xr-x 3 root root 4096 2009-11-09 15:16 .openoffice.org drwxr-xr-x 2 david david 4096 2009-11-04 09:33 pcmanfm drwxr-xr-x 2 david david 4096 2009-11-04 09:35 qtcurve drwxr-xr-x 2 david david 4096 2009-11-06 21:11 SpeedCrunch drwxr-xr-x 10 david david 4096 2009-11-05 16:50 tea -rw-r--r-- 1 david david 27665 2009-11-09 15:57 Trolltech.conf -rw------- 1 david david 24 2009-11-05 00:42 user-dirs.dirs 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 ... -- 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
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
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
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.
participants (2)
-
Alessandro Doro
-
David C. Rankin