Bug 165929 - Kmail's graphical emoticons won't die!
Summary: Kmail's graphical emoticons won't die!
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: kdepim
Version: 3
Hardware: i686
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-08-14 20:41 UTC by Mike
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: FC5
Clone Of:
Environment:
Last Closed: 2006-05-03 14:59:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Mike 2005-08-14 20:41:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050719 Fedora/1.7.10-1.3.1

Description of problem:
The new graphical emoticons keep returing in spite of configuring Kmail not to use them.  They seem to gone for a while after deselecting the configuration check box  but then an hour or two goes by, I look in another message and the darn yellow thing is back grinning maniacally.

Shudder .....

It seems as though any new messages downloaded after turning this "feature" off which contain an emoticon manages to turn the feature back on ( the configuration check box once more contains a check mark ).

Version-Release number of selected component (if applicable):
kdepim-3.4.2-0.fc3.1

How reproducible:
Always

Steps to Reproduce:
1. Read messages in KMail.
2.
3.
  

Actual Results:  Graphical Emoticons keep coming back.

Expected Results:  They shouldn't return on their own.

Additional info:

Comment 1 Mike 2005-08-19 22:33:24 UTC
It appears that this will work correctly if you quit kmail with the
configuration in your chosen state.  Perhaps a dialog box urging the user to
quit kmail and restart is in order....

Regards, Mike Klinke

Comment 2 Than Ngo 2006-05-03 14:59:58 UTC
FC3 is not suppported anymore. You should please update to FC5 current-release
which includes new KDE 3.5.2 and it should fix this problem. Thanks for your report.


Note You need to log in before you can comment on or make changes to this bug.