Can't calculate the upgrade with unofficial mesa/compiz packages

Please try sudo apt-get -f install if that doesnt work please install ubuntu-desktop package and try updating again.

After running both commands it informs me everything is uptoday and ubuntu-desktop is installed and current. The update still fails as well.

What is it failing on this time? can i have the full output of the dist-upgrade? Might not need it try this first. sudo apt-get install xserver-xorg-core xorg xserver-xorg-video-all. you might also need to install libgl1-mesa-glx. libgl1-mesa-glx not being installed seems to be the biggest issue with people upgrades the past few days

dude052@dude052-laptop:~$ sudo apt-get install xserver-xorg-core xorg xserver-xorg-video-all
Reading package lists... Done
Building dependency tree... Done
xserver-xorg-core is already the newest version.
E: Couldn't find package xorg
dude052@dude052-laptop:~$ sudo apt-get install libgl1-mesa-glx Reading package lists... Done
Building dependency tree... Done
E: Couldn't find package libgl1-mesa-glx

My error stands as before, it fails in the same place with the same error.

Can you please attach a copy of your /etc/apt/sources.list file it looks like you are missing "main" repo.

Attached is my sources.list.

Thanks for your bugreport.

The attached logs contain all the information needed. There is a problem with the packagename changes in xorg from dapper->edgy that confuses the upgrader.

Cheers,
 Michael

Could you please try the upgrade again? I uploaded a new version of the dist-upgrade tools that may fix the reported issue.

Ok, tried again but the error stands the same. Exact same place and same error message.

I've already upgraded via hand (dist-upgrade) and manually removed python and the above mentioned libraries. For me there is a current dbus issue though when I run the command:

root@atf:~# update-manager -c -d
/usr/lib/python2.4/site-packages/apt/__init__.py:17: FutureWarning: apt API not stable yet
  warnings.warn("apt API not stable yet", FutureWarning)
warning: could not initiate dbus
could not send the dbus Inhibit signal: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
root@atf:~#

However dbus is up except for the avahi-daemon bug:

joey@atf:~$ sudo /etc/init
init.d/ initramfs-tools/
joey@atf:~$ sudo /etc/init.d/dbus restart
 * Stopping System Tools Backends system-tools-backends [ ok ]
 * Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon [fail]
 * Stopping Hardware abstraction layer hald [ ok ]
 * Stopping system message bus dbus [ ok ]
 * Starting system message bus dbus [ ok ]
 * Starting Hardware abstraction layer hald [ ok ]
 * Starting System Tools Backends system-tools-backends Empty compile time value given to use lib at /usr/share/system-tools-backends-2.0/scripts/SystemToolsBackends.pl line 25
                                                                         [ ok ]
joey@atf:~$

This message is harmless and should probably be removed. It only most likely means that you have no gnome-power-manager runing.

I investigated this problem closer today and I'm pretty convinced that the root is the libgl1-mesa-dri package from the repository at http://www.beerorkid.com/compiz/.

Removing that package fixed the upgrade for me (the package has e.g. the problem that the version is bigger than the versionnumber of it in edgy).

I change the priority of this to low because the problem only exists with unofficial repositories.

I don't know much about package management, but it seems like it might be a few more packages than just libgl1-mesa-dri involved.

I attempted to just remove libgl1-dri earlier and perform an upgrade, but it continued to fail unless I removed more. There are a total of 7 packages I removed:

libgl1-mesa
libgl1-dev
libgl1-dri
libglu1-mesa
libglu1-mesa-dev
mesa-common-dev
mesa-utils

Some of those might not be essential to remove, but I did remove them nevertheless.

The trouble is that you can't just remove them. As Aum11 mentioned in one of the dups of this bug, x-window-system-core is dependent upon libgl1-dri.

I tried just downgrading that package to what is in the ubuntu repository, but I then got a report that there were about 50 apps that were going to be removed. They were important ones like gdm, gksu, nvidia-glx, hal-device-manager, etc.

