Mr. Konrad Lorentz 2 Report post Posted February 21, 2013 Hi,on some Linux distributions it might happen that CAESES/FFW will crash when opening FileDialogs in certain cases (taking screenshots, creating PDFs, and adding files to the SoftwareConnector).It was reported when using the local storage for the CAESES/FFW. Maybe moving the application directory onto a network share could help. If it does not, the following solution may work: edit as root : /etc/gnome-vfs-2.0/modules/default-modules.confand comment out the line "file:file"To verify that this solution will work for your problem, please detect the problem! :-)- open a Terminal- navigate to the location of the application launcher- start the application: export LD_LIBRARY_PATH=/opt/CAESES/lib/Linux.x86_64/:$LD_LIBRARY_PATH LD_DEBUG=files /opt/CAESES/bin/Linux.x86_64/CAESES 2>&1 | tail -50(please replace /opt/CAESES with your installation path)if you find an output like: calling init: /usr/lib64/gnome-vfs-2.0/modules/libfile.soopening file=/usr/lib64/gnome-vfs-2.0/modules/libfile.so [0]; direct_opencount=1/usr/lib64/gnome-vfs-2.0/modules/libfile.so: error: symbol lookup error: undefined symbol: g_module_check_init (fatal)/usr/lib64/gnome-vfs-2.0/modules/libfile.so: error: symbol lookup error: undefined symbol: g_module_unload (fatal)/usr/lib64/gnome-vfs-2.0/modules/libfile.so: error: symbol lookup error: undefined symbol: vfs_module_transform (fatal)the suggested fix will work.I hope that will help you!RegardsKonrad Share this post Link to post Share on other sites
Mr. Konrad Lorentz 2 Report post Posted July 20, 2015 If you still have problems, try to start CAESES with this additional argument: - open a Terminal- navigate to the location of the application launcher- start the application: ./CAESES -style plastique Share this post Link to post Share on other sites