The launcher does not come up.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When you log off, the launcher does not come up when you pull the cursor to the left edge.
steps:
1. Start Ubuntu
2. Logout
3. Log on
4. Start Chrome
and Launcher does not come up.
Switch to another workspace, then recovers.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: unity 4.20.0-0ubuntu2
ProcVersionSign
Uname: Linux 3.0.0-12-generic x86_64
.tmp.unity.
ApportVersion: 1.23-0ubuntu2
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Sat Oct 1 13:22:35 2011
DistUpgraded: Log time: 2011-08-12 20:00:23.116487
DistroCodename: oneiric
DistroVariant: ubuntu
GraphicsCard:
ATI Technologies Inc RV350 AS [Radeon 9550] [1002:4153] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited Device [174b:0200]
Subsystem: PC Partner Limited Device [174b:0201]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
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 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTek Computer Inc. K8N
ProcEnviron:
LANG=hu_HU.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: unity
UpgradeStatus: Upgraded to oneiric on 2011-09-26 (4 days ago)
dmi.bios.date: 02/16/2006
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1011.005
dmi.board.name: 'K8N'
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K8N
dmi.product.
dmi.sys.vendor: ASUSTek Computer Inc.
version.compiz: compiz 1:0.9.6+
version.ia32-libs: ia32-libs 20090808ubuntu25
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thanks for reporting the bug! However, I believe this is a duplicate of bug 832150. If you are still having problems after that got fixed, we can reopen this bug report.