Ubuntu
desktopcouch package

crash when starting ekiga

Bug #479602 reported by elenfoiro on 2009-11-09

This bug report is a duplicate of: Bug #465216: desktopcouch-service crashed with RuntimeError in find_port__linux(). Edit Remove

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	desktopcouch (Ubuntu)	New	Undecided	Unassigned

Bug Description

Binary package hint: desktopcouch

ekiga:
  Installé : 3.2.5-1ubuntu1
  Candidat : 3.2.5-1ubuntu1
Table de version :
*** 3.2.5-1ubuntu1 0
        500 http://fr.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

choosed Ekiga in the Ubuntu main menu and it crashed.

ProblemType: Crash
Architecture: i386
Date: Mon Nov 9 23:25:36 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/desktopcouch/desktopcouch-service
InterpreterPath: /usr/bin/python2.6
NonfreeKernelModules: nvidia
Package: desktopcouch 0.5-0ubuntu1
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/lib/desktopcouch/desktopcouch-service
ProcEnviron:
SHELL=/bin/bash
LANG=fr_FR.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
PythonArgs: ['/usr/lib/desktopcouch/desktopcouch-service']
SourcePackage: desktopcouch
Title: desktopcouch-service crashed with RuntimeError in find_port__linux()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Tags:

Revision history for this message

elenfoiro (frederic-maccari) wrote on 2009-11-09:

Traceback.txt Edit (1.0 KiB, text/plain; charset="utf-8")
XsessionErrors.txt Edit (2.7 KiB, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2009-11-09: This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #465216, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.