[ Didier Roche ]
* add dep on autopilot-desktop.
* Revert the panel on upstart from ted, it doesn't respawn as expected
when another service try to communicate with the panel service and
the consequence is a lot of tests failing

[ Nick Dedekind ]
* Uses a gobject weak ref to test for object deletion in the
GLibObject tests. Previously was checking with G_IS_OBJECT on an
invalid pointer, which was causing a segfault

[ Manuel de la Pena ]
* Adds support for payment previews that will allow users to buy music
from within the dash. .

[ Łukasz 'sil2100' Zemczak ]
* Now that we're using the new HUD, there have been some changes that
typically cause test_hud tests to fail. Fix the tests to fit the new
model. The first one is that generally we do not have indicator
entries visible in the HUD anymore. Only application menu entries
are in it now. The second one - the way the results are displayed is
different. Now, instead of "Menu > Entry" we have "Entry (Menu)"
etc.
* Fix two HUD failures related to HUD slow action activation.
* Fix some autopilot test failures, some related to test_shortcut_hint
and some to test_scroll in launcher.
* Modify all the hud_query_check lambdas to be more smart and error-
checking. Same for the selected_hud_button method in the HUD
emulator. Also, get rid of the troublesome test_gedit_undo and
change it into test_gedit_save, which is easier to test and anyway
tests what we want. Besides that we also now try to handle the
StateNotFoundError exception in the HUD emulator, another cause of
some AP failures.
* Add a flag for -Wno-error=unused-local-typedefs, since this causes a
FTBFS on ARM

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

@Dmitry Shachnev. thank you for your reply.
I don't know if i misunderstand something, but i was trying to install it by enabling proposed, updating and selecting it either in synaptic or update manager, but i can't find it.
Is the only way to download and install?

I'm still waiting to see the progress bar for unread mail reappear on my Thunderbird icon. I'm not competent to extract and install patches, I'm just waiting for the fix to appear in the standard updates. When can we expect that?

PS: I appreciate that you have added this to proposed updates for raring, but when I enable proposed updates, I see a great many items, including kernel updates, most of which I presumably do not want, and no way to identify the desired item or items.

Rowan, the update will be hopefully in main repository soon, but if you only want to update unity, just tick it on the update manager (unselecting the other ones with right-click menu).
Otherwise doing a "sudo apt-get update unity" in a terminal, would also work.

It isn't quite that simple, Marco. "Sudo apt-get update unity" returns "update accepts no arguments." As for the update manager, there are at least seven items in the "Ubuntu base" proposed list which could be relevant, and here is my list of them, but of course I cannot guarantee that there aren't others that are relevant: "Application lens for unity", "Common files for the Unity interface", "Core library for the Unity interface", "Display Manager", "Panel indicator applet - shared library" (twice, one 25kB and the other 29 kB), and "Services for the Unity interface". There is no separate category for "Unity" such that one can select that, or deselect other categories by right-click. Every item just has a tick box which one can untick. So unless I want unexpected proposed modifications installed, some of which might not work, I am better off not trying it. I need a definite name for the specific fix we are talking about, and then I can just untick everything else, tedious though that is (there are over 80 items in the proposed list currently). I think I might be wiser to wait.

If today's update is supposed to include this fix, I have to tell you, it isn't working. I have installed the update package and restarted, and I am still not getting a progress bar on my thunderbird icon when I receive new mail. What I have is all-vanilla up-to-date raring.

Rowan, what version of Unity do you have? Use "apt-cache policy unity" to see what version you have. If the installed and candidate versions say 7.0.0daily13.04.18~13.04-0ubuntu1, then you need to enable the -proposed pocket.

On 02/08/13 17:29, Saikrishna Arcot wrote:
> Rowan, what version of Unity do you have? Use "apt-cache policy unity"
> to see what version you have. If the installed and candidate versions
> say 7.0.0daily13.04.18~13.04-0ubuntu1, then you need to enable the
> -proposed pocket.
>
Yup, they say that. But as I said previously in this thread, 'proposed'
contained 80 items last time I looked, some of them doubtless
inadvisable, and none of them clearly labelled in any way which would
allow me to identify the desired one. If you could look at the
'proposed' list as seen in the ordinary user's GUI, not as seen by
developers, and tell me what I want, then I shall leave that (or those)
ticked, and untick the other ~79 items (the only way to do it. Thanks.

And why in fact am I not getting it, anyway? Why doesn't this fix work
for all versions of Unity? Why don't I have the desired version of
Unity? Why isn't that part of the general updates?

Yup, they say that. But as I said previously in this thread, 'proposed' contained 80 items last time I looked, some of them doubtless inadvisable, and none of them clearly labelled in any way which would allow me to identify the desired one. This is the first time I have tried to follow through a bug fix. Looking at the 'status' for this fix, I see:

Since the final line says "committed" but not "released", does that mean I could wait until the fix is "released" for "Raring", which would include Unity 7.0? I failed to spot that crucial qualification in the Status until just now, when you asked me which version of Unity I had, so I am only guessing.

> Since the final line says "committed" but not "released", does that mean I could wait until the fix is "released" for
> "Raring", which would include Unity 7.0?

Yes.

The -proposed pocket is there for testing release candidates to make sure (a) they fix the problem and (2) they do not introduce new problems. Once a few valiant testers verify those conditions hold, the package(s) is (are) moved into the general release archives and the bug marked 'Fix Released'.

So, assuming someone else is testing and verifying the package, you could just wait. The downside to that is nobody else may be interested in verifying the bug is fixed by the release candidate.

On 02/08/13 18:59, Saikrishna Arcot wrote:
> One method might be to run "sudo apt-get install
> unity=7.0.0daily13.06.19*" (without the quotes at the ends). This should
> update unity and necessary dependencies.
>
unity=7.0.0daily13.06.19* not found

On 02/08/13 19:09, Stephen M. Webb wrote:
>> Since the final line says "committed" but not "released", does that mean I could wait until the fix is "released" for
>> "Raring", which would include Unity 7.0?
> Yes.
>
> The -proposed pocket is there for testing release candidates to make
> sure (a) they fix the problem and (2) they do not introduce new
> problems. Once a few valiant testers verify those conditions hold, the
> package(s) is (are) moved into the general release archives and the bug
> marked 'Fix Released'.
>
> So, assuming someone else is testing and verifying the package, you
> could just wait. The downside to that is nobody else may be interested
> in verifying the bug is fixed by the release candidate.
>
Well, if I can get the right Unity update, which for whatever reason is
not as Saikrishna specified it, I can test.

The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.

S Kitterman #31 says " In the event that you encounter a regression using the package from -updates please report a new bug." Since the fix has not solved the problem I have done just that, and after 10 days no one has acknowledged or responded to my new bug report in any way.https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1208719