Apache OpenOffice (AOO) Bugzilla – Issue 71670
Chart2 Milestone 9 Won't Close Without Lockup
Last modified: 2013-02-24 21:19:57 UTC
I tried to put this in the right place, and don't know if you even want to track this issue. But milestone9 of Chart2 works great as root, but as any other user it locks when you hit the "X" of the window manager or do a File-->Quit. The whole UI grays out and becomes non-responsive. I tested several non-root users and it's doing the same thing for all of them. The process seems not to be spinning or taking CPU time, and just hangs. I put it on GDB with the hopes that this would help.
Created attachment 40661 [details] gdb backtrace
@BM: One for you.
->drichard: The install set is in a way a "single-user" installation. We put the user configuration into the unpacked installation directory, i.e. you will get all user-settings in <install-path>/UserInstallation/user. Therefore all users that use this developer snapshot will use the same configuration and need of course write access to the corresponding directory, which will usually not be the case. Apart from the missing write-access, it is no good idea to share the same settings between users. To get the user-configuration in the home-directories of the users, you can adapt the line containing UserInstallation in the <installation-path>/program/bootstraprc to: UserInstallation=$SYSUSERCONFIG/.ooo-chart2mst3-beta This is not a problem with the new chart, but with the kind of developer snapshot we offer for evaluation.
->IS: It turns out that there is a need for an installation of a developer's snapshot for more than one beta-tester. So, I think we should change the bootstraprc to point to the $HOME directory like in a regular installation. Advantage: You have the possibility to use the snapshot by more than one user without big effort. Disadvantage: After beta-testing every user will have a .openoffice-cwsname directory in her home-driectory that occupies space unnecessarily. Or do you see an easy way to make this configurable. (Maybe an additional script that patches the bootstraprc, if you want a network install after unpacking?)
Thank you for the 'fix' on a multi-user server. I'm making that change right now because I have about 2-3 people that are interested in testing the code. An idea would be to maybe point it to $HOME/.ooo-dev2 which is used for experimental versions anyway. If they are able to share data, that would be fine with us. Just made that change and verified that it's working, thanks.
There is only one line in bootstraprc, which defines the location of the user directory. So we have to decide, which content is more important: 1. User directory into home directory, to enable using the development version with more than one user 2. User directory into office installation, to keep all data in one directory and do no write temporary data into home directory. In the past, it was important for development versions, to write the user data into the office installation set. I suppose, that most developers prefer this. With a simple "rm -rf" the complete content is removed. Probably there will be some tasks, if we create the user directory in the home folder in future. I really do not like your suggested fix. You should collect additional intercessors :-)
->drichard: As your problem seems to be fixed, and this use-case is not the usual scenario for beta-testing, I would suggest to close this issue.Maybe we can add a comment on the download-page how to change the configuration. (Like described before)
Fair enough, and thanks all. Yes, maybe a short section describing how to enable multi-user on the download area would help others. Closing
Added a comment to http://graphics.openoffice.org/chart/readme2.html