Bug 159273

Summary: OO Calc dies on "Save As..." with new file
Product: [Fedora] Fedora Reporter: Bryn M. Reeves <bmr>
Component: gnome-vfs2Assignee: David Zeuthen <davidz>
Severity: high Docs Contact:
Priority: medium    
Version: 3CC: caolanm, mclasen
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-06-01 11:09:50 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
Bugbuddy backtrace from the oocalc crash none

Description Bryn M. Reeves 2005-06-01 10:33:21 UTC
Description of problem:
New oocalc release dies when selecting "Save As" for a new spreadsheet. The
error message when run in a terminal indicates an assertion failure in the
gnome-vfs code:

end from FAM server connection
failed to read() from server connection

libgnomevfs-ERROR **: file gnome-vfs-cancellation.c: line 133
(gnome_vfs_cancellation_cancel): assertion failed: (gnome_vfs_is_primary_thread())

The FAM related messages also appear when this problem is not manifested.

Version-Release number of selected component (if applicable):

How reproducible:
Happens more than 9 times out of 10. If I sit here running oocalc in a shell
loop, every now and again it will start to work. I can't see any obvious
diference between the app/system state between the failures and successes. Have
not been able to test on another system yet. 

Steps to Reproduce:
1. Start oocalc (from panel icon or terminal) 
2. Select "File" -> "Save As"

Actual results:
Application terminates.

Expected results:
Application opens "Save As" dialogue.

Additional info:
Seems like this might be related to BZ151558.

Comment 1 Bryn M. Reeves 2005-06-01 10:33:21 UTC
Created attachment 115019 [details]
Bugbuddy backtrace from the oocalc crash

Comment 2 Caolan McNamara 2005-06-01 11:09:50 UTC

*** This bug has been marked as a duplicate of 144607 ***