Laucher background not blurred when Dash is opened

Bug #1044927 reported by Sami Jaktholm
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Unity
Fix Released
Medium
Unassigned
7.2
Fix Released
Medium
Unassigned
unity (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

The launcher background is occasionally left without blur (see attached screenshot). This is a regression after updating unity from version 6.2.0-0ubuntu4 to 6.4.0-0ubuntu1.

Steps to reproduce:
Make sure that launcher is set to autohide and it's not visible.
1. Open dash pressing Super
2. Notice that the launcher background is not blurred.

This happens only when dash is opened pressing Super button. If launcher happens to be visible prior to opening dash, for example opening dash from BFB, the launcher background is blurred properly. If you open dash by using lens shortcuts (Super+F for example), the launcher background is blurred correctly most of the time.

Also, if the launcher background has no blur and you click something with your mouse inside dash, the launcher background gets blurred.

I think this is somehow related to bug 1044926 because the launcher background is never blurred if the dash is shown before the launcher.

ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: unity 6.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-11.11-generic 3.5.2
Uname: Linux 3.5.0-11-generic x86_64
ApportVersion: 2.5.1-0ubuntu4
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
Date: Sun Sep 2 10:37:48 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV620 [Mobility Radeon HD 3400 Series] [1002:95c4] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:19e2]
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64 (20120807.1)
MachineType: ASUSTeK Computer Inc. F5SR
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.5.0-11-generic root=UUID=40b6854e-96f6-477e-843b-810512211444 ro quiet splash
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 210
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: F5SR
dmi.board.vendor: PEGATRON CORPORATION
dmi.board.version: 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr210:bd04/01/2009:svnASUSTeKComputerInc.:pnF5SR:pvr1.0:rvnPEGATRONCORPORATION:rnF5SR:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
dmi.product.name: F5SR
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.38-0ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20120821.c1114c61-0ubuntu2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20120821.c1114c61-0ubuntu2
version.xserver-xorg-core: xserver-xorg-core 2:1.12.99.905-0ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120713.6ef1ad6a-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.3-0ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.1-4~ubuntu1

Revision history for this message
Sami Jaktholm (sjakthol) wrote :
Revision history for this message
Omer Akram (om26er) wrote :

thanks for the bug report. Can you please run 'unity --reset' in terminal the test and let us know if the issue is still there.

Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Sami Jaktholm (sjakthol) wrote :

This bug still occurs after running unity --reset. Also tested with guest session and current daily-live ISO and the bug appears there too.

Revision history for this message
Omer Akram (om26er) wrote :

please paste the result of '/usr/lib/nux/unity_support_test -p' in this bug report.

Revision history for this message
Omer Akram (om26er) wrote :

It could be specific to ATI, or a certain class of GPUs since I can't reproduce it on SandyBridge. will test it on a netbook.

Revision history for this message
Sami Jaktholm (sjakthol) wrote :

$ /usr/lib/nux/unity_support_test -p
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV620
OpenGL version string: 2.1 Mesa 8.1-devel

Not software rendered: yes
Not blacklisted: yes
GLX fbconfig: yes
GLX texture from pixmap: yes
GL npot or rect textures: yes
GL vertex program: yes
GL fragment program: yes
GL vertex buffer object: yes
GL framebuffer object: yes
GL version is 1.4+: yes

Unity 3D supported: yes

Revision history for this message
Omer Akram (om26er) wrote :

I can't reproduce the bug since I don't have ATI but since you can, I'll leave this one to NEW for now. Maybe someone else can reproduce the bug.

Changed in unity (Ubuntu):
status: Incomplete → New
Revision history for this message
Bilal Akhtar (bilalakhtar) wrote :

I'm not able to reproduce this either, Intel GPU. Seems ATI-only, yeah.

tags: added: hwsps
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

Right Im getting this on an intel chip (but not all the time). It helps when I try to go from the Hud -> Dash. Seems a logical check, or a ubus message to slow/fast.... but this is confirmed.

Changed in unity:
status: New → Triaged
Changed in unity (Ubuntu):
status: New → Triaged
Changed in unity:
importance: Undecided → Medium
Changed in unity (Ubuntu):
importance: Undecided → Medium
Changed in unity:
milestone: none → 7.1.0
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

Also make sure you have your launcher set to autohide....

Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.1.0 → 7.1.1
Revision history for this message
Brandon Schaefer (brandontschaefer) wrote :

Now I can't reproduce this... this might have accidentally been fixed with some blur changes that went on, if anyone can reproduce this in the mean time please make a comment!

Andrea Azzarone (azzar1)
Changed in unity:
status: Triaged → Incomplete
Changed in unity (Ubuntu):
status: Triaged → Incomplete
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.1.1 → 7.2.0
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for unity (Ubuntu) because there has been no activity for 60 days.]

Changed in unity (Ubuntu):
status: Incomplete → Expired
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.2.0 → 7.2.1
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.2.1 → 7.2.2
Changed in unity:
milestone: 7.2.2 → 7.2.3
Changed in unity:
milestone: 7.2.3 → 7.3.1
Changed in unity (Ubuntu):
status: Expired → Incomplete
Changed in unity (Ubuntu):
status: Incomplete → Expired
Andrea Azzarone (azzar1)
Changed in unity (Ubuntu):
status: Expired → Incomplete
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.3.1 → 7.3.2
Revision history for this message
Christopher Townsend (townsend) wrote :

This seems fixed as no new activity has occurred for this bug in some time. I also cannot reproduce, albeit, on an Intel graphics machine. Going to mark it Fixed Released. We can either reopen this bug or submit a new bug report if it still occurs for anyone.

Changed in unity:
status: Incomplete → Fix Released
milestone: 7.3.2 → none
Changed in unity (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.