Icons.keep.flashing
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
lost.use.
very.slow.
Icons.keep.flashing
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSign
Uname: Linux 4.15.0-36-generic x86_64
.tmp.unity_
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: None
Date: Fri Nov 2 09:56:43 2018
DistUpgraded: 2018-11-01 23:04:23,218 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics Controller (ThinkPad T520) [17aa:21cf]
InstallationDate: Installed on 2017-09-21 (407 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: LENOVO 42424WU
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-11-02 (0 days ago)
dmi.bios.date: 11/24/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET55WW (1.35 )
dmi.board.
dmi.board.name: 42424WU
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.family: ThinkPad T520
dmi.product.name: 42424WU
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.
version.libdrm2: libdrm2 2.4.91-2
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Thu Nov 1 10:46:56 2018
xserver.configfile: default
xserver.errors:
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.
xserver.
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find.