| Summary: | Map view freezing | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | _ <myaccount132> |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | caulier.gilles, metzpinguin |
| Priority: | NOR | ||
| Version First Reported In: | 6.4.0 | ||
| Target Milestone: | --- | ||
| Platform: | Mint (Ubuntu based) | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.7.0 | |
| Sentry Crash Report: | |||
|
Description
_
2022-03-22 06:26:42 UTC
How many images with geo-coordinates do you have in your collection? What type of database are they using. Maik Which digiKam and Marble versions did you use ? Look into Help/Components Info dialog for details... Gilles Caulier (In reply to Maik Qualmann from comment #1) > How many images with geo-coordinates do you have in your collection? What > type of database are they using. > > Maik There's 250k+ images, most of them having geolocations but unsure of exact number. (In reply to caulier.gilles from comment #2) > Which digiKam and Marble versions did you use ? Look into Help/Components > Info dialog for details... > > Gilles Caulier digikam 6.4.0 Marble 0.27.20 But this has been problem for very long. Changing thumbnails to pins years ago helped first, but now that's nearly unusable too. (In reply to Maik Qualmann from comment #1) > What type of database are they using. SQlite Can you test with the lastest digiKam 7.6.0 AppImage Linux bundle to see if the problem remain with a more recent version ? https://download.kde.org/stable/digikam/7.6.0/ Thanks in advance Gilles Caulier However, you should make a backup copy of your databases in case you want to revert to older digiKam versions. Would it be possible to provide the digikam4.db so we can reproduce it? Maik (In reply to caulier.gilles from comment #6) > Can you test with the lastest digiKam 7.6.0 AppImage Linux bundle to see if > the problem remain with a more recent version ? I think I'll wait month for Ubuntu LTS upgrade instead and see if it helps. As this has been constant and gradually worsening feature I doubt it, but I'll comment then. The only problem is that more recent Ubuntu digiKam packages are snap packages. Snap uses a sandbox and digiKam is useless with these packages on Ubuntu, we've had a lot of problems reported with it. Either AppImage or there is a private repository that builds native digiKam packages for Ubuntu. Maik (In reply to Maik Qualmann from comment #9) > The only problem is that more recent Ubuntu digiKam packages are snap > packages. Snap uses a sandbox and digiKam is useless with these packages on > Ubuntu, we've had a lot of problems reported with it. Either AppImage or > there is a private repository that builds native digiKam packages for Ubuntu. Thanks, will check this out but have to wait two weeks for better time anyway so I may be better to do all this after OS upgrade. Correction: likely I haven't had this issue for so many years I remembered since I checked that I have been using geolocations extensively only for three years. It's possible that this problem actually is related to this 20.04 LTS distribution and digikam version, but can't definitely confirm that either. In any case, there is a possibility that the problem may have been fixed or that the performance is greatly increased. There were some commits by Justus Schwartz as an external author. This merge request as an example, read the description: https://invent.kde.org/graphics/digikam/-/merge_requests/139 Maik Looking to your system and version listed previously, all is very old now. This is not new from Ubuntu packaging which is weird at all. Also the new Snap bundle is really a worse. It work for simple and small applications, but with something like digiKam which require to access to host system to delegate operations, this is a very bad solution. For other Linux system which use FlatPak, It's the same. Bad design, no check of the real needs from applications developers. For ex, Kate editor team left this king of packaging, because it's impossible to run the application at all, or with to decrease the usability. This is why we started to work since many years now with AppImage bundle. It's more simple and do not limit at all the access to the host system, excepted if the user want to set this (it's the inverse with Snap and FlatPak and then...) The AppImage bundle host all the libraries for the application and is open to the system. All bundled libraries are _up_to_date_, compared to the Ubuntu stuff... AppImage is just a file to make executable and run. It decompress in memory a file system with a chrooted Linux hierarchy file system. Nothing is installed, only the application settings is written to your home directory, as the native version. AppImage is not perfect, it had few limitation, but at least, digiKam work as expected at 85% inside. The advantage to the bundle solution is that we update it every day with last changes performed in source code. It's very suitable to check step by step fixes and improvements. Voilà, as Maik said previously, before to run digiKam 7 instead 6, backup your database, as the internal schema is upgraded. If you go back to digiKam 6, a new database schema will not compatible. Best Gilles Caulier (In reply to Maik Qualmann from comment #11) > In any case, there is a possibility that the problem may have been fixed or > that the performance is greatly increased. There were some commits by Justus > Schwartz as an external author. This merge request as an example, read the > description: > > https://invent.kde.org/graphics/digikam/-/merge_requests/139 This fix has likely done the trick. Did quick test with 7.6.0 appimage version and map seems to be scrolling fine. Thanks both for your kind help! Digikam has been great app and nice to get this feature back. |