[Desktop-packages] [Bug 1720741] Re: On 17.10, two-finger scrolling on thinkpad x1 3rd generation non-working

Sergio: Yes, I noticed the same also after my comment about it being solved, but as of today as well this problem seems to be resolved. Hopefully. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/

[Desktop-packages] [Bug 1720741] Re: On 17.10, two-finger scrolling on thinkpad x1 3rd generation non-working

This seems to have been solved by the latest updates -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1720741 Title: On 17.10, two-finger scrolling on thinkpad x1 3rd generation non- wor

[Desktop-packages] [Bug 1720741] [NEW] On 17.10, two-finger scrolling on thinkpad x1 3rd generation non-working

Public bug reported: Two-finger scrolling is non-functional after upgrade to 17.10 beta. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: xorg 1:7.7+19ubuntu2 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 .tmp.unity_support_test.0: ApportVer

[Desktop-packages] [Bug 1628866] Re: After upgrading to 16.10, Chrome has become unusable because of extremely slow update

Starting chrome with LIBGL_DRI3_DISABLE=1 definitely seems to make a difference, it is now blazingly fast. Do you know if there is any general solution planned? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.

[Desktop-packages] [Bug 1628866] [NEW] After upgrading to 16.10, Chrome has become unusable because of extremely slow update

Public bug reported: Both Chrome and Firefox actually were extremely slow regarding visual update (1 second after clicking a tab, lagging when entering text). Examining this old report: https://bugs.launchpad.net/ubuntu- gnome/+bug/1386721, I tried disbling bootloader graphics and VESA framebuffer

[Desktop-packages] [Bug 1628841] [NEW] launcher placement drop-down disappeared from the display settings dialog

Public bug reported: In 16.10 beta2, upgraded from 16.04, I have no more a launcher placement (or any other general options) in the display settings dialog – see attachment ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: unity-control-center 15.04.0+16.10.20160705.1-0ubuntu1 ProcVersionSign

[Desktop-packages] [Bug 1565667] Re: When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This was

With the latest update, it seems like the problem has been resolved. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1565667 Title: When returning from suspend, my external Apple monitor

[Desktop-packages] [Bug 1565667] Re: When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This was

Running "sudo xdiagnose" provided useful results, showing that the retrievel of EDID information fails: [26303.206855] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* too many voltage retries, give up [26303.528370] usb 3-3.1: new SuperSpeed USB device number 6 using xhci_hcd [26303.75

[Desktop-packages] [Bug 1566164] [NEW] When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This wa

*** This bug is a duplicate of bug 1565667 *** https://bugs.launchpad.net/bugs/1565667 Public bug reported: This is data from after the suspend, with the problem apparent. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-16.32-gene

[Desktop-packages] [Bug 1565667] [NEW] When returning from suspend, my external Apple monitor is not detected, and nothing I do seem to enable it. Rebooting makes everything work as it should. This wa

Public bug reported: After rebooting, xrandr --prop gives me: DP2-1 connected primary 1920x1200+0+0 (normal left inverted right x axis y axis) 495mm x 310mm EDID: 000006101c928cb90102 1112010380311f782efd45a3574a9e25 135054