Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 55536 - argouml 1.15.6 fails to run as regular user but works as root
Summary: argouml 1.15.6 fails to run as regular user but works as root
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: x86 Linux
: High critical (vote)
Assignee: Java team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-06-29 04:20 UTC by ville
Modified: 2004-08-16 13:43 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description ville 2004-06-29 04:20:05 UTC 
If I run argouml as a regular user it fails to run while it works nicely when run as root. It fails with:

log4j:ERROR setFile(null,true) call failed.
java.io.FileNotFoundException: argouml.log (Permission denied)
        at java.io.FileOutputStream.openAppend(Native Method)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:177)
        at java.io.FileOutputStream.<init>(FileOutputStream.java:102)
        at org.apache.log4j.FileAppender.setFile(FileAppender.java:272)
        at org.apache.log4j.RollingFileAppender.setFile(RollingFileAppender.java:156)
        at org.apache.log4j.FileAppender.activateOptions(FileAppender.java:151)
        at org.apache.log4j.config.PropertySetter.activate(PropertySetter.java:247)
        at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:123)
        at org.apache.log4j.config.PropertySetter.setProperties(PropertySetter.java:87)
        at org.apache.log4j.PropertyConfigurator.parseAppender(PropertyConfigurator.java:645)
        at org.apache.log4j.PropertyConfigurator.parseCategory(PropertyConfigurator.java:603)
        at org.apache.log4j.PropertyConfigurator.configureRootCategory(PropertyConfigurator.java:500)
        at org.apache.log4j.PropertyConfigurator.doConfigure(PropertyConfigurator.java:406)
        at org.apache.log4j.PropertyConfigurator.configure(PropertyConfigurator.java:340)
        at org.argouml.application.Main.<clinit>(Main.java:555)

I do get to see a flashscreen saying: "ArgoUML 1.15.6" and some sort of paper hat and there's a progress bar at bottom saying: "Making Project Browser".


Reproducible: Always
Steps to Reproduce:
1. emerge argouml
2. as regular user in xterm run the application
3. ???

Actual Results:  
The program fails to run with the above Java stack trace.

Expected Results:  
The program would work.
Comment 1 Ant 2004-08-12 16:42:46 UTC 
The reason is that the argouml is being denied permissions of some sort to it's log file in /opt/argouml/argouml.log. Possibly argouml is trying to delete the log file before starting a new session? Seems strange because my user can directly access the log file fine. (Except deleting it)

The lastest version 0.16 seems to work fine despite the log file errors.
 
This argouml bug mentions it.
http://argouml.tigris.org/servlets/ReadMsg?list=issues&msgNo=14560

You can also possibly configure the log4j logger. See http://logging.apache.org/log4j/docs/manual.html not that I could work out how to.
Comment 2 Ant 2004-08-12 17:15:33 UTC 
After further investigation it looks as though the ebuild is incorrectly creating /opt/argouml/argouml.log when it really wants to create /opt/argouml/lib/argouml.log and then chmod 666 to this file. Do this as root and this should remove the annoying java exceptions cause by the failure to access the log file.

If this solves your problem, feel free to close this bug.
Comment 3 Chris Aniszczyk (RETIRED) gentoo-dev 2004-08-16 13:43:43 UTC 
Issue resolved in new .16 ebuild