Bug 716456

Summary: [abrt] pidgin-2.7.11-1.fc13: __poll: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: philverb
Component: pidginAssignee: Stu Tomlinson <stu>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: fedora, itamar, stu
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:c2c02c896d13cd51b0c940ce35018f1a3ab4e880
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 11:39:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description philverb 2011-06-24 13:57:24 UTC
abrt version: 1.1.14
architecture: x86_64
cmdline: pidgin -d
comment: Crash occurs whenever an inbound Google Talk call request is received by the Google Mail accounts, when those accounts are targets of the same Google Voice configuration, i.e., "ring computer" where "computer" is equal  to a Gmail login and when a browser session is logged-into the aforementioned GMail accounts.
component: pidgin
crash_function: __poll
executable: /usr/bin/pidgin
kernel: 2.6.34.8-68.fc13.x86_64
package: pidgin-2.7.11-1.fc13
rating: 4
reason: Process /usr/bin/pidgin was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1308901216
uid: 500

backtrace
-----
[New Thread 2508]
[New Thread 8795]
[New Thread 8797]
[New Thread 8801]
[New Thread 8800]
[New Thread 8804]
[New Thread 8796]
[New Thread 8807]
[New Thread 8806]
[New Thread 8802]
[New Thread 8805]
[New Thread 8799]
warning: "/var/cache/abrt-di/usr/lib/debug/.build-id/e4/dbdda37da23d15e060b530b45bf850ce434896.debug": separate debug info file has no debug info
Core was generated by `pidgin -d'.
Program terminated with signal 6, Aborted.
#0  0x0000003323a328f5 in raise (sig=6)
    at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
64	../nptl/sysdeps/unix/sysv/linux/raise.c: No such file or directory.
	in ../nptl/sysdeps/unix/sysv/linux/raise.c

Thread 12 (Thread 8799):
#0  0x0000003323ad7323 in __poll (fds=<value optimized out>, 
    nfds=<value optimized out>, timeout=<value optimized out>)
    at ../sysdeps/unix/sysv/linux/poll.c:87
        __arg2 = 2
        _a3 = -1
        _a1 = 140656180726544
        resultvar = <value optimized out>
        __arg3 = -1
        __arg1 = 140656180726544
        _a2 = 2
        resultvar = <value optimized out>
        oldtype = 0
        result = <value optimized out>
#1  0x00007fed121580cb in task_monitor_alsa (data=0x36c7420)
    at gstalsamixer.c:453
        pfds = 0x7fed11b00b10
        nfds = 1
        rnfds = 1
        revents = <value optimized out>
        mixer = 0x36c7420
        ret = <value optimized out>
        __PRETTY_FUNCTION__ = "task_monitor_alsa"
#2  0x00000034ac88519e in gst_task_func (task=0x7fece4033b10 [GstTask])
    at gsttask.c:271
        lock = 0x192d960
        tself = 0x1896830
        priv = 0x7fece4033bb0
        __PRETTY_FUNCTION__ = 
Timeout exceeded: 60 second, killing gdb

How to reproduce
-----
1.  Configure Google Voice account to "ring" one mobile phone and each of two separate GMail accounts.
2.  Use Google-Chrome browser to Log-in to at least one of the GMail Accounts.
3.  Use Pidgin to log-into both of the GMail accounts configured as targets of the aforementioned GMail accounts , when Pidgin's built-in functionality for voice and video (which apparently offers no options for deactivating that funtionality) is set up to work.
4.  Await and receive a call while both the browser and Pidgin are running, and when they each concomitantly recognize the inbound call.
5.  "Answer" the call using the browser rather than using Pidgin to 'answer' the call.
6.  Allow this process to be repeated three times.
7.  Pidgin crashes consistently after this process has occured three times.

Comment 1 philverb 2011-06-24 13:57:26 UTC
Created attachment 509767 [details]
File: backtrace

Comment 2 Bug Zapper 2011-06-27 11:39:42 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 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.