compiz error start ubuntu only with gnome classic no effect
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
unity (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
After upgrade i need to start ubuntu only in gnome classic non effect version for show my desktop
if i try to start with unity or gnome classic i show only a black screen
when i type same 2 keys ( e.s 2 times the r key or 2 time the backspace button,etc) with my keyboard quicly the system stop to write and the screen blink!
i have a sony vaio 64 bit amd processor and amd radeon video card
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: Sun Mar 25 01:47:47 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Sony Corporation VPCYB15KX
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: unity
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2010
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0160Z7
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnInsydeCo
dmi.product.name: VPCYB15KX
dmi.product.
dmi.sys.vendor: Sony Corporation
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.