Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
BigPick, You have been working incredibly hard on this, and I'm sure you are very tired and frustrated. You have done a great service already. You have already fixed the biggest issue and gotten the thing back to working much better. Many have already reported that your patches have enabled them to get their system upgraded. Your frustration is evidence of your deep commitment to Ubuntu and to excellence in everything you do. (And maybe a healthy dose of perfectionism thrown in as well?) You have many comrades who understand exactly what it feels like to bang your head against the wall, see the wall move farther than anyone else has ever done before, and still be pissed off that you can't move it the rest of the way. This is open source: it's all volunteer. Don't lose your sanity over it. If you are tired, take a break. Go do something else. One of three things will happen: It will still be there when you get back and you will have fresh perspectives, you will take a second look at it and decide you have better things to do, or someone will have picked up where you left off. If the problem is big enough, someone else will jump in to help, just like you did. St Jude is the patron saint of difficult cases. Perhaps while you are taking the weekend off, he can go have a talk with the One who programmed us all. :-) Happy Trails, Loye Young On Friday, October 26, 2007 5:01:06 pm BigPick wrote: All right, I am completely frustrated. First at my inability to fix the second memory leak and second by the total lack of developer input on this issue. My current working thoery is that commit() function in the Cache class of the python-apt library runs into an infinite loop if an archive install returns a result of Incomplete. My inability to replicate this error, and lack of familiarity with the python-apt library have thwarted my attempts to fix the problem. For now, I am just going to post the third revision of my patch, which is essentially a regression. The patch no longer alters the types of Exceptions caught by the programs try/catch statements as this was mainly an attempt at getting more information. This revision just has the single memory leak fix. I am incredibly displeased and disgusted by this entire situation. ** Attachment added: BigPick dist-upgrade patch rev 3 http://launchpadlibrarian.net/10180893/gutsy-dist-upgrade_bigpick_0.3.patch -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
All right, I am completely frustrated. First at my inability to fix the second memory leak and second by the total lack of developer input on this issue. My current working thoery is that commit() function in the Cache class of the python-apt library runs into an infinite loop if an archive install returns a result of Incomplete. My inability to replicate this error, and lack of familiarity with the python-apt library have thwarted my attempts to fix the problem. For now, I am just going to post the third revision of my patch, which is essentially a regression. The patch no longer alters the types of Exceptions caught by the programs try/catch statements as this was mainly an attempt at getting more information. This revision just has the single memory leak fix. I am incredibly displeased and disgusted by this entire situation. ** Attachment added: BigPick dist-upgrade patch rev 3 http://launchpadlibrarian.net/10180893/gutsy-dist-upgrade_bigpick_0.3.patch -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
yeah BigPick I also had your problem, trying to resolve a big problem and lack of devels. Unfortunately they have a lot of works and sometimes this a good excuse sometimes not. anyway try to write an email to the package maintainer [EMAIL PROTECTED] pointing your patches, I'm sure that he wants to resolve this bis issue with so many duplicates :) -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
BigPick: I'll test your patch as soon I go back home to see if I can confirm your results. However, I insist on what I (and others) have said. Until a definitive fix for this has been released, this should be considered a critical bug and, as it clearly affects many users, upgrading from Feisty should not be recommended. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Agreed. I should add that there are bugs in KDEsu (1), which hamper the use of adept-updater etc. Of 5 computers upgraded at home and at work, two were left in a completely unusable state (one recovered so far), the third is affected by this memory-bug (2). The fourth and fifth have been running gutsy for a long time and only required some manual downloading and installing of .deb files for udev volumeid, because this wasn't handled automatically. This was deemed not a bug because I should have use adept or the upgrade manager, which was obviously not possble because of bugs (1) and (2). All in all, I'm NOT impressed: 0 out of 5 upgrades successful. For now, I recommend against upgrading. Therefore, creating the patch is very important and I hope it works out, but for now I'm too busy fixing my unbootable machine to try it. On 10/25/07, FerranRius [EMAIL PROTECTED] wrote: BigPick: I'll test your patch as soon I go back home to see if I can confirm your results. However, I insist on what I (and others) have said. Until a definitive fix for this has been released, this should be considered a critical bug and, as it clearly affects many users, upgrading from Feisty should not be recommended. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a direct subscriber of a duplicate bug. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Many thanks for the help you guys. I would also like to thank John and Christian Assig for their efforts so far. FerranRius's comment is very prudent and correct however, this upgrade should not be attempted whatsoever by anyone who uses their machine for work, school, or other important operations. The patch I posted is simply the fix I came up with for my situation when I attempted to upgrade Feisty on the laptop I use around campus. I never thought I'd be thankful for dual-booting windows, and to be honest, I resent the need to rely on it. Luckily, I have two old towers I use as sandboxes for messing around with networking and various Unix installations. One is an Intel/nVidia, the other is AMD/ATI, both failed the upgrade and became unbootable (so I'm 0 for 3), making them perfect candidates for trying to fix this. Currently there are two memory leaks occurring as far as I can tell, only one of which I have identified and addressed in the patch. The second appears to be coming from the fetching of backport archives, which occurs prior to the main upgrade. I am unable to replicate this leak on my machines, so I have relied on the work of Christian Assig to track this down. He deserves many thanks for bearing with my sophomoric efforts. Although this patch does not fix the second leak, Christian did report dist-upgrade faied gracefully instead of crashing by bringing up an error window and attempting to recover and reset the system. I need to repeat that I am not an official developer. I am a user with just enough information to make me dangerous. Nonetheless, I greatly appreciate your efforts to assist me in solving this critical issue. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
What happens if you use aptitude --full-upgrade instead of apt-get --dist-upgrade in the script? On 10/25/07, BigPick [EMAIL PROTECTED] wrote: Many thanks for the help you guys. I would also like to thank John and Christian Assig for their efforts so far. FerranRius's comment is very prudent and correct however, this upgrade should not be attempted whatsoever by anyone who uses their machine for work, school, or other important operations. The patch I posted is simply the fix I came up with for my situation when I attempted to upgrade Feisty on the laptop I use around campus. I never thought I'd be thankful for dual-booting windows, and to be honest, I resent the need to rely on it. Luckily, I have two old towers I use as sandboxes for messing around with networking and various Unix installations. One is an Intel/nVidia, the other is AMD/ATI, both failed the upgrade and became unbootable (so I'm 0 for 3), making them perfect candidates for trying to fix this. Currently there are two memory leaks occurring as far as I can tell, only one of which I have identified and addressed in the patch. The second appears to be coming from the fetching of backport archives, which occurs prior to the main upgrade. I am unable to replicate this leak on my machines, so I have relied on the work of Christian Assig to track this down. He deserves many thanks for bearing with my sophomoric efforts. Although this patch does not fix the second leak, Christian did report dist-upgrade faied gracefully instead of crashing by bringing up an error window and attempting to recover and reset the system. I need to repeat that I am not an official developer. I am a user with just enough information to make me dangerous. Nonetheless, I greatly appreciate your efforts to assist me in solving this critical issue. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a direct subscriber of a duplicate bug. -- Loye Young Isaac Young Computer Company Laredo, Texas (956) 857-1172 [EMAIL PROTECTED] -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
i have managed to make the update after all with several apt-get upgrade commands so i cannot provide this information anymore, sorry ... On 10/25/07, Loye Young [EMAIL PROTECTED] wrote: What happens if you use aptitude --full-upgrade instead of apt-get --dist-upgrade in the script? On 10/25/07, BigPick [EMAIL PROTECTED] wrote: Many thanks for the help you guys. I would also like to thank John and Christian Assig for their efforts so far. FerranRius's comment is very prudent and correct however, this upgrade should not be attempted whatsoever by anyone who uses their machine for work, school, or other important operations. The patch I posted is simply the fix I came up with for my situation when I attempted to upgrade Feisty on the laptop I use around campus. I never thought I'd be thankful for dual-booting windows, and to be honest, I resent the need to rely on it. Luckily, I have two old towers I use as sandboxes for messing around with networking and various Unix installations. One is an Intel/nVidia, the other is AMD/ATI, both failed the upgrade and became unbootable (so I'm 0 for 3), making them perfect candidates for trying to fix this. Currently there are two memory leaks occurring as far as I can tell, only one of which I have identified and addressed in the patch. The second appears to be coming from the fetching of backport archives, which occurs prior to the main upgrade. I am unable to replicate this leak on my machines, so I have relied on the work of Christian Assig to track this down. He deserves many thanks for bearing with my sophomoric efforts. Although this patch does not fix the second leak, Christian did report dist-upgrade faied gracefully instead of crashing by bringing up an error window and attempting to recover and reset the system. I need to repeat that I am not an official developer. I am a user with just enough information to make me dangerous. Nonetheless, I greatly appreciate your efforts to assist me in solving this critical issue. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a direct subscriber of a duplicate bug. -- Loye Young Isaac Young Computer Company Laredo, Texas (956) 857-1172 [EMAIL PROTECTED] -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) https://bugs.launchpad.net/bugs/107188 You received this bug notification because you are a direct subscriber of a duplicate bug. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
so the problem is a memory leak, then developers have for sure more details now, well I hope. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I am pleased to report that using the above patch, my second sandbox tower was finally able to upgrade using the dist-upgrade.py script without error. I will run the test again on my other sandbox tower as soon as I revert it back to a Feisty install. Right now, I need to go to bed. While this result bodes well, I still need you all to try out the patch and report your results back here. Doing so will greatly aid in the resolution of other errors that still may be lurking. If you need some help applying the patch I posted instructions in the other bug report linked above, just make sure you download the second patch revision instead of the one used in the example. Once you have run the patch, successful or not, please post the log files located in /var/log/dist- upgrade/. I am not a developer, I am just a lowly peon user who had his install corrupted when the update-manager crashed. As such I need your assistance in getting this patch tested and, if successful, pushed to the higher-ups. Thank you for your help. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Hello fellow frustrated users. I also ran into this problem earlier. I have been working on a patch that resolves a major memory leak in the dist-upgrade scripts. Certain raised exceptions are causing infinite loops to occur. Currently, I have only been able to resolve one of these infinite loops, but the memory leak still remains. On the plus side, the upgrade is able to gracefully fail with the current patch and attempt recovery instead of just exiting. I would love to have some of you all test it out and post your resulting logs. It will greatly help diagnose the problem. For full info see this other bug: https://bugs.launchpad.net/ubuntu/+source/adept/+bug/154493 ** Attachment added: BigPick dist-upgrade patch rev 2 http://launchpadlibrarian.net/10144385/gutsy-dist-upgrade_bigpick_0.2.patch -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Hi! It seems that I am one the clueless users that have been hit by this bug. I even filled a bug report (https://bugs.launchpad.net/ubuntu/+source/update-manager/+bug/154278), that was obviously marked as duplicate. I wonder what is the best way of action for me. I can think the following actions: a) Wait until the bug is solved. After reading this thread it doesn't seem that this is going to happen nearly b) Install the Gnome part of Ubuntu and do the upgrade using the Gnome updater tool c) Use a more or less cryptic workaround d) Wait until Kubuntu 8.04 e) Other that I cannot think right now The truth is that not upgrading the distro is not a big problem for me. In fact I will do it only to get the newest OpenOffice.org (I wish that Ubuntu prepared packets for older distributions to avoid upgrading the distro, but this is another story). What do you suggest me to do? Thanks, Javier -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I had the same problem during upgrade to the RC: I confirmed to remove some packages and pretty much immediately afterwards the update manager(kde) hung up reproducibly. I have 512 RAM and 768 Swap. I tried upgrading once more, it crashed at the same spot. Then I used apt-get dist-upgrade which seemed to pretty much install everything. But now I still get the message: An upgrade for your system is available. When I now run the update-manager it tells me it needs to remove packages. After I confirm this, it tells me that my distribution is already up to date. But e.g. compiz was not activated or even installed. My memory error is the following: updateStatus: Systemaktualisierung wird durchgeführt Error in sys.excepthook: Traceback (most recent call last): File /tmp/kde-root/adept_managert7pdwb.tmp-extract/DistUpgradeViewKDE.py, line 460, in _handleException if not run_apport(): File /tmp/kde-root/adept_managert7pdwb.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_managert7pdwb.tmp-extract/dist-upgrade.py, line 59, in module app.run() File /tmp/kde-root/adept_managert7pdwb.tmp-extract/DistUpgradeControler.py, line 1346, in run self.fullUpgrade() File /tmp/kde-root/adept_managert7pdwb.tmp-extract/DistUpgradeControler.py, line 1328, in fullUpgrade if not self.doDistUpgrade(): File /tmp/kde-root/adept_managert7pdwb.tmp-extract/DistUpgradeControler.py, line 798, in doDistUpgrade res = self.cache.commit(fprogress,iprogress) File /tmp/kde-root/adept_managert7pdwb.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 res = self.installArchives(pm, installProgress) File /usr/lib/python2.5/site-packages/apt/cache.py, line 178, in installArchives res = installProgress.run(pm) File /usr/lib/python2.5/site-packages/apt/progress.py, line 213, in run pid = self.fork() File /tmp/kde-root/adept_managert7pdwb.tmp-extract/DistUpgradeViewKDE.py, line 244, in fork self.child_pid = os.fork() OSError: [Errno 12] Cannot allocate memory updateStatus: Paketverwaltung wird überprüft X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device X Error: BadDevice, invalid or uninitialized input device 169 Major opcode: 145 Minor opcode: 3 Resource id: 0x0 Failed to open device adept_manager: Kein Prozess beendet adept_updater: Kein Prozess beendet and the second time: updateStatus: Systemaktualisierung wird durchgeführt Error in sys.excepthook: Traceback (most recent call last): File /tmp/kde-root/adept_manager8rwcHb.tmp-extract/DistUpgradeViewKDE.py, line 460, in _handleException if not run_apport(): File /tmp/kde-root/adept_manager8rwcHb.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_manager8rwcHb.tmp-extract/dist-upgrade.py, line 59, in module app.run() File /tmp/kde-root/adept_manager8rwcHb.tmp-extract/DistUpgradeControler.py, line 1346, in run self.fullUpgrade() File /tmp/kde-root/adept_manager8rwcHb.tmp-extract/DistUpgradeControler.py, line 1328, in fullUpgrade if not self.doDistUpgrade(): File /tmp/kde-root/adept_manager8rwcHb.tmp-extract/DistUpgradeControler.py, line 798, in doDistUpgrade res = self.cache.commit(fprogress,iprogress) File /tmp/kde-root/adept_manager8rwcHb.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 res = self.installArchives(pm, installProgress) File /usr/lib/python2.5/site-packages/apt/cache.py, line 178, in installArchives res = installProgress.run(pm) File /usr/lib/python2.5/site-packages/apt/progress.py, line 213, in run pid = self.fork() File
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Missed Something - I also find it a very serious thing that this outstanding issue is not mentioned in the release notes or upgrade guide. This is for some a critical defect, and I would definitely expect a mention of it there. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Cascokid - follow the links at the bottom of the email notification, and log in to launchpad (use the remind me tool if you have forgotten your login). Then in the menu on the top left, there is an Unsubscribe button that will do the magic for you. I will second Tzvetan and say that I view this as a serious defect that may turn people away from Ubuntu and possibly from Linux if that is their user experience. While I would be confident to apply such patches, I say so knowing that I am a software engineer with many years experience coding and using nix variants. To the average user, that simply does not apply, and it will frustrate them. It is worth reading the top of the defect and noting that although in the initial posting it complains about being out memory and the upgrade actually appears to have succeeded, later comments expressed machines no longer booting or failing to connect to the network. I would go as far as strongly suggesting that the KDE release of Gutsy should not be recommended as an upgrade path from Feisty (or earlier) without a reinstall until this is fixed. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I don't think it is realistic to expect that ordinary users will be able to find this bug and administer a workaround from the command line on their own. At the very least a detailed description of the problem and the workaround should be prominently displayed in the upgrade instructions. I still keep getting notifications of new people submitting duplicates of this bug when upgrading to Gutsy. Once people lose confidence in the OS, it's very tough trying to restore it. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Workaround or not. I also think that this bug is very serious. It is really too bad that it has not been fixed yet. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Does anyone know how to unsubscribe to these notifications? Tzvetan Mikov wrote: I don't think it is realistic to expect that ordinary users will be able to find this bug and administer a workaround from the command line on their own. At the very least a detailed description of the problem and the workaround should be prominently displayed in the upgrade instructions. I still keep getting notifications of new people submitting duplicates of this bug when upgrading to Gutsy. Once people lose confidence in the OS, it's very tough trying to restore it. -- Peter Leopold, Ph.D. President BioAnalyte Inc. 58 Fore St. Bldg 5 Portland, ME 04101 (tel) 207-780-6777 x202 (fax) 207-221-1385 (cel) 207-831-5561 [EMAIL PROTECTED] http://www.bioanalyte.com STATEMENT OF CONFIDENTIALITY The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain confidential or privileged information. If you are not the intended recipient, please notify the sender immediately at either (207) 780-6777 x202 or at [EMAIL PROTECTED], and destroy all copies of this message and any attachments. Thank you for your cooperation. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Guys, is there any progress on this bug ? It is extremely serious. It was reported during the upgrade to Feisty, and it looks like it is still present during the upgrade to Gutsy. I was bitten before, when I upgraded a coworker's computer to Feisty (thank god he didn't attempt to do it alone). I checked the Kubuntu upgrade instructions (http://kubuntu.org/announcements/7.10-release.php#upgrade) and there is no mention of this problem or a workaround. So, is it safe to upgrade ? -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I sent in a work around for this, so I don't think it's extremely serious, just extremely annoying. :-) From my recall, the upgrade had been completed, it was just the cleanup that was not done, and the workaround allows you to clean up manually. It is too bad that the bug hasn't been fixed though. Robin Murray Tzvetan Mikov wrote: Guys, is there any progress on this bug ? It is extremely serious. It was reported during the upgrade to Feisty, and it looks like it is still present during the upgrade to Gutsy. I was bitten before, when I upgraded a coworker's computer to Feisty (thank god he didn't attempt to do it alone). I checked the Kubuntu upgrade instructions (http://kubuntu.org/announcements/7.10-release.php#upgrade) and there is no mention of this problem or a workaround. So, is it safe to upgrade ? -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I've tried again today to see if something had changed. I had to power off the computer. I restarted in safe mode and did an apt-get update apt-get dist-upgrade and everything seems to be working fine together. I think this is a very important issue, as it seems to be affecting quite a lot of people using Kubuntu Gutsy, and 'kdesu adept_manager --version-upgrade' is supposed to be the recommended way to upgrade from Feisty to Gutsy. My opinion as a user is that this bug should be fixed before Gutsy release or, if it's not possible, a workaround for upgrading should be recommended. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
*disclaimer: first launchpad posting* # 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 (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Same problem while trying 'kdesu adept_manager --dist-upgrade-devel' (I was already using Gutsy). I have 512 MB of ram, when the upgrader started to download packages, the system became very slow and all the ram and 500 MB of swap were used. ** Attachment added: /var/log/dist-upgrade/main.log http://launchpadlibrarian.net/9708258/main.log -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Upon further investigation, it looks like a python-kde3/konsole issue. See Bug #117731. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
I think this is a fundamental design problem that is going to take some serious rework if this is going to work on low memory systems. I hunted down were the memory is getting eaten up. It's in DistUpgradeControler.py. I added comments to the procedure below to show the fatal line. The bottom line is that the system is just trying to cache more than a machine with limited memory can hande. Someone who knows more about the what and the why of the cache will have to look and see if it can be slimmed down. def doDistUpgrade(self): # get the upgrade currentRetry = 0 fprogress = self._view.getFetchProgress() iprogress = self._view.getInstallProgress(self.cache) # retry the fetching in case of errors maxRetries = self.config.getint(Network,MaxRetries) while currentRetry maxRetries: try: # THIS IS THE FATAL LINE: res = self.cache.commit(fprogress,iprogress) # THE ONE ABOVE THIS ONE. except SystemError, e: logging.error(SystemError from cache.commit(): %s % e) # check if the installprogress catched a pkgfailure, if not, generate a fallback here if iprogress.pkg_failures == 0: errormsg = SystemError in cache.commit(): %s % e apport_pkgfailure(update-manager, errormsg) # invoke the frontend now msg = _(The upgrade aborts now. Your system could be in an unusable state. A recovery will run now (dpkg --configure -a).) if not run_apport(): msg += _(\n\nPlease report this bug against the 'update-manager' package and include the files in /var/log/dist-upgrade/ in the bugreport.\n %s % e) self._view.error(_(Could not install the upgrades), msg) # installing the packages failed, can't be retried self._view.getTerminal().call([dpkg,--configure,-a]) self._rewriteAptPeriodic(self.apt_minAge) return False except IOError, e: # fetch failed, will be retried logging.error(IOError in cache.commit(): '%s'. Retrying (currentTry: %s) % (e,currentRetry)) currentRetry += 1 continue # no exception, so all was fine, we are done self._rewriteAptPeriodic(self.apt_minAge) return True -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
$ top | grep python 24518 root 17 0 132m 92m 46m R 3.5 36.9 0:45.67 python 24518 root 17 0 132m 92m 46m D 16.4 37.0 0:46.17 python 24518 root 18 0 750m 156m 23m D 35.1 62.5 0:47.23 python 24518 root 18 0 750m 155m 21m D 4.8 62.0 0:47.40 python 24518 root 18 0 750m 160m 20m D 3.6 64.3 0:47.51 python 24518 root 18 0 750m 165m 12m D 6.3 66.2 0:47.70 python The jump from 132m to 750m (the size of the swap file on this system) was almost instantaneous when the update-manager transitioned from download packages to starting the upgrade. So the system is truly out of memory it would appear. -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Baltix doesn't use KDE as default ** Changed in: update-manager (Baltix) Status: New = Invalid -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
Still getting this on PIII-700 w/256 MB RAM and current Feisty Kubuntu + 3.5.7: Traceback (most recent call last): File dist-upgrade.py, line 56, in module app.run() File /home/kitterma/upgrader/DistUpgradeControler.py, line 1255, in run self.fullUpgrade() File /home/kitterma/upgrader/DistUpgradeControler.py, line 1237, in fullUpgrade if not self.doDistUpgrade(): File /home/kitterma/upgrader/DistUpgradeControler.py, line 769, in doDistUpgrade res = self.cache.commit(fprogress,iprogress) File /usr/lib/python2.5/site-packages/apt/cache.py, line 203, in commit res = self.installArchives(pm, installProgress) File /usr/lib/python2.5/site-packages/apt/cache.py, line 178, in installArchives res = installProgress.run(pm) File /usr/lib/python2.5/site-packages/apt/progress.py, line 213, in run pid = self.fork() File /home/kitterma/upgrader/DistUpgradeViewKDE.py, line 227, in fork self.child_pid = os.fork() OSError: [Errno 12] Cannot allocate memory -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
** Summary changed: - [MASTER] [kde] Upgrade tool crashed (edgy - feisty) + [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) ** 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 -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
[Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty)
** Tags added: metabug -- [MASTER] [kde] Upgrade tool crashed with Cannot allocate memory (edgy - feisty) 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
