Dynamic desktop background when TearFree is true
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
In my 20-intel.conf file in either /etc/X11/
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSign
Uname: Linux 5.4.0-28-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckR
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun May 3 00:34:27 2020
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingI
GraphicsCard:
Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 (Whiskey Lake) [1043:16a1]
InstallationDate: Installed on 2020-04-30 (2 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f3:0903 Elan Microelectronics Corp. ELAN:Fingerprint
Bus 001 Device 002: ID 13d3:56dc IMC Networks USB2.0 HD UVC WebCam
Bus 001 Device 004: ID 8087:0aaa Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX392FA_UX392FA
ProcKernelCmdLine: BOOT_IMAGE=
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/17/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX392FA.301
dmi.board.
dmi.board.name: UX392FA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.family: ZenBook
dmi.product.name: ZenBook UX392FA_UX392FA
dmi.product.
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.
version.
version.
version.
version.
version.
version.
If you are using the 'intel' driver then this would be a duplicate of bug 1867668, but the attached logs show you're not using that driver (which is good in theory).
To verify which it is, please wait until the problem happens again and then run:
journalctl -b0 > journal.txt
and attach the file 'journal.txt' here.