Bug 318613

Summary:	kmail forgets application association after restart
Product:	[Applications] kmail2	Reporter:	abrahams
Component:	config dialog	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	montel
Priority:	NOR
Version:	4.9.5
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:

Description abrahams 2013-04-20 00:52:21 UTC

I have a message with an attached .wav file.  When I attempt to open the attachment, I get a dialog that asks me to choose an application.  I choose Dragon Player and then ask kmail to remember the association.  Then Dragon Player opens the .wav file, as it should.   If I close Dragon Player and again click on the attachment, kmail2 remembers that Dragon Player is my chosen association -- as it should.

But if I now close kmail2 and restart it, the association has been forgotten, and I again have to go through the dialog to choose Dragon Player.

Reproducible: Always

Steps to Reproduce:
1. Try to open an attachment to an incoming message.
2. Choose an application and ask that the association be remembered.
3. Use the selected application to examine the attachment.
4. Open the attachment again.   kmail2 now offers to use the selected application to open the attachment.
5. Close and reopen kmail2.
6. Try again to open the attachment.  kmail2 has forgotten the association.


Expected Results:  
After the restart, kmail should remember the association and offer to use it.

Comment 1 Laurent Montel 2013-04-23 05:52:00 UTC

Work fine here.

Comment 2 abrahams 2013-06-09 16:42:46 UTC

I've verified that the problem is with kmail, not file associations in general.  If I store the .wav file and then open it (from Dolphin or otherwise), it opens correctly with Dragon Player.  As far as I know, kmail2 doesn't have its own facility for determining file associations, but tries to use the more general mechanism.

Comment 3 Denis Kurz 2016-09-24 17:59:37 UTC

This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kmail2 (version 5.0 or later, as part of KDE Applications 15.12 or later), it gets closed in about three months.

Comment 4 Denis Kurz 2017-01-07 21:56:03 UTC

Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.