Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: alltray (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/551872
Title:
I think this is fixed. It works for me.
$ dpkg -l |grep alltray
ii alltray 0.71b-1 amd64
$ dpkg -l |grep chrome
ii google-chrome-stable33.0.1750.152-1 amd64
$ lsb_release -dc; uname -srm
Description:Linux Mint 16 Petra
Codename: petra
Linux
Hi,
Thanks for reporting this bug.
Can you run AllTray with debugging enabled and post the output when
trying to run Chrome with it? That would help to see what is going on,
since I have neither Chrome 5 beta nor Karmic installed at this point.
Thanks!
** Changed in: alltray
Status:
How do I run AllTray with debugging enabled? Pardon my ignorance.
--
Google Chrome can't be docked
https://bugs.launchpad.net/bugs/551872
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For AllTray 0.69, just add -d to the command line options. So, for
example, to run Chrome:
$ alltray -d google-chrome
There are also more options and information in AllTray's man page, which
you can see by typing:
$ man alltray
In a terminal window.
--
Google Chrome can't be docked
Ah, thank you. Just one quick note: when running the command you
suggested, AllTray correctly docks a Chrome window. However, when
running a Chrome window normally and trying to use the AllTray GUI to
dock it, it doesn't work; I just keep clicking the Chrome window and
nothing happens. Okay,
On 03/30/2010 03:08 PM, Josh wrote:
Ah, thank you. Just one quick note: when running the command you
suggested, AllTray correctly docks a Chrome window. However, when
running a Chrome window normally and trying to use the AllTray GUI to
dock it, it doesn't work; I just keep clicking the
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),
It solidifies my thought that the problem might be related to the
multiprocess model that Chrome uses, yes. I'll try to get something
setup to test this notion later, and also test against the development
release and see if it is a problem there. At this point, I don't yet
have enough
