Dash bg color doesn't match its surroundings

I can confirm this behavior and the initial black behind the Dash is due to the fact that OpenGL 1.4 is being forced as the workaround for the poor performance for Mesa 9.2. Why it takes changing the background to get the correct blurring still needs to be investigated.

I expect this is probably an issue in Mesa 9.2 than in Unity/Nux since I can't see any recent changes in Unity/Nux that would potentially cause this.

Status changed to 'Confirmed' because the bug affects multiple users.

Fix committed into lp:unity at revision None, scheduled for release in unity, milestone 7.2.0

Status changed to 'Confirmed' because the bug affects multiple users.

Will this bug ever be fixed in Saucy or would we have to wait for Trusty?

@apandada1 The status in saucy (Unity 7.1) just changed to "In Progress", they are working on it :)

This bug was fixed in the package unity - 7.1.2+14.04.20131106.1-0ubuntu1

---------------
unity (7.1.2+14.04.20131106.1-0ubuntu1) trusty; urgency=low

  [ Ted Gould ]
  * Clean up NIH Errors so they don't get reported on exit. (LP:
    #1236720)

  [ Brandon Schaefer ]
  * Workaround for now, replace all blacklisted chars in the results
    name with a '?'. So we can still render all the results with out a
    crash. This needs to be fixed in pango/harfbuzz. (LP: #1239381)
  * Get the current char before moving on to the next char!.

  [ Marco Trevisan (Treviño) ]
  * UnityScreen: also redraw the HudView if it has not been fully
    damaged. (LP: #1240322)
  * OverlayRenderer: only and correctly initialize the BGLayer when not
    on GLSL codepath Make sure we set the initial bg_layer_ value to the
    average color, and do this only if really needed. (LP: #1232726)
  * Launcher: desaturate the inactive icons when in Spread mode. (LP:
    #1238892, #1238638)
  * LauncherIcon: add MultiMonitor quirks support A quirk can be now set
    for all monitors or for just one. (LP: #1051913, #1215738, #1240750,
    #1240737)
  * UnityScreen: CreateSuperNewAction with Shift and Numpad for launcher
    This fixes the bug that caused Super+Shift+KP_x not to work as it
    should. (LP: #1240806)
  * AnimationUtils: add Start, Skip and SetValue methods These allows to
    start an animation, to skip it or to just set its value. The
    templates now are more intelligent and we define the values that can
    assume just once, by specializing a StartValueForDirection function.
  * Support libxpathselect1.4. (LP: #1243529)
  * LauncherIcon: use nux::Animation for each Quirk property Update
    Launcher and Icons code accordingly, get rid of the timespec. Remove
    unneded Quirks, reduce redraws and update tests.
  * Invalidate the Icon Centers when the monitor layout changes, so we
    make sure that if an icon center is set, then the icon is available
    on that monitor. Added GetCenterForMonitor that allows to retrieve
    the nearest valid icon center for a given monitor, and in this way
    we can get the best icon that can handle a window minimization. (LP:
    #767752)

  [ Lars Uebernickel ]
  * panel-service.c: don't warn about unknown image type unnecessarily
    Don't warn about indicators that explicitely don't have an image
    set. However, continue warning when the set image is of an unknown
    type.

  [ Chris Townsend ]
  * Instead of using NeedSoftRedraw(), use QueueDraw() for the Launcher
    and Panel to force a redraw to fix issue where leaving a full screen
    unredirected window would not redraw the Launcher and Panel. (LP:
    #1240595)

  [ Eleni Maria Stea ]
  * Added --compiz-path parameter to the unity startup script. It allows
    us to start unity with custom builds of compiz (not only
    /usr/bin/compiz) like that: ./unity --compiz-path
    custom_compiz_build_directory/bin/compiz --replace ccp.

  [ Francis Ginther ]
  * Reverting support for libxpathselect1.4. (LP: #1245988)

  [ Łukasz 'sil2100' Zemczak ]
  * DebugDBusInterface: add support to libxpathselect-1.4 Some cleanups
    and reworking of glib::Variant and debug::...

I still have this bug in 13.10. I see that it's fixed in 14.04. When will it be fixed in 13.10?

I gave Trusty a spin, and the bug is fixed. I guess it's a matter of time before the fix hits Saucy :)

Today I upgraded to Ubuntu 14.04 and this bug is no longer present, you can also solve it on 13.10?

Please, stop repeating the same question. Just click the "Affects me too"
since the question has already been asked. Notice that the status says "In
Progress" that means they are working on it (or are conscious of the bug
already).

On Thu, Nov 14, 2013 at 8:46 AM, Carlo <email address hidden> wrote:

> Today I upgraded to Ubuntu 14.04 and this bug is no longer present, you
> can also solve it on 13.10?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1232726
>
> Title:
> Dash bg color doesn't match its surroundings
>
> Status in Unity:
> Fix Committed
> Status in Unity 7.1 series:
> In Progress
> Status in “mesa” package in Ubuntu:
> Invalid
> Status in “unity” package in Ubuntu:
> Fix Released
> Status in “unity” source package in Saucy:
> In Progress
>
> Bug description:
> Lately, after login the Dash keeps a black background even if the
> Launcher and panel follow the current wallpaper color. I've added a
> screenshot. If I change the wallpaper, Dash recovers its chameleonic
> effect (until next reboot).
>
> Also, this started happening at the same time that a new error message
> (at log time) appeared, I've attached this error message, too.
>
> Description: Ubuntu Saucy Salamander (development branch)
> Release: 13.10
>
> unity:
> Installed: 7.1.1+13.10.20130927.1-0ubuntu1
> Candidate: 7.1.1+13.10.20130927.1-0ubuntu1
> Version table:
> *** 7.1.1+13.10.20130927.1-0ubuntu1 0
> 500 http://us.archive.ubuntu.com/ubuntu/ saucy/main i386
> Packages
> 100 /var/lib/dpkg/status
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.10
> Package: unity 7.1.1+13.10.20130927.1-0ubuntu1
> ProcVersionSignature: Ubuntu 3.11.0-9.16-generic 3.11.2
> Uname: Linux 3.11.0-9-generic i686
> .tmp.unity.support.test.0:
>
> ApportVersion: 2.12.5-0ubuntu1
> Architecture: i386
> CompizPlugins: No value set for
> `/apps/compiz-1/general/screen0/options/active_plugins'
> CompositorRunning: compiz
> CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
> CompositorUnredirectFSW: true
> Date: Sun Sep 29 08:00:07 2013
> DistUpgraded: Fresh install
> DistroCodename: saucy
> DistroVariant: ubuntu
> GraphicsCard:
> Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated
> Graphics Controller [8086:27a2] (rev 03) (prog-if 00 [VGA controller])
> Subsystem: Hewlett-Packard Company Device [103c:30a2]
> Subsystem: Hewlett-Packard Company Device [103c:30a2]
> InstallationDate: Installed on 2013-08-31 (28 days ago)
> InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha i386
> (20130830)
> MachineType: Hewlett-Packard HP Compaq nx7400 (GF451LA#ABM)
> MarkForUpload: True
> PccardctlIdent:
> Socket 0:
> no product info available
> PccardctlStatus:
> Socket 0:
> no card
> ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.11.0-9-generic
> root=UUID=cab2c6d5-2bf8-4db8-ba85-daaf28b1afec ro quiet splash
> SourcePackage: unity
> UpgradeStatus: No upgrade log present (probably fresh install)
> dmi.bios.date: 12/18/2006
> dmi.bios.vendor: Hewle...

Fix committed into lp:unity/7.1 at revision None, scheduled for release in unity, milestone 7.1.2

@Mark,

I'm not sure which version of Ubuntu you are using, but this is only currently fixed for 14.04. It is scheduled to be included in an SRU for 13.10, but unfortunately, I don't have a time table of when that will be.

still no fix for ubuntu 13.10

Why is this "invalid" for Saucy? Because it's too late in the day?

Fix Released in Unity Unity 7.2.0.