This is not an Unity/BAMF bug.
New chromium doesn't seem to support anymore the --class parameter, as
you can see checking the windows with "xprop WM_CLASS".
Please fill a bug upstream, since we can't do anything at Ubuntu level
to recognize these instances as different.
** Changed in: unity
Status: New => Invalid
** Also affects: bamf
Importance: Undecided
Status: New
** Changed in: unity
Status: Invalid => Won't Fix
** Changed in: bamf
Status: New => Won't Fix
** Also affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Changed in: chromium-browser (Ubuntu)
Status: New => Confirmed
** Summary changed:
- Unity groups windows that differ in their StartupWMClass value
+ Chromium aura doesn't honor the --class parameter anymore
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1311795
Title:
Chromium aura doesn't honor the --class parameter anymore
To manage notifications about this bug go to:
https://bugs.launchpad.net/bamf/+bug/1311795/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
