<br><br><div class="gmail_quote">On Sat, Mar 7, 2009 at 11:15, Yves-Alexis Perez <span dir="ltr"><<a href="mailto:corsac@debian.org">corsac@debian.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On mer, 2007-07-18 at 13:39 +0200, Javier Kohen wrote:<br>
> Using GConf Editor I clicked on "remove entry" (translating the label<br>
> from Spanish) for key /desktop/gnome/interface/monospace_font_name . The<br>
> old and new values were Monospace 10 (in other words, the value didn't<br>
> change).<br>
><br>
> Evolution crashed as soon as I triggered that action. Its window was in<br>
> a different workspace, so no direct user interaction took place.<br>
><br>
Does this still happen in recent evo in unstable and/or experimental. It<br>
seems that there were quite a few reports about “invalid memory<br>
reference” around 2.10.1 time. So maybe it was something related to the<br>
lib states at that time.</blockquote><div><br>To be honest I don't know. I migrated away from Evolution about a year ago, and I don't remember anything related to this issue.<br><br>I guess you can close it.<br><br>
Thanks a lot!<br></div></div><br>