Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 41846 bytes cmdline: gnumeric component: gnumeric Attached file: coredump, 60272640 bytes crash_function: g_type_check_instance_is_a executable: /usr/bin/gnumeric-1.10.14 kernel: 2.6.35.12-90.fc14.i686 package: gnumeric-1:1.10.14-1.fc14 rating: 4 reason: Process /usr/bin/gnumeric-1.10.14 was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1305221824 uid: 500 How to reproduce ----- 1. Attempted to save a CSV file to a remote machine over SSH 2. That failed (failed to reload directory contents) 3. Subsequent activity caused a crash
Created attachment 498602 [details] File: backtrace
terr
If this repeatable?
Not trivially. I repeated the steps (save local gnumeric document, save as remote csv document) without seeing an error. I strongly suspect that the failure to update the remote directory contents when attempting to save the remote document exposed the error path.
I note that thread 5 is in libc thread 4 is in pulse audio thread 3 is glib related thread 2 is gio related thread 1 is deep inside gio/gtkfilechooser The chances that this is caused by Gnumeric are pretty slim. We have no special code for ssh or any other non-local protocol -- we just pass it on to gio. However, I triggered the error path deliberately by write-protecting a directory and I see no valgrind events there.
Does the relevant gtk library contain the threading fixes discussed starting here... http://mail.gnome.org/archives/gtk-devel-list/2011-March/msg00101.html ?
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping