https://bugs.kde.org/show_bug.cgi?id=426912
Bug ID: 426912
Summary: digikam-7.1.0-x86-64.appimage fails to start on CentOS
8.2-2.2004.0.2
Product: digikam
Version: 7.1.0
Platform: Appimage
OS: Linux
https://bugs.kde.org/show_bug.cgi?id=419458
--- Comment #4 from Simon J Mudd ---
This has the same issue as described before. You are assuming that the system
glibc is good enough to use and matches and that is not the case.
Output with the beta3 shows:
$ chmod +x digikam-7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=419458
--- Comment #3 from Simon J Mudd ---
Just as an update I have found an alternative way to run digikam. It's not as
convenient but running it with a docker image locally using this image:
rpufky/digikam:stable. This seems to work. (Currently running
https://bugs.kde.org/show_bug.cgi?id=419458
Bug ID: 419458
Summary: digikam 6.4.0 appimage fails to run on centos 7.7
Product: digikam
Version: 6.4.0
Platform: Appimage
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=412778
--- Comment #7 from Simon J Mudd ---
I only run the 64 bit app and OS.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412778
--- Comment #5 from Simon J Mudd ---
ok, so I searched around and found this:
$ sudo yum install jack-audio-connection-kit
That seems to fix the libjack.so issue.
So I try again:
$ ./digikam-6.4.0-git-20191005T120037-x86-64.appimage
-- digiKam
https://bugs.kde.org/show_bug.cgi?id=412778
--- Comment #3 from Simon J Mudd ---
So looks like the missing libjack.so.0 library is the issue.
--
You are receiving this mail because:
You are watching all bug changes.
https://bugs.kde.org/show_bug.cgi?id=412778
Simon J Mudd changed:
What|Removed |Added
Component|Bundle-AppImage |Setup-FirstRun
--- Comment #2 from Simon J Mudd
https://bugs.kde.org/show_bug.cgi?id=412778
Bug ID: 412778
Summary: digikam 6.3.0 appimage fails to run on centos 7.6
Product: digikam
Version: 6.3.0
Platform: Appimage
OS: Linux
Status: REPORTED
https://bugs.kde.org/show_bug.cgi?id=404797
--- Comment #5 from Simon J Mudd ---
So digikam-6.1.0-git-20190321T102236-x86-64.appimage now runs for me. Thanks.
I still see the following issue:
...
[user@host ~]$ Downloads/digikam-6.1.0-git-20190321T102236-x86-64.appimage
libfontconfig.so
/tmp
https://bugs.kde.org/show_bug.cgi?id=405233
Bug ID: 405233
Summary: digikam: symbol lookup error:
/tmp/.mount_digika5N9rGH/usr/lib/libQt5XcbQpa.so.5:
undefined symbol: FT_Property_Set
Product: digikam
Version:
https://bugs.kde.org/show_bug.cgi?id=404894
Bug ID: 404894
Summary: 6.0.0 x86-64 appimage startup complains about mssing
']' (startup bash script being called) ?
Product: digikam
Version: 6.0.0
Platform: Appimage
https://bugs.kde.org/show_bug.cgi?id=404893
Bug ID: 404893
Summary: Digikam::DigikamApp::slotSolidDeviceChanged:
slotSolidDeviceChanged: messages referring to
directory that digikam should not care about
Product: digikam
https://bugs.kde.org/show_bug.cgi?id=404797
--- Comment #2 from Simon J Mudd ---
Hi. That might be hard as I have not seen this happen again. It is not
direcctly reproducible.
I had hoped the report would be enough. I guess it is not.
Perhaps I will try to run it again in debug mode in case
https://bugs.kde.org/show_bug.cgi?id=404797
Bug ID: 404797
Summary: digikam-6.0.0-x86-64.appimage: stack trace shortly
after startup.
Product: digikam
Version: 6.0.0
Platform: Other
OS: Linux
15 matches
Mail list logo
