Bug 705493

Summary: [abrt] ekiga-3.2.7-4.fc14: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: John Williams <web582>
Component: ekigaAssignee: Peter Robinson <pbrobinson>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: amatrix2k2, chessmarcosz, geslinux, gustik, mikhail.v.gavrilov, pbrobinson, stuart
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:0aeeab5039773814e7461c755496f0ce35d8a633
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 15:03:11 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
Backtrace on Fedora 16 i686 none

Description John Williams 2011-05-17 19:32:54 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 45081 bytes
cmdline: ekiga
component: ekiga
Attached file: coredump, 23724032 bytes
executable: /usr/bin/ekiga
kernel: 2.6.35.13-91.fc14.x86_64
package: ekiga-3.2.7-4.fc14
rating: 3
reason: Process /usr/bin/ekiga was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305660310
uid: 500

How to reproduce
-----
1.Closing the program from the panel icon
2.
3.

Comment 1 John Williams 2011-05-17 19:32:57 UTC
Created attachment 499430 [details]
File: backtrace

Comment 2 Lars Schotte 2011-06-01 22:22:00 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. start
2.
3.

Comment 3 Grzegorz Witkowski 2011-06-05 00:10:30 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
Did nothing. The crash just appeared.

Comment 4 MD 2011-07-06 21:32:26 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.close ekiga
2.
3.

Comment 5 MD 2011-07-09 17:06:18 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.closed ekiga
2.
3.

Comment 6 MD 2011-07-09 17:58:39 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.closed ekiga
2.
3.

Comment 7 chessmarcosz 2011-08-10 10:56:42 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.I open Ekiga
2. no conection
3. when i close the appp it Crashed


Comment
-----
1.I open Ekiga
2. no conection
3. when i close the appp it Crashed

Comment 8 Stuart D Gathman 2011-11-07 16:50:00 UTC
Package: ekiga-3.2.7-4.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Right click on Ekiga notifier
2. Select Quit from popup menu
3.


Comment
-----
Exited Ekiga

Comment 9 Stuart D Gathman 2012-01-31 19:07:15 UTC
Still broken on Fedora 16.

Comment 10 Stuart D Gathman 2012-01-31 19:12:10 UTC
Created attachment 558667 [details]
Backtrace on Fedora 16 i686

Can someone update version to f16?

Comment 11 Fedora End Of Life 2012-08-16 15:03:15 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