[Dapper] mailcap race condition

[Dave Gilbert]

I'm using mutt and in my .mailcap I had:

application/msword; ooffice %s

I'm finding on dapper that I get word documents displayed corrupted
when displayed out of mutt but fine on the command line.

I think I've tracked this down to the fact that mutt deletes the /tmp file
it creates when the binary returns and thus there is a race where
ooffice starts, spawns off the app (which reads the file) but in the mean time the ooffice
returns and mutt deletes the /tmp

I can't see what a neat solution to this is - I don't want to make mutt just take copies of the file
and pollute my /tmp.
If I call /usr/lib/openoffice/program/swriter in the mailcap then it works - but that also seems messy.
It feels like ooffice should have a flag for 'delete this temporary when you are done' or the like?

Note: the original reporter indicated the bug was in package 'openoffice'; however, that package was not published in Ubuntu.

[Andrew McCarthy (andrewmccarthy)]

Confirmed. Can somebody please raise the importance? I think this is definitely more than a "wishlist" report. Thanks!

[Mariano Mara (marplatense)]

This is still happening in Hardy Heron. Any news regarding this issue?