Dapper upgrade problem

Bug #48260 reported by Ana George
6
Affects Status Importance Assigned to Milestone
update-manager (Ubuntu)
Invalid
Medium
Brian Murray

Bug Description

When trying to upgrade from Breezy to Dapper using the upgrade tool, I got the following error:

Could not install 'libgnomecupsui1.0-1'

subprocess post-removal script returned error exit status 135

The same message occurs when I do the following from the command line:

% sudo apt-get -f install

I'm doing all this on an i386-class desktop machine.

Revision history for this message
Manuel López-Ibáñez (manuellopezibanez) wrote :

guessing package

Revision history for this message
Michael Vogt (mvo) wrote :

Thanks for your bugreport.

Can you please attach the files /var/log/dist-upgrade*.log to this bugreport?

Thanks,
 Michael

Changed in update-manager:
status: Unconfirmed → Needs Info
Revision history for this message
Ana George (ana-r-george) wrote : Re: [Bug 48260] Re: Dapper upgrade problem

Probably not. After trying (and failing) to upgrade, I attempted to
install from CDs, and that failed also (some kind of odd thing with
the disk partition utility; it wouldn't put a filesystem on my disk).
So I reinstalled 5.10. Meanwhile, all data from that disk were lost.

Ana

On 6/14/06, Michael Vogt <email address hidden> wrote:
> Thanks for your bugreport.
>
> Can you please attach the files /var/log/dist-upgrade*.log to this
> bugreport?
>
> Thanks,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Status: Unconfirmed => Needs Info
>
> --
> Dapper upgrade problem
> https://launchpad.net/bugs/48260
>

Revision history for this message
Brian Murray (brian-murray) wrote :

We are closing this bug report as it lacks the information, described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and feel free to submit bug reports in the future.

Changed in update-manager:
assignee: nobody → brian-murray
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.