Closed Philipp91 closed 1 year ago
sudo snap revert digikam --revision 47
"fixes" the issue.
I'm trying to run the revision 47 snap on Ubuntu 20.04.3 LTS and after reverting I still see the following error:
➜ ~ digikam
Qt: Session management error: Could not open network socket
QObject::connect: No such signal QDBusAbstractInterface::DeviceAdded(QString)
QObject::connect: No such signal QDBusAbstractInterface::DeviceRemoved(QString)
digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin...
QtAV 1.13.0(Jul 22 2021, 18:31:17)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
kf.xmlgui: Unhandled container to remove : Digikam::DigikamApp
/snap/digikam/47/usr/bin/digikam: symbol lookup error: /snap/digikam/47/usr/lib/x86_64-linux-gnu/libdigikamcore.so.7.3.0: undefined symbol: _ZNKSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEE7compareERKS4_, version Qt_5
When I try to run digiKam 7.3.0 from the Snap, I get:
Relevant
snap connections
output:I'm using Linux Mint 20.2 with KDE Frameworks 5.68.0 and Qt 5.12.8.
This was definitely working a couple months ago, so presumably some update (my main suspect is the
kde-frameworks-5-qt-*
slot) broke the compatibility here. Given that 7.4.0 is available upstream in two days, if that propagates to the Snap quickly enough, maybe I should just wait for that?