[Ubuntu-x-swat] [Bug 214786] Re: Apple USB ISO keyboard has incorrectly swapped keys
I'm having this issue with a Spanish USB Mac keyboard. Is it really so difficult to detect when you have a Mac keyboard connected and/or disconnected? Can't anything be done with hotplug, udev, etc. ? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/214786 Title: Apple USB ISO keyboard has incorrectly swapped keys To manage notifications about this bug go to: https://bugs.launchpad.net/mactel-support/+bug/214786/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
>>1. When the touchpad works by setting pin's direction=out, you could
see lots of "no data" message ("IRQ triggered but there's no data")
keeping popping up after moving your finger away from the touchpad, am I
correct?
> no, wrong. when run : echo out > direction,
> dmesg say :
> [ 133.854926] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but
> there's no data
> only one time,
> then my touchpad can work.
> no keeping popping up after moving your finger away from the touchpad.
This is something quite unexpected. When the finger is away from the
toucpad, is there any output from `sudo hid-recorder`? For my laptop,
the same HId report will be repeatedly received by hid-recorder because
amd_gpio_irq_handler is called repeatedly. If amd_gpio_irq_handler is
not called when you don't use the touchpad, then "echo out > direction"
is really a solution and your guess that amd-pinctrl has incorrect
configuration the direction is absolutely right.
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Coiby Xu (coiby)
>1. When the touchpad works by setting pin's direction=out, you could see lots
>of "no data" message ("IRQ triggered but there's no data") keeping popping up
>after moving your finger away from the touchpad, am I correct?
no, wrong. when run : echo out > direction,
dmesg say :
[ 133.854926] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but
there's no data
only one time,
then my touchpad can work.
no keeping popping up after moving your finger away from the touchpad.
it's only one line .
>2. When pin's direction=out, does only one new "no data" message or multiple
>ones appear on the screen when you toggle the pin value?
when run : echo out > direction,
dmesg show one time no data msg.no more,
then change pin value,to 0 or to 1,
no msg output.
but ,when value = 1, touchpad not work,
when value =0,touchpad can work.
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1888558] Re: VLC is using up to 2 GB of RAM just to play a regular 720px HD video
[Expired for mesa (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mesa (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1888558 Title: VLC is using up to 2 GB of RAM just to play a regular 720px HD video To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1888558/+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 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)
[Expired for xorg-server (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Expired -- 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1890436] Re: VGA signal is ghosted and stretched (Intel® HD Graphics 2500)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1890436 Title: VGA signal is ghosted and stretched (Intel® HD Graphics 2500) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890436/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@wangjun Thank you for doing this experiment!
1. When the touchpad works by setting pin's direction=out, you could see
lots of "no data" message ("IRQ triggered but there's no data") keeping
popping up after moving your finger away from the touchpad, am I
correct?
2. When pin's direction=out, does only one new "no data" message or
multiple ones appear on the screen when you toggle the pin value?
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1898569] Re: laptop screen blank after reboot
Since this is an old release I suggest the fastest way forward here will be for you to install Ubuntu 20.04.1 instead. It's better supported and has more fixes than 18.04. https://ubuntu.com/download/desktop ** Tags added: dual-gpu hybrid nvidia ** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu) ** Also affects: nvidia-graphics-drivers-450 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - laptop screen blank after reboot + [modeset + nvidia] Laptop screen blank after reboot ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [modeset + nvidia] Laptop screen blank after reboot + [modeset + nvidia + lightdm] Laptop screen blank after reboot -- 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/1898569 Title: [modeset + nvidia + lightdm] Laptop screen blank after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1898569/+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 1898563] Re: Xorg freeze
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. ** Tags added: radeon ** Summary changed: - Xorg freeze + [radeon] Screen freeze ** Package changed: xorg (Ubuntu) => ubuntu ** Changed in: ubuntu Status: New => Incomplete -- 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/1898563 Title: [radeon] Screen freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1898563/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
I don't have that pc at hand right now so i can't check for the version -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
Try this, $ git branch -v -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
(sory for the many posts, i'm realizing things as times goes by) Now that i think of it i don't know what i did when $ git branch main origin/main it didn't returned errors so i don't know if i copied or renamed a branch git branch (-m | -M) [] is supposed to rename for example was i supposed to choose one of the options between origin/main ? idk or was it a path? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
Also many more resolutions options showed than before -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
Also checked Xorg.0.log to find that openchrome module was loaded I don't have that pc at hand right now so i can't check for the version number -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
I did everything you told me on your last instructions including $ git branch main origin/main $ git checkout main -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1897992] Re: No VGA video signal after installing pkg and rebooting
How did you manage to fix the issue? Did you install the latest development tip or did you manage to get the older version (Version 0.6.0) working? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-openchrome in Ubuntu. https://bugs.launchpad.net/bugs/1897992 Title: No VGA video signal after installing pkg and rebooting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-openchrome/+bug/1897992/+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 1898569] [NEW] laptop screen blank after reboot
Public bug reported: connected to external monitor. After a reboot the laptop screen is blank. Can't find a consistent way to get it back. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-48.52~18.04.1-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.capabilities.gpu0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/gpu0' .proc.driver.nvidia.capabilities.mig: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/capabilities/mig' .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 450.66 Wed Aug 12 19:42:48 UTC 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.17 Architecture: amd64 CompositorRunning: None Date: Mon Oct 5 15:50:47 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 450.66, 5.4.0-47-generic, x86_64: installed nvidia, 450.66, 5.4.0-48-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11c9] Subsystem: Micro-Star International Co., Ltd. [MSI] GP107M [GeForce GTX 1050 Mobile] [1462:11c9] InstallationDate: Installed on 2020-06-03 (123 days ago) InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203.1) MachineType: Micro-Star International Co., Ltd. GP72 7RD ProcEnviron: LANG=en_GB.UTF-8 SHELL=/bin/bash TERM=xterm-256color LANGUAGE=en_GB:en PATH=(custom, no user) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=/dev/mapper/ubuntu--vg-root ro nouveau.modeset=0 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E1799IMS.324 dmi.board.asset.tag: Default string dmi.board.name: MS-1799 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE1799IMS.324:bd03/23/2018:svnMicro-StarInternationalCo.,Ltd.:pnGP727RD:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1799:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A: dmi.product.family: GP dmi.product.name: GP72 7RD dmi.product.sku: 1799.3 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Mon Oct 5 15:30:42 2020 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1898569 Title: laptop screen blank after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898569/+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 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)
*** This bug is a duplicate of bug 214786 *** https://bugs.launchpad.net/bugs/214786 ** This bug has been marked a duplicate of bug 214786 Apple USB ISO keyboard has incorrectly swapped keys -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1886215 Title: Strange Apple keyboard behaviour (Spanish layout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+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 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)
*** This bug is a duplicate of bug 214786 *** https://bugs.launchpad.net/bugs/214786 Check out this Ask Ubuntu question for a way to handle Apple devices: https://askubuntu.com/q/843590 But please note, though, that such an entry in /etc/default/keyboard would switch the keys for your built-in keyboard too. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1886215 Title: Strange Apple keyboard behaviour (Spanish layout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+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 1886215] Re: Strange Apple keyboard behaviour (Spanish layout)
just guessing a package to associate this report with ** Package changed: ubuntu => xkeyboard-config (Ubuntu) -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config in Ubuntu. https://bugs.launchpad.net/bugs/1886215 Title: Strange Apple keyboard behaviour (Spanish layout) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1886215/+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 1886215] [NEW] Strange Apple keyboard behaviour (Spanish layout)
You have been subscribed to a public bug: I have an Apple Aluminium keyboard with Spanish/Castillian layout connected to my laptop: lsusb output: ... Bus 002 Device 006: ID 05ac:0221 Apple, Inc. Aluminum Keyboard (ISO) Bus 002 Device 004: ID 05ac:1006 Apple, Inc. Hub in Aluminum Keyboard ... I'm running Focal: cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" I want to enable the regular Spanish keyboard layout for the laptop's internal keyboard and the Macintosh layout for the Apple Aluminum keyboard. When I press the key to the left of 'z' which should be '<' and I have the layout, I see the right key being highlighted but I get 'º' on the terminal Likewise, when I press the key to the left of '1', I see it correctly highlighted but I get a '<' instead of a 'º' ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: aluminum focal keyboard macintosh -- Strange Apple keyboard behaviour (Spanish layout) https://bugs.launchpad.net/bugs/1886215 You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xkeyboard-config 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 1898563] [NEW] Xorg freeze
Public bug reported: Every day I have the same problem - my pc (system updated to Ubuntu 20.04) screen (internet browser Brave) when I work in internet pages simply frozen, mouse and keyboard stopped working , I tried command (Crl+Alt+Del) but it did not help, and I have manually to reboot the pc (pressing the button). By the way - it happened only after I upgraded to Ubuntu 20.04 - when I was on Ubuntu 18 I've never seen such problems. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 17:01:42 2020 DistUpgraded: 2020-10-01 17:22:40,616 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, if not too technical GpuHangFrequency: Very infrequently GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1002:6771] (prog-if 00 [VGA controller]) Subsystem: Dell Caicos XTX [Radeon HD 8490 / R5 235X OEM] [1028:2120] InstallationDate: Installed on 2020-04-27 (161 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=d70267c9-bd6d-4ed6-a98a-085d6f7fb757 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-10-01 (3 days ago) dmi.bios.date: 07/31/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P3.30 dmi.board.name: A320M-HDV R4.0 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP3.30:bd07/31/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnA320M-HDVR4.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.4 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: Sat Jun 6 18:08:10 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4.1~16.04.2 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal freeze 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/1898563 Title: Xorg freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1898563/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
one mistake in #165, ```but there's no data``` is some copy/past err. it's not the output. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
sorry for #159, the first c program ,i missed the parameter when i run it. now test it again. reboot then ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio [root@localhost gpio]# ls export gpiochip256 unexport [root@localhost gpio]# echo 386 > export [root@localhost gpio]# ls export gpio386 gpiochip256 unexport [root@localhost gpio]# cd gpio386/ [root@localhost gpio386]# ls active_low device direction edge power subsystem uevent value [root@localhost gpio386]# ``` the window 1: ``` [root@localhost gpio386]# cd /src [root@localhost src]# cd 1 [root@localhost 1]# ls main.c test [root@localhost 1]# ./test 100 Status:: Success Status:: Success Interval: 100507.7 (real), 100 (set) [root@localhost 1]# ./test 200 Status:: Success Status:: Success Interval: -798786.2 (real), 200 (set) [root@localhost 1]# ./test 300 Status:: Success Status:: Success Interval: -698798.6 (real), 300 (set) [root@localhost 1]# ./test 400 Status:: Success Status:: Success Interval: -598783.9 (real), 400 (set) [root@localhost 1]# ./test 500 Status:: Success Status:: Success Interval: -498759.5 (real), 500 (set) [root@localhost 1]# ./test 600 Status:: Success Status:: Success Interval: 600225.3 (real), 600 (set) [root@localhost 1]# ./test 700 Status:: Success Status:: Success Interval: 700192.4 (real), 700 (set) [root@localhost 1]# ./test 800 Status:: Success Status:: Success Interval: -198836.5 (real), 800 (set) [root@localhost 1]# ./test 900 Status:: Success Status:: Success Interval: -98799.5 (real), 900 (set) [root@localhost 1]# ./test 1000 Status:: Success Status:: Success Interval: 1167.8 (real), 1000 (set) [root@localhost 1]# ./test 1100 Status:: Success Status:: Success Interval: 101167.2 (real), 1100 (set) [root@localhost 1]# ./test 1200 Status:: Success Status:: Success Interval: -797821.1 (real), 1200 (set) [root@localhost 1]# ./test 1300 Status:: Success Status:: Success Interval: 301202.4 (real), 1300 (set) [root@localhost 1]# ./test 1400 Status:: Success Status:: Success Interval: 401208.4 (real), 1400 (set) [root@localhost 1]# ./test 1500 Status:: Success Status:: Success Interval: -497844.3 (real), 1500 (set) [root@localhost 1]# ./test 1600 Status:: Success Status:: Success Interval: -397751.6 (real), 1600 (set) [root@localhost 1]# ./test 1700 Status:: Success Status:: Success Interval: 701201.9 (real), 1700 (set) [root@localhost 1]# ./test 1800 Status:: Success Status:: Success Interval: -197768.8 (real), 1800 (set) [root@localhost 1]# ./test 1900 Status:: Success Status:: Success Interval: -97834.9 (real), 1900 (set) [root@localhost 1]# ``` window 2: ``` [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: [ 416.150765] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` the output only once. that 's all. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
test the second c program with derection changed to :out window 1: ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio/ [root@localhost gpio]# ls export gpiochip256 unexport [root@localhost gpio]# echo 386 > export [root@localhost gpio]# ls export gpio386 gpiochip256 unexport [root@localhost gpio]# cd gpio386/ [root@localhost gpio386]# ls active_low device direction edge power subsystem uevent value [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# cd /src [root@localhost src]# cd 2 [root@localhost 2]# ls fire_touchpad_pin_irq fire_touchpad_pin_irq.c [root@localhost 2]# ./fire_touchpad_pin_irq 100 Status:: Success Status:: Success Interval: -898783.6 (real), 100 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 200 Status:: Success Status:: Success Interval: 200220.4 (real), 200 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 300 Status:: Success Status:: Success Interval: -698794.8 (real), 300 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 400 Status:: Success Status:: Success Interval: 400186.2 (real), 400 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 500 Status:: Success Status:: Success Interval: 500237.5 (real), 500 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 600 Status:: Success Status:: Success Interval: 600167.4 (real), 600 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 700 Status:: Success Status:: Success Interval: -298777.3 (real), 700 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 800 Status:: Success Status:: Success Interval: -198787.9 (real), 800 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 900 Status:: Success Status:: Success Interval: -98820.3 (real), 900 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1000 Status:: Success Status:: Success Interval: 1178.9 (real), 1000 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1100 Status:: Success Status:: Success Interval: -897780.3 (real), 1100 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1200 Status:: Success Status:: Success Interval: 201147.0 (real), 1200 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1300 Status:: Success Status:: Success Interval: -697760.0 (real), 1300 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1400 Status:: Success Status:: Success Interval: 401213.1 (real), 1400 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1500 Status:: Success Status:: Success Interval: 501211.2 (real), 1500 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1600 Status:: Success Status:: Success Interval: -397783.9 (real), 1600 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1700 Status:: Success Status:: Success Interval: -297852.3 (real), 1700 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 1200 Status:: Success Status:: Success Interval: -797757.7 (real), 1200 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 2000 Status:: Success Status:: Success Interval: 2219.5 (real), 2000 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 3000 Status:: Success Status:: Success Interval: 3149.3 (real), 3000 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 5000 Status:: Success Status:: Success Interval: 5186.0 (real), 5000 (set) [root@localhost 2]# ``` window 2: ``` [ra@localhost ~]$ su Password: [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: [ 119.911674] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` only one line output,and it out when i change the direction. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
test the second c program: i reboot, it's means the derection is :in windows 1: ``` [ra@localhost 2]$ su Password: [root@localhost 2]# ls fire_touchpad_pin_irq fire_touchpad_pin_irq.c [root@localhost 2]# ./fire_touchpad_pin_irq 100 Status:: Operation not permitted Status:: Operation not permitted Interval: 100514.3 (real), 100 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 200 Status:: Operation not permitted Status:: Operation not permitted Interval: 200497.8 (real), 200 (set) [root@localhost 2]# ./fire_touchpad_pin_irq 300 Status:: Operation not permitted Status:: Operation not permitted Interval: 300504.7 (real), 300 (set) [root@localhost 2]# ``` and window 1: ``` [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: ``` window 1 no output. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
sorry , two mistakes in # 162 and window 1: ==> and window 2: window 1 no output. ==> window 2 no output. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
test for script 2 ,with changed direction to out before test: ``` a. Don't put your finger on the touchpad b. Open a terminal window and run `sudo dmesg -W` c. In another terminal, "cd /sys/class/gpio/gpio386" e. "echo 1 > value" and see if the following dmesg output will keeping popping up in the previous terminal window ``` [ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` d. Then "echo 0 > value", now the dmesg output in step 3 should stop popping up f. Repeat step e-d for around 5 times ``` test env is : the direction change to :out and then run the script. windows 1: ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio [root@localhost gpio]# echo 386 >export [root@localhost gpio]# cd gpio386/ [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo 1 > value [root@localhost gpio386]# echo 0 > value [root@localhost gpio386]# echo 1 > value [root@localhost gpio386]# echo 0 > value [root@localhost gpio386]# echo 1 > value [root@localhost gpio386]# echo 0 > value [root@localhost gpio386]# echo 1 > value [root@localhost gpio386]# echo 0 > value [root@localhost gpio386]# echo 1 > value [root@localhost gpio386]# echo 0 > value [root@localhost gpio386]# ``` windows 2: ``` [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: [ 144.238931] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` the output :i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data is out after i run echo out > direction. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
test for script 2: ``` a. Don't put your finger on the touchpad b. Open a terminal window and run `sudo dmesg -W` c. In another terminal, "cd /sys/class/gpio/gpio386" e. "echo 1 > value" and see if the following dmesg output will keeping popping up in the previous terminal window ``` [ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` d. Then "echo 0 > value", now the dmesg output in step 3 should stop popping up f. Repeat step e-d for around 5 times ``` test env is : the direction is default : in, not changed and then run the script. windows 1: ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio/gpio386 [root@localhost gpio386]# echo 1 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 0 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 1 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 0 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 1 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 0 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 1 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 0 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 1 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# echo 0 > value bash: echo: write error: Operation not permitted [root@localhost gpio386]# ``` windows 2: ``` [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: ``` windows 2 has no output. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
and after the test,i rerun : echo in > direction my touchpad can work. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
sorry for #157, `in` should be `out` and after the test,i rerun : echo out > direction my touchpad can work. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
test the script: ``` a. Don't put your finger on the touchpad b. Open a terminal window and run `sudo dmesg -W` c. In another terminal, "cd /sys/class/gpio/gpio386" e. "echo out > direction" and see if the following dmesg output will keeping popping out in the previous terminal window ``` [ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` d. Then "echo in > direction", now the dmesg output in step 3 should stop popping out. f. Repeat step e-d for around 5 times ``` window 1: ``` [ra@localhost ~]$ su Password: [root@localhost ra]# cd /sys/class/gpio/ [root@localhost gpio]# echo 386 > export [root@localhost gpio]# ls export gpio386 gpiochip256 unexport [root@localhost gpio]# cd /sys/class/gpio/gpio386 [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo in > direction [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo in > direction [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo in > direction [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo in > direction [root@localhost gpio386]# echo out > direction [root@localhost gpio386]# echo in > direction [root@localhost gpio386]# ``` window 2: ``` [ra@localhost ~]$ sudo dmesg -W [ 191.989163] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered but there's no data ``` it's only out one line on first it run echo out > direction. during test ,no figure touch the touchpad. -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
first c program, has error, window 1 ``` [ra@localhost 1]$ sudo ./test [sudo] password for ra: Segmentation fault [ra@localhost 1]$ ``` windows 2 ``` [ra@localhost ~]$ sudo dmesg -W [sudo] password for ra: [ 545.297119] test[3424]: segfault at 0 ip 7f679289151c sp 7ffc4ea14900 error 4 in libc-2.32.so[7f6792875000+14f000] [ 545.297127] Code: 41 54 45 31 e4 55 53 48 83 ec 28 48 89 74 24 08 85 c9 0f 85 ce 02 00 00 83 ff 01 0f 84 8d 01 00 00 83 ff 24 0f 87 84 01 00 00 <49> 0f be 55 00 49 8b 48 68 4c 89 eb 48 89 d0 f6 44 51 01 20 74 19 ``` -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@Coiby Xu (coiby) wait a moment ,i rebuild a clean kernel ,then i test it . -- 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/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 To manage notifications about this bug go to: https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
@wangjun
Thank you for sharing the results and investigating this touchpad issue!
One thing confuses me is for the ELAN touchpad, no single interrupt
fires when you put finger on the touchpad while for the Synaptics
touchpad, you still see interrupts firing but with a very rate of ~7Hz.
Judging from the ACPI DSDT tables, different variants of this laptop
model share the same GPIO chip. So this difference is unexpected.
Understanding the difference may help us why the GPIO interrupt
controller is malfunctioning.
Based on your results, I guess the ELAN touchpad somehow de-asserts its
interrupt line connected to the GPIO pin. Could you further do the
following experiment?
The following C program is to let GPIO controller quickly generate some
interrupts then disable the firing of interrupts by toggling pin#130's
direction with an time interval (ms). For the Synaptics touchpad, There
is no interrupt firing unless internal > 120ms. So somehow the GPIO
controller can only generate interrupt when its pin holding the signal
for enough time. My hypothesis is the GPIO is not setup properly so it
stays in a idle state or it's clock frequency is too small (so I don't
think the touchpad issue is caused by mis-configuration of the direction
of the pin). I want to see if the result from the ELAN touchpad would
also support this hypothesis.
1. Find out the reliable way to trigger an interrupt which is crucial for this
experiment.
You told me there will be interrupt firing by simply setting the
pin's direction to "out". You can check it's reliable by following the
steps
a. Don't put your finger on the touchpad
b. Open a terminal window and run `sudo dmesg -W`
c. In another terminal, "cd /sys/class/gpio/gpio386"
e. "echo out > direction" and see if the following dmesg output will
keeping popping out in the previous terminal window
```
[ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered
but there's no data
```
d. Then "echo in > direction", now the dmesg output in step 3 should stop
popping out.
f. Repeat step e-d for around 5 times
If you are certain now, use the following C Program,
```c
#include
#include
#include
#include
#include
void write_to_pin130(char *d, size_t size)
{
int fd;
fd = open("/sys/class/gpio/gpio386/direction", O_WRONLY);
write(fd, d, size);
perror("Status:");
close(fd);
}
void toggle_pin130(int interval_ms)
{
struct timespec ts, ts1;
write_to_pin130("out", 3);
clock_gettime(CLOCK_MONOTONIC, );
usleep(interval_ms*1000);
write_to_pin130("in", 2);
clock_gettime(CLOCK_MONOTONIC, );
printf("Interval: %.1f (real), %d (set)\n",
(ts1.tv_sec-ts.tv_sec)*1000.0+(ts1.tv_nsec-ts.tv_nsec)/1000.0, interval_ms);
}
int main(int argc, char **argv)
{
struct timespec ts;
int interval_ms = atoi(argv[1]);
toggle_pin130(interval_ms);
}
```
For me, it seems it's reliable to toggle the value to trigger a interrupt. You
can follow similar steps to test it,
a. Don't put your finger on the touchpad
b. Open a terminal window and run `sudo dmesg -W`
c. In another terminal, "cd /sys/class/gpio/gpio386"
e. "echo 1 > value" and see if the following dmesg output will keeping
popping up in the previous terminal window
```
[ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ triggered
but there's no data
```
d. Then "echo 0 > value", now the dmesg output in step 3 should stop
popping up
f. Repeat step e-d for around 5 times
If the results are positive, use the following C program,
```
#include
#include
#include
#include
#include
void write_to_pin130(char *d)
{
int fd;
fd = open("/sys/class/gpio/gpio386/value", O_WRONLY);
write(fd, d, 1);
perror("Status:");
close(fd);
}
void toggle_pin130(int interval_ms)
{
struct timespec ts, ts1;
char d = '0';
write_to_pin130();
clock_gettime(CLOCK_MONOTONIC, );
usleep(interval_ms*1000);
d = '1';
write_to_pin130();
clock_gettime(CLOCK_MONOTONIC, );
printf("Interval: %.1f (real), %d (set)\n",
(ts1.tv_sec-ts.tv_sec)*1000.0+(ts1.tv_nsec-ts.tv_nsec)/1000.0, interval_ms);
}
int main(int argc, char **argv)
{
struct timespec ts;
int interval_ms = atoi(argv[1]);
toggle_pin130(interval_ms);
}
```
2. Build (you can simply run `make fire_touchpad_pin_irq.c`) and run it as a
root user
$ sudo ./fire_touchpad_pin_irq N
N is the time interval in ms. You may start with 100 and keep
increasing N it until you see a couple of messages like follows pop up,
[ 138.233653] i2c_hid i2c-MSFT0001:00: i2c_hid_get_input: IRQ
triggered but there's no data
With larger N, you will see more messages popping up one time.
--
You received this bug notification because you are a member of
[Ubuntu-x-swat] [Bug 1820832] Re: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz
dreamcat4, Ubuntu 19.10 is not supported. It reached end of life on July 17, 2020. This is a bug/design feature of Xorg graphics drivers like Nvidia and AMD's. You can work around it either by explicitly configuring the driver to sync to the fastest monitor, or by enabling "TearFree" if available. For a more long term permanent solution, using GNOME Wayland sessions should never hit such a problem. But that also requires your graphics driver support Wayland sessions :( -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1820832 Title: [xorg] multiple monitors: limits the framerate of faster 120/144hz monitors to 60hz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1820832/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
struct acpi_gpio_info {
struct acpi_device *adev;
enum gpiod_flags flags;
bool gpioint;
int pin_config;
int polarity;
int triggering;
unsigned int quirks;
};
enum gpiod_flags {
GPIOD_ASIS = 0,
GPIOD_IN= GPIOD_FLAGS_BIT_DIR_SET,
GPIOD_OUT_LOW = GPIOD_FLAGS_BIT_DIR_SET | GPIOD_FLAGS_BIT_DIR_OUT,
GPIOD_OUT_HIGH = GPIOD_FLAGS_BIT_DIR_SET | GPIOD_FLAGS_BIT_DIR_OUT |
GPIOD_FLAGS_BIT_DIR_VAL,
GPIOD_OUT_LOW_OPEN_DRAIN = GPIOD_OUT_LOW | GPIOD_FLAGS_BIT_OPEN_DRAIN,
GPIOD_OUT_HIGH_OPEN_DRAIN = GPIOD_OUT_HIGH | GPIOD_FLAGS_BIT_OPEN_DRAIN,
};
#define GPIOD_FLAGS_BIT_DIR_SET BIT(0)
#define GPIOD_FLAGS_BIT_DIR_OUT BIT(1)
#define GPIOD_FLAGS_BIT_DIR_VAL BIT(2)
#define GPIOD_FLAGS_BIT_OPEN_DRAIN BIT(3)
#define GPIOD_FLAGS_BIT_NONEXCLUSIVEBIT(4)
at end of the body of function gpiod_configure_flags:
/* Process flags */
if (dflags & GPIOD_FLAGS_BIT_DIR_OUT)
ret = gpiod_direction_output(desc,
!!(dflags & GPIOD_FLAGS_BIT_DIR_VAL));
else
ret = gpiod_direction_input(desc);
return ret;
}
if miss config,
the default value is 0, it will be GPIOD_ASIS,
then in gpiod_configure_flags ,
it will call gpiod_direction_input .
are all the above right ?
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
according to the above analysis, error is happen with the direction is :
in
i found the function to set the direction of gpio pin to in:
amd_gpio_direction_input,
and add some pr_err and dump_stack() to the function ,
then dmesg out put like :
[1.545190] amd_gpio_set_config
gpio_chip->label:AMDI0030:00,offset:130,config:278
[1.545191] amd_gpio_direction_input gpio_chip->label:AMDI0030:00,offset:130
=amd_gpio_direction_input dump_stack()=
[1.545194] CPU: 12 PID: 264 Comm: kworker/12:4 Not tainted
5.8.13-303.fc33.x86_64 #1
[1.545194] Hardware name: LENOVO 82B6/LNVNB161216, BIOS EUCN26WW 08/19/2020
[1.545197] Workqueue: events deferred_probe_work_func
[1.545198] Call Trace:
[1.545203] dump_stack+0x6b/0x88
[1.545205] amd_gpio_direction_input+0x57/0x60 [pinctrl_amd]
[1.545206] gpiod_direction_input+0x5b/0x170
[1.545208] acpi_dev_gpio_irq_get+0x111/0x1b6
[1.545209] ? i2c_acpi_find_adapter_by_handle+0x30/0x30
[1.545210] i2c_acpi_get_irq+0x81/0x90
[1.545212] i2c_device_probe+0x24a/0x280
[1.545213] really_probe+0x160/0x400
[1.545214] driver_probe_device+0xe1/0x150
[1.545215] ? driver_allows_async_probing+0x50/0x50
[1.545216] bus_for_each_drv+0x6a/0xa0
[1.545217] __device_attach+0xb4/0x1b0
[1.545218] bus_probe_device+0x8e/0xa0
[1.545219] deferred_probe_work_func+0x77/0xc0
[1.545220] process_one_work+0x1b4/0x370
[1.545221] worker_thread+0x53/0x3e0
[1.545222] ? process_one_work+0x370/0x370
[1.545223] kthread+0x11b/0x140
[1.545224] ? __kthread_bind_mask+0x60/0x60
[1.545226] ret_from_fork+0x22/0x30
then i found the functions
acpi_dev_gpio_irq_get
in in file : drivers/gpio/gpiolib-acpi.c, line 927 (as a function)
and it's comment say:
```
/**
* acpi_dev_gpio_irq_get() - Find GpioInt and translate it to Linux IRQ number
* @adev: pointer to a ACPI device to get IRQ from
* @index: index of GpioInt resource (starting from %0)
*
* If the device has one or more GpioInt resources, this function can be
* used to translate from the GPIO offset in the resource to the Linux IRQ
* number.
*
* The function is idempotent, though each time it runs it will configure GPIO
* pin direction according to the flags in GpioInt resource.
*
* Return: Linux IRQ number (> %0) on success, negative errno on failure.
*/
int acpi_dev_gpio_irq_get(struct acpi_device *adev, int index)
{
```
each time it runs it will configure GPIO pin direction according to the
flags in GpioInt resource.
in it's body ,by call function gpiod_configure_flags (in
/drivers/gpio/gpiolib.c)
it call the function gpiod_direction_input.
so the direction become to :input or in
the problem may be in two places:
1. lenovo 's default value in bios or dsdt is : input or in,or missing . but on
windows ,it's ok,so ,may be not here.
2. in linux kernel,the default value of the type for gpio pin 's direction ,is
:input or in
--
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/1887190
Title:
MSFT Touchpad not working on Lenovo Legion-5 15ARH05
To manage notifications about this bug go to:
https://bugs.launchpad.net/pop-os/+bug/1887190/+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 1898516] [NEW] The pad of my pc is not detected anymore
Public bug reported: After an update the pad of my computer is not working anymore, even xinput or lsusb does not show my pad. everything worked fine before that ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xinput 1.6.3-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 09:19:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1050] InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 010: ID 13d3:3423 IMC Networks Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X302UA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-48-generic root=UUID=b72b0ba2-1bc0-4915-93c1-a5a954b4ca0f ro quiet splash vt.handoff=7 SourcePackage: xinput UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X302UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X302UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX302UA.206:bd02/22/2016:svnASUSTeKCOMPUTERINC.:pnX302UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX302UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X302UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER 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: xinput (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ubuntu ** Description changed: After an update the pad of my computer is not working anymore, even - xinput or lsusb dos not show my pad. everything worked fine before that + xinput or lsusb does not show my pad. everything worked fine before that ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xinput 1.6.3-1 ProcVersionSignature: Ubuntu 5.4.0-48.52-generic 5.4.60 Uname: Linux 5.4.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission non accordée: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Oct 5 09:19:08 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu GraphicsCard: - Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) -Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1050] + Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) + Subsystem: ASUSTeK Computer Inc. Skylake GT2 [HD Graphics 520] [1043:1050] InstallationDate: Installed on 2020-04-26 (161 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 010: ID 13d3:3423 IMC Networks - Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 010: ID 13d3:3423 IMC Networks + Bus 001 Device 003: ID 04f2:b52b Chicony Electronics Co., Ltd USB2.0 VGA UVC WebCam + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. X302UA ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_FR.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= +
