| Summary: | Digikam and Marble (black map on digikam) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Olivier Placais <olivier.placais> |
| Component: | RPM Packages | Assignee: | Angelo Naselli <anaselli> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | anaselli, caulier.gilles, marja11 |
| Version: | 6 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | digikam | CVE: | |
| Status comment: | |||
| Bug Depends on: | 21408 | ||
| Bug Blocks: | |||
|
Description
Olivier Placais
2017-07-30 08:28:54 CEST
Assigning to the registered maintainer of digikam CC:
(none) =>
marja11 i committed a possible fixing in cauldron, please review it and if ok we can do it also into mga6 branch.
Marja Van Waes
2017-08-02 23:24:02 CEST
CC:
(none) =>
caulier.gilles To use Marble map in digiKam, the Marble data package (including all local map files) must be installed. It work perfectly here with digiKam 5.6.0. Gilles Caulier @Gilles i added marble to kipi-plugins-geolocator but i saw no differences, so i need to understand if it is another package that is needed and if that dependency is for that plugin or digikam itself. Thanks Gilles hmm my fault that plugin is not built. Could someone try cauldron version if ok? Problem reproducible here with MGA6 official. Reason : Marble map data files are not installed with libmarble. If you install marble application, all work fine in digiKam. The map data files are in marble RPM, not in libmarble. libmarble cannot work at run time if map data files are not present. It show a black hole silently. Digikam of course use libmarble... Gilles Caulier submitted mga6 core testing Hi, I just try an update of digikam on Mga6 with "core testing" and it work fine. Marble is ok in digikam and i see my picture on the map. Olivier
Angelo Naselli
2017-08-13 19:17:21 CEST
Status:
NEW =>
ASSIGNED Suggested advisory: ======================== digikam missed marble dependency to work properly. This update fixed this issue. Updated packages in core/updates_testing: ======================== digikam-5.5.0-2.1.mga6.x86_64.rpm lib64digikamdatabase5-5.5.0-2.1.mga6.x86_64.rpm lib64digikamgui5-5.5.0-2.1.mga6.x86_64.rpm lib64kf5kipiplugins5-5.5.0-2.1.mga6.x86_64.rpm lib64digikamcore5-5.5.0-2.1.mga6.x86_64.rpm lib64digikam-devel-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-imageshackexport-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-remotestorage-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-imgurexport-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-sendimages-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-dropbox-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-jalbum-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-smug-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-facebook-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-kmlexport-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-vkontakte-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-flashexport-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-piwigo-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-wikimedia-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-flickr-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-printimages-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-yandexfotki-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-googleservices-5.5.0-2.1.mga6.x86_64.rpm kipi-plugins-rajceexport-5.5.0-2.1.mga6.x86_64.rpm showfoto-5.5.0-2.1.mga6.x86_64.rpm Source RPM: digikam-5.5.0-2.1.mga5.src.rpm
Angelo Naselli
2017-08-13 19:18:00 CEST
CC:
(none) =>
anaselli ehm Source RPM: digikam-5.5.0-2.1.mga6.src.rpm Why a devel rpm for digiKam ? there is no header files to share since a while, as all image editor plugins have been integrated in digiKam core as tools not shared... Gilles Caulier so link files i think... but i just rebuilt Nicolas adding new dependencies work :) Two bugs, one package Angelo. Can you choose one, set blocks and update the advisory for both issues.
Angelo Naselli
2017-08-13 21:59:50 CEST
Depends on:
(none) =>
21408 De-assigning from QA so that it doesn't show twice in the QA list. The fix for this issue should be documented as part of the advisory for bug 21408. Assignee:
qa-bugs =>
anaselli Fixed by the update for bug 21408, which is about to be pushed. Resolution:
(none) =>
FIXED |