add-apt-repository crashed with error in get_ppa_info_from_lp(): (23, 'Failed writing body (0 != 1607)')

Status changed to 'Confirmed' because the bug affects multiple users.

There is a bug with a similar signature ranked 4rd on errors.ubuntu.com (over 2100 reports yesterday), the error is sometime different though:

  File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 80, in get_ppa_info_from_lp
    curl.perform()
error: (6, "Couldn't resolve host 'launchpad.net'")

Michael, do you think you could have a look or don't error out of connection issues?

file "/usr/bin/add-apt-repository", line 125, in ,module> ppa_info = get_info_from_lp (user,ppa_name)
file "usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 80, in get_ppa_info_from_lp curl.perform () pycurl.error: 6, "couldn't resolve host 'launchpad.net'"

after fresh install

Thanx for help

Didier, is there any chance that you look at this one as well (or get mvo to look at it by asking questions on how to fix it if needed ;-)

The bug scored 916 reports in 5 days on errors.ubuntu.com in July

The initial backtrace and the can't resolve backtrace seem to be quite different.
The first looks like it would be triggered by some bad data coming over https where the other one is simply because resolving fails.

Catching the DNS resolution problem should be trivial, the initial traceback isn't exactly clear on what's going on though.

Part of the reason there are two different tracebaks is that the duplicate database doesn't consider enough of the Traceback for the signatures to be unique:

936186 /usr/bin/add-apt-repository:error:<module>:get_ppa_info_from_lp

I suggest that we fix the issue that is being reported on errors.ubuntu.com.

Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 125, in <module>
    ppa_info = get_ppa_info_from_lp(user, ppa_name)
  File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 80, in get_ppa_info_from_lp
    curl.perform()
error: (7, "couldn't connect to host")

Additionally, based of data obtained from errors.ubuntu.com, (https://errors.ubuntu.com/bucket/?id=%2Fusr%2Fbin%2Fadd-apt-repository%3Aerror%3A%3Cmodule%3E%3Aget_ppa_info_from_lp), and since Quantal no longer uses curl but rather urllib2 this bug is fixed in Quantal.

same problem here jus started this morning
cmcanulty@HPTech:~$ sudo add-apt-repository ppa:gnome3-team/gnome3
[sudo] password for cmcanulty:
Traceback (most recent call last):
  File "/usr/bin/add-apt-repository", line 125, in <module>
    ppa_info = get_ppa_info_from_lp(user, ppa_name)
  File "/usr/lib/python2.7/dist-packages/softwareproperties/ppa.py", line 80, in get_ppa_info_from_lp
    curl.perform()
pycurl.error: (6, "Couldn't resolve host 'launchpad.net'")
cmcanulty@HPTech:~$

The Precise Pangolin has reached end of life, so this bug will not be fixed for that release