As the original reporter, I’m confirming that 5.20.0-0ubuntu2 from -proposed does contain the fix for this bug, i.e. the issue I reported above is no longer reproducible. I’m only hesitant about tagging this ’verification-done’ because PerformingSRUVerification is pretty adamant about having a solid test case and I’m not sure my sloppy initial report qualifies.

jani@saegusa:~$ LC_ALL=C apt-cache policy unity
unity:
Installed: 5.20.0-0ubuntu2
Candidate: 5.20.0-0ubuntu2
Version table:
*** 5.20.0-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64 Packages
100 /var/lib/dpkg/status
5.18.0-0ubuntu2 0
500 http://archive.ubuntu.com/ubuntu/ precise-updates/main amd64 Packages
5.10.0-0ubuntu6 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages

Songtapperia olen joskus kokeillut kappaleiden tunnistukseen, muttei se kovin hyvä ollut. Shazam taas tarvii pätkän autenttista materiaalia, mutta näköjään nykyisin on sellaisiakin joihin voi hyräillä tai soittaa virtuaalikoskettimin.

I already knew the Beeb’s predator dinosaurs have serious eyesight problems, but this one takes the cake. Getting surprised by the largest dinosaur ever, over a landscape of virtually nothing blocking the view! Come on!

This looks slightly more straightforward than thebodzio’s method, so I’m picking this as answering my original query for ”easiest”. For some reason both Colorify and Colorize have been translated as ”Väritä” in my (Finnish) locale, so it would’ve been difficult to realize it’s actually two different functions. They’re not particularly easy to tell apart in English either…

If the diamond you keep on your bathroom table is that huge, you must have basketball-sized ones in your living room.

Christopher, your test packages do indeed fix this, excellent! As I mentioned in the report, this was 100% reproducible with the packages from -proposed, and now with the packages from your PPA I could no longer reproduce it at all, during the multiple test logins I did.

Definitely not a showstopper for me Christopher, just a minor annoyance, so it’s a go-ahead from me. Thanks for asking!

Yep, that’s exactly the issue as it occurs here too. Thanks for looking into this Christopher! If you do get this narrowed down and need testing for potentially fixed builds, I’ll be happy to try them out.

Hi Christopher, sure. For the test user, I just go to the top right cog menu, select ”Startup Applications…” and ”Add” Firefox (/usr/bin/firefox). Firefox remembers the window size, so I start it once (manually), maximize the window and then close it. On the next login, it should start maximized.

Verifying that for both test cases the issue is no longer reproducible with the proposed packages. In other words, results with packages from -proposed are as described in ”Expected:” for each test case. (For both cases the issue was reproducible here with 1:0.9.7.0~bzr19-0ubuntu10.)

jani@saegusa:~$ LC_ALL=C apt-cache policy compiz-plugins-main compiz-plugins-main-default
compiz-plugins-main:
Installed: 1:0.9.7.0~bzr19-0ubuntu10.1
Candidate: 1:0.9.7.0~bzr19-0ubuntu10.1
Version table:
*** 1:0.9.7.0~bzr19-0ubuntu10.1 0
500 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1:0.9.7.0~bzr19-0ubuntu10 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
compiz-plugins-main-default:
Installed: 1:0.9.7.0~bzr19-0ubuntu10.1
Candidate: 1:0.9.7.0~bzr19-0ubuntu10.1
Version table:
*** 1:0.9.7.0~bzr19-0ubuntu10.1 0
500 http://archive.ubuntu.com/ubuntu/ precise-proposed/main amd64 Packages
100 /var/lib/dpkg/status
1:0.9.7.0~bzr19-0ubuntu10 0
500 http://archive.ubuntu.com/ubuntu/ precise/main amd64 Packages