[Bug 312241] [NEW] FreeMind shouldn't start in $HOME - it fails/takes long

malyvelky maly.velky at email.cz
Mon Dec 29 17:21:17 UTC 2008


Public bug reported:

Binary package hint: freemind

FreeMind shouldn't start in $HOME because this may lead to a failure or
to very, very long startup time (details below). It would be much better
for it to start e.g. in $HOME/.freemind.

Case 1 - failure
FreeMind wil fail with "Mode not available: MindMap." if there is, somewhere under the directory where it's started, a folder to which the user has no access. This may happen if you start some program as a root, in my case e.g. .kde/share/apps/kvpnc/.
See the bug https://sourceforge.net/tracker2/?func=detail&aid=2475036&group_id=7118&atid=107118
Notice that this also happens e.g. when starting from / (which also contains inaccessible subfolders).

Case 2 - long startup time
Even if the problem in Case 1 is fixed in FreeMind, still it isn't usable - at least for me it takes a very long time to start (I hadn't the time to wait till the end). This happens at the same place as the failure - during lookup of modes .xml files in ImportWizard. 

Proposed solution
To get rid of Case 1 and Case 2, FM should start somewhere else than in $HOME, I think the best would be $HOME/.freemind and therefore I'd add the following to /usr/share/freemind/freemind.sh:

if [ ! -d $HOME/.freemind ]; then mkdir $HOME/.freemind; fi
cd $HOME/.freemind

-------------------
Environment
Ubuntu 8.04.1
FreeMind  0.8.1-1

** Affects: freemind (Ubuntu)
     Importance: Undecided
         Status: New

-- 
FreeMind shouldn't start in $HOME - it fails/takes long
https://bugs.launchpad.net/bugs/312241
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list