I uninstalled these apps by hand, downgraded libgl1-dri, and reinstalled them. I was able to get through most of the upgrade, though it failed later on. I'll probably try to upgrade again later to see if I can work around the other error, but I'm not looking forward to uninstalling and reinstalling 50 packages by hand. :)

My question is whether it is a bug in synaptic which caused a forced downgrade in libgl1-dri to think it had to remove all of those (literally 50) packages. They clearly weren't dependent on the 6.5.1+cvs20060824 version because I was able to reinstall all 50 after removing them and downgrading libgl1-dri (and the other packages listed above.)

I know we are at fault for installing something that wasn't in the ubuntu repository, but I'm thinking that synaptic should be a little more helpful at bailing us out. :)

Thanks,
-M

Thanks for your detailed analysis.

There is a open bug against synaptic that it is not very good about dealing with downgrades (bug #15019).

To deal with your problem you may try to remove the unoffical compiz sources.list entry (or comment it out). Then run apt-get update (it is fine if the system is still dapper and has dapper sources.list entries) to make sure that your system knows about the available packages. Then:
$ sudo dpkg -r --force-depends libgl1-mesa libgl1-dev
libgl1-dri libglu1-mesa libglu1-mesa-dev mesa-common-dev mesa-utils
$ sudo apt-get install -f

Usually it is not a good idea to use --force-depends. The apt-get install -f should be able to cleanup the damage, but there is a chance that it screws your system. So be careful and have backups of your data :)

Cheers,
 Michael

Soory for waisting you time :)

But i did check i could not find the same any other report like this

Best regards

Duarte Molha

On 9/26/06, Gert Kulyk <email address hidden> wrote:
>
> ** Bug 62459 has been marked a duplicate of this bug
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
=========================
     Duarte Miguel Paulo Molha
         Tel: +447795416232
  Email: <email address hidden>
=========================

In the meantime reporting a bug does nothing have to do with waisting someones time :-). You should try not to duplicate reports, but often at a first glance it is not obvious that an issue is related to another. So keep on reporting bugs!

What could be the cause of this error on a freshly installed system. I recently reinstalled my ubuntu installation (keeping /home unchanged) and i get the same error without even entering the compiz webpage. Is it possible that i have something unappropriate left in my /home or what could it possible be?

I don't now either

:S

Hope you can get it to work again... I just gave up and did a completly new
instalation

Cheers

Duarte

On 10/2/06, Krister Svanlund <email address hidden> wrote:
>
> What could be the cause of this error on a freshly installed system. I
> recently reinstalled my ubuntu installation (keeping /home unchanged)
> and i get the same error without even entering the compiz webpage. Is it
> possible that i have something unappropriate left in my /home or what
> could it possible be?
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
=========================
     Duarte Miguel Paulo Molha
         Tel: +447795416232
  Email: <email address hidden>
=========================

I had the exact same problem and followed the steps in Comment #16. I then re-installed the ubuntu-desktop package.

After that, my upgrade to Edgy began to proceed.

Thanks for the tip,

Tim

Just another confirmation that this:

$ sudo dpkg -r --force-depends libgl1-mesa libgl1-dev
libgl1-dri libglu1-mesa libglu1-mesa-dev mesa-common-dev mesa-utils
$ sudo apt-get install -f

worked fine for me with exactly the same problem.

Thanks.

After removing the seven packages mentioned earlier, i have been able to do an upgrade.

It works again for almost everything, except Azureus won't start, but that's an other problem.

Thanks.

Just thought I'd be annoying and point out that: -
'A unresolvable problem occured while calculating the upgrade.' should read: -
'An unresolvable problem occured while calculating the upgrade.'

Might as well fix that spelling mistake while you're working in the same area! ;-)

Liam its fixed now can we worry about the bug and not so much the spelling?

Sorry, I didn't mean the description in the bugnote. I was talking about the error message displayed by the update-manager. The bugnote description of the error is--or was, rather--correct!

My apologies, perhaps I should have raised another bug note for this. Didn't think it was worth a new one as it was just a spelling mistake (in the error message).

Thanks Liam for reporting this spelling mistake! I value reports like this a lot especially since I'm not a native speaker and tend to make more spelling/grammar mistakes than others :)

