Bug 142188

Summary:	gaim has no smiley faces in FC3 for MSN and AOL connections
Product:	[Fedora] Fedora	Reporter:	David Kaplan <dmkaplan>
Component:	gaim	Assignee:	Daniel Reed <djr>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3	CC:	eblanton, lschiere+bugs, mark, stu, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2005-01-08 21:58:55 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Kaplan 2004-12-08 00:09:27 UTC

Description of problem:
In FC2, gaim had all sorts of smileys available, but when I use it
now, it says that "this theme has no available smileys".  I have tried
this for AIM and MSN connections, not sure about the rest.

Version-Release number of selected component (if applicable):
gaim-1.1.0-0.FC3

How reproducible:
always

Steps to Reproduce:
1.start gaim and open up an AIM or MSN connection
2.try to insert a smiley face.
3.
  
Actual results:
none are available.

Expected results:
should have lots.

Additional info:

Comment 1 David Kaplan 2004-12-08 00:10:48 UTC

I just noticed that there are no smiley themes and that you have to
enable them.  But why would the default be to disable them?

Comment 2 Luke Schierer 2004-12-08 01:16:21 UTC

a bug in the upgrade code causes the default for an unspecified theme
to be "None" instead of the previous default. this is the most likely
cause of this bug.

Comment 3 Warren Togami 2005-01-08 11:06:23 UTC

Luke, is this something that can be fixed in upstream gaim, or should we just
close this bug WONTFIX?

Comment 4 Warren Togami 2005-01-08 21:58:55 UTC

Luke said:

I'd close it as WONTFIX, because there really isn't any clean way to 
avoid this. the preference simply wasn't save (adequately) before, 
becuase it was identical to the default, so when the default changed, 
the users's experience was different, but from the point of view of 
reading the config file in and out, it was identical. 

we could insure this doesn't happen again on some future upgrade that 
changes the default theme, but we can't retroactively fix this to ensure 
current upgraders don't hit it.