Oh, and you can always put a tool in the chain, mess with it, and see its command in Help → Show Command…
1 Like
It’s how I remember what I did… 
1 Like
It doesn’t fix the issue indeed but I’d suggest to only worry if someone else reports it.
Both things fail.
I now get a nice windowed dialog that shows the doesn’t exists. shall I create with a yes/no option and, after yes a …populated with Ok window. However nothing is created and if I create it manually first it is not populated.
After that I get a mix of these 4 messages, multiple times, before it stops:
/tmp/.mount_rawpros4FZaZ/usr/bin/rawproc: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.29' not found (required by /tmp/.mount_rawpros4FZaZ/usr/lib/libcairo.so.2)
/tmp/.mount_rawpros4FZaZ/usr/bin/rawproc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by /tmp/.mount_rawpros4FZaZ/usr/lib/libglib-2.0.so.0)
/tmp/.mount_rawpros4FZaZ/usr/bin/rawproc: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.30' not found (required by /tmp/.mount_rawpros4FZaZ/usr/lib/libselinux.so.1)
/tmp/.mount_rawpros4FZaZ/usr/bin/rawproc: /lib/x86_64-linux-gnu/libp11-kit.so.0: no version information available (required by /tmp/.mount_rawpros4FZaZ/usr/lib/libgnutls.so.30)
As mentioned way back (reply 6) I’m on GLIBC_2.28.
1 Like
Geesh, i wrote that part in a separate file with the cp lines commented out, and I forgot to uncomment them when I pasted it into the AppImage script…
Now, that hurts. I’m not sure I can remove the exclusions for libc without causing other problems. The general recommendation in the AppImage docs is to build the appimage on an old OS version; I’m going to replace Ubuntu with Debian on an old server, so that might be the opportunity…
Thanks for trying…
You’re welcome !
Yeah, but Debian 10/Buster isn’t old, it’s the latest stable version. 11/Bullseye is TBA (probably mid 2021). Then again, Debian is notoriously stable and that is in part because they do not use the lates/greatest versions…
Just in case: I do hope you realise that I’m not dependent on the appimage. I’m happily using the one that I compiled/build/installed, without a hitch, from the rawproc-1.0.1.tar.gz package.
1 Like
Fixed, appimage updated to 20200107a…
Progress!
Created and populated:
[stasis] jade ~ $ ls -la ~/.rawproc/
total 512
drwxr-x--- 3 jade jade 4096 jan 8 08:28 .
drwxr-x--- 27 jade jade 4096 jan 8 08:28 ..
-rw-r----- 1 jade jade 166653 jan 8 08:28 camconst.json
-rw-r----- 1 jade jade 335068 jan 8 08:28 dcraw.c
-rw-r----- 1 jade jade 6858 jan 8 08:28 rawproc.conf
drwxr-x--- 2 jade jade 4096 jan 8 08:28 version_2
The GLIBC stuff is still there, but if I’m correct that wasn’t the goal of this particular fix.
1 Like
Yes, and that’ll live for a while. My first priority is probably going to be getting rid of the dependency…