Dash remains on top of screen locking dialog

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

Could it be specific to nvidia binary driver? seems like I cant reproduce this issue with my intel netbook after 4-5 attempts.

No other person who reported the same bug mentioned which GPU they use, or which driver they currently use. When reporting a unity bug its really helpful to use the command 'ubuntu-bug unity' so that the bug report have a little information about your system, without those the bug report is of very less use.

Bug #886605 reporter uses nvidia.

Bug #900152 is on an ATI system using the binary driver (this _is_ in the report...)

I have ab Intel i915 chipset in a Lenovo laptop

-----Original Message-----
From: Sam_
Sent: Monday, December 05, 2011 8:57 AM
To: Michael Henry
Subject: [Bug 859991] Re: Dash remains on top of screen locking dialog

Bug #886605 reporter uses nvidia.

--
You received this bug notification because you are subscribed to a
duplicate bug report (900103).
https://bugs.launchpad.net/bugs/859991

Title:
  Dash remains on top of screen locking dialog

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  The Unity dash remains open on top of the GNOME3 screen locking
  dialog. This potentially leaks information and is very confusing when
  unlocking the screen (as it is non-responsive but obscures the
  password input dialog).

  Steps to reproduce:
  1. Open the Dash.
  2. Wait for the screen to lock automatically.
  3. Move the mouse or press a key to wake the system.
  4. Observe that the dash is visible and obscuring the password input dialog.

  Expected results:
  The password input dialog is visible and no other part of the desktop is.

  Actual results:
  The dash is still displayed (non-interactively) over the password input dialog.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: unity 4.16.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.0.0-12.19-generic-pae 3.0.4
  Uname: Linux 3.0.0-12-generic-pae i686
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86 Kernel Module 280.13 Wed Jul 27 16:55:43 PDT 2011
   GCC version: gcc version 4.6.1 (Ubuntu/Linaro 4.6.1-9ubuntu3)
  .tmp.unity.support.test.0:

  ApportVersion: 1.23-0ubuntu1
  Architecture: i386
  CompizPlugins: [core,bailer,detection,composite,opengl,compiztoolbox,decor,resize,place,grid,imgpng,session,move,gnomecompat,mousepoll,wall,vpswitch,snap,regex,unitymtgrabhandles,animation,expo,workarounds,fade,scale,ezoom,unityshell]
  CompositorRunning: compiz
  Date: Mon Sep 26 16:11:18 2011
  DistUpgraded: Fresh install
  DistroCodename: oneiric
  DistroVariant: ubuntu
  GraphicsCard:
   nVidia Corporation C73 [GeForce 7100 / nForce 630i] [10de:07e1] (rev a2) (prog-if 00 [VGA controller])
     Subsystem: nVidia Corporation Device [10de:cb73]
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110922)
  JockeyStatus:
   xorg:nvidia_173 - NVIDIA accelerated graphics driver (Proprietary, Disabled, Not in use)
   xorg:nvidia_current - NVIDIA accelerated graphics driver (Proprietary, Enabled, In use)
   kmod:nvidia_173 - nvidia_173 (Proprietary, Disabled, Not in use)
   kmod:nvidia_current - nvidia_current (Proprietary, Disabled, Not in use)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 002 Device 002: ID 03f0:0024 Hewlett-Packard KU-0316 Keyboard
   Bus 002 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  MachineType: Unknow Unknow
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: B...

This happens to me, very intermittently , with an ATI Technologies Inc RV620 LE [Radeon HD 3450]

Note that this is a lot easier to reproduce by opening dash and pressing
Ctrl-Alt-L
to lock the screen.

Is somebody still seeing that in precise?

I have not seen this bug for quite some time in precise and have not been able to reproduce it (including by manually locking the screen).

thanks, let's close the bug since the recent duplicates are from 11.10 as well, if somebody still get similar issues in precise please open a new bug