Bug 447013 - No Local/.marble/plugins were loaded
Summary: No Local/.marble/plugins were loaded
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Geolocation-Marble (show other bugs)
Version: 7.4.0
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-12-15 07:09 UTC by HJ
Modified: 2022-01-04 08:41 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In: 7.5.0
Sentry Crash Report:


Attachments
errormessage (11.31 KB, image/png)
2021-12-15 07:09 UTC, HJ
Details

Note You need to log in before you can comment on or make changes to this bug.
Description HJ 2021-12-15 07:09:54 UTC
Created attachment 144566 [details]
errormessage

SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. A month ago, I updated the W10 with all the user programs reinstalled.
2. When opening the R-side map .marble or Edit Geolocation menu, the added error message is displayed

OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 Maik Qualmann 2021-12-15 12:50:35 UTC
The Marble plugins were previously expected under C:\Program Files\digiKam\plugins. Now Marble expects this one directory higher in the install root. I think I can remember a change in the MXE script.

Maik
Comment 2 caulier.gilles 2021-12-15 13:00:34 UTC
Hi Maik,

A change in bash script to build Windows installer or to build and install Marble in MXE bundle ?
Comment 3 Maik Qualmann 2021-12-16 07:07:26 UTC
It was that change, but it has nothing to do with where Marble is now looking for its plugins. 

https://invent.kde.org/graphics/digikam/-/commit/69ca750d29f1f37b1fa6dfce8c096ac963da7087

Maik
Comment 4 Martin P. 2021-12-17 16:46:22 UTC
Same here on Windows 11. Release changed to 7.4.0 as 7.5.0 seems to be a mistake.
Comment 5 Maik Qualmann 2021-12-17 19:34:01 UTC
Git commit 52ad002257e286225bc32edfb85633ab4daf7769 by Maik Qualmann.
Committed on 17/12/2021 at 19:33.
Pushed by mqualmann into branch 'master'.

just a workaround for the Marble plugins

M  +5    -0    project/bundles/mxe/installer/digikam.nsi

https://invent.kde.org/graphics/digikam/commit/52ad002257e286225bc32edfb85633ab4daf7769
Comment 6 Maik Qualmann 2021-12-17 19:35:57 UTC
This is just a first workaround to get the daily Windows build working again. The plugins are currently available twice in the installer and installed system. 

Maik
Comment 7 Maik Qualmann 2021-12-18 08:09:37 UTC
@Gilles,
It looks like MXE now needs the same patch for Marble as the AppImage.

Maik
Comment 8 caulier.gilles 2021-12-18 08:18:37 UTC
You want mean this one : https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/3rdparty/ext_marble/marble-libs-install-appimage.patch

Other point : currently we use Marble version 21.04.3. It an old version, perhaps this point is not necessary with last version 21.12.0, typically near to master code from git : https://invent.kde.org/education/marble

Gilles
Comment 9 Maik Qualmann 2021-12-18 15:57:26 UTC
I think the best way for the bundles is to assign the path to the plugins and maybe also to the datas with this function MarbleDirs::setMarblePluginPath() and not to patch it.

Maik
Comment 10 hardy.public 2021-12-18 17:32:45 UTC
Same here but I get the message on every launch of digiKam with the splash screen, not just Geolocation editor.
Comment 11 Maik Qualmann 2021-12-18 20:04:22 UTC
Git commit 2c063bbd23f59c9a5fc91e2463a0b930888f2851 by Maik Qualmann.
Committed on 18/12/2021 at 20:03.
Pushed by mqualmann into branch 'master'.

set Marble plugin path under Windows

M  +11   -1    core/utilities/geolocation/geoiface/backends/backendmarble.cpp
M  +0    -5    project/bundles/mxe/installer/digikam.nsi

https://invent.kde.org/graphics/digikam/commit/2c063bbd23f59c9a5fc91e2463a0b930888f2851
Comment 12 Maik Qualmann 2021-12-23 20:15:20 UTC
The problem of loading the Marble plugin has been fixed with the pre-release version of digiKam-7.5.0 from December 23, 2021.

https://files.kde.org/digikam/

Maik
Comment 13 Martin P. 2022-01-03 19:13:06 UTC
(In reply to Maik Qualmann from comment #12)
> The problem of loading the Marble plugin has been fixed with the pre-release
> version of digiKam-7.5.0 from December 23, 2021.
> 
> https://files.kde.org/digikam/
> 
> Maik

Thanks for the info.

But will there be an updated build of 7.4.0 for Windows? I usually don't use beta or prerelease software so I'm stuck on digiKam 7.3.

Martin
Comment 14 caulier.gilles 2022-01-03 20:01:14 UTC
Hi,

The 7.5.0 pre-release is safe. A large bugs triage was done, a major i18n update, and plenty of small fixes. No main changes have been introduced.

We plan to release 7.5.0 in a few weeks, if all works as expected.

So , you can use 7.5.0 pre-release safety, available at this url : 

https://files.kde.org/digikam/

Note : for Windows, you can use the XZ archive including all files. Uncompress the archive where you want and run digikam.exe. Like this, no needs to uninstall the official release.

Best

Gilles Caulier
Comment 15 Maik Qualmann 2022-01-03 20:01:49 UTC
No, there will be no updated digiKam-7.4.0. Alternatively, with a digiKam-7.4.0 installation, you can copy/move the DLL files from C:\Program Files\digiKam\plugins\*.dll   --to-->   C:\Program Files\digiKam\

Maik
Comment 16 Martin P. 2022-01-04 07:29:13 UTC
(In reply to caulier.gilles from comment #14)
> Hi,
> 
> The 7.5.0 pre-release is safe. A large bugs triage was done, a major i18n
> update, and plenty of small fixes. No main changes have been introduced.
> 
> We plan to release 7.5.0 in a few weeks, if all works as expected.
> 
> So , you can use 7.5.0 pre-release safety, available at this url : 
> 
> https://files.kde.org/digikam/
> 
> Note : for Windows, you can use the XZ archive including all files.
> Uncompress the archive where you want and run digikam.exe. Like this, no
> needs to uninstall the official release.
> 
> Best
> 
> Gilles Caulier

The Breeze icon theme seems to be broken in this build (3.1.2022). Whatever I switch to I always get dark icons...

Regards
Martin
Comment 17 Maik Qualmann 2022-01-04 08:41:35 UTC
Yes, the display of the icons are broken at the moment. We have updated the KDE libraries KF5. An auto icon color scheme feature has been added. It's a nice thing under a KF5 Plasma Desktop, the icons adapt to the color scheme immediately when they change. Since we are only using part of KF5 under Windows, we are now missing something. We are already looking for a solution.

Maik