update-manager crashed with timeout in readline(): timed out

Same on Precise

apt-cache policy update-manager
update-manager:
  Installato: 1:0.156.4
  Candidato: 1:0.156.4
  Tabella versione:
 *** 1:0.156.4 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

marcobra, do you know a reliable way to reproduce this crash ?

It looks to me like it is just timing out trying to read the meta release file and because this is from Oneiric it would be the development one.

http://changelogs.ubuntu.com/meta-release-development

I am able to access this without any issues. The following file is also read
/etc/update-manager/meta-release so it might help if that were added to the bug report.

The same is with the most actual Precise Pangolin. If the meta file isn't read, because of a short network hickup (while viewing a video on youtube or any other reason), this bug is still triggered.

update-manager: Installiert: 1:0.156.10 on Ubuntu 12.04 Beta 1 (nightly build)

Hint: If this bug doesn't show up, then update-manager will show instead the message in the attached picture.

Seems this bug is still present i get this bug request during a regular check of update-manager ( i was in trouble by accessing to my apt-cacher-ng proxy and i get this )

Description: Ubuntu precise (development branch)
Release: 12.04

apt-cache policy update-manager
update-manager:
  Installato: 1:0.156.10
  Candidato: 1:0.156.10
  Tabella versione:
 *** 1:0.156.10 0
        500 http://archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status

also affects precise pangolin

Confirm bug in Precise.

this is happping in precise. also days from last up date not changing

This bug was fixed in the package update-manager - 1:0.168

---------------
update-manager (1:0.168) quantal; urgency=low

  * Run tests under xvfb and don't try to use non-existant python3-coverage
  * Don't throw exception on socket timeout when downloading metarelease
    file. LP: #818760
 -- Michael Terry <email address hidden> Mon, 23 Jul 2012 07:17:00 +0200

Hello Hernan., or anyone else affected,

Accepted update-manager into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/update-manager/1:0.156.14.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

https://errors.ubuntu.com/bucket/?id=/usr/bin/update-manager:timeout:download:urlopen:open:_open:_call_chain:http_open:do_open:getresponse:begin:_read_status:readline shows 2000+ instances of this error in the month of August for the precise-updates version of update-manager, vs. 1 instance for the precise-proposed version (which is probably a misreported version). This is strong evidence that the bug is fixed.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

This bug was fixed in the package update-manager - 1:0.156.14.9

---------------
update-manager (1:0.156.14.9) precise-proposed; urgency=low

  * No change rebuild to pick up the fixed apt_clone.py

update-manager (1:0.156.14.8) precise-proposed; urgency=low

  * Fix removal_blacklist to blacklist "^screen$" instead of "screen".
    This fixes cases where the upgrade would fail because of a package
    containing "screen" being removed. (LP: #1029531)

update-manager (1:0.156.14.7) precise-proposed; urgency=low

  * DistUpgrade/DistUpgradeMain.py: call clone.save_state with
    scrub_sources set so that VarLogDistUpgradeAptclonesystemstate will be
    included in bug reports again (LP: #1029046)
  * DistUpgrade/DistUpgradeApport.py: check errormsg for the English version of
    the dependency problems error first (LP: #999890)
    - add apt-clone_system_state.tar.gz to white list of files to upload
  * In the apport source package hook collect apt-clone information if the bug
    report is about a distribution upgrade (LP: #1029046)
  * Don't throw exception on socket timeout when downloading metarelease file
    (LP: #818760)
 -- Stephane Graber <email address hidden> Thu, 09 Aug 2012 17:05:37 -0400

It is a very severe problem when we accept udates thruogh any packages using an unseccure internet connection. Through update manager faulty net connections give us faulty information about available updates. Some times they pump in large quadities of updates from other sources which may reject by official autherisation.

 While taking updates with Terminal using such 'free for all internet connection' it interupt downlading saying ....."something wicked happen......... there is no address associate with host name"or error 404 IP adress........... etc, and towards end of updating, the connection reset, users automatically pulled back to the satage of pre update. Many a security updates are blocked to users by this way, result in more bugs.

Open internet connections are problem to all linux users .It is suspected a lobby working behind such free internet service their motivation is simply anti OPEN SYSTEMS.