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
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
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
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
** 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
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
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.
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:
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
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:
@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
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
@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
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
@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
@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
@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
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
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
** 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
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
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
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
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
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
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
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
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
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
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
** 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
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
** 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
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:
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
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
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'
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
** 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
** 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
** 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.
** 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
** 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.
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
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.
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
@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
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
@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
@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
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.
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
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
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:
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
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:
--
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
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
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
59 matches
Mail list logo
