[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 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
[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 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
[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_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. + 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 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. 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 + 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 11:10:46 2018 xserver.configfile: default xserver.errors: - + xserver.logfile: /var/log/Xorg.0.log xserver.outputs: - + xserver.version: 2:1.19.6-1ubuntu3 ** Description changed: - Report created by following https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_Touchpad_features_like_scrolling.2C_tapping.2C_etc._do_not_work_at_all. + 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
[Ubuntu-x-swat] [Bug 1764097] Re: 'Apple touchpad bcm5974' stops being reponsive until finger is lifted after moving cursor a bit in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
** Attachment added: "evtest" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116385/+files/evtest -- 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' stops being reponsive until finger is lifted after moving cursor a bit in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
** Attachment added: "xev.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116386/+files/xev.log ** Summary changed: - 'Apple touchpad bcm5974' stops being reponsive until finger is lifted after moving cursor a bit in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 + 'Apple touchpad bcm5974' stops being responsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 ** Summary changed: - 'Apple touchpad bcm5974' stops being responsive after a few seconds of continuous input in 'Apple MacBookPro5,4 (mid 2009)' after upgrading to 18.04 Beta 2 + '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 -- 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' stops being reponsive until finger is lifted after moving cursor a bit in 'Apple MacBookPro5, 4 (mid 2009)' after upgrading to 18.04 Beta 2
** Attachment added: "xinput" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-input-synaptics/+bug/1764097/+attachment/5116384/+files/xinput -- 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] [NEW] '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
Public bug reported: 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 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. 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 11:10:46 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu3 ** Affects: xserver-xorg-input-synaptics (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu ** Attachment added: "xmodmap" https://bugs.launchpad.net/bugs/1764097/+attachment/5116367/+files/xmodmap -- 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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
A really helpful Ask Ubuntu summary is here: http://askubuntu.com/questions/76081/brightness-not-working-after- installing-nvidia-driver -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
Guys, I found the old bug #726692 (which had been even been filed by myself) which contains a fix at least for my hardware (which is not an Asus but a MacBook Pro, see comment #8). The fix for me is to add this line in xorg.conf: Option RegistryDwords EnableBrightnessControl=1 Then log out and in again, and it works for me. Sorry that I did not think of having filed this report before - I did not have to make this change for a long time. The fix is not my invention, but as I remember now has been frequently recommended since years ago: https://www.google.com/search?q=Option+%22RegistryDwords%22+%22EnableBrightnessControl%3D1%22+%22ubuntu%22 -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
@Rainer: In the link given by Jospeh, https://wiki.ubuntu.com/Bugs/Upstream/kernel, it says that the linux-usb list is for reporting USB bugs, which this is not. Follow the instructions under Reporting non-USB Bugs Upstream. When looking in the MAINTAINERS list linked from there, I think the correct maintainer might be this one, but I'm not sure: 252 ACPI VIDEO DRIVER 253 M: Zhang Rui rui.zh...@intel.com 254 L: linux-a...@vger.kernel.org 255 W: http://www.lesswatts.org/projects/acpi/ 256 S: Supported 257 F: drivers/acpi/video.c Maybe Joseph can weigh in. If that's correct, send the email to linux- a...@vger.kernel.org. In this and everything else follow the instructions at Reporting non-USB Bugs UpstreamMETICULOUSLY, otherwise the report might get ignored upstream or worse. Thanks. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
Anyway, I see in the Maintainers list that all ACPI-related reports except for hardware-specific special cases go to linux- a...@vger.kernel.org anyway, so it's maybe not crucial to be 100% sure about the maintainer. However, it might also be this one: 1214 ASUS NOTEBOOKS AND EEEPC ACPI/WMI EXTRAS DRIVERS 1215 M: Corentin Chary corenti...@iksaif.net 1216 L: acpi4asus-u...@lists.sourceforge.net 1217 L: platform-driver-...@vger.kernel.org 1218 W: http://acpi4asus.sf.net 1219 S: Maintained 1220 F: drivers/platform/x86/asus*.c 1221 F: drivers/platform/x86/eeepc*.c Joseph? -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
@Joseph: In the context of bug #1055475 I tested the 3.6 rc7 mainline kernel with nvidia-current and the nvidia-experimental (304.48) drivers on Quantal, and the backlight adjustment did not work. This is on a MacBook Pro 5,4, and not the Asus this bug report is about, but I figure it might well be the same problem. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
@Rainer in comment #21: Did you test this with the final 3.6 mainline kernel on the Asus hardware this bug is about? If so, could you change the tags as requested by Joseph in comment #19? That way I think the bug moves more quickly. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook (304.43)
Ugh, please disregard my previous comment, you already did change the tag, sorry. ** Tags removed: needs-upstream-testing -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook (304.43) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook
Same problem persists on my machine (see comments #8 and #9) when trying the nvidia-experimental-304 drivers (as opposed to the nvidia-current driver) that is being offered by the Additional Drivers tab in Software Sources. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook
Sorry, corrections to my previous comment #8: 1. Typo in the Macbook Pro version number. I meant to write: on a MacBook Pro 5,3 (mid-2009) 2. Actually I did run Precise on this machine with backlight control working with Nvidia. But this had been an Oneiric install which was upgraded. I did not verify the Nvidia backlight in a recent new install with 12.04.1, since I only ran nouveau for the time it took to upgrade to Quantal beta, where it does not work now. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1046088/+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 1046088] Re: No Brightness Control on ASUS G75VW Notbook
It seems that other hardware is also affected. Running Quantal, I don't have backlight control with Nvidia drivers on a MacBook Pro 5, (mid-2009) with NVIDIA GeForce 9600M GT. There is a forum thread discussing missing backlight control with this hardware in Precise: http://ubuntuforums.org/showthread.php?t=2042999 It says that it helped to install the nvidia_bl module from the same source as was given here i the Asus bug report in comment #5. Nvidia backlight control worked on this machine for all releases I tried starting in 2009 up to Oneiric. I skipped Precise (where it apparently was broken according to the forum thread), and now found it out of order in Quantal. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers-updates in Ubuntu. https://bugs.launchpad.net/bugs/1046088 Title: No Brightness Control on ASUS G75VW Notbook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-updates/+bug/1046088/+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 957699] Re: [bcm5974] Right-click no longer working
It seems to me that at least a part of the described problem (the part where multi-finger clicks stopped working) may be the intentional change in clickpad behavior as described in bug #941046 -- 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/957699 Title: [bcm5974] Right-click no longer working To manage notifications about this bug go to: https://bugs.launchpad.net/xserver-xorg-input-synaptics/+bug/957699/+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 726692] [NEW] Screen backlight stopped working on MacBook Pro 5, 4 and other hardware
Public bug reported: The nvidia-current drivers that have recently become available in Natty (270.29) work for me in general, but screen backlight adjustment does not work anymore on my MacBook Pro. Other hardware seems also affected, e.g an Nvidia GT330M in this thread: http://ubuntuforums.org/showthread.php?p=10505235 Neither the keyboard keys nor the brightness applet slider works, the applet icon showing a stop sign as usual when brightness adjustment is not available. Adding this to xorg.conf makes it somewhat work again after a reboot. Option RegistryDwords EnableBrightnessControl=1 However, this makes only the adjustment work as such; I still don't get the notification bubble that appeared with previous drivers, and which still appears in Natty when I use the nouveau drivers. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: nvidia-current 270.29-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6 Uname: Linux 2.6.38-5-generic x86_64 NonfreeKernelModules: nvidia wl .proc.driver.nvidia.gpus.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/0' .proc.driver.nvidia.registry: Binary: .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 270.29 Wed Feb 23 16:18:35 PST 2011 GCC version: gcc version 4.5.2 (Ubuntu/Linaro 4.5.2-3ubuntu3) Architecture: amd64 CompizPlugins: [core,bailer,detection,uTouch,composite,opengl,decor,move,place,regex,compiztoolbox,resize,grid,snap,vpswitch,mousepoll,wall,session,gnomecompat,animation,workarounds,expo,ezoom,staticswitcher,fade,scale] CompositorRunning: compiz Date: Mon Feb 28 19:03:50 2011 DistUpgraded: Yes, recently upgraded Log time: 2011-02-16 12:35:27.758238 DistroCodename: natty DistroVariant: ubuntu DkmsStatus: nvidia-current, 270.29, 2.6.38-5-generic, x86_64: installed bcmwl, 5.100.82.38+bdcom, 2.6.38-5-generic, x86_64: installed GraphicsCard: nVidia Corporation C79 [GeForce 9400M] [10de:0863] (rev b1) (prog-if 00 [VGA controller]) Subsystem: Apple Computer Inc. Device [106b:00ba] InstallationMedia: Ubuntu 10.04 Lucid Lynx - Alpha amd64 (20100131) MachineType: Apple Inc. MacBookPro5,4 ProcEnviron: LANGUAGE=en_US:en LANG=de_DE.utf8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-5-generic root=UUID=8d2a8ff1-ec5f-4fdb-8d1d-803044f16759 ro quiet splash vt.handoff=7 Renderer: Unknown SourcePackage: nvidia-graphics-drivers 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.name: MacBookPro5,4 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. version.compiz: compiz 1:0.9.4-0ubuntu1 version.libdrm2: libdrm2 2.4.23-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 7.10.1~git20110215.cc1636b6-0ubuntu2 version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A version.xserver-xorg: xserver-xorg 1:7.6~3ubuntu8 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.14.0-0ubuntu2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.14.0-1ubuntu11 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:0.0.16+git20110107+b795ca6e-0ubuntu5 ** Affects: nvidia-graphics-drivers (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug compiz-0.9 natty ubuntu -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight stopped working on MacBook Pro 5,4 and other hardware ___ 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 726692] Re: Screen backlight stopped working on MacBook Pro 5, 4 and other hardware
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight stopped working on MacBook Pro 5,4 and other hardware ___ 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 726692] Re: Screen backlight stopped working on MacBook Pro 5, 4 and other hardware
I verified the can't change backlight (without the xorg.conf option) both in a Unity session and a Classic session with effects. The 'still don't get a notification bubble was verified only in the Classic session so far, Unity will have to wait. -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight stopped working on MacBook Pro 5,4 and other hardware ___ 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 726692] Re: Screen backlight stopped working on MacBook Pro 5, 4 and other hardware
Even with EnableBrightnessControl=1, the Brightness Applet shows the stop sign and the slider position cannot be changed. (As stated above, the keyboard keys work though) ** Summary changed: - Screen backlight stopped working on MacBook Pro 5,4 and other hardware + Screen backlight adjustment stopped working on MacBook Pro 5,4 and other hardware -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to nvidia-graphics-drivers in ubuntu. https://bugs.launchpad.net/bugs/726692 Title: Screen backlight adjustment stopped working on MacBook Pro 5,4 and other hardware ___ 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
