what strange, is that we get a first google-chrome window: res_name : google-chrome(2588230); res_class : Google-chrome(2589030)
then a second: res_name : crx_nckgahadagoaajjgafhacjanaoiihapd(25884e0); res_class : Google-chrome(25892c0) The second has a convoluted name, which is usually for webapps. If it was a normal google-chrome window, it should have the same name/class as the first one. How did you open the 2nd window ? maybe google-chrome automatically considers a 2nd window as being a webapps ... 2013/11/25 Matthieu Baerts <[email protected]> > Hello, > > > You say that Chrome WebApps are considered separate apps from the > browser - I understand that - however, all I am trying to open is the > browser > > Oh, this is strange! > Are you using Chromium or Google Chrome? > > Can you open your browser, launch this command from a terminal, select > your browser's window and give us the output messages produced in your > terminal? > > $ xprop | grep CLASS > > And can you also give us output messages of this command? > > $ cairo-dock -l debug | grep "chromium application detected" > > -- > You received this bug notification because you are a member of Cairo- > Dock Devs, which is subscribed to Cairo-Dock Core. > https://bugs.launchpad.net/bugs/1254771 > > Title: > Launching Chrome results in new icon instance on main dock > > Status in Cairo-Dock : Core: > Invalid > > Bug description: > Ubuntu 12.04 64-bit (Unity) > Cairo-dock 3.3.2 > Chrome 31.0.1650.57 > > Within the past week, launching Chrome from my Cairo-dock main dock > now creates a new instance of the Chrome icon, in the area of the dock > normally reserved for applications that don't have a launcher. (On my > dock, that's towards the left side, just to the right of the separator > for the 'help' icon.). Clicking on the launcher again, consequently, > results in another instance of Chrome being launched. > > Prior to this, launching Chrome from CD would result in a white dot > under the launcher - the same as for any other application launched > from CD. My other launchers do not exhibit this behavior - e.g., > Firefox, LibreOffice, etc. all respond with a white dot (showing it's > running), and I can click on it to activate. > > Not sure of any changes to system, but it's possible that Chrome was > updated. > > I tried dropping and re-adding the Chrome launcher, but it did not > resolve the issue. > > Thanks in advance - attached is the text from the following command: > cairo-dock -l debug >debug.txt > > Note I had to ctrl-Z to get it to stop in command line (maybe b/c CD > was already running?) - not sure - so take the below with a grain of > salt. > > To manage notifications about this bug go to: > https://bugs.launchpad.net/cairo-dock-core/+bug/1254771/+subscriptions > > _______________________________________________ > Mailing list: https://launchpad.net/~cairo-dock-team > Post to : [email protected] > Unsubscribe : https://launchpad.net/~cairo-dock-team > More help : https://help.launchpad.net/ListHelp > -- You received this bug notification because you are a member of Cairo- Dock Devs, which is subscribed to Cairo-Dock Core. https://bugs.launchpad.net/bugs/1254771 Title: Launching Chrome results in new icon instance on main dock Status in Cairo-Dock : Core: Invalid Bug description: Ubuntu 12.04 64-bit (Unity) Cairo-dock 3.3.2 Chrome 31.0.1650.57 Within the past week, launching Chrome from my Cairo-dock main dock now creates a new instance of the Chrome icon, in the area of the dock normally reserved for applications that don't have a launcher. (On my dock, that's towards the left side, just to the right of the separator for the 'help' icon.). Clicking on the launcher again, consequently, results in another instance of Chrome being launched. Prior to this, launching Chrome from CD would result in a white dot under the launcher - the same as for any other application launched from CD. My other launchers do not exhibit this behavior - e.g., Firefox, LibreOffice, etc. all respond with a white dot (showing it's running), and I can click on it to activate. Not sure of any changes to system, but it's possible that Chrome was updated. I tried dropping and re-adding the Chrome launcher, but it did not resolve the issue. Thanks in advance - attached is the text from the following command: cairo-dock -l debug >debug.txt Note I had to ctrl-Z to get it to stop in command line (maybe b/c CD was already running?) - not sure - so take the below with a grain of salt. To manage notifications about this bug go to: https://bugs.launchpad.net/cairo-dock-core/+bug/1254771/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~cairo-dock-team Post to : [email protected] Unsubscribe : https://launchpad.net/~cairo-dock-team More help : https://help.launchpad.net/ListHelp
