** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Opinion = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in
I am unable to find any instances of this crash on the Error Tracker any
more so I am marking this as Fix Released.
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Incomplete = Opinion
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in
The errors listed in comment #6 aren't accessible at this point in time
due to the migration of errors.ubuntu.com, however looking at e.u.c for
new instances of this issue I don't see any so it may be fixed. Then
again there probably aren't a lot of distribution upgrades happening at
this point
AFAICT, check-new-release-gtk does not and never did accept a -q option.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in init_proxy(): [Errno
My mistake I really meant check-new-release -q, and check-new-release is
a symlink to do-release-upgrade. It may be worth looking at release-
upgrade-motd which calls check-new-release -q.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
After discussion on IRC and some additional investigations, it seems
like what's happening is that stderr is being closed at some point
during the update-motd process. If stderr is closed, then lsb_release
can exit with a non-zero status, and this will cause check-new-release
to try to write to
Marking as incomplete so that we can get more information from someone
who is affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in
** Tags added: patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in init_proxy(): [Errno 5]
Input/output error
To manage notifications
Okay, so the patch in #10 is just papering over the problem.
After further discussions, we think there's a possibility that LP:
#1094218 could be related, although we have no direct evidence of this.
For the sake of argument, let's say it is. If the IOError with error
code 10 that is displayed
This still seems possible with the code in raring.
** Package changed: update-manager (Ubuntu) = ubuntu-release-upgrader
(Ubuntu)
** Changed in: ubuntu-release-upgrader (Ubuntu)
Status: Confirmed = Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I believe this crash could happen because init_proxy from from
UpdateManager.Core.utils import prints to sys.stderr which may not be
available depending on how check-new-release-gtk is called.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The same thing seems to happen in get_dist when it writes to sys.stderr
and if check-new-release-gtk is called with -q.
You can see some crashes about this at:
https://errors.ubuntu.com/bucket/?id=/usr/bin/do-release-upgrade%3AIOError%3A%3Cmodule%3E%3A__init__%3Aget_dist
I wonder if a similar problem could be causing this error:
https://errors.ubuntu.com/problem/2ee37f473307472828bd2bc1b7fe749a69d3bc86
where we are getting an IOError when trying to print.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Hi,
this bug report is a bit old but as there is no answer yet, I'll describe my
own experience with it.
I had a similar error after login on a fresh install of precise desktop.
Launching do-release-upgrade on command line reported an invalid proxy error.
I found out that I had an invalid proxy
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-manager (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
** Changed in: update-manager (Ubuntu)
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in init_proxy(): [Errno
** Visibility changed to: Public
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/982082
Title:
do-release-upgrade crashed with IOError in init_proxy(): [Errno 5]
Input/output error
To manage
18 matches
Mail list logo
