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
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
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
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
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
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
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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
*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
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
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
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
$ 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
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
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
** 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
** 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
30 matches
Mail list logo
