Hi, On Mon, Dec 31, 2012 at 02:14:33PM -0500, Jason Stephenson wrote: > I was able to reproduce it on 3.6.4 from experimental. However, it took > a great deal more effort, perhaps so much effort that it is not likely > to be triggered in normal use.
OK, good. Better than having it completely fixed, but still good. Now the question is whether we should close this bug or not... > I am attaching gdb log output for the crashed session. This time I > opened three odg documents and messed around with text fields for > several minutes before anything happened. I used the default font for > the text fields, Liberation Sans 18 in my case. > > Unless the back trace tells you something, then it may not be worth > pursuing if 3.6.4 is mostly working. I googled a bit for the second frame in the backtrace[1] and the only hit I got (except this bugreport) is https://bugzilla.redhat.com/show_bug.cgi?format=multiple&id=870792 which was reported against 3.5.6.. Regards, Rene [1] The first one seems to be broad and gives loads of old, fixed bugs (even in OOo 3.2 etc.)... -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
