[Ubuntu-x-swat] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list-props 13" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369255/+files/xinput--list-props13.txt ** Description changed: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. - * "fingers": single-finger tap for a click, two-finger tap for a right click, - three-finger tap for a middle click - * "areas": tap in the lower right corner for a right click, tap in the upper - right corner for a middle click + * "fingers": single-finger tap for a click, two-finger tap for a right + click, three-finger tap for a middle click + * "areas": tap in the lower right corner for a right click, tap in the + upper right corner for a middle click After running the following command: - gsettings set org.gnome.desktop.peripherals.touchpad click-method - "'areas'" + gsettings set org.gnome.desktop.peripherals.touchpad click-method \ + "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: - cat /proc/bus/input/devices - xinput --list - xinput --list-props 13 # where 13 is the touchpad's ID + cat /proc/bus/input/devices + xinput --list + xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1877798] [NEW] The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
Public bug reported: I'm trying to switch from the "fingers" click-method to the "areas" click-method, because tapping with three fingers is awkward and I find that my three-fingers taps are rarely registered as such. * "fingers": single-finger tap for a click, two-finger tap for a right click, three-finger tap for a middle click * "areas": tap in the lower right corner for a right click, tap in the upper right corner for a middle click After running the following command: gsettings set org.gnome.desktop.peripherals.touchpad click-method \ "'areas'" I can verify with gsettings get... that the click-method is now "areas", however tapping in the lower/upper right corners of the touchpad does not elicit the expected right/middle clicks, whereas tapping with two fingers elicits a right click. This remains the case even after rebooting the computer. It's as if the click-method was ignored and defaulted to "fingers". I couldn't find any similar bug reports and don't know how to investigate this problem further. I assume this problem is specific to my hardware, otherwise it would have been noticed already. I attach the output of the following commands: cat /proc/bus/input/devices xinput --list xinput --list-props 13 # where 13 is the touchpad's ID Should I report this issue to upstream libinput (www.freedesktop.org/wiki/Software/libinput)? Or could this be something to do with GNOME instead? Using Ubuntu 20.04 with libinput 1.15.5-1 and xserver-xorg-input- libinput 0.29.0-1. ** Affects: xserver-xorg-input-libinput (Ubuntu) Importance: Undecided Status: New ** Attachment added: "cat /proc/bus/input/devices" https://bugs.launchpad.net/bugs/1877798/+attachment/5369253/+files/devices.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1877798] Re: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop
** Attachment added: "xinput --list" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+attachment/5369254/+files/xinput--list.txt -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1877798 Title: The "areas" click-method doesn't work with "SynPS/2 Synaptics TouchPad" on "Clevo N141ZU" laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1877798/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1847829] Re: Three finger tap to middle click stopped working
Hi Rip, > Three fingers results in a right-click now for whatever > reason. I have the appropriate settings enabled in KDE > (I haven't changed them). > > Middle click works sometimes after restarting the device > via xinput, but this is very rare. If your three-finger taps are inconsistent (sometimes registered as left clicks, sometimes as right clicks, sometimes as middle clicks), it could be related to the following upstream issues: https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 I am also affected by inconsistent three-finger taps (most often registered as right clicks) on a "SynPS/2 Synaptics TouchPad". ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #361 https://gitlab.freedesktop.org/libinput/libinput/-/issues/361 ** Bug watch added: gitlab.freedesktop.org/libinput/libinput/-/issues #473 https://gitlab.freedesktop.org/libinput/libinput/-/issues/473 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-libinput in Ubuntu. https://bugs.launchpad.net/bugs/1847829 Title: Three finger tap to middle click stopped working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-libinput/+bug/1847829/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1765832] Re: Two finger scrolling not working after suspend
*** This bug is a duplicate of bug 1722478 *** https://bugs.launchpad.net/bugs/1722478 thrantir's solution works for me in 20.04, is there a way to make this automatic on wake? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1765832 Title: Two finger scrolling not working after suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1765832/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1846374] Re: Having a video playing/paused when switched to another user generates gigabytes of error logs
I also experienced the same issue using Ubuntu 18.04 and VLC 3.0.8 version. (Nvidia-driver-435) I was not able to reproduce the same issue with another media player. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1846374 Title: Having a video playing/paused when switched to another user generates gigabytes of error logs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-418/+bug/1846374/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1876797] Re: Numerous issues
That would be great, but even ubuntu-bug is having problems. It will sit for hours not doing anything. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1876797 Title: Numerous issues To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1876797/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1877735] Re: Video playback is choppy
** Package changed: ubuntu => xorg (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1877735 Title: Video playback is choppy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1877735/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1877735] [NEW] Video playback is choppy
You have been subscribed to a public bug: After upgrade from 19.10 to 20.04 video playback is choppy ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a~dev-generic 5.4.30 Uname: Linux 5.4.0-7626-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat May 9 06:43:40 2020 DistUpgraded: 2020-05-08 18:55:15,812 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: System76, Inc. Wild Dog Performance ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-7626-generic root=UUID=6ce8ac8b-f6ef-47b4-9428-b35e00870dfa ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-05-08 (0 days ago) dmi.bios.date: 01/20/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0806 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: H87-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: System76, Inc. dmi.chassis.version: wilp10 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0806:bd01/20/2014:svnSystem76,Inc.:pnWildDogPerformance:pvrwilp10:rvnASUSTeKCOMPUTERINC.:rnH87-PLUS:rvrRevX.0x:cvnSystem76,Inc.:ct3:cvrwilp10: dmi.product.family: ASUS MB dmi.product.name: Wild Dog Performance dmi.product.sku: All dmi.product.version: wilp10 dmi.sys.vendor: System76, Inc. modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2014-05-27T19:28:01.524954 version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 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 xserver.bootTime: Thu Nov 9 16:56:44 2017 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.3-1ubuntu1.3 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal performance third-party-packages ubuntu -- Video playback is choppy https://bugs.launchpad.net/bugs/1877735 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xorg in Ubuntu. ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
[Ubuntu-x-swat] [Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
I can confirm this is still an issue. The odd part is, however, that I did not have this issue on 19.10 with the nvidia drivers from the ppa. Upgrading to 20.04 introduced this issue to me. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1845801/+subscriptions ___ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
