Gnome shell and ubuntu unity do not appear.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xserver-xorg-video-ati (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
When I log into unity or gnome shell I do not get gnome shell at all just gnome classic with worse icnos and things (attached screenshot. Unity is not proper clean unity it has the same poor icons and jittery performance.
This started happening about four days ago.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: xorg 1:7.6+7ubuntu7
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
.tmp.unity.
.tmp.unity.
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: None
Date: Tue Oct 4 18:52:49 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
ATI Technologies Inc AMD Radeon HD 6310 GraphicsATI [1002:9802] (prog-if 00 [VGA controller])
Subsystem: Hewlett-Packard Company Device [103c:1611]
MachineType: Hewlett-Packard HP Pavilion dm1 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/26/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.12
dmi.board.
dmi.board.name: 1611
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 96.39
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: HP Pavilion dm1 Notebook PC
dmi.product.
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.6+
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
affects: | xorg (Ubuntu) → xserver-xorg-video-ati (Ubuntu) |
Hey conor-smurf,
Hi, thanks for reporting this issue during the development period of
Ubuntu.
I notice there's not been further comments to the bug report since the
release came out, would you mind updating us on the status of it in the
release?
Are you still able to reproduce the issue? If not, do you think the bug
report can be closed, or do you think we should continue tracking it?