Hide Forgot
abrt version: 1.1.18 architecture: x86_64 Attached file: backtrace, 40266 bytes cmdline: pidgin comment: na component: pidgin Attached file: coredump, 88383488 bytes crash_function: sighandler executable: /usr/bin/pidgin kernel: 2.6.35.13-92.fc14.x86_64 package: pidgin-2.9.0-1.fc14 rating: 4 reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1310619835 uid: 500 How to reproduce ----- start use crash
Created attachment 512800 [details] File: backtrace
Package: pidgin-2.9.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Run Pidgin 2. Log in to VPN 3. Crash follows shortly? Comment ----- Uncertain of circumstances to replicate, issues potentially about logging into a VPN and switching to another IP address?
Package: pidgin-2.9.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- was not even using the darn thing
Package: pidgin-2.9.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- - leave it overnight connected and it crashed
Package: pidgin-2.9.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- was not using it - it was running (connected to few servers) and it just crashed .. I was not even at home
Package: pidgin-2.9.0-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I forgot. It just happened?
Package: pidgin-2.9.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Every time i lock my system, pidgin crashes shortly there after. 2. 3. Comment ----- Once i lock my computer, for a longer amount of time; i.e. go to lunch or go home for the day, pidgin always crashes.
Package: pidgin-2.9.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I'm not sure how to reproduce, it happens randomly when pidgin is in the background.
*** Bug 757403 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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