I use MARBLE and the OSM tiles on a mobile device. After I have updated to version 1.5 I noticed, that all maps a lost. I noticed also, that reqires 100% Processor load in a dual core system with Win7. Reproducible: Always Steps to Reproduce: 1. change the "expire" value in the dgml file, it has no effect 2. at a other PC with WinXP and MARBLE Version 1.41 there is only a processor load of about 20% and no map tiles will be deleted. 3. I have also a MARBLE Installation under OpenSuse Linux (MARBLE Version 1.3.4), it also does not show these bad habits Actual Results: see above Expected Results: no deleting of map tiles when a high "expire" value is given instead that older map tiles will be deleted it shoulld only overwritten by newer ones I belive it is a bug of version 1.5
I just re-installed Version 1.4.1 on Win7 PC, it shows the same bad habit as Version 1.5.
I spent further time to find out the reason of this behaviour. I installed Version 1.5 on a fresh installed WIn8 PC. Marble deas not show the reported bad behaviour. Next I deinstalled Marble from the Win7 PC. I removed all Marble files and cleaned the Registry. Then I installed Version 1.5 again and copied about 1 GByte of OSM tiles back into the ...\AppData\Roaming\.marble\data\maps\earth\... path. Now Marble works acceptable. That mean it refreshes older OSM tiles only (not deleting all OSM tiles). Conclusion: the bad behaviour requires a complete cleaning of the PC, a re-installation is not sufficient! The De-Installition program of Marble works not efficient :-(( By the way I revealed an other curious effect: I removed in both installations the unwanted maps in 'programs'\Marble\datamaps\earth\... In tthe fresh Win8 installation the deleted maps disappered, in the cleaned Win7 installation the deleted maps still visible as grey pictures. I have no idea where the the information of the deleted maps remains.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!