Hello, I reported a bug I found in https://pharo.fogbugz.com/default.asp?10849_d0g95e46s78671vi The issue was closed in fogbugz. I couldn't really figure out why, until I looked at Penelope to find out that bug was considered a duplicate. I had a hard time finding that information and the information on the duplicate (I could figure it out yesterday night, but can't reproduce the way to find the information today). From what I understood yesterday, this bug is supposed to be fixed in Pharo-3.0? The images that are offered for downloading seem to all include this bug. I have a notebook with ubuntu-13.04 and 8GB RAM, of which around 7GB are used for hard disk caching. As far as I understood from reading the bug tracking entries, heavy caching triggers the bug earlier? Anyhow, with this bug, the changes file gets garbaged (or, at least, the pointers to it) and the image is unuseable. Abandoning the RemoteString error message looks to the user as if the issue wasn't all that bad, but is a nuclear attack on the image soon to come. Correct me if I am wrong please. About issue tracking: is the process closed to the public on purpose? I have to admit I misused the google code bugtracker in the past, because I reported an incident from the user point of view and later learned, that the bug reporting & fixing process was meant to be used only from a developers perspective. When I have a "user" issue - am I supposed to report to the mailing list instead and an issue will be created by the pharo core team? Kind regards, Markus