Bug 239076 – aliases not kept over app restart cycle

Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.

Bug 239076 - aliases not kept over app restart cycle

Summary:	aliases not kept over app restart cycle

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	pidgin (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Warren Togami
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2007-05-04 15:14 EDT by Andrew Overholt
Modified:	2008-02-11 10:20 EST (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-02-11 10:20:33 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Andrew Overholt 2007-05-04 15:14:18 EDT

Description of problem:
Buddy aliases (ie. real names I give them) aren't kept if I quit and restart pidgin

Version-Release number of selected component (if applicable):
pidgin-2.0.0-0.36.beta7.fc7.i386

How reproducible:
Always

Steps to Reproduce:
1. Start pidgin and add some buddies
2. Alias one of them (right-click -> Alias ...)
3. Quit and restart pidgin
  
Actual results:
Your buddy's chosen nickname is still there

Expected results:
Your alias is used for your buddy

Additional info:

Comment 1 Stu Tomlinson 2008-02-09 13:53:31 EST

This is quite an old bug, is this still an issue with current Pidgin? If so,
which protocol(s) does this affect?

Comment 2 Andrew Overholt 2008-02-11 10:20:33 EST

This seems to work now.  Closing.

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