OTR Settings not saved for AIM Blast

Bug #681858 reported by WxDan
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
pidgin-otr (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: pidgin-otr

Using pidgin-otr 3.2.0-5, pidgin 1:2.7.3-1ubuntu2 on maverick.

The AIM Blast feature is provided by AIM as a "chat room" feature, similar to an invite-only IRC channel. It appears in your buddy list as a single user, just like any other AIM account. However, if you make changes to the OTR settings specific to that blast - for example, to disable automatic initiation of OTR, they will not be saved between sessions.

Steps to reproduce:

1) Right-click on AIM blast, choose OTR Settings
2) Uncheck Use Default OTR Settings for this buddy"
3) Uncheck "Enable Private Messaging" (All checkboxes should either be empty or greyed out at this point)
4) Select Ok
5) Sign off of the AIM account associated with the blast
6) Sign on to the AIM account associated with the blast
7) Check OTR settings again - they will not be saved, and Use Default OTR Setting for this buddy will be checked again

It is expected that these settings will be saved and not revert back when you sign back on to the AIM account. These settings are saved with other AIM buddies, but do not save with blasts.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: pidgin-otr 3.2.0-5
ProcVersionSignature: Ubuntu 2.6.35-23.40-generic 2.6.35.7
Uname: Linux 2.6.35-23-generic x86_64
Architecture: amd64
CheckboxSubmission: c21570075344d7271c59dad4b61f6624
CheckboxSystem: d00f84de8a555815fa1c4660280da308
Date: Fri Nov 26 11:54:44 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: pidgin-otr

Revision history for this message
WxDan (dan-wxdan) wrote :
Revision history for this message
Ted (tedks) wrote :

I can confirm this bug by following the original reporter's steps.

Changed in pidgin-otr (Ubuntu):
status: New → Confirmed
Revision history for this message
WxDan (dan-wxdan) wrote :

Using the steps I reported, I was able to replicate this on a Windows machine. Issue is upstream and not related to Ubuntu.

Revision history for this message
Nate Carlson (natecarlson) wrote :

Confirmed also. Annoying too. ;)

Revision history for this message
Ted (tedks) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream. Thanks in advance!

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.