On Fri, 8 May 2026 16:38:25 +0200 Sebastiaan Couwenberg <[email protected]> wrote: > severity 1136020 important > notfound 1136020 merkaartor/0.20.0+ds-3
The initial report was by reproducing in unstable using 0.20.0+ds-3 but never mind. > Use JOSM, merkaartor might not be dead upstream just yet, but it's at > least terminally ill. JOSM has an awful interface, IMHO, but yes, merkaartor upstream isn't healthy. > You can still use it to open already downloaded OSM data, adjusting > severity accordingly. This was the clue I needed. A new user won't have any ready downloaded OSM data but the upstream bug report I linked to contained another clue. The change was to Preferences source code. I've confirmed that, once I was able to save a file, it can be reopened cleanly after removing the ~/.merkaartor/ directory to reset the Preferences. What is completely hidden from a new user is that the first action is not to click on download but to click on Tools|Preferences|Data and enter their active OSM username and password. *Then* a download proceeds, in both versions. If this had been apparent when I encountered the problem, I would never have filed the bug at such a severity. I'd have likely chosen 'minor'. On that basis, I think it would be useful to keep this bug open, at minor severity, and retitle it to something like: Fails if OSM login is not set in Tools|Preferences|Data before Download. I'm happy to do that, as long as that is OK with you. (Most users aren't going to check closed bugs when first reaching for reportbug and such a title would have helped me when considering filing this bug.) > > I have also been able to reproduce this in stable. > > > > The seg fault appears to be in OSMServer.cpp - > > Download failed: Invalid argument; > > So I'm suspecting the program is too old to use > > the current OSM API. > > (The release is 2 yrs old and no recent commits upstream.) > > Sounds like: #1118401 > The commit mentioned in that issue still hasn't found its way into a > new upstream release. Understood. > Perhaps we should just remove merkaartor from the archive, nobody > cares enough about the package to cherry-pick the upstream commit to > fix this issue. I understand the impulse to remove under these circumstances and, let me be blunt, I am in no position to take on the work of keeping merkaartor in Debian. So if removal is a likely result, I'm not going to oppose that. Merkaartor is a bit easier to use than JOSM, IMHO, but it's still much too complicated for my liking, even after downloading OSM data. It's aimed at surveyors not "ordinary" users, just like JOSM (and vespucci on mobile). I'm likely to stick with the OSM web browser interface and StreetComplete on mobile. Thanks for responding quickly. -- Neil Williams ============= [email protected] https://www.codehelp.co.uk/
