Gdk-WARNING**XID collision;trouble ahead

What makes it happen?

On Mon, Jun 6, 2011 at 6:16 PM, actionparsnip
<email address hidden> wrote:
> Your question #160430 on gnome-terminal in Ubuntu changed:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/160430
>
>    Status: Open => Needs information
>
> actionparsnip requested more information:
> What makes it happen?
>
> --
Halo!
 My whole laptop and installation have something wrong with.
Always my terminal behaved in unusual manner. I am not an expert with
administration , this time I had some doubt about Firefox settings. So I
changed its master password and some other security settings and closed
it. Then opened firefox using terminal command .After sometime When I
closed Firefox, I saw my terminal report the above message in
repetition.(Gdk-WARNING**XID collision;trouble ahead ). I cannot
understand what the message mean. Next I un-installed terminal using
Ubuntu software centre.To my surprise update manager which was not
working since this installation, the icon came back on the upper
panel ,listing that updates are now available.Because I was not
receiving updates, I had uninstalled Update manager earlier.From where
does that icon appeared remains no answer.after update this icon never
reappeared.My panel always misrepresent network icon.Because of this I
have disabled wireless and bluetooth.
shaju
7-6-2011

> To answer this request for more information, you can either reply to
> this email or enter your reply at the following page:
> https://answers.launchpad.net/ubuntu/+source/gnome-terminal/+question/160430
>
> You received this question notification because you asked the question.
>

http://ubuntuforums.org/showthread.php?p=7506398 talks about the Gdk-WARNING**XID collision; trouble ahead message. One user posted that an upgrade to Firefox 3.6.4 cleared this problem.

Recommendation #1: Install update manager again. You will eventually want to upgrade something. Like Firefox.

Recommendation #2: Install terminal again -- the error messages you are getting were Firefox bugs.