Oh yes, that was a bug in one of the versions. It happened because you had two simultaneous quests for this location. What version are you running now?
Versión 0.5.2
Oh, this was fixed in version 0.5.5. You'll either need to wait for its public release or load an earlier save (check the Autosaves tab).
