Bug 386874 - Cursor changes to forbidden symbol when dragging picture(s) to map
Summary: Cursor changes to forbidden symbol when dragging picture(s) to map
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-Generic-GeolocationEdit (other bugs)
Version First Reported In: 5.7.0
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-13 21:40 UTC by silvanociru
Modified: 2017-11-14 20:58 UTC (History)
2 users (show)

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

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description silvanociru 2017-11-13 21:40:01 UTC 
When I drag one or more pictures to a map (no matter if Marble Virtual Globe or Google Maps) the mouse cursor changes to an arrow with a small forbidden/prohibited symbol next to it and no click (neither left nor right) generates a reaction. The only possibility to restore the normal mouse cursor is pressing the Escape key.

I've tried different combinations and the result is the same.

This is the output in the console when starting Digikam from the command line:

digikam.geoiface: Loading GPS bookmarks from "/home/silvavlis/.local/share/digikam/geobookmarks.xml"
digikam.geoiface: "setting backend marble"
digikam.geoiface: "HYBRID"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "backend marble is ready!"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "marble:900"
digikam.geoiface: 900 3500 900
digikam.geoiface: "backend marble is ready!"
digikam.geoiface: 900 3500 900
digikam.geoiface: 900 3500 900
digikam.geoiface: "marble:900"
digikam.geoiface: 900 3500 900
digikam.metaengine: DateTime => Exif.Photo.DateTimeOriginal =>  QDateTime(2017-08-20 15:28:19.000 CEST Qt::TimeSpec(LocalTime))
digikam.geoiface: ----
digikam.general: 0 1
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0 searched)"
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0 searched)"
digikam.geoiface: "level 5: 0 non empty tiles sorted into 0 clusters (0 searched)"
Comment 1 Maik Qualmann 2017-11-13 21:45:28 UTC 
There is already a workaround for this problem in digiKam-5.8.0. Question: Which Qt version is used? I close this bug.

Maik
Comment 2 silvanociru 2017-11-14 20:47:13 UTC 
(In reply to Maik Qualmann from comment #1)
> There is already a workaround for this problem in digiKam-5.8.0. Question:
> Which Qt version is used? I close this bug.
> 
> Maik

Thank you!

I'll then wait for digikam-5.8.

The Qt version being used is 5.
Comment 3 caulier.gilles 2017-11-14 20:58:18 UTC 
You can already try the 5.8.0 pre-version through the bundle that we share here :

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

Gilles Caulier