Bug 132085 - Error While Starting Listener
Error While Starting Listener
Product: Fedora
Classification: Fedora
Component: gnomemeeting (Show other bugs)
i686 Linux
medium Severity medium
: ---
: ---
Assigned To: Daniel Reed
Depends On:
  Show dependency treegraph
Reported: 2004-09-08 14:06 EDT by kaye gee
Modified: 2007-11-30 17:10 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-09-08 14:31:27 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description kaye gee 2004-09-08 14:06:16 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.2)

Description of problem:
When I launch gnomemeeting, I get the following error message:  Error
while starting the listener.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Click on gnomemeeting


Actual Results:  The error message below is displayed.

Error while starting the listener

You will not be able to receive incoming calls. Please check that    
no other program is already running on the port used by Gnomemeeting.   

Expected Results:  Gnomemeeting should launch without any errors

Additional info:

nmap -sT -O localhost returned the following information with or
without gnomemeeting active.

Starting nmap 3.55 ( http://www.insecure.org/nmap/ ) at 2004-09-08
14:05 EDT
sendto in send_ip_raw: sendto(4, packet, 28, 0,, 16) =>
Operation not permitted
Interesting ports on XXXXX.XXXXXXXX.XXX (
(The 1651 ports scanned but not shown below are in state: closed)
22/tcp   open  ssh
25/tcp   open  smtp
53/tcp   open  domain
111/tcp  open  rpcbind
139/tcp  open  netbios-ssn
445/tcp  open  microsoft-ds
631/tcp  open  ipp
953/tcp  open  rndc
1720/tcp open  H.323/Q.931
Comment 1 Daniel Reed 2004-09-08 14:31:27 EDT
Open a terminal and examine the output of (run as root):

netstat -l -v -p -n

This should show which process is listening on port 1720 (which is
what gnomemeeting wants). If it is another instance of gnomemeeting,
see if you can find where it is and either use that instance or kill
it. If it is something else, you may need to shut it down. If it is
something else and you think gnomemeeting and the other process
shouldn't conflict with each other, feel free to reopen this and
include the output of the netstat command (above).

Comment 2 kaye gee 2004-09-08 17:39:59 EDT
The output from the command showed that port 1720 was not used by
anything. I'm not sure what caused this, but I rebooted the box and it
cleared the port. Was it a bug??? If it was, it would probably be hard
to track down the root cause.

tcp        0      0 :::1720                     :::*                 
      LISTEN      -

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