Olin hieman pettynyt, kun leimautumiskohde paljastuikin kumikontioiksi oikeiden otsojen sijasta.

Next, try catching a couple of live ones checkmating on there.

  ”vähintään miljoona vuotta, parhaimmassa tapauksessa kymmenen”

Vähintään miljoona vuotta, mutta parhaimmassa tapauksessa kymmenen vuotta! Siinäpä vasta saavutus.

This looks a bit like RH 426383 [1], but isn’t as grave as that one (all windows apart from the one) are shown here.

*[1] https://bugzilla.redhat.com/show_bug.cgi?id=426383

I have two Chromium windows open, 0x31fd46b and 0x3072dc8 (this one):

jani@saegusa:~$ xwininfo -root -tree | grep Chromium-browser
0x31d2a67 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 321×216+275+321 +275+321
0x30fb2de ”Chromium”: (”chromium-browser” ”Chromium-browser”) 246×307+1232+305 +1232+305
0x3157fd9 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 246×307+36+124 +36+124
0x31fd391 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 1×1+-100+-100 +-100+-100
0x31b19f6 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 513×132+1011+38 +1011+38
0x30b5ffa ”Chromium”: (”chromium-browser” ”Chromium-browser”) 397×125+4+82 +4+82
0x3092643 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 321×216+791+829 +791+829
0x3030c84 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 306×230+587+441 +587+441
0x3030681 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 462×342+127+133 +127+133
0x3000027 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 200×200+0+0 +0+0
0x3000024 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 200×200+0+0 +0+0
0x3000001 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 10×10+10+10 +10+10
0x31fd46b ”Yleisurheilun Eliittikisat | Tv | Areena | yle.fi – Chromium”: (”chromium-browser” ”Chromium-browser”) 1014×438+2322+227 +2322+227
0x3072dc8 ”Chromium”: (”chromium-browser” ”Chromium-browser”) 1659×50+94+83 +94+83
0x30000c3 ”Report a bug about “wmctrl” package in Ubuntu : Bugs : “wmctrl” package : Ubuntu – Chromium”: (”chromium-browser” ”Chromium-browser”) 1920×1056+0+0 +0+24

But wmctrl only knows about the one:
jani@saegusa:~$ wmctrl -l
0x01c00006 0 saegusa jani@saegusa: ~
0x02200003 0 N/A DNDCollectionWindow
0x02200004 0 N/A launcher
0x02200006 0 N/A panel
0x02200007 0 N/A Dash
0x02200008 0 N/A Hud
0x030000c3 0 saegusa Report a bug about “wmctrl” package in Ubuntu : Bugs : “wmctrl” package : Ubuntu – Chromium
0x03e00003 0 saegusa Rytmilaatikko
0x04200009 0 saegusa Kuvakaappaus
0x04600081 0 saegusa Synaptic-pakettienhallinta

This may be related to the fact that the other window has fallen out of view: it’s not visible on any workspace, but it’s still there as the audio’s still playing. It got out of sight due to another bug (probably in Compiz) which I have yet to report.

eBay just sucks or it simply hates me

That’s an easy one: eBay sucks. Not as much as Facebook but about as much as Amazon. It’s astounding how the web’s biggest money-making sites are built with the most modern technologies to look and feel like they were built with technology from the 1990s.

Please prove you’re not a robot (bottom of this form)

But… but if I am? My robot senses are having a hard time identifying that first word!

FWIW, based on the above comments and my experience I’d lay at least some of the blame on this on nouveau: I have two setups affected by the Plymouth no-show, both with Nvidia graphics:

01:00.0 VGA compatible controller: NVIDIA Corporation G73 [GeForce 7300 GT] (rev a2) (prog-if 00 [VGA controller])
and
00:0d.0 VGA compatible controller: NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] (rev a2) (prog-if 00 [VGA controller])

At the same time all the other systems I have access to that run Precise on non-Nvidia graphics (some half dozen computers, old and new) don’t manifest it, i.e. they display Plymouth’s boot logo screen just fine on every boot without any workarounds. (The Nvidias need either FRAMEBUFFER=y or plymouth:force-drm.)

Also, on the G73, Grub menu shows at a low resolution without GRUB_GFXMODE specified, but on the C61 it’s ”Out of range”. It shows on both if I specify 1280×1024 (the maximum supported by the connected LCDs) as GRUB_GFXMODE. This too is Nvidia-specific, though I suppose the Grub menu is outside nouveau’s jurisdiction.

Brilliant, this seems to work exactly as I wanted! And it seems to work for non-greyscale originals as well. Thank you!

I have an image I wish to colorize using a picked color. What is the handiest/easiest way to do this in GIMP?

I’ve tried my best by checking the palette for my picked color’s HSV, then using it as starting point to find corresponding HSL values for the Colorize window. But this seems absurdly difficult and imprecise. I don’t do much image processing, but I repeatedly come across this specific problem, so there must be a better way that I just don’t know about.

Hi Gary. I now tested this in a VM running up-to-date Precise and am happy to report the problem no longer occurs. I’m thus marking this as being fixed.