| Summary: | DigiKam becomes unresponsive when clicking on NFS-mounted photos | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Cengiz Gunay <cengique> |
| Component: | Database-Media | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 6.1.0 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.1.0 | |
| Sentry Crash Report: | |||
|
Description
Cengiz Gunay
2019-12-02 03:48:45 UTC
Which kind of database type do you use ? Mysql or sqlte ? Where are stored your database file ? On the NFS mount path, in local, or in a remote server ? The crash at this point is not unknown. We used a CoreDbAccess here to synchronize the access. Meanwhile we use a QReadLocker. The crash should be fixed in a more recent digiKam version. Maik Please check with official last stable 6.4.0 release: https://www.digikam.org/download/ ...or with current 7.0.0 pre release bundles available here : https://files.kde.org/digikam/ Gilles Caulier Hi, Can you check if this problem still exist with last weekly bundle build of digiKam 7.0.0 available here: https://files.kde.org/digikam/ Thanks in advance Gilles Caulier digiKam 7.0.0 stable release is now published: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier Hi, I tried to run the 7.0.0 stable from the 64-bit AppImage on the same system, but I'm getting this core dump: $ ./digikam-7.0.0-x86-64_8da9c2c162c686a1161d2f7525ab3e3b.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. -- to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. libudev.so.0 libnss3.so -- Preloading shared libs: :/usr/lib64/libudev.so.0:/tmp/.mount_digikadKlQVY/usr/lib64/libnss3.so unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: qglx_findConfig: Failed to finding matching FBConfig for QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize -1, redBufferSize 1, greenBufferSize 1, blueBufferSize 1, alphaBufferSize -1, stencilBufferSize -1, samples -1, swapBehavior QSurfaceFormat::SingleBuffer, swapInterval 1, colorSpace QSurfaceFormat::DefaultColorSpace, profile QSurfaceFormat::NoProfile) unknown: Could not initialize GLX /tmp/.mount_digikadKlQVY/AppRun: line 157: 896629 Aborted (core dumped) digikam $@ I'm not very familiar with AppImage so is there anything I can try? Try to start Appimage bundle with a preload a library like this : LD_PRELOAD=/usr/lib64/libxcb-dri3.so.0 ./digikam-7.0.0-x86-64.appimage Name and path to libxcb can change in different system. Gilles Caulier (In reply to caulier.gilles from comment #1) > Which kind of database type do you use ? Mysql or sqlte ? > > Where are stored your database file ? On the NFS mount path, in local, or in > a remote server ? Sorry for not replying to this earlier. I didn't know how to look it up. It's a QSQLITE backend, but it's saved on a local drive, not the NFS drive. (In reply to caulier.gilles from comment #7) > Try to start Appimage bundle with a preload a library like this : > > LD_PRELOAD=/usr/lib64/libxcb-dri3.so.0 ./digikam-7.0.0-x86-64.appimage > > Name and path to libxcb can change in different system. > > Gilles Caulier This worked, and I can confirm that I'm no longer getting crashes in the 7.0.0 version while browsing the NFS folders. Actually, I tried to track the crash down by running the system-installed version of DigiKam, but apparently it's already upgraded to 6.4.0, which also doesn't exhibit any crashes. It's quite slow because it's constantly scanning the files (it's a large database), but still functions. Also tried ShowFoto 6.4.0 because I wasn't sure if the crash was from there, but it also works. Thanks for your feebacks. I close this file now. Gilles Caulier You're welcome. Thanks for working on this nice tool! |