auto-update from ubuntu software update crashed out on linux package

[ghostdoc]

no further info, my first successful boot of ubuntu ;)

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 8.10
ErrorMessage: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not permitted
LsUsb:
 Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Package: linux-image-2.6.27-7-generic 2.6.27-7.14
ProcCmdLine: User Name=UUID=C4D6-0F72 loop=/hostname/disks/home/username.disk ro ROOTFLAGS=sync acpi=off noapic nolapic single
ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
SourcePackage: linux
Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to install/upgrade: unable to make backup link of `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation not permitted

[Leann Ogasawara (leannogasawara)]

Hi ghostdoc,

Is this a wubi installation? The reason I ask is this seems to be a duplicate of bug 252900. Please let us know, thanks.

[ghostdoc (mfhholmes)]

yes, it is...apologies if it's a duplicate but it's an auto-generated
report!

Bit of background if it helps: I had to run wubi in Windows Me compatability
mode to get it to run at all (on windows XP sp2). Wubi didn't complete
succesfully and I had to hand-craft the boot.ini entry for Ubuntu, and then
Ubuntu bootup didn't complete successfully and hung just before the login
screen. I ended up booting in recovery mode and removing compwiz. Ubuntu
finally booted and started working, and apart from hanging on shutdown (so
having to unplug the battery to get it to shut down) it's been working fine
(and very impressive once working).
This error occurred when doing the auto-update once it was up and running.
One of the packages crashed and brought down the auto-update process. I've
tried updating that package again, and no joy (it still crashes).
Running on a 5-year old samsung laptop with integrated graphics and only
500Mb memory. I can probably dig up specifics if they're required...

On Fri, Apr 10, 2009 at 9:30 AM, Leann Ogasawara <
<email address hidden>> wrote:

> Hi ghostdoc,
>
> Is this a wubi installation? The reason I ask is this seems to be a
> duplicate of bug 252900. Please let us know, thanks.
>
> ** Changed in: linux (Ubuntu)
> Status: New => Incomplete
>
> --
> auto-update from ubuntu software update crashed out on linux package
> https://bugs.launchpad.net/bugs/357737
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in “linux” source package in Ubuntu: Incomplete
>
> Bug description:
> no further info, my first successful boot of ubuntu ;)
>
> ProblemType: Package
> Architecture: i386
> DistroRelease: Ubuntu 8.10
> ErrorMessage: unable to make backup link of
> `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation
> not permitted
> LsUsb:
> Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
> Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
> Package: linux-image-2.6.27-7-generic 2.6.27-7.14
> ProcCmdLine: User Name=UUID=C4D6-0F72
> loop=/hostname/disks/home/username.disk ro ROOTFLAGS=sync acpi=off noapic
> nolapic single
> ProcVersionSignature: Ubuntu 2.6.27-7.14-generic
> SourcePackage: linux
> Title: package linux-image-2.6.27-7-generic 2.6.27-7.14 failed to
> install/upgrade: unable to make backup link of
> `./boot/vmlinuz-2.6.27-7-generic' before installing new version: Operation
> not permitted
>

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug '252900', so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.