Unity crashes on login
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
unity fails on login while a unity-2d session works. This used to work a few days back. I get the following error :
Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...no
Screen geometry changed:
0x0x1366x768
ERROR 2012-03-25 23:59:04 unity.bghash BGHash.cpp:538 could not open file (/home/
Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...no
Screen geometry changed:
0x0x1366x768
ERROR 2012-03-26 00:04:55 unity.bghash BGHash.cpp:538 could not open file (/home/
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: unity 5.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: None
Date: Mon Mar 26 00:08:20 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110921.2)
MachineType: LENOVO IdeaPad Y460p
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/12/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 3FCN11WW
dmi.board.name: KL2
dmi.board.vendor: LENOVO
dmi.board.version: Rev 1.0
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: IdeaPad Y460p
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.2-0ubuntu1
version.
version.ia32-libs: ia32-libs 20090808ubuntu35
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 963633, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.