abrt 1.1.1 detected a crash.
Attached file: backtrace
cmdline: ssindex -i /home/Donald/Documents/ecology/SOD/bayareaplots/SODmortality.xls
comment: I installed a large number of packages, but Gnumeric had been installed beforehand with no crashes. I rebooted, logged into Gnome, and started working. ABRT has announced two Gnumeric crashes in the last three hours. As it happens, I did use Gnumeric during this session, but one of the crashes was before I opened Gnumeric and the other crash was after I had closed Gnumeric. Something seems to be trying to index spreadsheets. I did install Beagle, but I uninstalled it after it started causing mono-core crashes ( I filed a bug report for that, too). I have not yet rebooted since I uninstalled Beagle, so maybe it's still working.
reason: Process /usr/bin/ssindex was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
1. It seems to reproduce itself.
Created attachment 429224 [details]
Gnumeric 1.10.9 is about to hit testing updates in a couple of days. Can you please retest if this is still a problem?
Yes, this is still an issue. I had not seen the bug since the day I found it, but in response to your query I tried reinstalling Beagle. Sure enough, after rebooting and working for a while, the crash happened again. I reported it and Bugzilla created a new bug: 626641.
*** Bug 626641 has been marked as a duplicate of this bug. ***
Sorry I was not specific enough. Please retest with gnumeric-1.10.9-1.fc13. It was pushed to testing today, you can install it with:
yum --enablerepo=updates-testing update gnumeric
you can also try new goffice too:
yum --enablerepo=updates-testing update goffice
Again, sorry for the confusion.
This morning I installed the gnumeric and goffice updates from the testing repository. I worked in Gnome for a while this morning, and then again this afternoon. This afternoon I used gnumeric to edit a spreadsheet. I did not see a crash at any point today. As far as I can tell, it's fixed!