From ae41fceba9ae06b60071e9e4a2be7fed2103479a Mon Sep 17 00:00:00 2001
From: Giovanni Campagna <gcampagna@src.gnome.org>
Date: Thu, 24 Nov 2011 16:59:11 +0100
Subject: [PATCH] alternative-status-menu: fix criticals when opening the menu

After enabling, the user menu was keeping a reference to a
destroyed actor, and then was updating it from signals. Updating
this (a StEntry) caused g_criticals because of a NULL ClutterText.
Instead we can null out the actor entirely, which will stop
the signal handler from doing any harm.
---
 extensions/alternative-status-menu/extension.js | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/extensions/alternative-status-menu/extension.js b/extensions/alternative-status-menu/extension.js
index 68523c23..c0b36469 100644
--- a/extensions/alternative-status-menu/extension.js
+++ b/extensions/alternative-status-menu/extension.js
@@ -95,6 +95,9 @@ function createSubMenu() {
 	this._session.ShutdownRemote();
     }));
     this.menu.addMenuItem(item);
+
+    // clear out this to avoid criticals
+    this._suspendOrPowerOffItem = null;
 }
 
 // Put your extension initialization code here