Arch Linux User Repository

Fennectech: At http://www.singularityviewer.org/downloads under the Linux64 section, it says “Singularity Viewer 1.8.7(6866) 64-bit Linux (missing, see alphas)”. I haven't the faintest idea why this is so… but anyway, you can use the alpha package https://aur.archlinux.org/packages/singularityviewer-alpha/ .

Downloading doesnt work on the latest version Would also like to see an alpha version

I will let upstream know, but I wouldn't expect much. Their building system isn't cutting edge, so they may not have the newest harfbuzz.

For the time being, I added the binaries from an old version of harfbuzz and CEF works properly.

Thanks for noticing and debugging, Test0.

Apart from an issue with harfbuzz[1], everything seems to be fine.

[1]: The cef plugin fails with this error message: "undefined reference to `FT_Get_Var_Blend_Coordinates'". It's probably due to the relatively recent ABI change, in which case upstream will need to rebuild against the new harfbuzz. Downgrading harfbuzz fixes this.

It took me ages, but I did what you asked. I also reworked the dependencies in general, according to namcap's result. Tell me if it's all right please.

I will look this up.

gconf should be added to the dependencies list. Singularity ships with libcef which depends on libgconf.

Apparently upstream decided to withdraw the update :S I will withdraw the commit as well. So latest official release remains 6866. If you want 6888, use aur/singularityviewer-test. Thank you, fennectech.

==> Retrieving sources...
-> Downloading Singularity_1_8_7_6888_x86_64.tar.xz...
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
curl: (22) The requested URL returned error: 404 Not Found
==> ERROR: Failure while downloading http://67.170.30.149/Singularity_1_8_7_6888_x86_64.tar.xz
Aborting...

PKG source 404!

Glad I could help :)

You, my friend Seanl, are a true Wizard, to whose ingenuity and wisdom I bow! Sed'ed and updated. Many, many, many thanks :-)

Ah, I didn't realize the same problem. I fixed it by changing lines 141-14 in /opt/singularityviewer/singularity to the following:

BINARY_TYPE="$(expr match "$(file -b bin/$VIEWER_BINARY)" '\(.*executable\)')"
if [ "${BINARY_TYPE}" == "ELF 64-bit LSB executable" ]; then
SL_ENV+='LD_LIBRARY_PATH="`pwd`/lib64:`pwd`/lib32:$LD_LIBRARY_PATH"'

i.e. I put quotes around $(expr...) on line 141 and added a space between LSB and executable on line 142. Not sure if the quotes on line 141 are really necessary since I did that first, but it's good hygeine. Works fine now.

Yes, it's a known thing (see some comments below). You have to either downgrade file to 5.13 or use singularityviewer-alpha. I recommend the latter. :)

I get the following error when trying to run it on 64 bit Arch:

bin/singularity-do-not-run-directly: error while loading shared libraries: libcollada14dom.so: cannot open shared object file: No such file or directory

collada-dom looks like the closest thing, but it appears to be the wrong version, 2.4 versus what I assume is 1.4.

Okay, I couldn't resist the temptation :-)
https://aur.archlinux.org/packages/singularityviewer-alpha/

Awesome :) Thank you LightDrake! I'm glad there are Archers in the Singularity team. In my opinion, Singularity and CoolVLViewer are the best viewers available. I will wait for the next stable release before updating, but the link for the alpha release with the issue fixed is https://files.streamgrid.net/singularity/?build_id=4253 , for whomever wants to update sooner.

The issues being experienced with file-5.14 should be fixed in this commit https://github.com/singularity-viewer/SingularityViewer/commit/4cc42cd5bd9b03eebc052ffe055e440dfe9a3aeb in our main repository.

Well, apparently I was wrong and the LD_PRELOAD workaround doesn't work after all. So I'm reverting the change and admitting defeat. Please stay at file-5.13 for the time being.

Updated to the new SSBA-capable version (yay! v1 lives!). Also added a workaround for the file bug, which means you should now be able to stop holding your "file" package.

Updated to the new SSBA-capable version (yay! v1 lives!). Also added a workaround for the file bug, which means you should now be able to update to stop holding your "file" package.

It seems there is an upstream bug report already: http://code.google.com/p/singularity-viewer/issues/detail?id=718&sort=-opened&colspec=ID%20Type%20Status%20Priority%20Stars%20Milestone%20Owner%20Summary%20Opened%20Modified
To me it's libllcommon.so.

According to the bug report, and I just confirmed it, downgrading the package file from 5.14 to 5.13 solves this issue. Why though… no idea.

After a recent system update, I'm not getting Singularity to run anymore, it errors out here:
bin/singularity-do-not-run-directly: error while loading shared libraries: libalut.so.0: cannot open shared object file: No such file or directory
*** Bad shutdown. ***

I have no idea why, libalut.so.0 is in the lib64 directory. :|

Fixed, thank you.

==> Validating source files with md5sums...
Singularity-x86_64-1.7.3.3624.tar.bz2 ... FAILED

Thank you, lightdrake!

Slight improvement for your PKGBUILD. You don't actually need to depend on libjpeg7 specifically you can just use libjpeg-turbo from extra as it's a drop-in replacement for jpeglib v8.

Slight improvement for your PKGBUILD, libjpeg7 isn't actually a hard dependency of the viewer...you could just switch it out for libjpeg-turbo as its a drop in replacement :P

I'm glad someone uses this :) Thanks for flagging. Updated.