After upgrading to 20.10 screens are not working properly

Bug #1901222 reported by Matyesz
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ubuntu
Incomplete
Undecided
Unassigned

Bug Description

Hello,

after upgrading to 20.10 from 20.04LTS I have the following issue:
I have a laptop in docker with 3 external screens connected (1 VGA, 2 HDMIs).
If I close the laptop lid all external screens work but when I start citrix workspace my screens start to flicker then xorg restarts and citrix either starts on an external screen or on the closed laptop screen. This was working without errors on 20.04 release.
Could you pls check?

Thanks, Zoltan

ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: xorg 1:7.7+19ubuntu15
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
BootLog:

CasperMD5CheckResult: skip
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 23 18:34:19 2020
DistUpgraded: Fresh install
DistroCodename: groovy
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller [1028:05bd]
InstallationDate: Installed on 2014-11-24 (2160 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Dell Inc. Latitude E6440
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=c2c28905-0487-4dc4-809c-0dc5648b2e91 ro
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/18/2014
dmi.bios.release: 4.6
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0X8DN1
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA05:bd02/18/2014:br4.6:svnDellInc.:pnLatitudeE6440:pvr01:rvnDellInc.:rn0X8DN1:rvr:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6440
dmi.product.sku: Latitude E6440
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1
version.libdrm2: libdrm2 2.4.102-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.1-1
version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.1-1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

Revision history for this message
Matyesz (zmatyas) wrote :
summary: - After upgradinf to 20.10 screens are not working properly
+ After upgrading to 20.10 screens are not working properly
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

affects: xorg (Ubuntu) → ubuntu
Changed in ubuntu:
status: New → Incomplete
Revision history for this message
Matyesz (zmatyas) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thanks. That seems to be bug 1897765 so let's track the problem there.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.