Bug 896307 - ettercap -C crash ncurses interface when ctrl+s is used
Summary: ettercap -C crash ncurses interface when ctrl+s is used
Keywords:
Status: CLOSED DUPLICATE of bug 862116
Alias: None
Product: Fedora
Classification: Fedora
Component: ettercap
Version: 17
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Gwyn Ciesla
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-01-17 01:21 UTC by xset1980
Modified: 2013-01-18 19:43 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-18 19:43:19 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
ettercap crashed and with maks of the descripted bug (44.04 KB, image/png)
2013-01-17 01:21 UTC, xset1980
no flags Details

Description xset1980 2013-01-17 01:21:58 UTC
Created attachment 679958 [details]
ettercap crashed and with maks of the descripted bug

Description of problem:

When ettercap is opened with ettercap -C, select sniff, unified sniffing, and press ctrl+s (scan hosts) 3 times, the ncurses interface show like the screenshot attached (crashed).

Version-Release number of selected component (if applicable):
Fedora 17 KDE
ettercap-0.7.5-2.fc17.1.20120906gitc796e5.x86_64
ncurses-5.9-4.20120204.fc17.x86_64
qt-4.8.4-6.fc17.x86_64                                                          
qt-4.8.4-6.fc17.i686
kdelibs-4.9.5-2.fc17.x86_64
3.6.11-1.fc17.x86_64

How reproducible:
Always

Steps to Reproduce:
1.ettercap -C
2.sniff->Unified Sniffing->select the iface (eth0 in my case)->intro
3.press ctrl+s (scan for hosts) 3 times, the ncurses interface crash
  
Actual results:


Expected results:


Additional info:

On Fedora 18 KDE final release, the bug is not present, no bug on ncurses or crashes, so, maybe some piece of the enviroment for ettercap (ncurses, Qt, KDE, etc) are involved, i don't know.

Comment 1 Gwyn Ciesla 2013-01-18 19:43:19 UTC

*** This bug has been marked as a duplicate of bug 862116 ***


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