Bug 699188 - [abrt] telepathy-salut-0.4.0-1.fc14: _int_free: Process /usr/libexec/telepathy-salut was killed by signal 11 (SIGSEGV)
Summary: [abrt] telepathy-salut-0.4.0-1.fc14: _int_free: Process /usr/libexec/telepath...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-salut
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:ba2893c46b8c947e746a2a37503...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-04-24 02:42 UTC by Samuel Greenfeld
Modified: 2012-08-16 12:14 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:14:17 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (40.75 KB, text/plain)
2011-04-24 02:42 UTC, Samuel Greenfeld
no flags Details

Description Samuel Greenfeld 2011-04-24 02:42:16 UTC
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 41723 bytes
cmdline: /usr/libexec/telepathy-salut
comment: I have not reproduced this again yet.  Other instances of Sugar in Fedora (all 64-bit) were already running on the local network via mDNS & Salut; this was the only 32-bit instance brought online at the time.
component: telepathy-salut
Attached file: coredump, 847872 bytes
crash_function: _int_free
executable: /usr/libexec/telepathy-salut
kernel: 2.6.35.12-88.fc14.i686
package: telepathy-salut-0.4.0-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-salut was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303611586
uid: 500

How to reproduce
-----
1. Groupinstall "sugar-desktop" as well as sugar-emulator {include the updates-testing repository}.
2. Launch sugar-emulator from GNOME; right click on the "XO" character, from the "My Settings" area go into Networking and remove the hostname seen.  Press the "checkmark" button and restart sugar-emulator.  This forces Sugar to use Salut locally instead of a jabber server.
3. Make sure that mDNS is open through Fedora's firewall using the Firewall System/Administration tool in GNOME.
4. As root run "/etc/init.d/avahi-daemon restart" in a terminal.

Comment 1 Samuel Greenfeld 2011-04-24 02:42:18 UTC
Created attachment 494482 [details]
File: backtrace

Comment 2 Fedora End Of Life 2012-08-16 12:14:20 UTC
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


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