Comment 6 for bug 551872

Well, to clarify, here's what I usually do. I'll launch an application, click on AllTray in my Gnome menu (which opens that little dialog that asks you to click on a window, and the cursor turns into a cross), and then click on the application window. Usually (like when I try that with Firefox), I have no problem docking just about any window. These steps do not work for Chrome, though. You're probably right; it probably has something to do with how Chrome treats processes. I also read something recently about how Chrome does sandboxing...could that be related?

Similar to the debugging command, I also tried starting Chrome with AllTray at the same time from the terminal with:

  $ alltray -s google-chrome

This worked successfully and without error. Does that answer your question? Any thoughts?