This is driving me nuts. Is there any more info I can add that will help track this down? I've attached a spreadsheet for testing that seems to be usable for triggering the crash.
Here's what I did: steps to reproduce: 1 open the doc 2 start gdb in a terminal (gdb) 3 attach gdb to this process (attach processid) 4 continue process (continue) 5 filter column a to y 6 select and delete the two rows containing y 7 filter column a to -all- 8 see rows haven't gone (weird) 9 scroll down and up to get screen to update 10 observe crash The doc contains the following data and an auto-filter applied: n a 1 x 2 x 3 y 4 x 5 y 6 x 7 x 8 x 9 x 10 x The output from gdb is below: (gdb) continue Continuing. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread -1249769792 (LWP 20992)] 0xb04f533c in ?? () from /usr/lib/openoffice/program/libsc680li.so (gdb) q The program is running. Quit anyway (and detach it)? (y or n) y Detaching from program: /usr/lib/openoffice/program/soffice.bin, process 20992 ** Attachment added: "document to use for reproducing the crash" http://launchpadlibrarian.net/12763121/test.ods -- spreadsheet crashes when deleting rows https://bugs.launchpad.net/bugs/123335 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
