abrt 1.0.3 detected a crash. Comment: Was working on Calc. Doing a s imple spreadsheet. Either navigating, editing or copying some cells. Calc crashes so hard it just disappears Attached file: backtrace cmdline: /usr/lib/openoffice.org3/program/swriter.bin -writer component: openoffice.org executable: /usr/lib/openoffice.org3/program/swriter.bin kernel: 2.6.31.12-174.2.3.fc12.i686.PAE package: openoffice.org-writer-1:3.1.1-19.14.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault)
Created attachment 386972 [details] File: backtrace
If I read the stack correctly, you wrote '=' to the input line, that trigerred an a11y event and then something in UNO dispatch went wild. I tried that with sample spreadsheet, but there was no crash and valgrind didn't show any problem either. I don't really understand the internals of UNO dispatching mechanism (and I'm not sure I want). Maybe Caolán will be able to shed some light on this.
Its an odd one. Clearly a11y related, and related to setting text to the ScPosWnd with FillFunctions which happens when editing/entering a formula. I can't imagine that the recurse to death afterwards is a bug of the uno->cpp bridge or anything like that, I feel the object at the top of that recurse must be busted somehow. That said, just entering some formulas and so on when a11y enabled doesn't do anything horrible for me. It does spit out various "Invalidate all children called" and various "Focused object has invalid index in parent" when expanding the dropdown of the ScPosWnd, but no crash death.
Its happened about 3 times on my side. But I'm never in a position to remember what I was doing. So I'm not really able to even try reproduce :(
Its definitely a11y related, so it can be avoided by disabling gnome's a11y from the desktop menus. Clearly it would be better to reproduce it and fix it, but I'd need to be able to reproduce it. If anyone knows how to get it to happen, feel free to reopen with that information.
*** Bug 569715 has been marked as a duplicate of this bug. ***
*** Bug 598201 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 626836 ***