contacts lost on changing the corrupted group name

[Bobs]

Binary package hint: pidgin

1) Ubuntu 7.10 Gutsy Gibbon
2) Source package: pidgin 2.2.1
3) Package version: 1:2.2.1-1ubuntu4.1
4) three or four groups was saved on server (using QIP under windows) and loaded with pidgin under ubuntu. Russian group names seem to be broken (some problems with cp1251<->utf8 encoding translation i think) and i decided to rename it using pidgin. The group consisted of some contacts, some of them required authorisation to add them to contact list. After renaming group Pidgin showed some "authorisation request" windows without any additional information.
5) The bug itself is incorrect group renaming realization. After renaming group it loses any of this group's contacts authorisation we have. If the user clicks "Cancel" in appearing "authorisation request" dialog - (s)he loses this contact without any additional information from program.

ProblemType: Bug
Architecture: i386
Date: Sat Mar 8 00:20:46 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/bin/pidgin
NonfreeKernelModules: nvidia
Package: pidgin 1:2.2.1-1ubuntu4.1
PackageArchitecture: i386
ProcCmdline: pidgin
ProcCwd: /home/bibi
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux Bibi-desktop 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux

[Bobs (cyberbobs)]

this bug is surely connected with bug #177962, as i got the same effect on my contact list. But the problems with contact re-authorisation after group renaming was not noticed on those post.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.