[digikam] [Bug 404894] 6.0.0 x86-64 appimage startup complains about mssing ']' (startup bash script being called) ?

2019-03-24 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404894

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Status|REOPENED|RESOLVED
 Resolution|--- |FIXED

--- Comment #3 from caulier.gil...@gmail.com ---
Fixed with 

https://files.kde.org/digikam/digikam-6.1.0-git-20190323T220709-x86-64.appimage.mirrorlist

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 404894] 6.0.0 x86-64 appimage startup complains about mssing ']' (startup bash script being called) ?

2019-03-20 Thread Nicofo
https://bugs.kde.org/show_bug.cgi?id=404894

Nicofo  changed:

   What|Removed |Added

 CC||nic...@tuxfamily.org
 Ever confirmed|0   |1
 Resolution|FIXED   |---
 Status|RESOLVED|REOPENED

--- Comment #2 from Nicofo  ---
Hello Gilles,
this bug is back with your last digikam bundle:


$ ./digikam-6.1.0-git-20190320T143140-x86-64.appimage 
libfontconfig.so
/tmp/.mount_digikaOG2FUr/AppRun: line 21: [: missing `]'
/tmp/.mount_digikaOG2FUr/AppRun: line 23: [: missing `]'
libfreetype.so
/tmp/.mount_digikaOG2FUr/AppRun: line 21: [: missing `]'
/tmp/.mount_digikaOG2FUr/AppRun: line 23: [: missing `]'
libudev.so
/tmp/.mount_digikaOG2FUr/AppRun: line 21: [: missing `]'
/tmp/.mount_digikaOG2FUr/AppRun: line 23: [: missing `]'
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam
application
-- Preloading shared libs: 
...

-- 
You are receiving this mail because:
You are watching all bug changes.

[digikam] [Bug 404894] 6.0.0 x86-64 appimage startup complains about mssing ']' (startup bash script being called) ?

2019-02-28 Thread bugzilla_noreply
https://bugs.kde.org/show_bug.cgi?id=404894

caulier.gil...@gmail.com changed:

   What|Removed |Added

 Resolution|--- |FIXED
   Version Fixed In||6.1.0
 Status|REPORTED|RESOLVED
 CC||caulier.gil...@gmail.com

--- Comment #1 from caulier.gil...@gmail.com ---
This is due to UTF8 encoding of hidden characters in bash script. I already
fixed this problem for next 6.1.0.

To test : https://files.kde.org/digikam/

Gilles Caulier

-- 
You are receiving this mail because:
You are watching all bug changes.