Javier there is a workaround, change the config file and start the update in 
text mode, this worked around for me.
I've copied into first post steps.

** Description changed:

  For some people the kde version of the release upgrader crashes with the
  follow stacktrace on a edgy to feisty release upgrade:
  
  Binary package hint: update-manager
  
  Traceback (most recent call last):
    File "dist-upgrade.py", line 56, in ?
      app.run()
    File "/home/bhughes/upgrader/DistUpgradeControler.py", line 1025, in run
      self.fullUpgrade()
    File "/home/bhughes/upgrader/DistUpgradeControler.py", line 1014, in 
fullUpgrade
      self.doPostUpgrade()
    File "/home/bhughes/upgrader/DistUpgradeControler.py", line 740, in 
doPostUpgrade
      res = self.cache.commit(fprogress,iprogress)
    File "/usr/lib/python2.4/site-packages/apt/cache.py", line 204, in commit
      if res == pm.ResultCompleted:
    File "/usr/lib/python2.4/site-packages/apt/cache.py", line 179, in 
installArchives
      installProgress.finishUpdate()
    File "/usr/lib/python2.4/site-packages/apt/progress.py", line 206, in run
      select.select([self.statusfd],[],[], self.selectTimeout)
    File "/home/bhughes/upgrader/DistUpgradeViewKDE.py", line 225, in fork
      self.child_pid = os.fork()
  OSError: [Errno 12] Cannot allocate memory
+ 
+ ############
+ TEMP WORKAROUND
+ ############
+ 
+ It looks like Scott might be right, it's a KDE/qt issue. The way I
+ worked around this during my upgrade from Feisty to Gutsy is the
+ following:
+ 
+ 1. Run 'kdesu "adept_manager --version-upgrade"', attempt the upgrade, and 
allow it to fail.
+ 2. Via a terminal, go to /tmp/kde-root/adept_manager(something).tmp-extract
+ 3. Edit DistUpgrade.cfg so that it only tries to do the upgrade in text mode 
since python can't load the libs for GTK, and QT has the memory issue
+ 4. Save file
+ 5. Run (as root) dist-upgrade.py

-- 
[MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory"
https://bugs.launchpad.net/bugs/107188
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to