Distribution Upgrade says "There are no upgrades available for your system. The upgrade will now be canceled" when updating Gutsy RC to Gutsy Official

[Konstantin Kostov]

Binary package hint: update-manager

I am using Kubuntu Gutsy RC.
Today I've noticed that a Version Upgrade was available as an option in Adept so I've started the Distribution Upgrade tool.
After disabling 3rd party sources and telling me that there are packages which are no longer supported, the program showed an error message stating that:

"There are no upgrades available for your system. The upgrade will now be canceled."

I find it curious that there are no updates available for the RC version. (last update was 2 days ago)

[Luca Citi (knulp79)]

Same exact error for me.

[Scott Kitterman (kitterman)]

You get the version upgrade because Gutsy is no longer a development release, but a production release.

There are no updates because there were no updates.

[Luca Citi (knulp79)]

Thanks for your quick answer.
I think the situation is different from what you imagine.
I would expect to see the "Version upgrade" button in adept, to click it, to receive an information message saying my system is up to date and to have Gutsy running.
What happens is that after clicking the "Version upgrade" button I get an _error_ message (white x on red bg) saying
"There are no upgrades available for your system. The upgrade will now be canceled."
Later, everytime I run adept, I am notified about a new version but if I click it I always receive the same message.
I am not bothered by this "Version upgrade" button but I would like to know whether I have a "real" Gutsy installed and whether I will receive updates when available.
Thank you again.

I am running 64bit Kubuntu.

[Luca Citi (knulp79)]

It is the same as Bug #153900
and similar to Bug #151943
but I have no /etc/apt/preferences (the user in Bug #151943 fixed the problem with)

[Konstantin Kostov (kostovnet)]

Yes, exactley the same situation, however I am running a 32bit version of the OS.
After looking through the apt.log in /var/log/dist-upgrade I've noticed something that might be related to this:

...after installing and checking dependencies (files attached)

kdecore (KProcess): WARNING: setPty()
kdecore (KProcess): WARNING: _attachPty() 93
updateStatus: Reading cache
updateStatus: Checking package manager
updateStatus: Updating repository information
updateStatus: Checking package manager
updateStatus: Asking for confirmation
updateStatus: Fetching
updateStatus: Upgrading
updateStatus: Searching for obsolete software
Error in sys.excepthook:
Traceback (most recent call last):
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeViewKDE.py", line 460, in _handleException
    if not run_apport():
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeApport.py", line 44, in run_apport
    ret = subprocess.call(p)
  File "/usr/lib/python2.5/subprocess.py", line 443, in call
    return Popen(*popenargs, **kwargs).wait()
  File "/usr/lib/python2.5/subprocess.py", line 593, in __init__
    errread, errwrite)
  File "/usr/lib/python2.5/subprocess.py", line 1061, in _execute_child
    self.pid = os.fork()
OSError: [Errno 12] Cannot allocate memory

Original exception was:
Traceback (most recent call last):
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/dist-upgrade.py", line 59, in <module>
    app.run()
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeControler.py", line 1346, in run
    self.fullUpgrade()
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeControler.py", line 1335, in fullUpgrade
    self.doPostUpgrade()
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeControler.py", line 945, in doPostUpgrade
    res = self.cache.commit(fprogress,iprogress)
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeCache.py", line 69, in commit
    apt.Cache.commit(self, fprogress, iprogress)
  File "/usr/lib/python2.5/site-packages/apt/cache.py", line 203, in commit
    if fetchProgress == None:
  File "/usr/lib/python2.5/site-packages/apt/cache.py", line 178, in installArchives
    # this can throw a exception
  File "/usr/lib/python2.5/site-packages/apt/progress.py", line 213, in run
    pid = self.fork()
  File "/tmp/kde-root/adept_managerfpj1ca.tmp-extract/DistUpgradeViewKDE.py", line 244, in fork
    self.child_pid = os.fork()
OSError: [Errno 12] Cannot allocate memory
X Error: BadDevice, invalid or uninitialized input device 158
  Major opcode: 150
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
X Error: BadDevice, invalid or uninitialized input device 158
  Major opcode: 150
  Minor opcode: 3
  Resource id: 0x0
Failed to open device
adept_manager: no process killed
adept_updater: no process killed
Starting
Starting 2
Done
MarkUpgrade() called on a non-upgrable pkg: 'kubuntu-desktop'
Error: "/var/tmp/kdecache-kosio" is owned by uid 1000 instead of uid 0.
updateStatus: Reading cache
updateStatus: Checking package manager
updateStatus: Updating repository information
updateStatus: Checking package manager
updateStatus: Asking for confirmation
upd...

[Slammer (slammer-o2)]

I have the same problem.
I am no Kubuntu developer but what I think this is is the updating tool incorrectly considered the message as an error during insallation and because of that the updater reverts all the changes that it has made (including the version change).

[beldon (beldon)]

Same error. Attempted to upgrade from devel to release. I have a Compaq Presario 2108US laptop using a wired ethernet connector (damned Broadcom!). 32-bits of course. Attached are my error logs.

[Slammer (slammer-o2)]

> You get the version upgrade because Gutsy is no longer a development release, but a production release. There are no updates because there were no updates.

The bug is not because the user gets the version update nor because there are no updates but because the version update does not succeed (and the upgrade option fails to dissapear).

[Slammer (slammer-o2)]

> "You get the version upgrade because Gutsy is no longer a development release, but a production release. There are no updates because there were no updates".
- The bug is reported not because the user gets the version update nor because there are no updates but because the version update does not succeed (and the upgrade option fails to dissapear).

[romassi (romassi1977)]

Same problem for me.
I've installed gutsy on 3 PCs (2 notebook and 1 desktop) since the release of tribe versions and regularly-daily updated all of them.
Last update found this morning (19 October).
This evening I noticed the bug: the version updater option in Adept manager is active even if the system is correctly updated.
I think the updater tool always undo all the changes made (including the erasing of itself) because it consider an error during upgrade the fact that the system is yet updated.

[alekiv (alekiv)]

 Same problem for me.

[kgfullerton (kevin-fullerton)]

Same problem here :(

[Konstantin Kostov (kostovnet)]

Today, I've noticed that the Version Upgrade option appears in adept ONLY if the Pre-released updates repository is enabled.
I have a second PC running Feisty and there I had the upgrade button without pre-released being enabled.

[deepdraft (dimitar.nedev)]

I tired turning of the pre-released updates, but nothig changed - the upgrade version button still appears.

[Stephen Seplowitz (sep1318)]

I get this bug, but from a clean install of Gutsy final.

[Brijam (brian-opensourcery)]

same issue here - Gutsy RC 64bit.

On my system Distribution Upgrade errors out at the Modifying the Software Channels stage.

[Sean McIntyre (s-mcintyre0)]

I installed Kubuntu final release today and I get this same message.

[Sandipan Mohanty (sandipan-mohanty)]

Yes, I also get this error, a day after installing the official release of Gutsy gibbon. I was surprised that adept told me there was a system upgrade available, when this thing is barely three days old. And then after doing some downloads, it told me that my system is up-to-date, and the upgrade will be cancelled. Not a real problem, but does not look good.

[diffuze (tina-drebel)]

I get the same message, problem with me is that I *have* the Gutsy final installed, made a clean install when it came out.

[Roger Downing (roger-downing)]

DItto here.

[bcscomp (bcscomp)]

me too:-((