subject:"\[Issue 127929\] Possible crash in Freetype code"

[Issue 127929] Possible crash in Freetype code

2019-09-13 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 Peter changed: What|Removed |Added CC||apa...@resellerdesktop.de --- Comment #12 from

[Issue 127929] Possible crash in Freetype code

2019-08-18 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 Matthias Seidel changed: What|Removed |Added Target Milestone|4.2.0 |4.1.7 -- You are receiving this mail

[Issue 127929] Possible crash in Freetype code

2018-12-03 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 Peter changed: What|Removed |Added Target Milestone|--- |4.2.0 Version|4.2.0-dev

[Issue 127929] Possible crash in Freetype code

2018-12-01 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 mechtilde changed: What|Removed |Added Keywords||crash Priority|P5 (lowest)

[Issue 127929] Possible crash in Freetype code

2018-11-12 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 Andrea Pescetti changed: What|Removed |Added CC||pesce...@apache.org -- You are

[Issue 127929] Possible crash in Freetype code

2018-11-12 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #9 from Pedro --- > Sorry, this is *not* fixed in 4.1.6. > Unfortunately this patch was too late for the release in process... I meant that the patch worked in 4.1.6 and the problem was fixed. It is unfortunate that it wasn't

[Issue 127929] Possible crash in Freetype code

2018-11-11 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #8 from Matthias Seidel --- (In reply to Pedro from comment #7) > (In reply to Arrigo Marchiori from comment #4) > > > Please excuse me if the question is silly, but why did you mark it > > resolved-fixed if trunk is still affected? >

[Issue 127929] Possible crash in Freetype code

2018-11-11 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #7 from Pedro --- (In reply to Arrigo Marchiori from comment #4) > Please excuse me if the question is silly, but why did you mark it > resolved-fixed if trunk is still affected? I do not know if trunk is still affected. I could not

[Issue 127929] Possible crash in Freetype code

2018-11-11 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #6 from SVN Robot --- "mseidel" committed SVN revision 1846349 into trunk: i127929 - Fix for crash in Freetype code -- You are receiving this mail because: You are the assignee for the issue.

[Issue 127929] Possible crash in Freetype code

2018-11-11 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #4 from Arrigo Marchiori --- (In reply to Pedro from comment #3) > Thank you Arrigo Marchiori for fixing this crasher! You are welcome! Please excuse me if the question is silly, but why did you mark it resolved-fixed if trunk is

[Issue 127929] Possible crash in Freetype code

2018-11-11 Thread bugzilla

https://bz.apache.org/ooo/show_bug.cgi?id=127929 --- Comment #5 from Matthias Seidel --- Hi Pedro, Please do not set an issue to RESOLVED/FIXED before the patch is in the code. But we can leave it for now, as I plan to commit it to trunk soon... -- You are receiving this mail because: You