Depends on KML file marble crashes or it happens nothing. Reproducible: Always Steps to Reproduce: 1. Go to Bookmarks / Manage Bookmarks / Import Bookmarks 2. Choose a file 3. OK Actual Results: Crashes with Executable: marble PID: 3997 Signal: Segmentation fault (11) Time: 03.09.15 12:53:09 Or it happends nothing Expected Results: Import my Bookmarks (KML file) I find this by very important. I use this free software because i can manage and sync my private bookmarks. I wouldn't use it without bookmark functional. I would glad to append the kml files but it seems to be not possible here. I can send them per mail
*** This bug has been marked as a duplicate of bug 316969 ***
(In reply to Dennis Nienhüser from comment #1) > > > *** This bug has been marked as a duplicate of bug 316969 *** It's not a dublicate of bug 316969. Marble don't crash, it do nothing by import
I still think it's a duplicate of bug 316969. The reason is likely that the imported placemarks are deleted when the bookmark file goes out of scope. This can lead to a crash, but it does not have to.
Thank you for the report. As it has been a while since this was reported, can you please test and confirm if this issue is still occurring or if this bug report can be marked as resolved. I have set the bug status to "needsinfo" pending your response, please change back to "reported" or "resolved/worksforme" when you respond, 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!