Based on version info you got this with bzr-explorer 1.1.2. Does this problem still exists in the latest explorer release?
Based on version info you got this with bzr-explorer 1.1.2. Does this problem still exists in the latest explorer release?