Hide Forgot
abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 18711 bytes cmdline: /usr/libexec/telepathy-salut component: telepathy-salut Attached file: coredump, 1474560 bytes crash_function: gibber_xmpp_stanza_add_build_va executable: /usr/libexec/telepathy-salut kernel: 2.6.35.12-88.fc14.x86_64 package: telepathy-salut-0.4.0-1.fc14 rating: 4 reason: Process /usr/libexec/telepathy-salut was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) time: 1303615259 uid: 500 comment ----- Yes, firewalling ports needed for an activity is obscure; but it should not lead to crashes. The Fedora Sugar Spin currently only seems to have mDNS open for incoming traffic through the firewall, so I was trying to figure out what ports were needed for Salut to work when this crash occured. How to reproduce ----- 1. Have two instances of sugar-emulator running using Salut (go into the My Settings area in Networking, and delete the Jabber server name if found). 2. Using the Chat (sugar-chat) activity, have computer A share the activity. 3. Make sure the firewall on computer B has incoming UDP port 5353 (mDNS) and TCP 5298 (telepathy-salut) support available, but does not have generic or salut-specific incoming multicast explicitly permitted. The firewall as configured in this step was done through Fedora 14's GNOME-based System/Administration Firewall utility. {Computer A was also identically configured firewall-wise.} 4. Using Sugar's Network view (F1 key), invite computer B running sugar-emulator to the Chat session. Accept it on Computer B by selecting the Chat from the frame. 5. Wait a bit, then press the Stop button to close the Chat activity on Computer A. Press the checkmark icon to close the journal documentation description if it appears. ABRT then caught this crash on Computer A.
Created attachment 494486 [details] File: backtrace
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