I’m running Oracular 24.10. Digikam has run previously, but on starting produces an error message:
digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin…
digikam.facedb: Face database: cannot process schema initialization
Path override failed for key base::DIR_APP_DICTIONARIES and path ‘/snap/digikam/93/usr/bin/qtwebengine_dictionaries’
[165757:165757:0120/094904.718258:FATAL:credentials.cc(126)] Check failed: . : Permission denied (13)
Trace/breakpoint trap (core dumped)
I’m running 8.4.0 and unable to revert to a previous version
snap list digikam --all
Name Version Rev Tracking Publisher Notes
digikam 8.5.0 95 latest/stable kde✓ disabled
digikam 8.4.0 93 latest/stable kde✓
Could you make sure to put three backticks ``` in the lines above and below pasted code so that the formatting stays intact, else it is really hard to read for all of us …
digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin… digikam.facedb: Face database: cannot process schema initialization Path override failed for key base::DIR_APP_DICTIONARIES and path ‘/snap/digikam/93/usr/bin/qtwebengine_dictionaries’ [165757:165757:0120/094904.718258:FATAL:credentials.cc(126)] Check failed: . : Permission denied (13) Trace/breakpoint trap (core dumped)
We started getting this exact same error, starting about a week ago. Same scenario, snap has been working fine previously without any issues. Interesting observation, our app uses Qt WebEngine as well (but no changes recently in our Qt vendor libraries). As a workaround, we are able to get app running if we set environment variable QTWEBENGINE_DISABLE_SANDBOX=1, but this is not desirable as it undermines security.
Many of our users have been reporting issue, and rolling back to previous snap versions does not solve…same error reported.
dmesg: read kernel buffer failed: Operation not permitted
Are there perhaps any additional permissions that need to be added to our snapcraft.yaml?
I would be interested if anyone has insights on this as well.
UPDATE: performed grep on dmesg for apparmor, just to, I see DENIED for snap. But nothing specifying our app, I don’t know if this is a root cause, just fyi.
This has worked with no issues for a long time, wondering why this has changed recently, root cause? In any event, thanks for the suggestion, just need to review the security around it.
Thank you scarlettmoore
for uploading a fixed Digikam.
After the installation on my UBUNTU 22 digikam starts, but at least two effects are new now:
Digikam crashes when you try to add more folder paths in the settings.
Face recognition no longer works, i.e. no more faces are listed after a face scan in the unconfirmed folder.
When starting via the terminal, a large collection of puzzling error messages appears.
elfe@wotan:~$ digikam
/usr/share/libdrm/amdgpu.ids: No such file or directory
digikam.metaengine: ExifTool process cannot be started ( “/snap/digikam/98/usr/bin/exiftool” )
digikam.general: DK_PLUGIN_PATH env.variable detected. We will use it to load plugin…
Sandboxing disabled by user.
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
No QtMultimedia backends found. Only QMediaDevices, QAudioDevice, QSoundEffect, QAudioSink, and QAudioSource are available.
Failed to create QVideoSink “Not available”
Failed to initialize QMediaPlayer “Not available”
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
kf.sonnet.core: Unable to handle language from dictionary “kmr_Latn” “C”
kf.sonnet.core: Unable to handle language from dictionary “ko_KR” “ko_KR”
kf.sonnet.core: Unable to handle language from dictionary “ko” “ko_KR”
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
kf.xmlgui: Unhandled container to remove : Digikam::DigikamApp
kf.i18n: Plural argument to message “You are about to cha…” not supplied before conversion.
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
digikam.marble: No plugins loaded. Please check if the plugins were installed in the correct path, or if any errors occurred while loading plugins.
Looking into it. I just added marble support and it is a struggle to get it to find it’s plugins. ffmpeg is broken, I can’t get it to build with snap so I used packages which seems to break runtime.
We were. Digikam won’t build do to a undefined reference with libva. I have asked @soumyaDghosh to take a look as he maintains the ffmpeg snap, but he was at a conference over the weekend. Hopefully he can get to it soon. Sorry and thank you for your patience.
Scarlett
Gnome guys silently stopped building libva from source. That’s why the problem arose. We needed to build it from source as they previously used to build it from source. And building it with older libva would have brought API incompatibilities.
