| Summary: | Geolocation: Severe rendering problems of map/satellite view | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | wuselwu <einmaladresse_2> |
| Component: | Geolocation-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | major | CC: | caulier.gilles, mike |
| Priority: | NOR | ||
| Version: | 2.4.1 | ||
| Target Milestone: | --- | ||
| Platform: | openSUSE | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 2.6.0 | |
| Sentry Crash Report: | |||
| Attachments: |
One more panning movement, and the map will be drawn again...
Short test run of Digikam only doing some geolocation stuff |
||
Additional note: Contrary to above, marble widget seems to work better, the google maps part is broken. Hi Larx, thank you for reporting this issue! I have no idea what may be causing it right now. - Can you please test whether Google Maps works fine in Konqueror? - Maybe there is a JavaScript bug occurring somewhere. Please check the status bars of the GPSSync dialog and digikam for a little red bug which is Konqueror's JavaScript error window button. It only appears for some JavaScript errors, not all of them. - Finally, debug output of digikam may be helpful. Please start digikam from a konsole: digikam 2>logfile.txt This causes any debug messages emitted by digikam to be written to logfile.txt, which you can then post here. Best regards, Michael Started Konqueror for the first time in years ;). Google Maps, both satellite and roadmap view, working fine there. There is no little red bug appearing somewhere. I'll look in the debug output later. One more link to a similar problem by another user (no reply yet): http://lists.opensuse.org/archive/opensuse-kde/2012-01/msg00241.html Created attachment 68007 [details]
Short test run of Digikam only doing some geolocation stuff
As far as I can judge it, the logfile does not seem to contain relevant info. I started Digikam, selected a few pics and did some geolocation stuff with them. The bug I described occured during this small exercise, as it does all the time.
In the current 2.5-version, the one remaining problem is that the scroll wheel does not work for zooming in the Google Earth view. No more rendering problems, so I'll close. |
Created attachment 67987 [details] One more panning movement, and the map will be drawn again... Version: 2.4.1 (using KDE 4.7.4) OS: Linux I have this problem since a few months, thus I cannot pinpoint the first time it occured. However, it occurs in different openSUSE incarnations (11.4, 12.1, Factory, Tumbleweed) and since Digikam 2.3, I think. The geolocation widget is unusable because of rendering problems in the map display. I also attach a picture to illustrate the problem, it's the same if using Google Maps, Marble or a satellite view. Graphics drivers are current versions of AMD Catalyst, if that's of relevance. Reproducible: Always Steps to Reproduce: When doing anything that would move around the display (panning, selecting different photos in the listview, etc.) chances are nearly 100% that this won't work, but the areas which should be drawn anew are simply blank. It's reproducable: If I select a picture that requires a completely different map section to be drawn, this will work most of the time. But: If only a partial redraw of the map is necessary, this won't work and the section which should be drawn anew are blank. If I use the arrows to pan around in the map, the map will be OK once again as soon as I have completely moved out of the previously displayed map section. So in the attached screenshot, which is almost completely blank, I will have to move one more step to be completely out of the area which has been rendered in the first place, and the map will be OK again. Panning around by simply clicking into the map an dragging does not work at all. And, maybe related: Sometimes geolocating pictures by dropping them into the picture does not work at all. They "fall down" out of the picture and are located somewhere south of the area the map displays. Yes, the pins are really and animatedly "falling down", which is very strange. Actual Results: See text above. Expected Results: See text above.