[Ubuntu-x-swat] [Bug 2061886] Re: Under VMWare resolution does not change automaticaly
Initials I was wrong, the display does get adjusted but no bigger than 1920x1024. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-video-vmware in Ubuntu. https://bugs.launchpad.net/bugs/2061886 Title: Under VMWare resolution does not change automaticaly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-vmware/+bug/2061886/+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 2061886] [NEW] Under VMWare resolution does not change automaticaly
Public bug reported: When resizing a VMWare Workstation, under Ubuntu20 the resolution would change automaticaly. It does not in the Ubuntu 24 Beta. During installation I have enabled download of third party driver. I can see vmtoold running. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.8.0-22.22-generic 6.8.1 Uname: Linux 6.8.0-22-generic x86_64 ApportVersion: 2.28.0-0ubuntu1 Architecture: amd64 CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: XFCE Date: Tue Apr 16 14:03:39 2024 DistUpgraded: Fresh install DistroCodename: noble DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller]) Subsystem: VMware SVGA II Adapter [15ad:0405] InstallationDate: Installed on 2024-04-16 (0 days ago) InstallationMedia: Xubuntu 24.04 LTS "Noble Numbat" - Beta amd64 (20240410.1) Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: VMware, Inc. VMware7,1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.8.0-22-generic root=UUID=93447c69-bef1-4d4b-917b-41be1fbda0ea ro SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/11/2023 dmi.bios.vendor: VMware, Inc. dmi.bios.version: VMW71.00V.21100432.B64.2301110304 dmi.board.name: 440BX Desktop Reference Platform dmi.board.vendor: Intel Corporation dmi.board.version: None dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 1 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.modalias: dmi:bvnVMware,Inc.:bvrVMW71.00V.21100432.B64.2301110304:bd01/11/2023:svnVMware,Inc.:pnVMware7,1:pvrNone:rvnIntelCorporation:rn440BXDesktopReferencePlatform:rvrNone:cvnNoEnclosure:ct1:cvrN/A:sku: dmi.product.name: VMware7,1 dmi.product.version: None dmi.sys.vendor: VMware, Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.120-2build1 version.libgl1-mesa-dri: libgl1-mesa-dri 24.0.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.11-2ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:22.0.0-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug noble resolution 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/2061886 Title: Under VMWare resolution does not change automaticaly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/2061886/+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 2058604] Re: Framework 16 disable touchpad when typing doesn't work
** Changed in: libinput (Ubuntu) Assignee: (unassigned) => Mario Limonciello (superm1) ** Changed in: libinput (Ubuntu) Status: New => Fix Committed -- 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/2058604 Title: Framework 16 disable touchpad when typing doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+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 2058604] [NEW] Framework 16 disable touchpad when typing doesn't work
Public bug reported: Due to the "input deck" the Framework 16 has a "USB" internal keyboard. This throws off heuristics for detection of keyboards to turn off when you select disable touchpad when typing. This is fixed in upstream libinput with the following change: https://gitlab.freedesktop.org/libinput/libinput/-/commit/566857bd98131009699c9ab6efc7af37afd43fd0 As that's not yet part of a release yet and it's a trivial change, could it be cherry picked for Ubuntu to give a better experience to Framework 16 users? ** Affects: libinput (Ubuntu) Importance: Undecided Status: New -- 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/2058604 Title: Framework 16 disable touchpad when typing doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/2058604/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
This is the same issue as https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573 Here is a commit that fixes the issue by changing default pre-emption policy since the kernel can't know about your mesa version. https://github.com/torvalds/linux/commit/d6a57588666301acd9d42d3b00d74240964f07f6 ** Changed in: linux (Ubuntu) Status: Won't Fix => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Won't Fix => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: Won't Fix => Confirmed -- 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/2043640 Title: amdgpu: GPU Recovery fails, frequent hangs To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043264] Re: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE)
Can you please try to reproduce using a mainline upstream build? https://kernel.ubuntu.com/mainline/v6.7-rc2/ If you can reproduce please share a new kernel log from a boot it occurs. -- 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/2043264 Title: [amdgpu] External monitor keeps blinking and not connected, with Kubuntu Linux (KDE) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2043264/+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 2044038] [NEW] package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: While updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.2 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) [1019:a55d] InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libx11 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: H310CH5-M2 dmi.board.vendor: EXO dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EXO dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629: dmi.product.family: Ready - Style dmi.product.name: Ready C2 - Style C2 dmi.product.sku: 3629 dmi.product.version: 1.0 dmi.sys.vendor: EXO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9 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: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/2044038 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/2044038/+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 2044040] [NEW] package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2
Public bug reported: bugs while updating ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libx11-6 2:1.6.9-2ubuntu1.6 ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.25 Architecture: amd64 CasperMD5CheckResult: skip CompositorRunning: None Date: Mon Nov 20 22:14:16 2023 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DuplicateSignature: package:libx11-6:2:1.6.9-2ubuntu1.2 Unpacking cups-filters-core-drivers (1.27.4-1ubuntu0.2) over (1.27.4-1) ... dpkg-deb: error: '/tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb' is not a Debian format archive dpkg: error processing archive /tmp/apt-dpkg-install-u8HHuH/037-libavahi-glib1_0.7-4ubuntu7.3_amd64.deb (--unpack): dpkg-deb --control subprocess returned error exit status 2 ErrorMessage: dpkg-deb --control subprocess returned error exit status 2 GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (rev 02) (prog-if 00 [VGA controller]) Subsystem: Elitegroup Computer Systems UHD Graphics 630 (Desktop 9 Series) [1019:a55d] InstallationDate: Installed on 2023-11-21 (0 days ago) InstallationMedia: Ubuntu 20.04.6 LTS "Focal Fossa" - Release amd64 (20230316) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1c4f:0034 SiGma Micro Usb Mouse Bus 001 Device 003: ID 1c4f:0002 SiGma Micro Keyboard TRACER Gamma Ivory Bus 001 Device 002: ID 046d:0825 Logitech, Inc. Webcam C270 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: EXO Ready C2 - Style C2 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-88-generic root=UUID=e1ccedca-0d59-4553-a2e6-566868da99ab ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.10 SourcePackage: libx11 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg-deb --control subprocess returned error exit status 2 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/02/2019 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.12 dmi.board.asset.tag: Default string dmi.board.name: H310CH5-M2 dmi.board.vendor: EXO dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: EXO dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.12:bd08/02/2019:br5.12:svnEXO:pnReadyC2-StyleC2:pvr1.0:rvnEXO:rnH310CH5-M2:rvr1.0:cvnEXO:ct3:cvr1.0:sku3629: dmi.product.family: Ready - Style dmi.product.name: Ready C2 - Style C2 dmi.product.sku: 3629 dmi.product.version: 1.0 dmi.sys.vendor: EXO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.9 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: libx11 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal need-duplicate-check ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libx11 in Ubuntu. https://bugs.launchpad.net/bugs/2044040 Title: package libx11-6 2:1.6.9-2ubuntu1.2 failed to install/upgrade: dpkg- deb --control subprocess returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/2044040/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
I've published a PPA here: https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please upgrade to that, drop the module parameter and see if things improve. # sudo add-apt-repository ppa:superm1/gitlab2971 # sudo apt upgrade # sudo reboot If they don't, you can remove the PPA using ppa-purge like this: # sudo ppa-purge ppa:superm1/gitlab2971 # sudo reboot -- 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/2043640 Title: amdgpu: GPU Recovery fails, frequent hangs To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2043640/+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 2043640] Re: amdgpu: GPU Recovery fails, frequent hangs
** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Package changed: mutter (Ubuntu) => mesa (Ubuntu) ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released ** Changed in: linux (Ubuntu) Status: New => Won't Fix ** Changed in: linux (Ubuntu Jammy) Status: New => Won't Fix ** Changed in: linux (Ubuntu Lunar) Status: New => Won't Fix ** Also affects: mesa via https://gitlab.freedesktop.org/drm/amd/-/issues/2971 Importance: Unknown Status: Unknown -- 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/2043640 Title: amdgpu: GPU Recovery fails, frequent hangs To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2043640/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
>From the upstream bug this is caused by PSR, so it's not a mesa issue. ** No longer affects: mesa (Ubuntu) ** No longer affects: mesa (Ubuntu Jammy) ** No longer affects: mesa (Ubuntu Lunar) ** No longer affects: mesa (Ubuntu Mantic) ** No longer affects: mesa (Ubuntu Noble) -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042054/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
It's unclear if this is a BIOS, mesa or kernel bug at this time, but it's certainly not an Xorg bug as it was reproduced in Wayland. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954 https://gitlab.freedesktop.org/drm/amd/-/issues/2954 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/2954 Importance: Unknown Status: Unknown ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-oem-6.5 (Ubuntu) Status: New => Invalid ** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Changed in: linux-oem-6.5 (Ubuntu Mantic) Status: New => Invalid ** Changed in: linux-oem-6.5 (Ubuntu Lunar) Status: New => Invalid -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2042054/+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 2042054] Re: 22.04.3, zen 4 7840, screen turn white exception
** Package changed: xorg (Ubuntu) => mesa (Ubuntu) -- 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/2042054 Title: 22.04.3, zen 4 7840, screen turn white exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2042054/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Please also take this fix at the same time for this same laptop. It will fix s2idle for it. https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform- drivers-x86.git/commit/?h=fixes=3bde7ec13c971445faade32172cb0b4370b841d9 ** Changed in: libinput (Ubuntu) Status: Confirmed => Invalid ** Package changed: linux-signed-hwe-6.2 (Ubuntu) => linux (Ubuntu) ** No longer affects: linux-signed-oem-6.5 (Ubuntu) ** Also affects: linux-oem-6.1 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libinput (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.1 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Noble) Importance: Undecided Status: Confirmed ** Also affects: libinput (Ubuntu Noble) Importance: Undecided Status: Invalid ** Also affects: linux-oem-6.1 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-6.5 (Ubuntu Noble) Importance: Undecided Status: New ** No longer affects: libinput (Ubuntu) ** Changed in: linux (Ubuntu Mantic) Status: New => Confirmed ** Changed in: linux (Ubuntu Lunar) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** No longer affects: linux-oem-6.1 (Ubuntu Lunar) ** No longer affects: linux-oem-6.1 (Ubuntu Mantic) ** No longer affects: linux-oem-6.1 (Ubuntu Noble) ** No longer affects: linux-oem-6.5 (Ubuntu Lunar) ** No longer affects: libinput (Ubuntu Jammy) ** No longer affects: libinput (Ubuntu Lunar) ** No longer affects: libinput (Ubuntu Mantic) ** No longer affects: libinput (Ubuntu Noble) ** No longer affects: linux-hwe-6.2 (Ubuntu Lunar) ** No longer affects: linux-hwe-6.2 (Ubuntu Mantic) ** No longer affects: linux-hwe-6.2 (Ubuntu Noble) ** No longer affects: linux-oem-6.5 (Ubuntu Mantic) ** No longer affects: linux-oem-6.5 (Ubuntu Noble) ** Changed in: linux-oem-6.5 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux-oem-6.1 (Ubuntu) Status: New => Invalid ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid -- 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/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2034477] Re: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop
Here is the upstream patch for this issue: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6 ** Also affects: linux via https://bugzilla.kernel.org/show_bug.cgi?id=218003 Importance: Unknown Status: Unknown -- 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/2034477 Title: Keyboard and Touchpad Not Working in New Lenovo V15 Gen4 Laptop To manage notifications about this bug go to: https://bugs.launchpad.net/ideapad-laptop/+bug/2034477/+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 2039868] Re: amdgpu reset during usage of firefox
6.5.6 has the fix for preemption issue, it should get fixed when stable updates come in Mantic. -- 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/2039868 Title: amdgpu reset during usage of firefox To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2039868/+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 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Ok in this case can you please open an upstream mesa bug? ** Changed in: mesa (Ubuntu) Status: Fix Released => Triaged -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037641/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed right after you reported this issue. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: Confirmed => Incomplete -- 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/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
I'd say that's very likely. That mesa upgrade just landed in the archive a few days ago and the trace you reported looks more like how a mesa bug manifests. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037641/+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 2037641] Re: amdgpu: [gfxhub0] no-retry page fault
Are you up to date on the current version of mesa in 23.10? 23.2.1-1ubuntu2? ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2037641 Title: amdgpu: [gfxhub0] no-retry page fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037641/+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 1987792] Re: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/1987792 Title: Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1987792/+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 2016435] Re: amdgpu driver randomly resets
Random resets are "typically" triggered by mesa or application bugs. Can you still trigger them in the latest mantic (which has a more up to date mesa and kernel)? ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Invalid ** Changed in: mesa (Ubuntu) Status: New => Incomplete -- 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/2016435 Title: amdgpu driver randomly resets To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2016435/+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 1094959] Re: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade
> NonfreeKernelModules: fglrx Nothing that will be done in mesa for an issue with fglrx anyway these days. ** Changed in: mesa (Ubuntu) Status: Incomplete => Won't Fix -- 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/1094959 Title: package libgl1-mesa-dri 8.0.4-0ubuntu0.2 failed to install/upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1094959/+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 2037672] Re: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen
In this case the kernel is the "messenger" for the page fault. This is more likely to be a mesa or application issue than a kernel issue. Can you please raise a ticket to the upstream mesa bug tracker? https://gitlab.freedesktop.org/mesa/mesa/ ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/2037672 Title: amdgpu: [gfxhub] page fault when switching a video to or from fullscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2037672/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
** Also affects: mesa (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Mantic) Importance: Undecided Status: Invalid ** Also affects: mesa (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-hwe-6.2 (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu Lunar) Status: New => Invalid ** Changed in: linux-hwe-6.2 (Ubuntu Jammy) Status: New => Invalid ** Changed in: mesa (Ubuntu Mantic) Status: New => Fix Released -- 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2033967/+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 2033967] Re: Laptop screen blinked, no tty works and 200 dmesg errors per second
I believe this likely needs the VCN fixes from https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported. ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728 https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-6.2 (Ubuntu) Status: New => Invalid ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 Importance: Unknown Status: Unknown -- 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/2033967 Title: Laptop screen blinked, no tty works and 200 dmesg errors per second To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/2033967/+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 2034105] Re: Cursor didn't show up in X session when output from amd dgpu
** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Status: New => Fix Committed ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Assignee: Kai-Chuan Hsieh (kchsieh) => (unassigned) ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy) Importance: Undecided => High -- 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/2034105 Title: Cursor didn't show up in X session when output from amd dgpu To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034105/+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 2020604] Re: After Mesa upgrades, Chrome won't show graphics
I believe the same thing can likely happen if llvm updates but mesa stays the same. Can you embed both into the string? -- 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/2020604 Title: After Mesa upgrades, Chrome won't show graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2020604] Re: After mesa upgrades, Chrome won't show graphics
It seems a way that this may be avoided is for GL_RENDERER string to always be updated when mesa updates. -- 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/2020604 Title: After mesa upgrades, Chrome won't show graphics To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/2020604/+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 2017142] Re: [jammy] VA-API doesn't work on DCN 3.1.4
** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 1608042] Re: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Confirmed => Invalid ** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Triaged => Won't Fix -- 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/1608042 Title: 64-bit XUbuntu 16.04 "Xenial" hybrid graphics (Intel + AMD): AMDGPU crashes / freezes / hangs entire system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1608042/+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 2017142] [NEW] [jammy] VA-API doesn't work on DCN 3.1.4
Public bug reported: [ Impact ] VA-API decoding doesn't work on DCN 3.1.4. Mesa 22.2.5 includes all the code to support it but is missing the chip ID. The device ID was included in upstream mesa 22.3.1. [ Test Plan ] * Verify that VA-API works using "mpv" or a similar tool that uses VA-API * Verify that '# vainfo' shows the correct information. [ Where problems could occur ] * If just the new ID is backported then they would be unique to DCN 3.1.4 as it's now running VA-API codepaths. * If newer mesa point release is adopted, then it could be a regression that happened in changes on common code in mesa between those two point releases. [ Other Info ] * It can be cherry picked with this single commit: https://gitlab.freedesktop.org/mesa/mesa/-/commit/4291e545d5a0f18c652f0ea57907f445392e8858 * AMD has already tested cherry-picked commit on top of the Ubuntu mesa 22.2.5 package and verified it works. ** Affects: mesa (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Tags: originate-from-2016915 ** Tags added: originate-from-2016915 ** Also affects: mesa (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Fix Released -- 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/2017142 Title: [jammy] VA-API doesn't work on DCN 3.1.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2017142/+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 1991761] Re: Backport packages for 22.04.2 HWE stack
At least from AMD's tests, backported mesa stack is working properly with RDNA3. Adjusting tag accordingly. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/1991761 Title: Backport packages for 22.04.2 HWE stack To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/directx-headers/+bug/1991761/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Just to correct a few of the targets on this issue. * The reverts mentioned in #30 need to be pulled into linux-firmware for focal. * They're already included in jammy. ** Changed in: amd Status: New => Fix Released ** No longer affects: mesa (Ubuntu) ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => Juerg Haefliger (juergh) ** Changed in: linux-firmware (Ubuntu) Status: Invalid => Fix Released -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1958673] [NEW] SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS
copy command hw packet" behind other unrelated 2D or 3D rendering commands or video decoding commands in the gpu hardware command stream. All this taken together usually causes the gpu copy operation only to start while the display is already inside the next active refresh cycle, which causes massive visual tearing artifacts and other rendering artifacts on many games and 3D applications. The old xorg-video-intel Intel ddx for Intel iGPU does not have this problem as it lacks checks for mismatched stride, so it "just worked" by accident there with any combination of Intel iGPU + AMD/NVidia dGPU on modern atomic modesetting capable Intel kms drivers. The xorg-video-amdgpu amdgpu ddx has checks in place to ignore stride mismatch on atomic modesetting capable amdgpu kms drivers on modern AMD iGPU's, so works whenever running on suitable hardware + kernel. This problem only affects the xorg-video-modesetting ddx which lacks handling for this. By default, Ubuntu 20.04 uses amdgpu-ddx for AMD iGPU's, so the combination of AMD iGPU + AMD dGPU is not affected by default. In the past Ubuntu used intel-ddx for Intel iGPU's, avoiding the problem as well. But current Ubuntu 20.04 uses the modesetting-ddx for Intel iGPU's by default, and has to use it for hw acceleration on recent Gen-10 and later Intel gpu's like Icelake, Tigerlake, ... so the problem is unavoidable for combinations of Intel iGPU + other dGPU. Therefore this patch could be considered a fix for a functional regression of Ubuntu on modern Intel graphics hardware. Not all combinations of iGPU + dGPU PRIME render offload hardware setups are affected at all video resolution settings. If mismatched stride happens and causes unusable bad tearing depends on the specific iGPU + dGPU hardware combo and display resolution settings. But if it happens, it defeats PRIME renderoffload. As "Optimus" hybrid graphics laptops are very common, and also models with Intel iGPU + AMD dGPU, this patch should make more of them work better at better performance. The problem was encountered and the patch extensively tested and confirmed to fix the problem on a Apple MacBookPro mid 2017 15 inch Retina model with Intel Kabylake GT2 (UHD graphics 630) as server display gpu and AMD Radeon Pro 560 (Polaris 11) render offload gpu. I assume many of the new Laptops with Intel + AMD will benefit from this fix as well. Thanks for consideration -mario ** Affects: psychtoolbox-3 (Ubuntu) Importance: Undecided Status: New ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New ** Also affects: psychtoolbox-3 (Ubuntu) Importance: Undecided Status: New -- 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/1958673 Title: SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psychtoolbox-3/+bug/1958673/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
Verified on YC with the following combination all from -proposed: # dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0." ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library ii linux-firmware 1.187.19 all Firmware for Linux kernel drivers ii linux-image-5.14.0-1005-oem5.14.0-1005.5 amd64Signed kernel image oem ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- 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/1945227 Title: drm/amdgpu: Add support for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1945227] Re: drm/amdgpu: Add support for Yellow Carp
With manually placing firmware in /lib/firmware (since SRU not started for that) and using 5.14 kernel confirmed that mesa looks good. Since we don't have linux-firmware SRU package yet and they are combined on this bug report I will not add "verification-done-focal". # glxinfo | grep "OpenGL render" -i OpenGL renderer string: AMD YELLOW_CARP (DRM 3.42.0, 5.14.0, LLVM 12.0.0) # dpkg -l | grep 21.0.3-0ubuntu0.3 ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the EGL API -- Mesa vendor library ii libgbm1:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64generic buffer management API -- runtime ii libgl1-mesa-dri:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- DRI modules ii libglapi-mesa:amd6421.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the GL API -- shared library ii libglx-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3 amd64free implementation of the OpenGL API -- GLX vendor library -- 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/1945227 Title: drm/amdgpu: Add support for Yellow Carp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1945227/+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 1928393] Re: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault"
Here's a PPA build with the mesa fix Alex mentioned backported: https://launchpad.net/~superm1/+archive/ubuntu/lp1928393 If you can follow the directions to add that PPA and upgrade to that mesa package you can see if that indeed fixes it. ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New -- 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/1928393 Title: linux-firmware 1.197 causes kernel to report error "amdgpu: [gfxhub0] retry page fault" To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1928393/+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 1924814] [NEW] Lag in laptop + ununtu20.04 + dock = 3 Displays
Public bug reported: Hi 1) $ lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 2) $ apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu14 Candidate: 1:7.7+19ubuntu14 Version table: *** 1:7.7+19ubuntu14 500 500 http://cl.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3) What you expected to happen I have a "HP EliteBook 840 G5 (3RF31LT#ABM)" laptop with ubuntu 20.04 Also I have a Dell dock model k17a connected with 2 monitors. The physical display is the following: laptop(landscape) | monitor 1 (landscape) | monitor 2 (portrait right) When I connect the USB-C plug, I expect nothing special but having 2 more display 4) What happened instead When I connect the USB-C plug, the whole UX gets super slow Xorg and gnome-shell are the top 2 cpu-consuming process and both inside the same CPU2 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.8.0-50.56~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Apr 16 16:50:08 2021 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company UHD Graphics 620 [103c:83b2] InstallationDate: Installed on 2021-04-04 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: HP HP EliteBook 840 G5 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=e6947647-3679-496c-8309-dbae876553c4 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2018 dmi.bios.release: 3.0 dmi.bios.vendor: HP dmi.bios.version: Q78 Ver. 01.03.00 dmi.board.name: 83B2 dmi.board.vendor: HP dmi.board.version: KBC Version 04.53.00 dmi.chassis.asset.tag: 5CG8364L0N dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.ec.firmware.release: 4.83 dmi.modalias: dmi:bvnHP:bvrQ78Ver.01.03.00:bd07/18/2018:br3.0:efr4.83:svnHP:pnHPEliteBook840G5:pvr:rvnHP:rn83B2:rvrKBCVersion04.53.00:cvnHP:ct10:cvr: dmi.product.family: 103C_5336AN HP EliteBook dmi.product.name: HP EliteBook 840 G5 dmi.product.sku: 3RF31LT#ABM dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.102-1ubuntu1~20.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.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 focal performance 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/1924814 Title: Lag in laptop + ununtu20.04 + dock = 3 Displays To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1924814/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Thanks so much! -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Thanks Joe! By chance can you upgrade to current BIOS too and get that dump again? There is that workaround now (blacklist intel-vbtn) which you should be able to use now if you have no other problems with current firmware. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
To anyone who has been affected - there is a discussion going on the kernel mailing lists regarding this issue and it would be helpful if you can provide an acpidump. You can attach it to this bug (or file a kernel bugzilla and attach it there). Desired would be the 1.2.0 firmware (which some people have downgraded to workaround this issue) as well as a current affected firmware. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Looking at the dmesg from #30, it's actually intel-hid. Here is how to blacklist: https://askubuntu.com/questions/110341/how-to-blacklist- kernel-modules -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Can you check if you have intel-vbtn or intel-hid driver loaded? I would think intel-vbtn. Whichever it is a good experiment with the above comment is to blacklist the module, rebuild initramfs and reboot. See if this helps. If it does then it's likely a situation of this driver starting in wrong state. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1865206] [NEW] package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev
Public bug reported: Received during focal apt dist-upgrade ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libxvmc-dev 2:1.0.12-0ubuntu2 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu18 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Fri Feb 28 12:26:12 2020 DistUpgraded: 2019-11-21 10:34:45,404 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu ErrorMessage: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 GraphicsCard: Intel Corporation UHD Graphics 620 (Whiskey Lake) [8086:3ea0] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 (Whiskey Lake) [1028:08af] InstallationDate: Installed on 2019-04-05 (328 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190405) MachineType: Dell Inc. XPS 13 9380 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=338eb039-e741-415d-bc9a-1d7c83c55c55 ro quiet splash i915.fastboot=1 vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.0-3ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.10 SourcePackage: libxvmc Title: package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 UpgradeStatus: Upgraded to focal on 2019-11-21 (99 days ago) dmi.bios.date: 12/03/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.1 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.1:bd12/03/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100-4 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.0-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.7-2ubuntu2 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 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: libxvmc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal has-workaround single-occurrence ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxvmc in Ubuntu. https://bugs.launchpad.net/bugs/1865206 Title: package libxvmc-dev 2:1.0.12-0ubuntu2 failed to install/upgrade: trying to overwrite '/usr/include/X11/extensions/vldXvMC.h', which is also in package x11proto-dev 2018.4-4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxvmc/+bug/1865206/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
I also see no change with BIOS 1.10.0 on Eoan (though with kernel 5.3 due to an unrelated issue; I ran 5.4 and 5.5 before with the 1.7.1 BIOS and had the problem with all three kernels). I also noticed that though I have the problem just for ca 13 secs most of the time, occasionally it never seems to start working (I waited more than a minute). However, a few times recently I sent the laptop to sleep with the power button while the problem was occurring. The power button works even when the keyboard does not, and on wake-up the problem was gone. It is possible that I happened to press the button exactly when the keyboard would have worked anyway, but as the procedure helped every time this seems unlikely. Can anyone confirm? -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
Not sure if it matters, but I just rebooted and the wait time at the login screen is actually approx. 13 secs, not 30 -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot
The BIOS 1.9.1 from prev. comment #50 apparently was pulled by Dell, there is no reason given at the link. I have a 9575 from September/October 2019 and BIOS 1.7.1 (from Aug 7, 2019, which is currently the latest one available on the Dell site (and, side note, fixes the annoying fans-always-on-in-tent-mode issue)), and I have the same behavior as described in comment #48, i.e. it is unresponsive for 30 secs at the login screen, then works fine. Still same problem in Focal Fossa with kernel 5.4. I am pretty sure I did not have this in previous BIOSes ( but not 100% sure. As someone asked, yes it is possible to downgrade BIOS, I went through them all bewteen 1.1.6 and 1.7.1 up and down to narrow down the known tent-fan and touchpad-lower-half-randomly-failing issues). -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & touchpad not working at gdm screen after boot
5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat. It's (confusingly) a very different system than 5530 which /is/ available with Ubuntu. ** Summary changed: - [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard & touchpad not working at gdm screen after boot + [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes, it's below the radar for something that is typically tested, tracked, or fixed from a BIOS or validation team perspective. -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
That's interesting to me. Yes the EC will emulate an PS2 mouse until the OS brings up the I2C controller. I would think you can accomplish a similar result by blacklisting psmouse potentially. Is this discussion in IRC or a mailing list? -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1836773] [NEW] .
Public bug reported: . ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18 Uname: Linux 4.15.0-54-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Tue Jul 16 11:02:21 2019 DistUpgraded: 2018-09-19 03:54:26,681 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] [1025:110f] InstallationDate: Installed on 2017-06-13 (763 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: Acer Aspire E5-475 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-54-generic root=UUID=4c1137ae-751e-401f-b13c-f08f19f96990 ro quiet splash SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-09-19 (300 days ago) dmi.bios.date: 03/29/2016 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.01 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: AntMan_SK dmi.board.vendor: Acer dmi.board.version: V1.01 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: SKL dmi.product.name: Aspire E5-475 dmi.product.version: V1.01 dmi.sys.vendor: Acer version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1.1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1.1~18.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Sep 18 19:57:00 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.6-1ubuntu4~16.04.1 xserver.video_driver: modeset ** 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/1836773 Title: . To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1836773/+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 1822394] Re: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot
FWIW a few other messages pop up to me in the above logs as suspicious to the described symptoms, especially with keyboard working in cryptsetup. Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce: offset negative (-111ms) Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce: offset negative (-44ms) Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client bug: timer event25 debounce short: offset negative (-57ms) When libinput initialized if it failed to configure those input devices, that /might/ explain the behavior. Flipping the hinge will cause them to come on/off the bus and let libinput try again. ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New -- 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/1822394 Title: [Dell BIOSes dated 27 Mar 2019] laptop keyboard & touchpad not working at gdm screen after boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1822394/+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 1827500] [NEW] 57Y6kpFYMVG4JPr
Public bug reported: 57Y6kpFYMVG4JPr ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3.1 ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177 Uname: Linux 4.4.0-146-generic i686 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.18 Architecture: i386 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true Date: Fri May 3 03:14:19 2019 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] (prog-if 00 [VGA controller]) Subsystem: Toshiba America Info Systems Wrestler [Radeon HD 6310] [1179:fde8] InstallationDate: Installed on 2019-04-16 (16 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release i386 (20160803) MachineType: TOSHIBA Satellite C655D ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-146-generic root=UUID=92c2b91a-d79e-4179-ae8f-406984690f92 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2011 dmi.bios.vendor: Insyde Corp. dmi.bios.version: 1.50 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: Portable PC dmi.board.vendor: TOSHIBA dmi.board.version: Base Board Version dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: AMD dmi.chassis.version: None dmi.modalias: dmi:bvnInsydeCorp.:bvr1.50:bd04/07/2011:svnTOSHIBA:pnSatelliteC655D:pvrPSC0YU-007008:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnAMD:ct10:cvrNone: dmi.product.name: Satellite C655D dmi.product.version: PSC0YU-007008 dmi.sys.vendor: TOSHIBA version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.libdrm2: libdrm2 2.4.91-2~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160325-1ubuntu1.2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2 xserver.bootTime: Fri May 3 02:48:52 2019 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: Invalid ** Tags: apport-bug compiz-0.9 i386 ubuntu xenial -- 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/1827500 Title: 57Y6kpFYMVG4JPr To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1827500/+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 1740894] Re: KEY_RFKILL is not passed to userspace
Confirm that it also works with Cosmic on the Asus ZenBook Flip UX561UD from my comment #1 xkb-data 2.23.1-1ubuntu1.18.10.1 -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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
Re: [Ubuntu-x-swat] [Bug 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt
This is still failing for me, 3.66s$ sudo apt-get purge -y libxfont1 Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: xfonts-encodings xserver-common Use 'sudo apt autoremove' to remove them. The following packages will be REMOVED: libxfont1* xfonts-base* xfonts-utils* xserver-xorg-core* xvfb* It seems that bdftopcf depends on xfonts-utils, https://packages.ubuntu.com/de/xenial/xfonts-utils, and this is still using https://packages.ubuntu.com/de/xenial/libxfont1. Do you know how can I workaround this issue so that I can XTS working? Thanks! On Mon, 4 Mar 2019 at 13:30, Timo Aaltonen wrote: > btw, libxfont2 is backported to xenial, so you should be able to build > XTS with libxfont-dev, not libxfont1-dev > > ** Changed in: libxfont (Ubuntu Xenial) >Status: New => Won't Fix > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1818428 > > Title: > bdftopcf: bdf input, xtfont4.bdf, corrupt > > Status in libxfont package in Ubuntu: > Fix Released > Status in libxfont source package in Xenial: > Won't Fix > Status in libxfont package in Nexenta Operating System: > Unknown > > Bug description: > Compiling the xorg Test Suite called XTS > (https://github.com/freedesktop/xorg-test-xts) on TravisCI (https > ://travis-ci.org/mjtrangoni/nx-libs/jobs/501145999), I am running on > this Bug, > > - > /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf > /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf > /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf > /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf > /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf > BDF Error on line 32: character 'ascii001' has out of range width, -8 > /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt > Makefile:767: recipe for target 'xtfont4.pcf' failed > --- > > Which seems to be fixed upstream, > > See RedHat Bugzilla 1241939 > (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream > fix here (https://lists.x.org/archives/xorg- > devel/2015-July/046914.html) > > I hope, I can get this fixed/backported soon on Ubuntu Xenial. > > Operating System Details: > Distributor ID: Ubuntu > Description: Ubuntu 16.04.5 LTS > Release: 16.04 > Codename: xenial > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+subscriptions > -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt
May I ask when was this Fix released? Is this fix landing at Xenial? If yes, with which version? Thanks! -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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 1818428] Re: bdftopcf: bdf input, xtfont4.bdf, corrupt
** Bug watch added: Red Hat Bugzilla #1241939 https://bugzilla.redhat.com/show_bug.cgi?id=1241939 ** Also affects: libxfont (Nexenta Operating System) via https://bugzilla.redhat.com/show_bug.cgi?id=1241939 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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 1818428] [NEW] bdftopcf: bdf input, xtfont4.bdf, corrupt
Public bug reported: Compiling the xorg Test Suite called XTS (https://github.com/freedesktop /xorg-test-xts) on TravisCI (https://travis-ci.org/mjtrangoni/nx- libs/jobs/501145999), I am running on this Bug, - /usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf /usr/bin/bdftopcf -t -o xtfont1.pcf xtfont1.bdf /usr/bin/bdftopcf -t -o xtfont2.pcf xtfont2.bdf /usr/bin/bdftopcf -t -o xtfont3.pcf xtfont3.bdf /usr/bin/bdftopcf -t -o xtfont4.pcf xtfont4.bdf BDF Error on line 32: character 'ascii001' has out of range width, -8 /usr/bin/bdftopcf: bdf input, xtfont4.bdf, corrupt Makefile:767: recipe for target 'xtfont4.pcf' failed --- Which seems to be fixed upstream, See RedHat Bugzilla 1241939 (https://bugzilla.redhat.com/show_bug.cgi?id=1241939) and its upstream fix here (https://lists.x.org/archives/xorg-devel/2015-July/046914.html) I hope, I can get this fixed/backported soon on Ubuntu Xenial. Operating System Details: Distributor ID: Ubuntu Description:Ubuntu 16.04.5 LTS Release:16.04 Codename: xenial ** Affects: libxfont (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libxfont in Ubuntu. https://bugs.launchpad.net/bugs/1818428 Title: bdftopcf: bdf input, xtfont4.bdf, corrupt To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxfont/+bug/1818428/+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 1800727] Re: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
** Description changed: + Airplane mode works (enable and disable) after the eventual fixes in bug + #1740894 and the regression does not occur. + + [Original report] + Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: - + DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai - Bus 001 Device 004: ID 27c6:5395 - Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. - 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 003: ID 0489:e0a2 Foxconn / Hon Hai + Bus 001 Device 004: ID 27c6:5395 + Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 -- 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/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1800727/+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 1740894] Re: KEY_RFKILL is not passed to userspace
And I can confirm that it is fixed on Disco as well -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Fixed by bug #1740894, confirmed in Cosmic and Disco ** Changed in: xkeyboard-config (Ubuntu) Status: Confirmed => Fix Released -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1800727] Re: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
Fixed by changed in bug #1740894 ** Changed in: xkeyboard-config (Ubuntu) Status: New => Fix Released -- 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/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1800727/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
This is most likely going to be fixed by the changes discussed in bug #1740894 -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1740894] Re: KEY_RFKILL is not passed to userspace
And your fix helps: Still with SRU version installed: $ cat /sys/class/dmi/id/modalias dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: So, edit edit /lib/udev/hwdb.d/60-keyboard.hwdb: evdev:atkbd:dmi:bvn*:bvr*:bd*:svnDell*:pnXPS159575:pvr* KEYBOARD_KEY_88=unknown $ sudo udevadm hwdb --update $ sudo udevadm trigger evemu-record shows KEY_UNKNOWN: # Waiting for events # E: 0.01 0004 0004 0028 # EV_MSC / MSC_SCAN 28 E: 0.01 0001 001c # EV_KEY / KEY_ENTER0 E: 0.01 # SYN_REPORT (0) -- +0ms E: 3.143316 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143316 0001 00f0 0001 # EV_KEY / KEY_UNKNOWN 1 E: 3.143316 # SYN_REPORT (0) -- +3143ms E: 3.143370 0004 0004 0136 # EV_MSC / MSC_SCAN 136 E: 3.143370 0001 00f0 # EV_KEY / KEY_UNKNOWN 0 E: 3.143370 # SYN_REPORT (0) -- +0ms >>> RESULT: The disabling of the airplane mode works now (and enabling still works). -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Thank you very much. With the SRU version installed (I hope that's right): sudo evemu-record Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: Sleep Button /dev/input/event3: Power Button /dev/input/event4: AT Translated Set 2 keyboard /dev/input/event5: Wacom HID 486A Pen /dev/input/event6: Wacom HID 486A Finger /dev/input/event7: Intel HID events /dev/input/event8: Intel Virtual Button driver /dev/input/event9: Intel HID 5 button array /dev/input/event10: Integrated_Webcam_HD: Integrate /dev/input/event11: Integrated_Webcam_HD: Integrate /dev/input/event12: DELL080D:00 06CB:7A13 Touchpad /dev/input/event13: Dell WMI hotkeys /dev/input/event14: Video Bus /dev/input/event15: HDA Intel PCH Headphone Mic /dev/input/event16: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event17: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event18: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event19: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event20: HDA Intel PCH HDMI/DP,pcm=10 Select the device event number [0-20]: 4 # EVEMU 1.3 # Kernel: 4.18.0-11-generic # DMI: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: # Input device name: "AT Translated Set 2 keyboard" # Input device ID: bus 0x11 vendor 0x01 product 0x01 version 0xab41 # Supported events: # Event type 0 (EV_SYN) # Event code 0 (SYN_REPORT) # Event code 1 (SYN_CONFIG) # Event code 2 (SYN_MT_REPORT) # Event code 3 (SYN_DROPPED) # Event code 4 ((null)) # Event code 5 ((null)) # Event code 6 ((null)) # Event code 7 ((null)) # Event code 8 ((null)) # Event code 9 ((null)) # Event code 10 ((null)) # Event code 11 ((null)) # Event code 12 ((null)) # Event code 13 ((null)) # Event code 14 ((null)) # Event code 15 (SYN_MAX) # Event type 1 (EV_KEY) # Event code 1 (KEY_ESC) # Event code 2 (KEY_1) # Event code 3 (KEY_2) # Event code 4 (KEY_3) # Event code 5 (KEY_4) # Event code 6 (KEY_5) # Event code 7 (KEY_6) # Event code 8 (KEY_7) # Event code 9 (KEY_8) # Event code 10 (KEY_9) # Event code 11 (KEY_0) # Event code 12 (KEY_MINUS) # Event code 13 (KEY_EQUAL) # Event code 14 (KEY_BACKSPACE) # Event code 15 (KEY_TAB) # Event code 16 (KEY_Q) # Event code 17 (KEY_W) # Event code 18 (KEY_E) # Event code 19 (KEY_R) # Event code 20 (KEY_T) # Event code 21 (KEY_Y) # Event code 22 (KEY_U) # Event code 23 (KEY_I) # Event code 24 (KEY_O) # Event code 25 (KEY_P) # Event code 26 (KEY_LEFTBRACE) # Event code 27 (KEY_RIGHTBRACE) # Event code 28 (KEY_ENTER) # Event code 29 (KEY_LEFTCTRL) # Event code 30 (KEY_A) # Event code 31 (KEY_S) # Event code 32 (KEY_D) # Event code 33 (KEY_F) # Event code 34 (KEY_G) # Event code 35 (KEY_H) # Event code 36 (KEY_J) # Event code 37 (KEY_K) # Event code 38 (KEY_L) # Event code 39 (KEY_SEMICOLON) # Event code 40 (KEY_APOSTROPHE) # Event code 41 (KEY_GRAVE) # Event code 42 (KEY_LEFTSHIFT) # Event code 43 (KEY_BACKSLASH) # Event code 44 (KEY_Z) # Event code 45 (KEY_X) # Event code 46 (KEY_C) # Event code 47 (KEY_V) # Event code 48 (KEY_B) # Event code 49 (KEY_N) # Event code 50 (KEY_M) # Event code 51 (KEY_COMMA) # Event code 52 (KEY_DOT) # Event code 53 (KEY_SLASH) # Event code 54 (KEY_RIGHTSHIFT) # Event code 55 (KEY_KPASTERISK) # Event code 56 (KEY_LEFTALT) # Event code 57 (KEY_SPACE) # Event code 58 (KEY_CAPSLOCK) # Event code 59 (KEY_F1) # Event code 60 (KEY_F2) # Event code 61 (KEY_F3) # Event code 62 (KEY_F4) # Event code 63 (KEY_F5) # Event code 64 (KEY_F6) # Event code 65 (KEY_F7) # Event code 66 (KEY_F8) # Event code 67 (KEY_F9) # Event code 68 (KEY_F10) # Event code 69 (KEY_NUMLOCK) # Event code 70 (KEY_SCROLLLOCK) # Event code 71 (KEY_KP7) # Event code 72 (KEY_KP8) # Event code 73 (KEY_KP9) # Event code 74 (KEY_KPMINUS) # Event code 75 (KEY_KP4) # Event code 76 (KEY_KP5) # Event code 77 (KEY_KP6) # Event code 78 (KEY_KPPLUS) # Event code 79 (KEY_KP1) # Event code 80 (KEY_KP2) # Event code 81 (KEY_KP3) # Event code 82 (KEY_KP0) # Event code 83 (KEY_KPDOT) # Event code 85 (KEY_ZENKAKUHANKAKU) # Event code 86 (KEY_102ND) # Event code 87 (KEY_F11) # Event code 88 (KEY_F12) # Event code 89 (KEY_RO) # Event code 90 (KEY_KATAKANA) # Event code 91 (KEY_HIRAGANA) # Event code 92 (KEY_HENKAN) # Event code 93 (KEY_KATAKANAHIRAGANA) # Event code 94 (KEY_MUHENKAN) # Event code 95 (KEY_KPJPCOMMA) # Event code 96 (KEY_KPENTER) # Event code 97 (KEY_RIGHTCTRL) # Event code 98 (KEY_KPSLASH) # Event code 99
[Ubuntu-x-swat] [Bug 1740894] Re: KEY_RFKILL is not passed to userspace
As an additional check I once more installed the SRU version (and rebooted): $ apt-cache policy xkb-data xkb-data: Installed: 2.23.1-1ubuntu1.18.10.1 Candidate: 2.23.1-1ubuntu1.18.10.1 Version table: *** 2.23.1-1ubuntu1.18.10.1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages 100 /var/lib/dpkg/status 2.23.1-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic/main i386 Packages Now the problem occurs again. I.e. the first key press still enables the airplane mode just like with the non-SRU version, but the second key press fails to disable the mode: 1.Press key (STILL OK) -> Airplane mode enables. The airplane mode icon appears in the Gnome panel. Wifi turns off. BT turns off. 2. Press key again (THIS IS NOW BROKEN) -> Airplane mode appears to disable momentarily: For a short moment the airplane mode icon disappears from the Gnome panel. HOWEVER, then the airplane mode immediately and automatically re-enables. The airplane mode icon reappears in the panel, Wifi and BT remain off. - does that command works to get out of airplane mode? (Command: gdbus call etc.) Yes, this still works -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastian: I reinstalled the non-SRU version: $ apt-cache policy xkb-data xkb-data: Installed: 2.23.1-1ubuntu1 Candidate: 2.23.1-1ubuntu1.18.10.1 Version table: 2.23.1-1ubuntu1.18.10.1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic-proposed/main i386 Packages *** 2.23.1-1ubuntu1 500 500 http://de.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages 500 http://de.archive.ubuntu.com/ubuntu cosmic/main i386 Packages 100 /var/lib/dpkg/status - on a stock XPS with the non-SRU version, what keycode do you get in xev I press Fn+Pos1 and I get: FocusIn event, serial 39, synthetic NO, window 0x201, mode NotifyUngrab, detail NotifyAncestor KeymapNotify event, serial 39, synthetic NO, window 0x0, keys: 4294967246 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 MappingNotify event, serial 39, synthetic NO, window 0x0, request MappingKeyboard, first_keycode 8, count 248 KeyPress event, serial 39, synthetic NO, window 0x201, root 0x1ce, subw 0x0, time 272898, (-557,525), root:(1274,1553), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XmbLookupString gives 0 bytes: XFilterEvent returns: False KeyRelease event, serial 39, synthetic NO, window 0x201, root 0x1ce, subw 0x0, time 272898, (-557,525), root:(1274,1553), state 0x0, keycode 255 (keysym 0x0, NoSymbol), same_screen YES, XLookupString gives 0 bytes: XFilterEvent returns: False - on a stock cosmic what happens when you use the key 1.Press key -> Airplane mode enables. The airplane mode icon appear in the Gnome panel. Wifi turns off. BT turns off 2. Press key again -> Airplane mode disables. The airplane mode icon disappears from the Gnome panel. Wifi turns on. BT turns on. I.e., it works perfectly. Every time I press the key, the airplane mode changes into the other state (on or off) - does that command works to get out of airplane mode? (Command: gdbus call etc.) Yes -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
To be clear, the above debugging output is with xkb-data 2.23.1-1ubuntu1.18.10.1 installed and therefore the DISabling of airplane mode by the dedicated key being broken $ aptitude show xkb-data Package: xkb-data Version: 2.23.1-1ubuntu1.18.10.1 State: installed -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: That's the thing, on the Dell XPS 15 9575 there IS a regression with xkb-data 2.23.1-1ubuntu1.18.10.1. On this machine, the airplane mode key worked perfectly out-of-the-box (i.e., the key enabled AND disabled the airplane mode) with the development version of Cosmic, using xkb-data 2.23. See my comment #13 further up in this bug. Here's the debug output for gnome-settings-daemon: [*** Airplane mode is off, Wifi and BT are on ***] /usr/lib/gnome-settings-daemon/gsd-rfkill -v (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 'WLAN' (idx=1): soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Read killswitch of type 'BLUETOOTH' (idx=11): soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:16.867: Added Bluetooth rfkill with ID 11 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.185: Registered client at path /org/gnome/SessionManager/Client29 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:17.187: Opened rfkill-input inhibitor. [*** Here I am pressing the airplane mode key to enable Airplane mode > Wifi/BT goes off ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.232: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.352: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:01:26.353: Changed Bluetooth rfkill with ID 11 [*** Here I am pressing the airplane mode key again to DISable Airplane mode > Wifi/BT should go back on. This fails and the airplane mode re- engages immediately as described ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:11.523: Changed Bluetooth rfkill with ID 11 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 1 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:03:12.394: Changed Bluetooth rfkill with ID 11 [*** Here I am pressing DISabling Airplane mode from the Gnome panel menu > Wifi/BT goes back on. This works ***] (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 1 type 1 (WLAN) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: RFKILL event: idx 11 type 2 (BLUETOOTH) op 2 (CHANGE) soft 0 hard 0 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed rfkill with ID 1 (gsd-rfkill:18272): rfkill-plugin-DEBUG: 19:05:10.298: Changed Bluetooth rfkill with ID 11 -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Sebastien: Yes, enable/disable airplane mode works from gnome-control-center. It also works to disalbe it from the Gnome panel manu. (Remember that it previously also could be enabled and disabled with the dedicated Fn+Pos1 key as long as xkb-data was 2.23). As for the verification-failed: I obviously accept the maintainers' decision. If you think that the xkb-data update is the right path forward despite this regression, by all means please go ahead. It would be good to fix the regression though. It seems that a very similar machine is sold as a Developer Edition with Ubuntu (Dell Precision 5530, https://bartongeorge.io/2018/05/24/welcome-the-new-dell-precision- developer-editions/) The failed disable of the airplane mode (i.e., failed re-enable of Wifi/BT) leaves this in journalctl: Nov 06 00:00:49 chronic systemd[1]: Starting Load/Save RF Kill Switch Status... Nov 06 00:00:49 chronic NetworkManager[777]: [1541458849.3593] manager: rfkill: WiFi now enabled by radio killswitch Nov 06 00:00:49 chronic systemd[1]: Started Load/Save RF Kill Switch Status. Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 118809 Nov 06 00:00:50 chronic kernel: ath10k_pci :02:00.0: Unknown eventid: 90118 Nov 06 00:00:50 chronic kernel: IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2459] device (wlp2s0): device not up after timeout! Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2462] manager: rfkill: WiFi now disabled by radio killswitch Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2514] manager: rfkill: WWAN hardware radio set enabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2516] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2584] manager: rfkill: WWAN hardware radio set disabled Nov 06 00:00:50 chronic NetworkManager[777]: [1541458850.2586] audit: op="radio-control" arg="wwan-enabled" pid=2286 uid=1000 result="success" -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
@Gunnar: Sure, happy to sacrifice my airport key :) New bug #1800727 for the XPS. -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1800727] [NEW] [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed
Public bug reported: Bug #1740894 proposed update to xkb-data 2.23.1-1ubuntu1.18.10.1 in order to pass KEY_RFKILL to userspace. Despite the issue described in bug #1740894, on Dell XPS 15 9575 the airplane mode key actually worked flawlessly out-of-the-box after installing Cosmic at beginning of September, using xkb-data 2.23. Updating to the proposed xkb-data 2.23.1-1ubuntu1.18.10.1 however leads to the following issue: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xkb-data 2.23.1-1ubuntu1.18.10.1 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CurrentDesktop: ubuntu:GNOME Date: Tue Oct 30 22:13:45 2018 Dependencies: DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu InstallationDate: Installed on 2018-09-13 (47 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180912) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 004: ID 27c6:5395 Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9575 PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=26ff4c95-5f68-4121-b7d0-989fa705fcc8 ro quiet splash SourcePackage: xkeyboard-config UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/08/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.1.9 dmi.board.name: 0C32VW dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.1.9:bd08/08/2018:svnDellInc.:pnXPS159575:pvr:rvnDellInc.:rn0C32VW:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9575 dmi.product.sku: 080D dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: xkeyboard-config (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic package-from-proposed ubuntu wayland-session -- 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/1800727 Title: [Regression] [Dell XPS 15 9575] Airplane mode key cannot deactivate airplane mode after update to xkb-data 2.23.1-1ubuntu1.18.10.1 from -proposed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1800727/+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 1740894] Re: KEY_RFKILL is not passed to userspace
A few weeks ago I submitted the similar Bug #1791367 for airplane mode key not working on Asus ZenBook Flip UX561UD. We did some tests updating xkb-data via ppa by Gunnar Hjalmarsson (gunnarhj). This update worked on the Asus, but broke the airplane mode key on Dell XPS 15 9575 2-in-1 where it had worked out-of-the-box with Cosmic and xkb-data 2.23. Now tested the update to 2.23.1 from -proposed and am seeing the same issue on the Dell as in #1791367: 1. Press airplane mode key Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", airplane icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", airplane icon remains in panel, Wifi and BT remain OFF. I can test the Asus as well in a few days, but based on previous results I expect that it will work there. -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1740894] Re: KEY_RFKILL is not passed to userspace
** Tags removed: verification-needed-cosmic ** Tags added: verification-failed-cosmic -- 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/1740894 Title: KEY_RFKILL is not passed to userspace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1740894/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Added comment to the other bug #1740894: Same issue on the Dell as we had here, the new update to 2.23-1 from -proposed breaks disabling the airplane mode on the Dell XPS 15 9575. -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
No worries, as the Dell shows it seems not a no-brainer anyway, so better to postpone. Thanks -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
No stop, disregard, SORRY!!! I don't know how, but I messed up, the update was not installed and I misread some check. Now I definitely do have the update installed and IT WORKS on the Asus. It still breaks the Dell though :) -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Test result on the Asus ZenBook Flip UX561UD: Sadly no improvement with the upgraded xkb-data 2.24 from the ppa. Behavior is completely the same as with the standard 2.23.1, the airplane mode key does not work in gnome-shell but works on the console. -- 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/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Anything I can do? -- 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/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Sorry for typo in previous comment, should have been OFF at the end: Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain *OFF* [not "on"] -- 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/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Thanks, Gunnar. I could not test it yet on the Asus from this bugreport, it will take a few days until I can get my hands on this one. However, I tested with my own Dell XPS 15 9575 and it breaks the Airplane mode switch there, which works perfectly with the standard xkb- data=2.23.1-1ubuntu1 from Cosmic: 2.23.1-1ubuntu1: 1. Press Fn+Pos1 -> Works. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Works. Pop-up says "Airplane mode disabled", icon disappears from panel, Wifi and BT are on. Updated 2.24-0ubuntu1, rebooted: 1. Press Fn+Pos1 -> Works same as before. Pop-up says "Airplane mode enabled", icon appears in panel, Wifi and BT are off. 2. Press Fn+Pos1 again -> Broken. Pop-up briefly says "Airplane mode disabled", then immediately changes to "... enabled", icon remains in panel, Wifi and BT remain on. -- 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/1791367 Title: [FFe]: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Upstream: The NoSymbol (rather than XF86RFKill) tells me that this is exactly the issue. Closing as a downstream issue. For downstream: The reason that the regression happened is commit 3810072d rfkill: Add property to Rfkill helper to inhibit kernel handling https://gitlab.gnome.org/GNOME/gnome-settings-daemon/commit/3810072d2b3776c1183303adc8cd9f50732841a2 -- 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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] Re: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10)
Following upstream suggestion ** Package changed: gnome-settings-daemon (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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console (Cosmic 18.10) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xkeyboard-config/+bug/1791367/+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 1791367] [NEW] Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console
Public bug reported: Please forgive if filed for wrong package. Problem occurs in X and Wayland sessions but not on console, so does not seem to be kernel. Repro on Asus UX561UD with Ubuntu 18.10 up to date: 1. Log into Gnome X or Gnome Wayland session 2. Press Fn+F2 which is the airplane mode key -> Airplane mode should turn on but nothing happens 3. Switch to console with Ctrl+Alt+F3 4. Log into console 5. Press Fn+F2 again 6. Switch back to GUI session with Ctrl+Alt+F2 -> Airplane mode is on, icon appeared in Gnome task bar Same for turning it off. This laptop seems not the only one with this problem. I got the idea of trying the console trick from ArenaL5's answer on Askubuntu, but unfortunately there is no solution there: https://askubuntu.com/questions/972367/airplane-mode-switch-does-not-respond Please let me know whatever I can do to help debug this. All other Fn+Fx special keys on this laptop work (display brightness, touchpad off, sound etc.) except for keyboard backlight, but that works with Ubuntu 18.04.1 and I will file a separate bug for this ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.17.0-9.10-generic 4.17.17 Uname: Linux 4.17.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Sep 7 21:37:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: nvidia, 390.87, 4.17.0-9-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. UHD Graphics 620 [1043:14ee] Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:14ee] InstallationDate: Installed on 2018-09-05 (1 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180822) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2b Intel Corp. Bus 001 Device 003: ID 13d3:5256 IMC Networks Bus 001 Device 002: ID 8644:800b Intenso GmbG Micro Line (4GB) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX561UD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.17.0-9-generic root=UUID=02bad6b5-ca8f-4184-b477-935995e14bdc ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX561UD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX561UD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX561UD.304:bd03/06/2018:svnASUSTeKCOMPUTERINC.:pnUX561UD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX561UD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0: dmi.product.family: ZenBook Flip dmi.product.name: UX561UD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.94-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.1.5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.1.5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1build1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug cosmic has-workaround reproducible ubuntu wayland-session ** Package changed: xorg (Ubuntu) => gnome-shell (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/1791367 Title: Airplane mode key on Asus ZenBook Flip UX561UD laptop not working in gnome-shell (X or Wayland) but working on console To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1791367/+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 1771539] Re: Xorg crash
A) sudo cat /var/lib/whoopsie/whoopsie-id 126a6c719bcce7c3ad86f82dbca39dc81524233531d72481f4d5a2a4f2fac31510f8ea9e7daf5748cbe4667770413d4cc3e5644d79f968c0df829149ea1011b5 B) At the moment it is not possible to reinstall Ubuntu. I'm able to work more less fine as is, with the issue occurring. When I upgrade I'll check. -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1771539] Re: Xorg crash
Since I've reinstalled the ubuntu 16.04, the problem persists, but the kernel parameter (radeon.runpm=0) is no longer present. I'll provide another log dump, when as soon as the problem occurs again. mc -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1771539] Re: Xorg crash
1) ``` $ls -la /var/crash/ total 8080 drwxrwsrwt 2 root whoopsie4096 Jun 7 01:30 . drwxr-xr-x 14 root root4096 Ago 1 2017 .. -rwxrwxrwx 1 root whoopsie 0 Jun 7 01:17 .lock -rw-r- 1 root whoopsie 8265453 Jun 7 01:28 _usr_lib_xorg_Xorg.0.crash -rw-r--r-- 1 root whoopsie 0 Jun 7 01:30 _usr_lib_xorg_Xorg.0.upload -rw--- 1 whoopsie whoopsie 0 Jun 7 01:30 _usr_lib_xorg_Xorg.0.uploaded ``` 2) I've probably added id, when trying to disable the graphic card, to use only one, as when trying to fix it came across some threads suggesting that (e.g. https://askubuntu.com/questions/771562/16-04 -power-off-discrete-graphics-ati-amd). (I'll test removing this later on the day). 3) Dell U2715H (REV A01, 2015) (http://accessories.ap.dell.com/sna/productdetail.aspx?c=hk=en=bsd=hkbsd1=210-ADSZ) 4) DisplayPort-to-DisplayPort (pc DisplayPort-MiniDisplayPort monitor) 5) No, it crashes. 6) Both, no difference. I start the laptop, from cold boot, first login screen displays properly in both monitors cloning the display. Afterwards I try to login and when setting new settings starts crashing repeatedly, trying to restart the xserver (as it seems). -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1771539] Re: Xorg crash
Hi, thanks for you promptly response, unfortunately only now I had the time to check the things above. The HWE is the latest: ``` ~$ sudo apt-get install --install-recommends linux-generic-hwe-16.04 xserver-xorg-hwe-16.04 Reading package lists... Done Building dependency tree Reading state information... Done linux-generic-hwe-16.04 is already the newest version (4.13.0.43.62). xserver-xorg-hwe-16.04 is already the newest version (1:7.7+16ubuntu3~16.04.1). The following packages were automatically installed and are no longer required: dkms libllvm4.0 linux-headers-4.10.0-28 linux-headers-4.10.0-28-generic linux-image-4.10.0-28-generic linux-image-extra-4.10.0-28-generic Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded. ``` The the bios is now updated, but the issue persists. ``` atritoman@atritoman-HP-EliteBook-840-G1:~$ sudo dmidecode -t 0 # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x000D, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: L71 Ver. 01.44 Release Date: 04/12/2018 Address: 0xF Runtime Size: 64 kB ROM Size: 8192 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.44 Firmware Revision: 21.89 ``` Meanwhile I had to reinstall ubuntu 16.04, its the default with Unity, same behavior. When I've started the newly reinstalled system, it seemed to work well, the dual display, after a reboot or two, it stoped working. The login screen works well and displays with dual display when I restart the laptop, but after I login it crashes, and it seems to restart the graphic environment/xserver maybe ... I can post some additional logs. -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1771539] Re: Xorg crash
Honestly, I think it got worst at some point, after some update or after I changed from Unity to Gnome. Unfortunately I don't really have any additional info. Why do you "say" that the bios is outdated ? It is the last from the manufacturer, HP Elite Book 840 G1. ``` # dmidecode 3.0 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x000D, DMI type 0, 24 bytes BIOS Information Vendor: Hewlett-Packard Version: L71 Ver. 01.39 Release Date: 09/26/2016 Address: 0xF Runtime Size: 64 kB ROM Size: 8192 kB Characteristics: PCI is supported PC Card (PCMCIA) is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Print screen service is supported (int 5h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) Printer services are supported (int 17h) ACPI is supported USB legacy is supported Smart battery is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 1.39 Firmware Revision: 21.89 ``` Thanks, for your reply. -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1771539] [NEW] Xorg crash
Public bug reported: When I try to use ubuntu with dual desktop display it crashes continuously, and entering into login mode. I cannot use dual display. To use an external monitor, I have to start the laptop with the computer closed. It seems to be related to the graphic card, maybe dual graphic card of the laptop. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117 Uname: Linux 4.4.0-124-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: GNOME-Classic:GNOME Date: Wed May 16 10:36:05 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 0b) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Haswell-ULT Integrated Graphics Controller [103c:198f] Advanced Micro Devices, Inc. [AMD/ATI] Mars [Radeon HD 8730M] [1002:6601] (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company Mars [Radeon HD 8730M] [103c:1990] InstallationDate: Installed on 2017-12-13 (153 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Hewlett-Packard HP EliteBook 840 G1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic root=UUID=e1833df7-4a4b-41b2-8393-d88536dd0165 ro quiet splash radeon.runpm=0 vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg crash UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/26/2016 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L71 Ver. 01.39 dmi.board.name: 198F dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 15.59 dmi.chassis.asset.tag: 5CG44010XD dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL71Ver.01.39:bd09/26/2016:svnHewlett-Packard:pnHPEliteBook840G1:pvrA3009DD10303:rvnHewlett-Packard:rn198F:rvrKBCVersion15.59:cvnHewlett-Packard:ct10:cvr: dmi.product.name: HP EliteBook 840 G1 dmi.product.version: A3009DD10303 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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: Thu Mar 8 12:39:32 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.19.5-0ubuntu2~16.04.1 xserver.video_driver: modeset ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug crash ubuntu xenial -- 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/1771539 Title: Xorg crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1771539/+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 1764097] Re: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5, 4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubunt
** Description changed: Report created by following https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected Let me know if anything is wrong or if I can give more info - Touchpad worked perfectly in Ubuntu 17.10 when using one and two fingers - clicks, two finger scrolling, and tapping. (I don't know if multitouch - worked, but IIRC it did in the past with Unity) + Touchpad worked perfectly in Ubuntu 17.10, with libinput 1.8.2. - After upgrading to Bionic Beaver it frequently becomes unresponsive, - during which I can neither move the mouse cursor or scroll. I can repro - it most of the time, even directly after rebooting, but not in 100% of - tries. Sometimes, without anything obvious happening (e.g., no reboot or - logging out), the problem may not occur for an hour or two and I cannot - repro it on purpose. Then after a while it is back. Checking the CPU - when it occurs does not show high load. Also repro on gdm screen and - logging in as a different user account and with a an alternative non- - gnome-shell session. + After upgrading to 18.04 (libinput 1.10.4) touchpad frequently becomes + unresponsive during normal operation, during which he mouse cursor and + scrolling does not work. Lifting the finger and starting again makes it + work until the next trigger. - There seem to be two slightly different kinds of unresponsiveness, one - provoked by one-finger movement, the other provoked by two-finger - scrolling: + Triggered apparently by premature palm detection which misdetects a + slightly larger finger area as a palm event. Hence easily reproducible + by placing a finger slightly flat. - One-finger movement: - - Triggered by: - Giving continuous input to touchpad for a second or two. E.g., move one finger in a small circle. After 1-3 circles the touchpad becomes unresponsive. (Making long straight left-right movements also tends to trigger it, but less clearly) - - Results in: - Stays unresponsive until the finger is lifted from and lowered on touchpad again. However, lifting+lowering only restores responsiveness briefly, then it stops again. Waiting a few seconds makes it work again, like for two-finger scrolling. - - Two-finger scrolling: - - Scroll up and down a few times. Does not seem to matter what the - application is. - - Results in: - Scrolling stops after a few movements. Lifting and re-lowering both fingers does not seem to make it go again, but it works after waiting a few seconds. However scrolling is jumpy most of the time and rarely as smooth as it was in 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-synaptics (not installed) ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Gave up waiting for suspend/resume device /dev/sda4: clean, 1015626/39428096 files, 55279634/157701376 blocks Gave up waiting for suspend/resume device /dev/sda4: clean, 1026169/39428096 files, 54683366/157701376 blocks CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 12:07:31 2018 DistUpgraded: 2018-04-08 10:29:35,542 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: bionic DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2037 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Apple Inc. MacBookPro5,4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to bionic on 2018-04-08 (7 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587A1 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro5,4 dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587A1 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev
[Ubuntu-x-swat] [Bug 1764097] Re: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5, 4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubunt
Running "sudo libinput measure touch-size" gives, for a single finger, max sizes between 580 (finger tip) and 1900 (when I deliberately put the first phalanx down flat). "Normal" finger placement size is approx 850 to 950. It seems to detect a palm event above 800, and this reliably reproduces the problem. -- 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/1764097 Title: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
** Attachment added: "libinput-list-devices.txt" https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1764097/+attachment/5138438/+files/libinput-list-devices.txt ** Summary changed: - 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 + 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 16.10) ** Summary changed: - 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 16.10) + 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 17.10) ** Bug watch added: freedesktop.org Bugzilla #106489 https://bugs.freedesktop.org/show_bug.cgi?id=106489 ** Also affects: libinput via https://bugs.freedesktop.org/show_bug.cgi?id=106489 Importance: Unknown Status: Unknown -- 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/1764097 Title: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5, 4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubunt
Upstream bug report: https://bugs.freedesktop.org/show_bug.cgi?id=106489 -- 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/1764097 Title: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
Indeed, running "sudo libinput debug-events --verbose" results in: event6 POINTER_MOTION +11.04s5.07/ -9.23 event6 POINTER_MOTION +11.05s 16.95/ -2.91 event6 POINTER_MOTION +11.06s 13.15/ -4.05 event6 - palm: touch size exceeded event6 - palm: palm detected (touch size) event6 - touch-size: end touch event6 - button state: from BUTTON_STATE_AREA, event BUTTON_EVENT_UP to BUTTON_STATE_NONE ** Package changed: xserver-xorg-input-synaptics (Ubuntu) => libinput (Ubuntu) -- 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/1764097 Title: 'Apple touchpad bcm5974' unresponsive after "palm: touch size exceeded" on 'Apple MacBookPro5,4 (mid 2009)' with 1.10.4 (Ubuntu 18.04), worked fine with 1.8.2 (Ubuntu 17.10) To manage notifications about this bug go to: https://bugs.launchpad.net/libinput/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
I'm not using Wayland but X though, would it still be libinput? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1764097 Title: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
Oh and is there a link to your upstream report, mailing list, or similar? Thanks -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1764097 Title: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
In my defense, the second paragraph seems to say that filing against xserver-xorg-input-synaptics is ok and bug triagers would assign it as needed. I really tried :) Thank you -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xserver-xorg-input-synaptics in Ubuntu. https://bugs.launchpad.net/bugs/1764097 Title: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+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 1764097] Re: 'Apple touchpad bcm5974' is temporarily unresponsive after a few seconds of continuous input in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
** Description changed: Report created by following https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_at_least_one_of_the_Touchpad_features_work.2C_but_does_not_work_correctly_and_as_expected Let me know if anything is wrong or if I can give more info Touchpad worked perfectly in Ubuntu 17.10 when using one and two fingers clicks, two finger scrolling, and tapping. (I don't know if multitouch worked, but IIRC it did in the past with Unity) After upgrading to Bionic Beaver it frequently becomes unresponsive, - during which I can neither move the mouse cursor or scroll. There seem - to be two slightly different kinds of unresponsiveness, one provoked by - one-finger movement, the other provoked by two-finger scrolling: + during which I can neither move the mouse cursor or scroll. I can repro + it most of the time, even directly after rebooting, but not in 100% of + tries. Sometimes, without anything obvious happening (e.g., no reboot or + logging out), the problem may not occur for an hour or two and I cannot + repro it on purpose. Then after a while it is back. Checking the CPU + when it occurs does not show high load. Also repro on gdm screen and + logging in as a different user account and with a an alternative non- + gnome-shell session. + + There seem to be two slightly different kinds of unresponsiveness, one + provoked by one-finger movement, the other provoked by two-finger + scrolling: One-finger movement: Triggered by: Giving continuous input to touchpad for a second or two. E.g., move one finger in a small circle. After 1-3 circles the touchpad becomes unresponsive. (Making long straight left-right movements also tends to trigger it, but less clearly) Results in: Stays unresponsive until the finger is lifted from and lowered on touchpad again. However, lifting+lowering only restores responsiveness briefly, then it stops again. Waiting a few seconds makes it work again, like for two-finger scrolling. Two-finger scrolling: Scroll up and down a few times. Does not seem to matter what the application is. Results in: Scrolling stops after a few movements. Lifting and re-lowering both fingers does not seem to make it go again, but it works after waiting a few seconds. However scrolling is jumpy most of the time and rarely as smooth as it was in 17.10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xserver-xorg-input-synaptics (not installed) ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 BootLog: Gave up waiting for suspend/resume device /dev/sda4: clean, 1015626/39428096 files, 55279634/157701376 blocks Gave up waiting for suspend/resume device /dev/sda4: clean, 1026169/39428096 files, 54683366/157701376 blocks CurrentDesktop: ubuntu:GNOME Date: Sun Apr 15 12:07:31 2018 DistUpgraded: 2018-04-08 10:29:35,542 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: bionic DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2012-09-15 (2037 days ago) InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1) MachineType: Apple Inc. MacBookPro5,4 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic root=UUID=1f4ef214-a70d-44ac-8515-2d4234f32e38 ro quiet splash vt.handoff=1 SourcePackage: xserver-xorg-input-synaptics UpgradeStatus: Upgraded to bionic on 2018-04-08 (7 days ago) dmi.bios.date: 06/15/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MBP53.88Z.00AC.B03.0906151647 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22587A1 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro5,4 dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22587A1 dmi.modalias: dmi:bvnAppleInc.:bvrMBP53.88Z.00AC.B03.0906151647:bd06/15/09:svnAppleInc.:pnMacBookPro5,4:pvr1.0:rvnAppleInc.:rnMac-F22587A1:rvrMacBookPro5,4:cvnAppleInc.:ct10:cvrMac-F22587A1: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro5,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.91-2 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Sun Apr 15