[digiKam-users] DK doesn't start

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

[digiKam-users] DK doesn't start

digikam-2
DK 5.9.0 appimage

I must have done something and screwed up.

My main drive was going on the fritz, so I replaced it and
reinstalled most of it.

Now when I start I get:

$ downloads/appimages/digikam-5.9.0-01-x86-64.appimage
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
digikam: symbol lookup error: /usr/lib/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var
$

and that's it

digikam4.db
recognition.db
thumbnails-digikam.db

are in the same directory as dk.5.9. appimage

What should I do to figure it out?

--
sknahT

vyS
Reply | Threaded
Open this post in threaded view
|

Re: DK doesn't start

Gilles Caulier-4
Hi,

It's clear: libfontconfig.so come from your system. It's not included in AppImage bundle. 

I suspect something is broken somewhere...

Gilles Caulier

2018-04-21 19:36 GMT+02:00 <[hidden email]>:
DK 5.9.0 appimage

I must have done something and screwed up.

My main drive was going on the fritz, so I replaced it and
reinstalled most of it.

Now when I start I get:

$ downloads/appimages/digikam-5.9.0-01-x86-64.appimage
-- digiKam AppImage Bundle
-- Use 'help' as CLI argument to know all available options
digikam: symbol lookup error: /usr/lib/libfontconfig.so.1: undefined symbol: FT_Done_MM_Var
$

and that's it

digikam4.db
recognition.db
thumbnails-digikam.db

are in the same directory as dk.5.9. appimage

What should I do to figure it out?

--
sknahT

vyS

Reply | Threaded
Open this post in threaded view
|

Re: DK doesn't start

digikam-2
On Sat, 21 Apr 2018 20:30:05 +0200
Gilles Caulier <[hidden email]> wrote:

> It's clear: libfontconfig.so come from your system. It's not
> included in AppImage bundle.
>
> I suspect something is broken somewhere...

Yes, I know. I'm just trying to figure out what. I've checked
fontconfig and the fonts and they all seem to be working properly.
That's why I asked.

--
sknahT

vyS