2008-05-18 21:20:30 |
Thinboy00 |
description |
I tried to upgrade from gutsy to hardy-beta (using update-manager -d and also through alternate-cd)
In both cases, it hangs in first phase(preparing to install).
The status shows "checking package manager".
Few debug info:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.10
Release: 7.10
Codename: gutsy
/var/log/dist-upgrade/main.log:
2008-03-23 00:09:06,460 INFO release-upgrader version '0.87.12' started
2008-03-23 00:09:07,002 DEBUG Using 'DistUpgradeViewGtk' view
2008-03-23 00:09:07,159 DEBUG lsb-release: 'gutsy'
2008-03-23 00:09:07,159 DEBUG _pythonSymlinkCheck run
2008-03-23 00:09:08,794 DEBUG checkViewDepends()
$ sudo apport-cli -f -P 9540
*** Collecting problem information
The collected information can be send to the developers to improve the
application. This might take a few minutes.
Traceback (most recent call last):
File "/usr/bin/apport-cli", line 282, in <module>
app.run_argv()
File "/var/lib/python-support/python2.5/apport/ui.py", line 253, in run_argv
self.run_report_bug()
File "/var/lib/python-support/python2.5/apport/ui.py", line 237, in run_report_bug
self.collect_info()
File "/var/lib/python-support/python2.5/apport/ui.py", line 348, in collect_info
icthread.exc_raise()
File "/var/lib/python-support/python2.5/apport/REThread.py", line 37, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
File "/var/lib/python-support/python2.5/apport/ui.py", line 38, in thread_collect_info
report.add_hooks_info()
File "/var/lib/python-support/python2.5/apport/report.py", line 499, in add_hooks_info
assert self.has_key('Package')
AssertionError |
I tried to upgrade from gutsy to hardy-beta (using update-manager -d and also through alternate-cd)
In both cases, it hangs in first phase(preparing to install).
The status shows "checking package manager".
Few debug info:
$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 7.10
Release: 7.10
Codename: gutsy
/var/log/dist-upgrade/main.log:
2008-03-23 00:09:06,460 INFO release-upgrader version '0.87.12' started
2008-03-23 00:09:07,002 DEBUG Using 'DistUpgradeViewGtk' view
2008-03-23 00:09:07,159 DEBUG lsb-release: 'gutsy'
2008-03-23 00:09:07,159 DEBUG _pythonSymlinkCheck run
2008-03-23 00:09:08,794 DEBUG checkViewDepends()
$ sudo apport-cli -f -P 9540
*** Collecting problem information
The collected information can be send to the developers to improve the
application. This might take a few minutes.
Traceback (most recent call last):
File "/usr/bin/apport-cli", line 282, in <module>
app.run_argv()
File "/var/lib/python-support/python2.5/apport/ui.py", line 253, in run_argv
self.run_report_bug()
File "/var/lib/python-support/python2.5/apport/ui.py", line 237, in run_report_bug
self.collect_info()
File "/var/lib/python-support/python2.5/apport/ui.py", line 348, in collect_info
icthread.exc_raise()
File "/var/lib/python-support/python2.5/apport/REThread.py", line 37, in run
self._retval = self.__target(*self.__args, **self.__kwargs)
File "/var/lib/python-support/python2.5/apport/ui.py", line 38, in thread_collect_info
report.add_hooks_info()
File "/var/lib/python-support/python2.5/apport/report.py", line 499, in add_hooks_info
assert self.has_key('Package')
AssertionError
UPDATE: This also happens to normal hardy (bug is a little old). |
|
2009-02-05 10:04:40 |
Michele Mangili |
update-manager: statusexplanation |
Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Ubuntu release? Thanks in advance. |
Hello, Philippe!
Your problem doesn't seem related to this bug report. So I suggest you should file a new report to describe your problem!
In the meantime I'm going to mark this report as "Invalid" because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again! |
|