Bug 1206363
Summary: | [abrt] pidgin: sighandler(): pidgin killed by SIGABRT | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Jared Smith <jsmith.fedora> | ||||||||
Component: | pidgin | Assignee: | Jan Synacek <jsynacek> | ||||||||
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 22 | CC: | afield, ali+rhbugzilla, beaver.pv, branto, buttsoups, ciro.deluca, dx, fukidid, itamar, jclere, jkaluza, jskarvad, jsynacek, matt, omega13a, simon.sigre, stu, tom, vsapronenko | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
URL: | https://retrace.fedoraproject.org/faf/reports/bthash/ce91946cfbefd5b9a32962ab4e9a7479d63b8309 | ||||||||||
Whiteboard: | abrt_hash:cd620f1dcf061b2b78c9b5ddd5cc2268fca1f224 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2016-07-19 13:13:09 UTC | Type: | --- | ||||||||
Regression: | --- | Mount Type: | --- | ||||||||
Documentation: | --- | CRM: | |||||||||
Verified Versions: | Category: | --- | |||||||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
Cloudforms Team: | --- | Target Upstream Version: | |||||||||
Embargoed: | |||||||||||
Attachments: |
|
Description
Jared Smith
2015-03-26 21:21:23 UTC
Created attachment 1006982 [details]
File: backtrace
Created attachment 1006983 [details]
File: cgroup
Created attachment 1006984 [details]
File: core_backtrace
Another user experienced a similar problem: Just using pidgin as normal with purple-sipe plugin, not sure if the remote user tried to send a file or anything, but Pidgin just bombed reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin global_pid: 2657 kernel: 4.0.3-300.fc22.x86_64 package: pidgin-2.10.11-10.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: Spontaneous crash while not in active use. reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin global_pid: 5767 kernel: 4.0.4-303.fc22.x86_64 package: pidgin-2.10.11-12.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I apologize if this isn't helpful, but it's just been crashing on my during regular usage. I'll be typing a message to someone with a couple tabs of chat windows open and it just shuts down. reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin global_pid: 2629 kernel: 4.0.6-300.fc22.x86_64 package: pidgin-2.10.11-12.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 Another user experienced a similar problem: I was having a conversation with a friend when Pidgin's sound failed followed by the program crashing like 30 seconds later. This happened twice in one day. reporter: libreport-2.6.0 backtrace_rating: 4 cmdline: pidgin crash_function: sighandler executable: /usr/bin/pidgin global_pid: 13817 kernel: 4.0.6-300.fc22.x86_64 package: pidgin-2.10.11-12.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 I use the sipe plugin when I'm working from home. This crash only seems to happen when I've enabled the sipe account. Another user experienced a similar problem: I had just sent a message in a private chat when the crash happened reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: pidgin --session 10d4717f005d82f9c0139927878130172400000028010032 --display :0 crash_function: sighandler executable: /usr/bin/pidgin global_pid: 2157 kernel: 4.1.3-200.fc22.x86_64 package: pidgin-2.10.11-12.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 I have noticed something new the last time this crash occurred. I have sound notifications on so each time I send or receive a message, my machine beeps. I noticed that the beeps were not happening right before Pidgin crashed this time as I was in the middle of chatting with someone. Hope this helps. Another user experienced a similar problem: I had chat with vk.com user reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: pidgin --session 2f23b3ba7-d449-405c-ba1f-8fbdfe19c61d --display :0.0 crash_function: sighandler executable: /usr/bin/pidgin global_pid: 1730 kernel: 4.1.7-200.fc22.x86_64 package: pidgin-2.10.11-12.fc22 reason: pidgin killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000 This is a file descriptor leak every time a sound is played. Once it reaches the file descriptor limit, a crash happens. Workaround: mute sounds. Upstream bug: https://developer.pidgin.im/ticket/16752 Commit with the fix: https://hg.pidgin.im/pidgin/main/rev/902b1fd334bd This probably affects any package with the original gstreamer 1.0 patch applied (pidgin-2.10.11-gstreamer1.patch) but not this one. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. To clarify: This is fixed in pidgin 2.10.12, available in fedora 23 and newer. |