= Impact =
Users of update-manager will not receive an error message in the event that there is an error but instead a Traceback from the error dialog window. This isn't very helpful and prevents users from knowing what went wrong.
= Test Case =
1) run 'update-manager -d' in a terminal
2) disconnect my network connection
3) click upgrade to 12.10
4) see release notes error message and click 'upgrade' again
You'll then receive the Traceback described below ending in 'RunTimeError: unable to get the value'.
For Oneiric to recreate this you'll need to disconnect your network connection after viewing the release notes - otherwise you will see a 'could not donwload release notes' error.
= Original Description =
I tried updating Kubuntu 11.10 to 12.04 (beta) with
$ update-manager -d
but I did receive error in console:
authenticate 'precise.tar.gz' against 'precise.tar.gz.gpg'
extracting 'precise.tar.gz'
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/UpdateManager/UpdateManager.py", line 1099, in on_button_dist_upgrade_clicked
fetcher.run()
File "/usr/lib/python2.7/dist-packages/UpdateManager/Core/DistUpgradeFetcherCore.py", line 284, in run
_("The error message is '%s'.") % e.strerror)
File "/usr/lib/python2.7/dist-packages/UpdateManager/DistUpgradeFetcher.py", line 41, in error
return error(self.window_main, summary, message)
File "/usr/lib/python2.7/dist-packages/UpdateManager/Core/utils.py", line 404, in error
d.window.set_functions(Gdk.FUNC_MOVE)
RuntimeError: unable to get the value
I belive that line 284 DistUpgradeFetcherCore.py is error handling routine so probably root error did occured few lines earierl and stack trace was printed for bug in method for displaying errod dialog.
Running update-manager with sudo did help with this issue, but it failed later and prompted me to report a bug.
Using
$ do-release-upgrade -m desktop -d
gives same result as sudo update-manager
Wystąpił nierozwiązywalny problem podczas obliczania aktualizacji:
E:Error, pkgProblemResolver::Resolve generated breaks, this may be
caused by held packages.
I did tried manually turning off any non standard repositories but it did not help.
Please let me know if you need any aditional logs/configs.
Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/