Marked bug #65792 as a dup of this bug.

This command

$ sudo dpkg -r --force-depends libgl1-mesa libgl1-dev
libgl1-dri libglu1-mesa libglu1-mesa-dev mesa-common-dev mesa-utils
$ sudo apt-get install -f

also fixed my problem, which appears to be the same as the one mentioned in this bug report.

I have the same bug. Tried a few things documented here:
http://ubuntuforums.org/showthread.php?p=1638020#post1638020
but still same error.

I have had this same issue, but when I attempt a full upgrade in Synaptic, I get an error further down the line about xsession5 or something! I have used Automatix to get backports etc, I wonder if everyone else has done this too?

My current installation does not have the automatix; I used easy ubuntu.

On 10/20/06, Will McCourt <email address hidden> wrote:
>
> I have had this same issue, but when I attempt a full upgrade in
> Synaptic, I get an error further down the line about xsession5 or
> something! I have used Automatix to get backports etc, I wonder if
> everyone else has done this too?
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

Hi Michael,

I run exactly into the same issue. My compiz entry in sources.list was already commented out... and in fact, I thought I was running only official packages (I did a downgrade from the compiz ones a couple of months ago, when I run into an ugly font problem).

Running

$ sudo dpkg -r --force-depends libgl1-mesa libgl1-dev
libgl1-dri libglu1-mesa libglu1-mesa-dev mesa-common-dev mesa-utils
$ sudo apt-get install -f

solved the problem, but I lost ubuntu-desktop and x-window-system-core in the process.

After that, update-manager could do its job, and now It's happy downloading all the Edgy packages.

Given the fact that MANY users have been playing with GLX and compiz, I think it would be really nice if the update-manager could "learn" to deal with this problem for the final release. Otherwise, I'm afraid the mailing lists and forums will be flooded with messages regarding this issue.

Hi Mariano,

losing ubuntu-desktop in the process of cleaning this up is no problem. Update-manager will noticed and install it for you.

I'm looking into a fix for this problem currently. Unfortunately its not easy because the package version number from the unofficial repository is higher than the one in edgy. This means that those packages needs to be downgraded - something that is avoided by libapt usually. I'm currently investigating if it is feasbile to force the downgrade during the upgrade.

Cheers,
 Michael

I uploaded a new version of the dist-upgrader that should be able to deal with this situtation. It will be available in the archive soon and I would appreciate testing from people who haven't manually resolved the issue yet. What out for a directory called 20061023.1441 in http://archive.ubuntu.com/ubuntu/dists/edgy/main/dist-upgrader-all/ if you want to test it.

Thanks,
 Michael

The new version of the upgrader is now available, I would very much appreciate if you could give it a go if you haven't upgraded yet.

Thanks,
 Michael

Great, I'm going to give that a shot.
Sadly.. I screwed up my X somehow... a separate issue :(

-----Original Message-----
From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
Michael Vogt
Sent: Monday, October 23, 2006 12:44 PM
To: Davidson, William (<email address hidden>)
Subject: [Bug 58424] Re: Can't calculate the upgrade with
unofficialmesa/compiz packages

The new version of the upgrader is now available, I would very much
appreciate if you could give it a go if you haven't upgraded yet.

Thanks,
 Michael

--
Can't calculate the upgrade with unofficial mesa/compiz packages
https://launchpad.net/bugs/58424

Thks for this upgrade ... it worked fine :)
zero bug to report ... but i noticed that update-manager's window freezed
while cleaning ... is there any solution for that ?
And i had a small problem with xorg after restarting the system, seems that
it doesnt install nvidia driver so it cannot load it.
Good job anyway :)

On 10/23/06, Michael Vogt <email address hidden> wrote:
>
> The new version of the upgrader is now available, I would very much
> appreciate if you could give it a go if you haven't upgraded yet.
>
> Thanks,
> Michael
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Mehdi Dogguy
http://dogguy.info/
GNU/Linux user #371248

I'll second that, the upgrade worked, just my system didn't...

The xorg problem persisted with all drivers, but that's another issue (probably made worse by my use of beta nvidia drivers, compiz and all)

