Hi Sense,

Thanks for having taken the time to open this bug here, as I don't follow launchpad bugzilla.

I'm afraid I'm not able to reproduce this bug out of the box on my fedora12 box, on 2.29.1 version (which I suppose if the buggy one, as seen in launchpad).

I'll have to install an Ubuntu 10 on a vbox to trigger this bug.

Stay tuned.

Regards
Pierre

Grr.. Could you please give me a link to an iso for the Ubuntu 10.04 you're using ? I only found versions 8 and 9 :(

Thanks in advance
Pierre

ok - found as 'Lucid'.

If you haven't found it yet: the ISOs can be found at <http://cdimage.ubuntu.com/releases/lucid/alpha-2/>, the source used by Ubuntu to compile the packages is located at <http://archive.ubuntu.com/ubuntu/pool/universe/n/nautilus-actions/>.

I've tracked down the bug to GtkBuilder which no more fills in the 'name' field of the GtkWidget.

- In gdb, with Gtk 2.18 (Fedora 12)

(gdb) print *child
$3 = { object =
		{ parent_instance =
			{ g_type_instance = { g_class = 0x8105a00 },
			  ref_count = 2,
			  qdata = 0x0
			},
		  flags = 2098976
		},
	  private_flags = 13824,
	  state = 0 '\000',
	  saved_state = 0 '\000',
	  name = 0x8105260 "vbox1",
	  style = 0x8106108,
	  requisition = { width = 0, height = 0 },
	  allocation = { x = -1, y = -1, width = 1, height = 1 },
	  window = 0x0,
	  parent = 0x8104820
	 }

- In Ubuntu 10.04 Alpha 2 with Gtk+ 2.19.3

$7 = { object =
		{ parent_instance =
			{ g_type_instance = { g_class = 0x810d060 },
			  ref_count = 2,
			  qdata = 0x8106440
			},
		  flags = 2101024
		},
	  private_flags = 13824,
	  state = 0 '\000',
	  saved_state = 0 '\000',
	  name = 0x0,
	  style = 0x810a0f0,
	  requisition = { width = 0, height = 0 },
	  allocation = { x = -1, y = -1, width = 1, height = 1 },
	  window = 0x0,
	  parent = 0x8109108
	 }

I'll fix this asap in git.

Do you prefer a 2.29.4 (only fixing the current unstable in master) or a 2.29.1.1 (providing a fixed 2.29.1) ?

Just do it the way you'd like, Ubuntu 10.04 will ship with GNOME 2.30 anyway, so we'll get the fix sooner or later.

So it is fixed in latest unstable 2.29.4 release.

Thanks a lot for your time.