Bug 478516 - Auto-Reply does not work properly
Auto-Reply does not work properly
Product: Fedora
Classification: Fedora
Component: pidgin (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: Warren Togami
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2008-12-31 02:07 EST by ken cao
Modified: 2010-06-28 07:03 EDT (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-06-28 07:03:20 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description ken cao 2008-12-31 02:07:10 EST
Description of problem:
pidgin is set to auto-reply when the status is away (or idle).
however, if the other one talk to me, s/he will not get the 
auto-reply message.
*during the test using AIM, I just got the Auto-Reply worked 
correctly once a day.

Version-Release number of selected component (if applicable):

How reproducible:
99% reproducible on my machine

Steps to Reproduce:
1. login an AIM account
2. on the 'Buddy List' window, choose
Tools | Preferences (or Ctrl + P)
3. on the 'Preferences' window, choose the 'Status/Idle' tab 
4. set Away -> Auto-Reply to 'When Both away and idle' or 
'when away', and close the 'Preferences' window.
5. set the status to 'Away', or make it 'Away' by whatever way 
you like
6. type some words (or letters) in the status message box which 
is under the status choosing button(list) on the bottom of the 
'Buddy List' window
7. have someone talk to you.
8. exit pidgin
9. repeat from step 1 to 7 for several time.

Actual results:
execute step 8, for most times, pidgin won't show Auto-Reply 

Expected results:
get Auto-Reply messages when send messages to someone who set 
pidgin to auto-reply.

Additional info:
Comment 1 David Ye 2009-03-24 22:15:15 EDT
It can be reproduce when login MSN account in pidgin-2.5.5-1.fc10.x86_64
Comment 2 Yewei Shao 2009-05-15 03:43:11 EDT
It can be reproduced in pidgin-2.5.2-1.fc10.i386.
Comment 3 Bug Zapper 2009-06-09 06:33:33 EDT
This bug appears to have been reported against 'rawhide' during the Fedora 11 development cycle.
Changing version to '11'.

More information and reason for this action is here:
Comment 4 Bug Zapper 2010-04-27 08:40:00 EDT
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '11'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 11's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 11 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
Comment 5 Bug Zapper 2010-06-28 07:03:20 EDT
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

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