[Touch-packages] [Bug 1898210] [NEW] X11 applications do not refresh in a timely fashion, resulting in screen corruption
Public bug reported:
Many X11 applications do not refresh in a timely fashion, and the window
must be disturbed to achieve refresh. Typical disturbances causing
refresh are: typing in the window, interacting with the mouse, focusing
a different application, etc.
I have seen this behavior in:
* Firefox
* Electron apps (Slack, Keybase, Element, Discord)
* Zoom
* Possibly Emacs (see #1893969)
* Xournal
* VMware Player (both the host GUI and the guest screen)
I am attaching a video of this behavior in Firefox; you can see that
when I close a tab, the tab that takes its place paints only partially,
and even mousing with tooltip popups and typing in a text entry cause
only partial corrections. Mousing away from the Firefox window to focus
a window on a different display causes a complete repaint. (Mousing to
another window on the _same_ display would also cause a repaint, it just
so happens that I focused a window on a different display).
I can reproduce this problem with no compositor running, or with compton
running.
This bug is trivial to reproduce and happens nearly constantly. I have
trouble taking screen shots / videos of the behavior on this machine
only because this is a workstation that I use for teaching a University
course and much of the work that I do on it would disclose student
information if shared. I will try to produce more evidence if required,
but it requires some time to do so.
My desktop configuration is three displays. The displays are arranged
in a horizontal row. The left and center monitors are external Full HD
DisplayPort monitors, daisy chained, and the right monitor is the
internal display on my laptop. The left display is DP-2-1, which is
connected to the center monitor by a DisplayPort daisy chain. The
center display is DP-2-8, which is connected to the laptop via
DisplayPort over USB 3 (USB C). The right display is eDP-1. All three
displays have a logical resolution of 3840x2160. The left and center
displays are scaled to Full HD, and the eDP-1 runs at its native
resolution. I use the following xrandr command to configure this:
HIX=3840
HIY=2160
HI=${HIX}x${HIY}
xrandr --fb $(($HIX * 3))x$HIY \
--output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
--output DP-2-8 --auto --panning ${HI}+$HIX+0 \
--scale-from $HI --left-of eDP-1 --scale 2x2 \
--output DP-2-1 --auto --panning $HI+0+0 \
--scale-from $HI --left-of DP-2-8 --scale 2x2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop:
Date: Fri Oct 2 10:02:50 2020
DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus:
v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
v4l2loopback, 0.12.3, 5.4.0-47-generic, x86_64: installed
v4l2loopback, 0.12.3, 5.4.0-48-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0962]
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-06-21 (102 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption focal ubuntu
** Attachment added: "firefox-kill-tab.mp4"
https://bugs.launchpad.net/bugs/1898210/+attachment/5416639/+files/firefox-kill-tab.mp4
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ub
[Touch-packages] [Bug 1893969] [NEW] Screen corruption and delayed update using onboard Intel video
Public bug reported:
I frequently get screen corruption or delayed screen updates using
onboard Intel video (i7-10710U in a Dell XPS 13 7390). I am attaching a
screen shot of an example of this in Emacs, where you can see echoes of
past cursor locations (center right side of screen, the highlighted word
"boolean").
A frequent failure is that an application updates its window, but the
updates do not appear on screen until I take some action to disturb the
window (move or resize it, change focus, change desktops, etc.), after
which it cleans itself up. Small changes (such as selecting text) will
often clean up the image where the change is made without repainting the
entire window.
My display panel is 4K UHD+, and I have attached two external Full HD
DisplayPort monitors using chaining with 2x2 scale using XrandR. This
corruption appears to happen on all three surfaces. The configuration
for my desktop is:
HIX=3840
HIY=2160
HI=${HIX}x${HIY}
xrandr --fb $(($HIX * 3))x$HIY \
--output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
--output DP-2-8 --auto --panning ${HI}+$HIX+0 \
--scale-from $HI --left-of eDP-1 --scale 2x2 \
--output DP-2-1 --auto --panning $HI+0+0 \
--scale-from $HI --left-of DP-2-8 --scale 2x2
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: skip
CompositorRunning: None
CurrentDesktop:
Date: Wed Sep 2 11:48:03 2020
DistUpgraded: 2020-06-21 15:36:52,619 DEBUG Running PostInstallScript:
'./xorg_fix_proprietary.py'
DistroCodename: focal
DistroVariant: ubuntu
DkmsStatus: v4l2loopback, 0.12.3, 5.4.0-42-generic, x86_64: installed
DpkgLog:
ExtraDebuggingInterest: Yes
GraphicsCard:
Intel Corporation Device [8086:9bca] (rev 04) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:0962]
MachineType: Dell Inc. XPS 13 7390
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-42-generic
root=UUID=aeb9197c-491f-493d-9a7a-7094efd5023c ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to focal on 2020-06-21 (72 days ago)
dmi.bios.date: 11/25/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.0
dmi.board.name: 0377MH
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.4.0:bd11/25/2019:svnDellInc.:pnXPS137390:pvr:rvnDellInc.:rn0377MH:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390
dmi.product.sku: 0962
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.101-2
version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug corruption focal ubuntu
** Attachment added: "corruption.png"
https://bugs.launchpad.net/bugs/1893969/+attachment/5407026/+files/corruption.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1893969
Title:
Screen corruption and delayed update using onboard Intel video
Status in xorg package in Ubuntu:
New
Bug description:
I frequently get screen corruption or delayed screen updates using
onboard Intel video (i7-10710U in a Dell XPS 13 7390). I am attaching
a screen shot of an example of this in Emacs, where you can see echoes
of past cursor locations (center right side of screen, the highlighted
word "boolean").
A frequent failure is that an application updates its window, but the
updates do not appear on screen until I take some action to disturb
the window (move or resize it, change focus, change desktops, etc.),
after which it cleans itself up. Small changes (such as selecting
text) will often clean up the image where the change is made without
repainting the entire window.
My display panel is 4K UHD+, and I have attached two external Full HD
DisplayPort monitors using chaining with 2x2 scale using XrandR. This
corruption appears to happen on all three surfaces. The configuration
for my desktop is:
HIX=3840
HIY=2160
HI=${HIX}x${HIY}
xrandr --fb $(($HIX * 3))x$HIY \
--output eDP-1 --auto --panning ${HI}+$(($HIX * 2))+0 \
--output DP-2-8 --auto --panning ${HI}+$HIX+0 \
[Touch-packages] [Bug 1581241] Re: bluetooth headset doesn't automatically configure for a2dp correctly (regression)
I have isolated a method for making things work, for others who may have similar problems: 1) Connect headset by turning it on. 2) Set headset to headset (not a2dp) mode using blueman-manager 3) Disconnect headset from blueman-manager 4) Reconnect headset from blueman-manager; it will show Audio Profile: off 5) Set audio profile to A2DP At this point, it generally seems to work. Shorter sequences have not yet reliably worked for me. Some parts of the dance can be done in pavucontrol, but it's easiest to do it all in one place. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1581241 Title: bluetooth headset doesn't automatically configure for a2dp correctly (regression) Status in bluez package in Ubuntu: New Bug description: I have a bluetooth headset capable of several modes of connection (headset, handsfree, and a2dp). In 15.10, once I had correctly configured it for a2dp once, applications using pulseaudio could use it freely each time it was connected to the machine. In 16.04, upon connection, applications that attempt to use it appear to hang waiting for something. I have to fiddle with its settings (and sorry I can't be more specific, but it's not clear to me exactly what sequence fixes it; I change it to/from headset and A2DP in blueman a few times, do the same in pavucontrol, etc., and at some point it starts working) for several minutes to get it working in a2dp mode. It appears that after connection I can put it in headset mode and start playing to it immediately, but of course the audio quality is horrible. Once I've fiddled it into working, it works until disconnected, and upon reconnect it behaves the same as before I fiddled it into submission: a2dp connection, but clients accessing it hang. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 12 18:38:16 2016 InstallationDate: Installed on 2015-06-04 (342 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-04-22 (20 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/07/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:7C:03:11 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1391 acl:0 sco:0 events:164 errors:0 TX bytes:27517 acl:0 sco:0 commands:163 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1581241/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1581241] [NEW] bluetooth headset doesn't automatically configure for a2dp correctly (regression)
Public bug reported: I have a bluetooth headset capable of several modes of connection (headset, handsfree, and a2dp). In 15.10, once I had correctly configured it for a2dp once, applications using pulseaudio could use it freely each time it was connected to the machine. In 16.04, upon connection, applications that attempt to use it appear to hang waiting for something. I have to fiddle with its settings (and sorry I can't be more specific, but it's not clear to me exactly what sequence fixes it; I change it to/from headset and A2DP in blueman a few times, do the same in pavucontrol, etc., and at some point it starts working) for several minutes to get it working in a2dp mode. It appears that after connection I can put it in headset mode and start playing to it immediately, but of course the audio quality is horrible. Once I've fiddled it into working, it works until disconnected, and upon reconnect it behaves the same as before I fiddled it into submission: a2dp connection, but clients accessing it hang. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 12 18:38:16 2016 InstallationDate: Installed on 2015-06-04 (342 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-04-22 (20 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/07/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. hciconfig: hci0: Type: BR/EDR Bus: USB BD Address: 5C:51:4F:7C:03:11 ACL MTU: 1021:5 SCO MTU: 96:5 UP RUNNING PSCAN RX bytes:1391 acl:0 sco:0 events:164 errors:0 TX bytes:27517 acl:0 sco:0 commands:163 errors:0 ** Affects: bluez (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1581241 Title: bluetooth headset doesn't automatically configure for a2dp correctly (regression) Status in bluez package in Ubuntu: New Bug description: I have a bluetooth headset capable of several modes of connection (headset, handsfree, and a2dp). In 15.10, once I had correctly configured it for a2dp once, applications using pulseaudio could use it freely each time it was connected to the machine. In 16.04, upon connection, applications that attempt to use it appear to hang waiting for something. I have to fiddle with its settings (and sorry I can't be more specific, but it's not clear to me exactly what sequence fixes it; I change it to/from headset and A2DP in blueman a few times, do the same in pavucontrol, etc., and at some point it starts working) for several minutes to get it working in a2dp mode. It appears that after connection I can put it in headset mode and start playing to it immediately, but of course the audio quality is horrible. Once I've fiddled it into working, it works until disconnected, and upon reconnect it behaves the same as before I fiddled it into submission: a2dp connection, but clients accessing it hang. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: bluez 5.37-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 Date: Thu May 12 18:38:16 2016 InstallationDate: Installed on 2015-06-04 (342 days ago) InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. XPS13 9333 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic.efi.signed root=/dev/mapper/lubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to xenial on 2016-04-22 (20 days ago) dmi.bios.date: 11/07/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A06 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnDellInc.:bvrA06:bd11/07/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr0.1: dmi.product.name: XPS13 9333 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 5C:51:4F:7C:03:11 ACL MTU: 1021:5 SCO MTU: 96:5
[Touch-packages] [Bug 258008] Re: gnupg 1.4.6 in hardy heron fails to verify some files signed by gnupg 1.4.9
This bug can be closed. As far as I know it is still valid, but as it was not addressed in a timely fashion it is no longer relevant. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnupg in Ubuntu. https://bugs.launchpad.net/bugs/258008 Title: gnupg 1.4.6 in hardy heron fails to verify some files signed by gnupg 1.4.9 Status in gnupg package in Ubuntu: New Bug description: Ubuntu 8.04.1 gnupg 1.4.6-2ubuntu5 The gnupg 1.4.6 shipping with Hardy Heron fails to verify some files which are signed by newer versions of gnupg. I unfortunately cannot (at this time) provide public examples of such files. Stock gnupg 1.4.6 exhibits the same problem; stock 1.4.9 compiled for the system works properly. The problem seems to be in older versions of gnupg itself, not Ubuntu, though neither the gnupg ChangeLog nor NEWS specifically mention any fixes for such failures post-1.4.6. I am not marking this bug as a security vulnerability, although it certainly has security implications in some situations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnupg/+bug/258008/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
