emesene crashed with ValueError in _configure(): Wrong host or port number : (, 80)

Bug #731137 reported by Andrea Torlaschi
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
emesene (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: emesene

Description: Ubuntu Natty (development branch)
Release: 11.04

emesene:
  Installato: 2.0~git20110303-0ubuntu1
  Candidato: 2.0~git20110303-0ubuntu1
  Tabella versione:
 *** 2.0~git20110303-0ubuntu1 0
        500 http://it.archive.ubuntu.com/ubuntu/ natty/universe i386 Packages
        100 /var/lib/dpkg/status

I started the software but suddently he gave me a message in wich he told me that a crash was happened.

But the app continued to work right.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: emesene 2.0~git20110303-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Mar 8 10:05:14 2011
ExecutablePath: /usr/share/emesene/emesene/emesene
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/emesene
ProcEnviron:
 LANGUAGE=it_IT:en
 PATH=(custom, no user)
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/emesene']
SourcePackage: emesene
Title: emesene crashed with ValueError in _configure(): Wrong host or port number : (, 80)
UpgradeStatus: Upgraded to natty on 2011-03-01 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Revision history for this message
Andrea Torlaschi (runnerway) wrote :
Revision history for this message
Apport retracing service (apport) wrote : 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 #729544, 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.

tags: removed: need-duplicate-check
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.