KDE PIM

Bug #70981
Comment #7

Comment 7 for bug 70981

Revision history for this message

Andres Mujica (andres.mujica) wrote on 2007-03-28: Re: [Bug 70981] Re: OO attachment won't open in Kmail

Well, what i've learned is that almost every tiem i try to open an OO
attachment from kmail, i must try several times as faster as i can and it
finally opens.

If the attachment has ñ ò ì type characters it won't open at all, but this is
part of another bug.

BUT.. as i mentioned earlier on this bug report i've noticed this:

I clic to open the OO attachment file

OO throws a file not found error pointing to the non-existant file

/tmp/kde-andres.mujica/call flow II.xls_[yJLETA].xls

but if i check at /tmp i've found the file here:

/tmp/kde-andres.mujica/kontactb74dfa.5/call flow ii.xls

even if i clic on openoffice ok to accept the error.

If the gods are with me and the file opens, it appears to be opened
from /tmp/kde-andres.mujica/call flow II.xls_[vutiJA].xls

and surpringsily for me , the file is not there!!!! haven't noticed this....

that's what i can tell about this.

If you've got any ideas of a formal check or some debug that i can do in order
to help solve this bug i would be glad to do it.

Sometime ago i've triied to find something similar upstream without success..
so maybe we'rea alone on this one.

Regards!

El Miércoles, 28 de Marzo de 2007 15:04, Matthew Carpenter escribió:
> I believe this has to do with the hand-off from Kmail to OOo, to the
> component of OOo handling the attachment. Kmail hands off to OOo, and
> when OOo exits (or the file is not opened? - lsof style), it deletes the
> file in /tmp. While this is a fine approach for most apps, OOo probably
> does some internal hand-off which delays loading of the temporary
> attachment. Kmail deletes the file, thinking that it's job is done, but
> the OOo component app never had a chance to open it.
>
> This has been an issue for some time. Can we get it resolved? Kmail
> should either hand off to a different component, or (mo betta) figure
> out the timing issue and wait a little longer before deleting it, or
> track usage better.

--
Andrés Mauricio Mujica Zalamea
Consultor Linux RHCE #804005093216652
SEAQ SERVICIOS CIA LTDA

Well, what i've learned is that almost every tiem i try to open an OO 
attachment from kmail, i must try several times as faster as i can and it 
finally opens.

If the attachment has ñ ò ì type characters it won't open at all, but this is 
part of another bug.

BUT.. as i mentioned earlier on this bug report i've noticed this:

I clic to open the OO attachment file

OO throws a file not found error pointing to the non-existant file

/tmp/kde-andres.mujica/call flow II.xls_[yJLETA].xls

but if i check at /tmp i've found the file here:

/tmp/kde-andres.mujica/kontactb74dfa.5/call flow ii.xls

even if i clic on openoffice ok to accept the error.

If the gods are with me and the file opens, it appears to be opened 
from /tmp/kde-andres.mujica/call flow II.xls_[vutiJA].xls

and surpringsily for me ,  the file is not there!!!! haven't noticed this....

that's what i can tell about this.

If you've got any ideas of a formal check or some debug that i can do in order 
to help solve this bug i would be glad to do it.

Sometime ago i've triied to find something similar upstream without success.. 
so maybe we'rea alone on this one.

Regards!

El Miércoles, 28 de Marzo de 2007 15:04, Matthew Carpenter escribió:
> I believe this has to do with the hand-off from Kmail to OOo, to the
> component of OOo handling the attachment.  Kmail hands off to OOo, and
> when OOo exits (or the file is not opened? - lsof style), it deletes the
> file in /tmp.  While this is a fine approach for most apps, OOo probably
> does some internal hand-off which delays loading of the temporary
> attachment.  Kmail deletes the file, thinking that it's job is done, but
> the OOo component app never had a chance to open it.
>
> This has been an issue for some time.  Can we get it resolved?  Kmail
> should either hand off to a different component, or (mo betta) figure
> out the timing issue and wait a little longer before deleting it, or
> track usage better.

-- 
Andrés Mauricio Mujica Zalamea
Consultor Linux RHCE #804005093216652
SEAQ SERVICIOS CIA LTDA