abrt version: 1.1.13 architecture: x86_64 cmdline: /usr/lib64/openoffice.org3/program/scalc.bin -calc file:///home/dswift/Jobs/Intersystems/Q5146-Intersystems-Glasgow/90-WIP/IntersystemsGlasgow-Inconsistencies.xls component: openoffice.org crash_function: __poll executable: /usr/lib64/openoffice.org3/program/scalc.bin kernel: 2.6.32.21-168.fc12.x86_64 package: openoffice.org-calc-1:3.1.1-19.34.fc12 rating: 4 reason: Process /usr/lib64/openoffice.org3/program/scalc.bin was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine) time: 1287396771 uid: 500 backtrace ----- [New Thread 8058] [New Thread 8059] [New Thread 8060] [New Thread 8061] [New Thread 8062] warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/79/54845c1b360b0d9d2562a1c4f67d2baea60f66.debug": separate debug info file has no debug info Core was generated by `/usr/lib64/openoffice.org3/program/scalc.bin -calc file:///home/dswift/Jobs/Int'. Program terminated with signal 11, Segmentation fault. #0 0x000000350ac35a18 in GetItem (this=0x18d3e00, cTyped=<value optimized out>) at ../../../inc/patattr.hxx:82 82 ../../../inc/patattr.hxx: No such file or directory. in ../../../inc/patattr.hxx Thread 6 (Thread 8062): #0 0x0000003e010d5353 in __poll (fds=<value optimized out>, nfds=<value optimized out>, timeout=<value optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87 Timeout exceeded: 60 second, killing gdb How to reproduce ----- 1. Editing a simple spreadsheet. 2. Copied and pasted a single formatted column from an .xls open in OpenOffice. 3. Editied the column, continued to edit the other fields on a single sheet 4. Edits included, change font & size, merge fields, insert columns and rows 5. Application froze (<10 seconds) then crashed.
Created attachment 454093 [details] File: backtrace
Err, are you able to reproduce this from scratch. Or with a specific spreadsheet. I mean, you describe quite a few operations, and the goal is for me to be able to get it to crash in the same way, which I'm unable to currently do.
Thanks for the quick response. It hasn't crashed again since I reported it. I'm not certain of the exact set of actions I used to build the spreadsheet, so I'm fairly certain I could not repeat it. If you can't get anything from the abrt report then I would suggest closing it as unrepeatable. Thanks Dylan
Pity, well if you figure out how to get it to happen feel free to reopen this with the extra information