Severe startup regression in areca 7.2.2 wrt 7.2.1 on linux
Brought to you by:
aventin
Menu
▾
▴
#395 Severe startup regression in areca 7.2.2 wrt 7.2.1 on linux
On kubuntu 11.04 (natty) 64 bits
Areca 7.22 cannot find the workspace at startup
Invariably it starts by saying
11-09-11 15:38 - INFO - Parameters detected : Workspace=""
even if it is set up to start at some assigned workspace or if it is setup to start at the last closed workspace
Furthermore it cannot find the ACL libraries
11-09-11 15:38 - WARNING - com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor cannot be used on this system. Got the following error : "java.lang.UnsatisfiedLinkError : no acl in java.library.path"
11-09-11 15:38 - WARNING - You should check that the 'acl' package is properly deployed on your computer.
In most cases, there should be a 'libacl.so' file or symbolic link somewhere on your filesystem.
If it is not the case, you should check for a 'libacl.<some version="" number="">.so' file and create a symbolic link named 'libacl.so' on it.
If no such file can be found, just install the 'acl' package using your standard package manager.</some>
11-09-11 15:38 - WARNING - [com.myJava.file.metadata.posix.jni.JNIMetaDataAccessor] not validated. The default metadata accessor will be used instead. See FAQ for more informations about file metadata management. (ACL & extended attributes)
Obviously libacl.so is there in lib
areca 7.2.1 was just fine
The libacl issue was probably my fault and depending on the fact that recent distros store libacl in /lib/x86_64-linux-gnu/ (I guess due to multiarch support).
Please ignore it, though it would not be bad to have the location of libacl storable in areca's preferences rather than having to create a link. Sorry for the noise.
Most important:
The fact that areca 7.2.2 cannot use the workspace stored in the preferences always starting with 11-09-11 15:38 - INFO - Parameters detected : Workspace="" is indeed there.
Apparently, areca reads its preference file in .areca, but then cannot deal with the workspace part.
Downgraded to 7.2.1 and that version of areca works just fine so it is indeed a regression.
Hi
There was indeed a regression on Linux. I've updated the 3.2.2 Linux files to include a fix.
could you re-download it and give it a try ?
If it doesn't work, just add a "-ws <your wprkspace="">" option as a temporary workaround ... I'll have a closer look at it</your>
thanks
The recently re-uploaded 7.2.2 is fine, closing the bug.
Thanks for the prompt action.