Bug 301064 - async task UI persists on leaving geolocation UI
Summary: async task UI persists on leaving geolocation UI
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: ProgressManager-Usability (show other bugs)
Version: 2.6.0
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-06-02 16:32 UTC by jon33040
Modified: 2022-02-05 15:59 UTC (History)
1 user (show)

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


Attachments
picture of screen showing unwanted UI dialogs (263.46 KB, image/jpeg)
2012-06-02 16:35 UTC, jon33040
Details

Note You need to log in before you can comment on or make changes to this bug.
Description jon33040 2012-06-02 16:32:12 UTC
I go into the geolocation UI. Add locations to some pictures. Click "apply" and then close the UI.
When I exit, two of the async task UIs appear in the bottom right corner of the main window. Both have the words "GPS sync" in them. One showing 100%, the other showing 0%. The indicator below them is moving from left to right and back but neither of the async task UIs updates. 
- If I go back to add locations to some more pictures, I get two more of these each time I leave the geolocation UI - progressively taking up more and more of the digikam window.
- If I click on the moving indicator below them, they vanish. Next time I exit the geolocation UI, digikam sometimes crashes.

Reproducible: Always

Steps to Reproduce:
1. Go into the geolocation UI
2. Add a location to an image
3. apply
4. close
Actual Results:  
See attached picture.
Comment 1 jon33040 2012-06-02 16:35:28 UTC
Created attachment 71516 [details]
picture of screen showing unwanted UI dialogs
Comment 2 jon33040 2012-06-02 16:36:59 UTC
Here's the components information for this build of DK.
digiKam version 2.6.0-beta3
Exiv2 can write to Jp2: Yes
Exiv2 can write to Jpeg: Yes
Exiv2 can write to Pgf: Yes
Exiv2 can write to Png: Yes
Exiv2 can write to Tiff: Yes
Exiv2 supports XMP metadata: Yes
LibCImg: 130
LibClapack: internal library
LibExiv2: 0.22
LibJPEG: 62
LibJasper: 1.900.1
LibKDE: 4.7.4 (4.7.4)
LibKExiv2: 2.3.0
LibKGeoMap: 2.0.0
LibKdcraw: 2.1.0
LibLCMS: 119
LibLensFun: external shared library
LibLqr: internal library
LibPGF: 6.11.42 - internal library
LibPNG: 1.2.46
LibQt: 4.7.4
LibRaw: 0.14.5
LibTIFF: LIBTIFF, Version 3.9.5 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc.
Marble Widget: 0.12.2 (stable release)
Parallelized demosaicing: Yes
Database backend: QSQLITE
LibGphoto2: 2.4.13
LibKface: 2.0.0
LibKipi: 1.6.0
LibOpenCV: 2.1.0
Libface: 0.2
Comment 3 jon33040 2012-06-02 16:51:55 UTC
I've tried upgrading from beta 3 to the RC but the RC tarball won't compile on this system.

home/jon/src/digikam_and_dependencies/digikam-software-compilation-2.6.0-rc/extra/libkface/libkface/kfaceutils.cpp:48:39: fatal error: opencv2/highgui/highgui_c.h: No such file or directory                                               
compilation terminated.
make[2]: *** [extra/libkface/libkface/CMakeFiles/kface.dir/kfaceutils.cpp.o] Error 1
make[1]: *** [extra/libkface/libkface/CMakeFiles/kface.dir/all] Error 2
make: *** [all] Error 2
Comment 4 caulier.gilles 2012-06-02 17:52:45 UTC
Your opencv library installation is uncomplete...

Gilles Caulier
Comment 5 jon33040 2012-06-03 11:31:35 UTC
After a lot of fighting library and package dependency conflicts, I have the RC built. I've used the RC enough now to confirm that this bug has gone away.
Comment 6 caulier.gilles 2019-12-29 04:55:40 UTC
Not reproducible with 7.0.0 beta 1.