[Ubuntu-x-swat] [Bug 1696929] [NEW] Laptop touchpads are unresponsive (with hysteresis enabled by default)

2017-06-09 Thread Daniel van Vugt
Public bug reported: Some laptop touchpads are annoyingly unresponsive when the software implements any kind of hysteresis. This includes Lenovo X1 Carbon gen 4 and 5. Such devices have lower precision and higher lag in the touchpad hardware than you might expect, so need the software to not slow

[Ubuntu-x-swat] [Bug 1696929] Re: Laptop touchpads are unresponsive (with hysteresis enabled by default)

2017-06-09 Thread Daniel van Vugt
An interesting test is to move your finger around in small circles on the touchpad. If the hysteresis is too high then you will see the cursor move in a more square-like shape. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. h

[Ubuntu-x-swat] [Bug 1696929] Re: Laptop touchpads are unresponsive (with hysteresis enabled by default)

2017-06-09 Thread Daniel van Vugt
See also: https://bugs.freedesktop.org/show_bug.cgi?id=98839 https://bugs.freedesktop.org/show_bug.cgi?id=94986 Hmm, if blacklisting or writing custom configs is the solution then maybe this bug should be hardware-specific. ** Bug watch added: freedesktop.org Bugzilla #94986 https://bugs.freed

[Ubuntu-x-swat] [Bug 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

2017-06-09 Thread Julien SCORDIA
This bug affected me in Ubuntu 16.04 (using Xfce), and it was very annoying. I have installed Ubuntu 17.04 (Kernel 4.10): the problem seems to be solved, it did not appear in more than one month. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xo

[Ubuntu-x-swat] [Bug 1696929] Re: X1 Carbon gen4 and gen5 touchpads are unresponsive and laggy

2017-06-09 Thread Bug Watch Updater
** Changed in: libinput Status: Unknown => Confirmed ** Changed in: libinput Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libinput in Ubuntu. https://bugs.launchpad.net/bugs/1696929 Title: X1 Carbon

[Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
hi Danniel, This forwarded mail are from Huawei guy which to say "PCI_BRIDGE_CTL_VGA" are only used on X86 but not for AMR64. The English line was my translated for Chines text. thanks, Mao -- Forwarded message -- From: wanghuiqiang Date: 2017-06-09 13:38 GMT+08:00 Subject: 答复:

[Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
This 4.5.1 seems form "PCI-to-PCI Bridge Architecture Specification", the full document can be download from below link: https://cds.cern.ch/record/551427/files/cer-2308933.pdf -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https

Re: [Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
hi Danniel, This forwarded mail are from Huawei guy which to say "PCI_BRIDGE_CTL_VGA" are only used on X86 but not for AMR64. The English line was my translated for Chines text. thanks, Mao -- Forwarded message -- From: wanghuiqiang Date: 2017-06-09 13:38 GMT+08:00 Subject: 答复:

[Ubuntu-x-swat] [Bug 1691991] Re: Xorg Segmentation fault on Hisilicon D05 board (arm64)

2017-06-09 Thread Zhanglei Mao
This is mail thread we haved discussed about ARM to compliance for PCI standard as other platform for x86, powerpc, ia64 etc. They key point form Huawei guys are below: "这部分ARM应该不能遵循,因为VGA EN开辟的空间是给legacy的系统使用的,1M以下的空间划分是x86向前兼容性的做法,只有在CSM支持传统的系统才还这样做,在新的方案里能不用就不用,开辟IO空间对ARM来说更不合适,因为ARM在定义之初就没有IO这

[Ubuntu-x-swat] [Bug 1696903] Re: 3d hardware problem

2017-06-09 Thread Marc Deslauriers
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 privile

[Ubuntu-x-swat] [Bug 560571] Re: BUG: using smp_processor_id() in preemptible [00000000] code: Xorg/1157

2017-06-09 Thread fs
Hi there! A little bit late! SOLUTION: --- firegl_public.c.modified2017-06-09 16:41:29.334991812 +0200 +++ firegl_public.c 2017-06-08 18:25:25.835817920 +0200 @@ -4273,8 +4273,8 @@ { unsigned long orig_level; -orig_level = __get_cpu_var(kasExecutionLevel); -__get_cpu_var(

[Ubuntu-x-swat] [Bug 1686189] Re: External monitor connecting problem on Intel graphics card

2017-06-09 Thread Shay Perlstein
NVidia setup is also including a second intel card (for power saving mode), but yes I mainly try to use NVidia profile (kernel used to complain about the intel card just like it is in your case). Secondly not only 4.4.0-72-generic is working also 4.10.1-041001-generic does very good job. As for l

[Ubuntu-x-swat] [Bug 1697093] [NEW] Black Screen after boot.

2017-06-09 Thread Abhiroj
Public bug reported: Please bear with me as This is the last place to resolve the as I have tried different resources available for the problem already, but with no effect.Long story short, Ubuntu 16.04 was working fine for a long time but since recently, It is showing up the black screen after bo

[Ubuntu-x-swat] [Bug 1687981] Re: Backport packages for 16.04.3 HWE stack

2017-06-09 Thread Olcay Korkmaz
Hi, is llvm-toolchain-4.0 final release looks like it's rc1 llvm-toolchain-4.0_4.0.orig is not same as llvm-4.0.0.src from llvm.org clang version 4.0.0-1ubuntu1~16.04.1 (tags/RELEASE_400/rc1) Target: x86_64-pc-linux-gnu Thread model: posix InstalledDir: /usr/bin it make is trouble like when bui