abrt 1.0.8 detected a crash. architecture: i686 Attached file: backtrace cmdline: pidgin component: pidgin executable: /usr/bin/pidgin kernel: 2.6.32.9-70.fc12.i686.PAE package: pidgin-2.6.6-2.fc12 rating: 4 reason: Process /usr/bin/pidgin was killed by signal 8 (SIGFPE) release: Fedora release 12 (Constantine) comment ----- Trying to connect from a Laptop connected behind a Fortigate FG-60 Firewall from FORTINET, with IM/p2p filtering enabled to allow only specific msn logins from a list. after a few seconds, Pidgin crashes. How to reproduce ----- 1. Laptop connected behind a Fortigate FG-60 Firewall from FORTINET, with IM/p2p filtering enabled to allow only specific msn logins from a list. 2. 3.
Created attachment 401388 [details] File: backtrace
How to reproduce ----- 1. Just crashed 2. 3. Comment ----- Just crashed
How to reproduce ----- 1. Configure one msn messenger account and one internal XMPP account 2. Use a Fortinet FG-60 firewall version 3.0 MR7 patch 7 in front of the network, allowing only outbound ports tcp/1863 and tcp/80 for msn messenger. 3. Enable the IM/p2p filters and set msn messenger as allowed to login but blocking audio and file transfer ports, and then specified your msn login in the allowed list. 4. Attempt to connect to the msn messenger going thru the firewall, it'll crash shortly after connecting. Comment ----- I'm connecting to my msn messenger account and one internal XMPP account. There is a Fortinet FG-60 firewall in front of this network, allowing only ports tcp/1863 and tcp/80 for msn messenger out to Internet. This Fortinet firewall also filters IM/p2p applications. I set msn messenger as allowed to login but blocking audio and file transfer ports, and then specified my msn login in the allowed list. Pidgin connects but it crashes shortly after. It crashes only once i connect to the msn account going thru the firewall. I'm forced to use aMSN which doesn't crash at all under the same circumstances. i've came across this same problem with previous versions of Pidgin, while some others have worked just perfectly going thru Fortinet firewalls and the Instant Messaging filters.
How to reproduce ----- 1. it just crashed 2. 3.
How to reproduce ----- 1. one chat window opened only. 2. 3.
*** Bug 576336 has been marked as a duplicate of this bug. ***
*** Bug 593395 has been marked as a duplicate of this bug. ***
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. just messaging on msn 2. 3. Comment ----- just messaging on msn
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. msn messenger 2. 3. Comment ----- msn messenger
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. open with msn messenger only 2. 3. Comment ----- open with msn messenger only
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. open with msn messenger and one XMPP account 2. 3. Comment ----- open with msn messenger and one XMPP account
*** Bug 595575 has been marked as a duplicate of this bug. ***
*** Bug 595820 has been marked as a duplicate of this bug. ***
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. msn messenger and 2 xmpp accounts open 2. 3. Comment ----- msn messenger and 2 xmpp accounts open
Package: pidgin-2.6.6-2.fc12 Architecture: i686 OS Release: Fedora release 12 (Constantine) How to reproduce ----- 1. open with msn messenger 2. 3. Comment ----- open with msn messenger
*** Bug 596366 has been marked as a duplicate of this bug. ***
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.