Bug 182423

Summary:	When changing between identities in the composer, signature is not updated accordingly.
Product:	[Unmaintained] kmail	Reporter:	Adam Hill <sidepipeuk>
Component:	composer	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	jon.armond
Priority:	NOR
Version:	1.11.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Adam Hill 2009-01-30 14:01:13 UTC

Version:            (using KDE 4.2.0)
OS:                Linux
Installed from:    Ubuntu Packages

This is actually the same as 178351, and so I would guess that it is a regression.

In the composer window if "automatically insert signature" is selected but you have multiple identities with multiple signatures, changing the selected identity does not change the signature. This is true in KMail 1.11.0.

Comment 1 Jaime Torres 2009-02-07 12:14:59 UTC

It works for me in opensuse (kde 4.2.0).

Comment 2 Adam Hill 2009-02-16 08:36:14 UTC

(In reply to comment #1)
> It works for me in opensuse (kde 4.2.0).
> 

After seeing this I ( eventually ) got round to doing some more digging... I did a clean install and indeed it worked.

My main system was upgraded from an earlier ( KDE 3.5 ) version of KMail, so I then went in to each of my identities and changed the dictionary language. This then strangely cleared the "Append Signature" box ( which was definitely previously checked and as I said the sig *was* being appended, just not changed when I changed identities. ) So, I went back though and ticked the box again, and now it works correctly.

It seems, then, that this was caused by some difference in the settings files between the old and new versions, which presumably was fixed when I changed the identity settings ( probably not the fact that I changed language, just the fact that the identity files were re-written. )

Comment 3 Jonathan Armond 2009-06-14 09:27:24 UTC

So this works properly in recent KMail? Can bug be closed?

Comment 4 Adam Hill 2009-06-15 12:01:49 UTC

Well, there obviously is a bug in the upgrade process from 3.5 to 4.x which caused this to happen. However, I don't have the time to investigate it further, so I guess that unless someone jumps in it will have to be closed ( if loads of others don't have the problem then it was probably something specific to me anyway. )

Comment 5 Jaime Torres 2009-06-15 12:20:53 UTC

Marking as solved then. There has been some work to improve the upgrade procedure, so maybe you were alone with this bug.