Upgrade from Lucid to Precise does not install packages for Global Menu: indicator-appmenu

Thanks for taking the time to report this bug and helping to make Ubuntu better. Could you please add the log files from '/var/log/dist-upgrade/' to this bug report as separate attachments? Thanks in advance.

I was able to reproduce it during an upgrade from Ubuntu Desktop lucid amd64 to precise.

Excerpt from apt.log
Investigating (0) indicator-appmenu [ amd64 ] < none -> 0.3.97-0ubuntu1 > ( gnome )
Broken indicator-appmenu:amd64 Conflicts on libdbusmenu-glib1 [ amd64 ] < 0.2.9-0ubuntu3.1 > ( libs ) (< 0.3.7)
  Considering libdbusmenu-glib1:amd64 9 as a solution to indicator-appmenu:amd64 3
  Holding Back indicator-appmenu:amd64 rather than change libdbusmenu-glib1:amd64

Closing task for Quantal since it occurs during an upgrade to Precise.

... was just about to upload the required files from my machine. You got it already. Let me know if you need any further information.

libdbusmenu-glib1 is being brought in by libbrasero-media0, which has previously been identified as a problem for upgrades (bug #1029531). A Breaks: from indicator-appmenu to libbrasero-media0 may help with this. However, the upgrade log shows -proposed was not enabled for this test, and liblaunchpad-integration-3.0-1 *was* processed by apt before hitting the libbrasero-media0 problem. It's possible the fixes from 1029531 are sufficient to address this. Please re-test with -proposed enabled.

resolver logs with proposed enabled.

Ok. We should try to fix with this by adding the described Breaks: on libbrasero-media0.

Hello Andre, or anyone else affected,

Accepted indicator-appmenu into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/indicator-appmenu/0.3.97-0ubuntu1.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

indicator-appmenu 0.3.97-0ubuntu1.1 doesn't fix the issue and is still not installed after upgrade from Lucid.

Investigating (0) indicator-appmenu [ amd64 ] < none -> 0.3.97-0ubuntu1.1 > ( gnome )
Broken indicator-appmenu:amd64 Conflicts on libdbusmenu-glib1 [ amd64 ] < 0.2.9-0ubuntu3.1 > ( libs ) (< 0.3.7)
  Considering libdbusmenu-glib1:amd64 9 as a solution to indicator-appmenu:amd64 3
  Holding Back indicator-appmenu:amd64 rather than change libdbusmenu-glib1:amd64

full apt.log attached.

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1034668

I upgraded today a 32-bit Ubuntu 10.04 and had this same issue.
Installing manually indicator-appmenu solved it.

I think the commited patch does not solve this bug. So I confirm the "verification-failed" tag.

I could reproduce this issue in a Virtualbox machine, with or without -proposed enabled.

I ran a first test without -proposed enabled.
You will find the dist-upgrade/apt.log attached.
It reproduced the issue, related to a conflict with libdbusmenu-glib1.

I ran a second test with -proposed enabled on 10.04, and also had the same issue after the dist-upgrade.
You will find the apt.log attached, too

Each time, before the dist-upgrade, I had installed all the upgrades of 10.04.
As I made a snapshot before the upgrade, I will be able to run any needed tests

There is another occurring of this bug in the duplicate. We should make another attempt at fixing this.

  Installing libdbusmenu-glib1 as Depends of indicator-me
[...]
Broken indicator-appmenu:amd64 Conflicts on libdbusmenu-glib1 [ amd64 ] < 0.2.9-0ubuntu3.1 > ( libs ) (< 0.3.7)
  Considering libdbusmenu-glib1:amd64 9 as a solution to indicator-appmenu:amd64 3
  Holding Back indicator-appmenu:amd64 rather than change libdbusmenu-glib1:amd64

So this is triggered by the obsolete indicator-me package. indicator-messages already conflicts with indicator-me, but the conflict is applied too late in the upgrade.

Aside from libraries, this is the only reverse dependency of libdbusmenu-glib1 in lucid that does not have a version available for upgrade in precise; so chances are that adding a conflict against indicator-me will be sufficient to get this upgrade to go through correctly. If it *doesn't*, then we should deal with this via an update-manager PostDistUpgradeCache quirk instead to force upgrade of indicator-appmenu instead of continuing to hack around it with conflicts.

New version of indicator-appmenu uploaded with the added breaks on indicator-me. Resetting bug state pending SRU acceptance.

Hello Andre, or anyone else affected,

Accepted indicator-appmenu into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/indicator-appmenu/0.3.97-0ubuntu1.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please change the bug tag from verification-needed to verification-done. If it does not, change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

I tested the upgrade again in Virtualbox. It did not solve the issue for me.

I have first activated -proposed in 10.04, then installed all available upgrades, and then launched the dist-upgrade
After the dist-upgrade, the package indicator-appmenu is not installed and global menu is not activated.

I attach the dist-upgrade/apt.log, where there are the following lines :

Investigating (0) indicator-appmenu [ i386 ] < none -> 0.3.97-0ubuntu1.2 > ( gnome )
Broken indicator-appmenu:i386 Conflicts on libdbusmenu-glib1 [ i386 ] < 0.2.9-0ubuntu3.1 > ( libs ) (< 0.3.7)
  Considering libdbusmenu-glib1:i386 9 as a solution to indicator-appmenu:i386 3
  Holding Back indicator-appmenu:i386 rather than change libdbusmenu-glib1:i386

> Installing libdbusmenu-glib1 as Depends of libappindicator0

Well, as I said if this was still causing problems we should add an update-manager quirk instead of continuing to pile up the Breaks. Reassigning.

I removed indicator-appmenu from precise-proposed, I has been sitting there for four years.