Upgrade to Edgy fails ("Cannot remove /usr/X11R6/bin directory") if Opera is installed

Bug #68983 reported by Matthew Paul Thomas
4
Affects Status Importance Assigned to Milestone
Ubuntu
Undecided
Michael Vogt

Bug Description

While upgrading from Ubuntu 6.06.1 to Ubuntu 6.10, with Opera installed from the dapper-commercial repository, I received an error message: "This upgrade requires that the /usr/X11R6/bin directory be removed and replaced with a symlink. An attempt was made to do so, but it failed, most likely because the directory is not yet empty. You must move the files that are currently in the directory out of the way so that the installation can complete. If you like, you may move them back after the symlink is in place."

This is a very well-written error message, but expecting people to follow these instructions themselves is still far beyond the realm of most people who use computers. One possible solution is for the installation process to create the new directory, then move the contents of /usr/X11R6/bin/ to that new directory, *then* replace /usr/X11R6/bin with a symlink.

Furthermore, the instructions don't actually work. Even after moving the opera/ subdirectory out of the way, the dist-upgrade still fails, with a message like "trying to overwrite /user/X11R6/bin, which is also used by package opera". And if I use Synaptic to try uninstalling Opera first, it wants me to uninstall half the world at the same time (including gdm, gksu, update-notifier, and xserver-xorg).

Revision history for this message
Fabio Massimo Di Nitto (fabbione) wrote :

This bug needs to be fixed in opera. The script does not check only the contents of /usr/X11R6/bin but also what's recorded in the package database. Moving files around at random won't work. Also.. we did kill usr/X11R6/bin before dapper. That means that opera package in commercial repo is wrong.

description: updated
Revision history for this message
Matthew Paul Thomas (mpt) wrote :

This bug is not a bug in update-manager, because update-manager denied knowledge of any new version of Ubuntu, so (following the instructions on <https://help.ubuntu.com/community/EdgyUpgrades>) I used aptitude dist-upgrade instead.

Changed in update-manager:
assignee: nobody → mvo
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers