[digiKam-users] appimage problems on Centos 7 and Fedora 29

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

[digiKam-users] appimage problems on Centos 7 and Fedora 29

digikam-3

Hi

 

I have just tried the latest appimage on both Centos 7 and Fedora 29 test systems with similar problems

 

[phil@C7-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage help

libfreetype.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

libudev.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

[phil@C7-VB ~]$

 

phil@F29-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage

libfreetype.so

libudev.so

/tmp/.mount_digikaJO0Oaf/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaJO0Oaf/AppRun: line 23: [: missing `]'

[phil@F29-VB ~]$

 

The previous appimage (digikam-6.0.0-beta3-20181228T114626-x86-64.appimage) runs successfully on both systems.

 

I’ve also tried the latest appimage with debug which doesn’t give any further information so I suspect this is an issue with the latest appimage build/activation process.

 

Regards, Phil

 

Reply | Threaded
Open this post in threaded view
|

Re: appimage problems on Centos 7 and Fedora 29

Gilles Caulier-4
You don't have the last one AppImage bundle. I already fixed this problem :


Best

Gilles Caulier

Le lun. 21 janv. 2019 à 14:26, <[hidden email]> a écrit :

Hi

 

I have just tried the latest appimage on both Centos 7 and Fedora 29 test systems with similar problems

 

[phil@C7-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage help

libfreetype.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

libudev.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

[phil@C7-VB ~]$

 

phil@F29-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage

libfreetype.so

libudev.so

/tmp/.mount_digikaJO0Oaf/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaJO0Oaf/AppRun: line 23: [: missing `]'

[phil@F29-VB ~]$

 

The previous appimage (digikam-6.0.0-beta3-20181228T114626-x86-64.appimage) runs successfully on both systems.

 

I’ve also tried the latest appimage with debug which doesn’t give any further information so I suspect this is an issue with the latest appimage build/activation process.

 

Regards, Phil

 

Reply | Threaded
Open this post in threaded view
|

Re: appimage problems on Centos 7 and Fedora 29

digikam-3

Hi Giles

 

Apologies for being ‘late to the party’; the latest appimage has indeed fixed this problem.

 

Thanks, Phil

 

From: Gilles Caulier <[hidden email]>
Sent: 21 January 2019 14:05
To: [hidden email]; digiKam - Home Manage your photographs as a professional with the power of open source <[hidden email]>
Subject: Re: [digiKam-users] appimage problems on Centos 7 and Fedora 29

 

You don't have the last one AppImage bundle. I already fixed this problem :

 

 

Best

 

Gilles Caulier

 

Le lun. 21 janv. 2019 à 14:26, <[hidden email]> a écrit :

Hi

 

I have just tried the latest appimage on both Centos 7 and Fedora 29 test systems with similar problems

 

[phil@C7-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage help

libfreetype.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

libudev.so

/tmp/.mount_digikaSJ51KV/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaSJ51KV/AppRun: line 23: [: missing `]'

[phil@C7-VB ~]$

 

phil@F29-VB ~]$ ./digikam-6.0.0-20190119T184553-x86-64.appimage

libfreetype.so

libudev.so

/tmp/.mount_digikaJO0Oaf/AppRun: line 21: [: missing `]'

/tmp/.mount_digikaJO0Oaf/AppRun: line 23: [: missing `]'

[phil@F29-VB ~]$

 

The previous appimage (digikam-6.0.0-beta3-20181228T114626-x86-64.appimage) runs successfully on both systems.

 

I’ve also tried the latest appimage with debug which doesn’t give any further information so I suspect this is an issue with the latest appimage build/activation process.

 

Regards, Phil