This bug appears to continue with SoapUI 4.6.4, at least on Ubuntu 12.04 64bit.
I've done the following to work around it:
groupadd soapui
chgrp -R soapui /usr/local/SmartBear
chmod g+w /usr/local/SmartBear
chmod g+w /usr/local/SmartBear/SoapUI-4.6.4/bin/*.log
chmod -R g+w /usr/local/SmartBear/SoapUI-4.6.4/.JxBrowser
useradd <username> soapui
Then before running soapui:
newgrp soapui
The default installation seems to want to place TestPBE-workspace.xml in /usr/local/SmartBear. It also wants to log to the log files in /usr/local/SmartBear/SoapUI-4.6.4/bin/. Finally, it appears to be using /usr/local/SmartBear/SoapUI-4.6.4/.JxBrowser for caching of some sort.
Not an optimal solution. At least with the restriction to a group we can minimize the potential mayhem.