Great job, and thanks again

Thanks a lot for your tests!

I would like to know more about the xorg failures. If the upgrade worked and the system didn't, could you please attach the logs from the upgrade from /var/log/dist-upgrade/ ? And a short description what fails (e.g. nvidia driver not installed)? Or is this always related to installing the latest nvidia drivers by hand? If so, maybe we can find a way to fix/workaround this during the upgrade.

Cheers,
 Michael

The system upgraded and it works fine ... but i had to install manually
nvidia driver.
When in restarted my computer rightt after the upgrade, xorg used the old
xorg.conf in which nvidia driver is used in section "Device", so it cant be
loaded et xorg fails to start ... all i done is to put "nv" instead of
"nvidia" et try to re-install (when i got x) the nvidia driver.

Cheers,
Mehdi

On 10/24/06, Michael Vogt <email address hidden> wrote:
>
> Thanks a lot for your tests!
>
> I would like to know more about the xorg failures. If the upgrade worked
> and the system didn't, could you please attach the logs from the upgrade
> from /var/log/dist-upgrade/ ? And a short description what fails (e.g.
> nvidia driver not installed)? Or is this always related to installing
> the latest nvidia drivers by hand? If so, maybe we can find a way to
> fix/workaround this during the upgrade.
>
> Cheers,
> Michael
>
> ** Changed in: update-manager (Ubuntu)
> Status: Fix Committed => Fix Released
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Mehdi Dogguy
http://dogguy.info/
GNU/Linux user #371248

what nvidia driver are you using? how did you install it? Is this the nvidia-glx-beta from a 3rd party repo, or nvidia-glx from ubuntu.com repo, or did you install the beta drivers by hand?

in my dapper (before upgrading), i had nvidia driver from ubuntu.com (i
don't remember the driver's version)...
it's not a big problem, i think trying to update nvidia driver or install it
when u see nvidia used in section device in xorg.conf is the simpliest
solution.

@Mehdi: If the upgrade didn't upgrade your nvidia package that is something I really would like to investigate. Could you please tell attach your logs from /var/log/dist-upgrade/ (if you haven't done so already)?

Thanks,
 Michael

My xorg is also broken after upgrading. I have an ATI mobility chip in my
laptop. I cannot remember whether or not I had installed a third party
driver though. my xorg.conf is looking for a driver called "ati" and not
finding it.

On 10/24/06, Mehdi <email address hidden> wrote:
>
> in my dapper (before upgrading), i had nvidia driver from ubuntu.com (i
> don't remember the driver's version)...
> it's not a big problem, i think trying to update nvidia driver or install
> it
> when u see nvidia used in section device in xorg.conf is the simpliest
> solution.
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Tyler Hardeman

@wunderbar: Can you please attach your logs?

I did on a second e-mail. I had forgotten to on the first one.

On 10/24/06, Michael Vogt <email address hidden> wrote:
>
> @wunderbar: Can you please attach your logs?
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Tyler Hardeman

OK, I'll just add my grain of salt to the xorg bug.

After upgrading, my nvidia drivers wouldn't load (normal, since I'd installed the beta 9xxx drivers from nzone), so I edited my xorg.conf to use the nv driver.

On restarting xorg, it didn't (restart). I unfortunately don't have the logs (I re-installed from edgy beta and upgraded to current) but they mentioned version incompatibilities between the xorg binary and the modules, which meant that said modules refused to load.

In the two systems I have this has happened to me when upgrading: the former
video drivers are kept (under packages named xorg-xserver-driver-xxxx). If
you manually select the package xorg-xserver-video-all (note the change from
driver to video), all old versions are deinstalled, new ones installed, and
X resume working flawlessly.

any instructions on how to actually do this? I'd like to try, but have
little experence manually tweaking xorg. One of the few areas of linux I
don't touch much.

On 10/24/06, mosteo <email address hidden> wrote:
>
> In the two systems I have this has happened to me when upgrading: the
> former
> video drivers are kept (under packages named xorg-xserver-driver-xxxx). If
> you manually select the package xorg-xserver-video-all (note the change
> from
> driver to video), all old versions are deinstalled, new ones installed,
> and
> X resume working flawlessly.
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Tyler Hardeman

