Chrome + Radeon + hardware acceleration: black Google maps tab
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
mesa (Ubuntu) |
Fix Released
|
Undecided
|
Maarten Lankhorst |
Bug Description
When opening Google Maps, i got a completely black tab instead - see the attached image.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: libgl1-mesa-dri 10.1.3-0ubuntu0.1
ProcVersionSign
Uname: Linux 3.13.0-34-generic x86_64
.tmp.unity.
ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CompositorUnred
CompositorUnred
CurrentDesktop: Unity
Date: Wed Aug 20 17:29:32 2014
DistUpgraded: 2014-04-04 15:34:47,605 DEBUG enabling apt cron job
DistroCodename: trusty
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Park [Mobility Radeon HD 5430] [1002:68e1] (prog-if 00 [VGA controller])
Subsystem: PC Partner Limited / Sapphire Technology Caicos [Radeon HD 5450] [174b:3000]
InstallationDate: Installed on 2012-11-15 (643 days ago)
InstallationMedia: Ubuntu-Server 12.10 "Quantal Quetzal" - Release amd64 (20121017.2)
MachineType: Intel Corporation Shark Bay Client platform
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: mesa
UpgradeStatus: Upgraded to trusty on 2014-04-04 (138 days ago)
dmi.bios.date: 01/28/2013
dmi.bios.vendor: Intel Corporation
dmi.bios.version: HSWLPTU1.
dmi.board.
dmi.board.name: Flathead Creek Crb
dmi.board.vendor: Intel Corp.
dmi.board.version: 2
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.
dmi.modalias: dmi:bvnIntelCor
dmi.product.name: Shark Bay Client platform
dmi.product.
dmi.sys.vendor: Intel Corporation
version.compiz: compiz 1:0.9.11.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.52-1
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Wed Aug 20 11:04:41 2014
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.15.1-0ubuntu2
xserver.
i forgot to mention that turning off the "hardware acceleration" in chrome -> Settings -> System, makes the bug disappear.