Sounds like Maemo Mapper should try to reset the connection if/when it starts receiving continues G_IO_STATUS_ERROR errors. A bit of a hack, but this issue will likely disappear with Maemo Mapper v2.0, which is hopefully coming soon.

In the meantime, you can edit the code to do that yourself, if you like. Just call rcvr_disconnect() and rcvr_connect_later() when Maemo Mapper encounters one (or maybe a few in a row) G_IO_STATUS_ERROR errors.