I wonder if the problems with the nvidia driver could be due to bug #67775 ?

Actually I didn't have unofficial packages so I'm not sure if this is the same bug (I reported it under other number but I think it got marked as dupe). In any case, the only thing I did to get X working again was:

sudo apt-get install xserver-xorg-video-all

No editing of xorg.conf or anything.

@mosteo: if the upgrade happend with the update-manager, could you please attach the logs in /var/log/dist-upgrade? So that I can diagnose the problem ?

@Vogt: Sorry, I updated via sources.list editing and apt-get

I failed to say that I had enabled the universe and multiverse repositories;
I'm not sure if it matters.

Mosteo, that fix worked for me as well. Required a reboot, but i'm now
typing this on the gnome desktop of my new Ubuntu 6.10RC

On 10/24/06, Michael Vogt <email address hidden> wrote:
>
> @mosteo: if the upgrade happend with the update-manager, could you
> please attach the logs in /var/log/dist-upgrade? So that I can diagnose
> the problem ?
>
> --
> Can't calculate the upgrade with unofficial mesa/compiz packages
> https://launchpad.net/bugs/58424
>

--
Tyler Hardeman

@wunderbar: glad to hear. To avoid the restart one can do:

$ sudo /etc/init.d/gdm restart

(or kdm instead if you're a kubunter).

All works fine now with the update !
Cool !

I can reproduce that under some circumstance the nvidia driver will not be upgraded. I will update the upgrader ASAP to fix this.

Thank you for fixing this Michael. Marking this as fix Released. If this is still a problem for anyone please feel free to reopen the bug with more info Thank You.

Thank you for all the helps.

There is a very similar problem using Debootstarp and Edgy release:

debootstrap --arch i386 edgy /mnt/buildroot
## ... everything goes fine
chroot /mnt/buildroot /bin/su
## ... everything goes fine. Now here is the problem:

root@navid-laptop:/# apt-get install ubuntu-desktop
...
You might want to run `apt-get -f install' to correct these:
The following packages have unmet dependencies:
  libgl1-mesa-dri: Depends: libgl1-mesa (= 6.5.1+cvs20060824)

What I did:

apt-get install xorg
   xorg: Depends: libgl1-mesa-dri but it is not going to be installed

apt-get install libgl1-mesa-dri
The following extra packages will be installed:
  libgl1-mesa
The following packages will be REMOVED:
  libgl1-mesa-glx
The following NEW packages will be installed:
  libgl1-mesa libgl1-mesa-dri

apt-get install xorg
 xorg: Depends: libgl1-mesa-glx but it is not going to be installed

And as you may see, I can not install "libgl1-mesa-glx" and "libgl1-mesa-dri" together. One will remove the other and Xorg depends on both. And Ubuntu-Desktop depends on Xorg!

Could you please have a look?

Thank you,
Navid

I had similar problems, but with a bad /etc/rc2.d/S91Samba link to a nonexistent /samba directory. The error message implied something was wrong with one of the samba*.deb files. However, removing the symlink resolved this problem.

Then I ran into problems with firestarter (while running the recommended "sudo apt-get install -f" command. I had installed firestarter previously, but it failed to start during the install/upgrade. I tried running it separately from the command line and I got an error that it had never been configured before (?). I "solved" this problem using "dpkg" to remove firestarter.

At this point, the update manager completed successfully and I rebooted successfully. However, samba and firestarter will have to be re-installed, it appears (I upgraded about an hour ago).

I am having similar problems, Open Office seems to be messing up the upgrade process. I tried following your directions, but they don't seem to be correcting my problem.
I am going to attach my apt.log for your guys to take a look at. Any help would be greatly appreciated!

Thanks.

These are the "broken" packages on my system. Might be part of the problem?

I alo get the same error. I had some packages that were not required anymore and removed those with apt-get autoremove. But it did not work.

I have attached the log-files suggested and also my original sources.list (which is changed automatically to remove third party repositories during upgrade).