cairo-dock-team team mailing list archive

[Launchpad Bug Tracker <587664@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package chromium-browser -
5.0.375.70~r48679-0ubuntu0.10.04.1

---------------
chromium-browser (5.0.375.70~r48679-0ubuntu0.10.04.1) lucid-security; urgency=low

  * New upstream release from the Stable Channel (LP: #591474)
    Fixes the following security issues:
    - [15766] Medium Cross-origin keystroke redirection. Credit to Michal
      Zalewski of Google Security Team.
    - [39985] High Cross-origin bypass in DOM methods. Credit to Sergey
      Glazunov.
    - [42723] High Memory error in table layout. Credit to wushi of team509.
    - [43304] High Linux sandbox escape. Credit to Mark Dowd under contract to
      Google Chrome Security Team.
    - [43307] High Bitmap stale pointer. Credit to Mark Dowd under contract to
      Google Chrome Security Team.
    - [43315] High Memory corruption in DOM node normalization. Credit to Mark
      Dowd under contract to Google Chrome Security Team.
    - [43487] High Memory corruption in text transforms. Credit to wushi of
      team509.
    - [43902] Medium XSS in innerHTML property of textarea. Credit to
      sirdarckcat of Google Security Team.
    - [44740] High Memory corruption in font handling. Credit: Apple.
    - [44868] High Geolocation events fire after document deletion. Credit to
      Google Chrome Security Team (Justin Schuh).
    - [44955] High Memory corruption in rendering of list markers. Credit:
      Apple.
  * Add a --temp-profile knob to the launcher script starting Chromium with
    a new profile which will last only for the duration of the session
    - update debian/chromium-browser.sh
  * Change StartupWMClass to Chromium-browser in the desktop launcher so
    cairo-dock does the right thing (LP: #587664)
    - update debian/chromium-browser.desktop
  * Set XLIB_SKIP_ARGB_VISUALS=1 in the wrapper to prevent flash from dying
    with a Gdk-ERROR when gtk2 is built with RGBA support (like in Maverick).
    (LP: #584959)
    - update debian/chromium-browser.sh
  * Unbreak get-orig-source when it needs to drop its cache after a channel jump
    (replace brace expansion - which is a bashism - with proper $(wildcard))
    - update debian/rules
 -- Fabien Tassin <fta@xxxxxxxxxx>   Wed, 09 Jun 2010 07:30:50 +0200

** Changed in: chromium-browser (Ubuntu Lucid)
       Status: Fix Committed => Fix Released

-- 
Cairo: clicking the Chromium launcher opens an application icon instead of just marking the launcher with arrow
https://bugs.launchpad.net/bugs/587664
You received this bug notification because you are a member of Cairo-
Dock Team, which is subscribed to cairo-dock in ubuntu.

Status in “cairo-dock” package in Ubuntu: Invalid
Status in “chromium-browser” package in Ubuntu: Fix Released
Status in “cairo-dock” source package in Lucid: Invalid
Status in “chromium-browser” source package in Lucid: Fix Released
Status in “cairo-dock” source package in Maverick: Invalid
Status in “chromium-browser” source package in Maverick: Fix Released

Bug description:
Binary package hint: cairo-dock

It doesn't happen with any other application but Chromium, or I haven't realized so far. Check the screenshot, I have 2 Chromium icons on the dock, 1 on the left side (launcher), the other 1 on the right side (application icon).

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: cairo-dock-core 2.1.3-10-lucid-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
Architecture: i386
Date: Sun May 30 23:05:37 2010
ExecutablePath: /usr/bin/cairo-dock
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
ProcEnviron:
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: cairo-dock
XsessionErrors:
 (polkit-gnome-authentication-agent-1:10489): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (nm-applet:10476): Gdk-CRITICAL **: gdk_window_thaw_toplevel_updates_libgtk_only: assertion `private->update_and_descendants_freeze_count > 0' failed
 (gnome-terminal:11094): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed