Everything is ok but The only is disappointing I cannot control display brightness through ubuntu provided brightness control option.And when I am playing any video it looks like my onboard graphics can't handel the video's graphics but, when i was on windows i didn't see any kind of problem like this.should I need to use any graphics card.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg (Ubuntu) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
My system specs;-Intel pentium 2010g processor
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSign
Uname: Linux 4.13.0-37-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Mar 23 19:21:08 2018
DistUpgraded: Fresh install
DistroCodename: artful
DistroVariant: ubuntu
GraphicsCard:
Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:0152] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller [8086:2111]
InstallationDate: Installed on 2018-03-21 (2 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: To be filled by O.E.M. To be filled by O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 4.6.5
dmi.board.
dmi.board.name: H61
dmi.board.vendor: INTEL Corporation
dmi.board.version: To be filled by O.E.M.
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: To be filled by O.E.M.
dmi.product.name: To be filled by O.E.M.
dmi.product.
dmi.sys.vendor: To be filled by O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.83-1
version.
version.
version.
version.
version.
version.
version.
I was able to recreate this bug running Bionic daily (Using VMWare) - 27/03/2018