Bug 447002 - Ekiga crashes after configuration wizard
Summary: Ekiga crashes after configuration wizard
Keywords:
Status: CLOSED DUPLICATE of bug 441202
Alias: None
Product: Fedora
Classification: Fedora
Component: ekiga
Version: 9
Hardware: i386
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-05-16 22:15 UTC by Pavel Polischouk
Modified: 2008-05-20 07:48 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-05-20 07:48:59 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
Crash backtrace (1.66 KB, text/plain)
2008-05-16 22:15 UTC, Pavel Polischouk 		no flags Details
View All

Description Pavel Polischouk 2008-05-16 22:15:50 UTC 
Description of problem:
Ekiga crashes with segmentation fault after completing configuration wizard.

Version-Release number of selected component (if applicable):
ekiga-2.0.12-2.fc9.i386

How reproducible:
Always

Steps to Reproduce:
1. Start Ekiga, go through configuration wizard
2. Press Finish.
3. Ekiga crashes
  
Actual results:
Segmentation fault.

Expected results:
Should work.

Additional info:
Attached crash backtrace from gdb
Comment 1 Pavel Polischouk 2008-05-16 22:15:50 UTC 
Created attachment 305773 [details]
Crash backtrace
Comment 2 Edouard Bourguignon 2008-05-19 17:12:02 UTC 
same problem on x86_64. If you cancel the wizard you get ekiga but it crash on
first call. And typing with the numeric keypad is weird (pressing 1 then 2
prints 21 instead of 12)
Comment 3 Alexey Lubimov 2008-05-19 22:05:31 UTC 
Ekiga  linked with wrong opal library.

Solution: rebuild (or update from fedora updates) packages opal and ekiga.
Comment 4 Alexey Lubimov 2008-05-19 22:20:21 UTC 
duplicate bug

https://bugzilla.redhat.com/show_bug.cgi?id=441202
Comment 5 Daniel Veillard 2008-05-20 07:48:59 UTC 

*** This bug has been marked as a duplicate of 441202 ***
Note You need to log in before you can comment on or make changes to this bug.