Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 246284 - Sporadic crashes when completing a nick
Sporadic crashes when completing a nick
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: 2007-06-29 15:46 EDT by Ignacio Vazquez-Abrams
Modified: 2007-11-30 17:12 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-08-26 18:59:29 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Partial pidgin backtrace (6.40 KB, text/plain)
2007-07-18 11:36 EDT, Ignacio Vazquez-Abrams
no flags Details
Full pidgin backtrace (29.77 KB, text/plain)
2007-07-23 06:43 EDT, Ignacio Vazquez-Abrams
no flags Details

  None (edit)
Description Ignacio Vazquez-Abrams 2007-06-29 15:46:56 EDT
Description of problem:
pidgin crashes when it's been running for a few days and I try to complete a nick.

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

How reproducible:

Steps to Reproduce:
1. Use pidgin run for a few days, not quitting it in that time
2. Use Tab to complete a nick
3. Watch pidgin spontaneously quit
Actual results:
pidgin quits without notice

Expected results:
The nick should be completed

Additional info:
Comment 1 Ignacio Vazquez-Abrams 2007-07-18 11:36:24 EDT
Created attachment 159528 [details]
Partial pidgin backtrace 

Here's a partial backtrace. I'll install the rest of the -debuginfo packages
and complete it.
Comment 2 Ignacio Vazquez-Abrams 2007-07-23 06:43:27 EDT
Created attachment 159772 [details]
Full pidgin backtrace

Here you go. BTW, this is on IRC.
Comment 3 Ignacio Vazquez-Abrams 2007-08-26 18:59:29 EDT
Looks like 2.1 fixes this.

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