Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)

2007-10-27 Thread Loye Young 
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

Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)

2007-10-25 Thread valten 
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

Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)

2007-10-25 Thread Loye Young 
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)

2007-10-25 Thread wateenellende 
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

Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)

2007-10-19 Thread cascokid 
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] 
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

Re: [Bug 107188] Re: [MASTER] [kde] Upgrade tool crashed with " Cannot allocate memory" (edgy -> feisty)

2007-10-18 Thread mvsjes2 
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