Initials I was wrong, the display does get adjusted but no bigger than
1920x1024.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xserver-xorg-video-vmware in Ubuntu.
https://bugs.launchpad.net/bugs/2061886
Title:
Under VMWare resolution does
Public bug reported:
When resizing a VMWare Workstation, under Ubuntu20 the resolution would
change automaticaly. It does not in the Ubuntu 24 Beta. During
installation I have enabled download of third party driver.
I can see vmtoold running.
ProblemType: Bug
DistroRelease: Ubuntu 24.04
** Changed in: libinput (Ubuntu)
Assignee: (unassigned) => Mario Limonciello (superm1)
** Changed in: libinput (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
Public bug reported:
Due to the "input deck" the Framework 16 has a "USB" internal keyboard.
This throws off heuristics for detection of keyboards to turn off when
you select disable touchpad when typing.
This is fixed in upstream libinput with the following change:
This is the same issue as
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2045573
Here is a commit that fixes the issue by changing default pre-emption
policy since the kernel can't know about your mesa version.
Can you please try to reproduce using a mainline upstream build?
https://kernel.ubuntu.com/mainline/v6.7-rc2/
If you can reproduce please share a new kernel log from a boot it
occurs.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
Public bug reported:
While updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.2
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
Public bug reported:
bugs while updating
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libx11-6 2:1.6.9-2ubuntu1.6
ProcVersionSignature: Ubuntu 5.15.0-88.98~20.04.1-generic 5.15.126
Uname: Linux 5.15.0-88-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.25
Architecture: amd64
I've published a PPA here:
https://launchpad.net/~superm1/+archive/ubuntu/gitlab2971/+packages
This has builds both for 22.04 (Jammy) and 23.04 (Lunar). Please
upgrade to that, drop the module parameter and see if things improve.
# sudo add-apt-repository ppa:superm1/gitlab2971
# sudo apt
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
** Package changed: mutter (Ubuntu) => mesa (Ubuntu)
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Lunar)
Importance: Undecided
Status: New
>From the upstream bug this is caused by PSR, so it's not a mesa issue.
** No longer affects: mesa (Ubuntu)
** No longer affects: mesa (Ubuntu Jammy)
** No longer affects: mesa (Ubuntu Lunar)
** No longer affects: mesa (Ubuntu Mantic)
** No longer affects: mesa (Ubuntu Noble)
--
You
It's unclear if this is a BIOS, mesa or kernel bug at this time, but
it's certainly not an Xorg bug as it was reproduced in Wayland.
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #2954
** Package changed: xorg (Ubuntu) => mesa (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2042054
Title:
22.04.3, zen 4 7840, screen turn white exception
To manage notifications about
Please also take this fix at the same time for this same laptop. It
will fix s2idle for it.
https://git.kernel.org/pub/scm/linux/kernel/git/pdx86/platform-
drivers-x86.git/commit/?h=fixes=3bde7ec13c971445faade32172cb0b4370b841d9
** Changed in: libinput (Ubuntu)
Status: Confirmed =>
Here is the upstream patch for this issue:
https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git/commit/?h=x86/urgent=38d54ecfe293ed8bb26d05e6f0270a0aaa6656c6
** Also affects: linux via
https://bugzilla.kernel.org/show_bug.cgi?id=218003
Importance: Unknown
Status: Unknown
--
6.5.6 has the fix for preemption issue, it should get fixed when stable
updates come in Mantic.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2039868
Title:
amdgpu reset during usage of
Ok in this case can you please open an upstream mesa bug?
** Changed in: mesa (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2037641
Title:
Also - can you still repro with mesa 23.2.1-1ubuntu2? This just landed
right after you reported this issue.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you
I'd say that's very likely. That mesa upgrade just landed in the archive
a few days ago and the trace you reported looks more like how a mesa bug
manifests.
** Changed in: linux (Ubuntu)
Status: Confirmed => Invalid
** Changed in: mesa (Ubuntu)
Status: New => Fix Released
--
You
Are you up to date on the current version of mesa in 23.10?
23.2.1-1ubuntu2?
** Also affects: mesa (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
** Changed in: mesa (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1987792
Title:
Totem and VLC crash when playing dvd with VAAPI radeon mesa drivers
Random resets are "typically" triggered by mesa or application bugs.
Can you still trigger them in the latest mantic (which has a more up to
date mesa and kernel)?
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: New => Invalid
** Changed in: mesa (Ubuntu)
Status: New =>
> NonfreeKernelModules: fglrx
Nothing that will be done in mesa for an issue with fglrx anyway these
days.
** Changed in: mesa (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
In this case the kernel is the "messenger" for the page fault. This is
more likely to be a mesa or application issue than a kernel issue.
Can you please raise a ticket to the upstream mesa bug tracker?
https://gitlab.freedesktop.org/mesa/mesa/
** Also affects: mesa (Ubuntu)
Importance:
** Also affects: mesa (Ubuntu Mantic)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2 (Ubuntu Mantic)
Importance: Undecided
Status: Invalid
** Also affects: mesa (Ubuntu Lunar)
Importance: Undecided
Status: New
** Also affects: linux-hwe-6.2
I believe this likely needs the VCN fixes from
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728 backported.
** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #9728
https://gitlab.freedesktop.org/mesa/mesa/-/issues/9728
** Also affects: mesa (Ubuntu)
Importance: Undecided
** Also affects: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Importance: Undecided
Status: New
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Jammy)
Status: New => Fix Committed
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Fix Committed => Fix Released
**
I believe the same thing can likely happen if llvm updates but mesa
stays the same. Can you embed both into the string?
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After Mesa
It seems a way that this may be avoided is for GL_RENDERER string to
always be updated when mesa updates.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2020604
Title:
After mesa upgrades,
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/2017142
Title:
[jammy]
** Changed in: linux (Ubuntu)
Status: Triaged => Fix Released
** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
Status: Confirmed => Invalid
** Changed in: xserver-xorg-video-amdgpu (Ubuntu Xenial)
Status: Confirmed => Invalid
** Changed in: linux (Ubuntu Xenial)
Public bug reported:
[ Impact ]
VA-API decoding doesn't work on DCN 3.1.4.
Mesa 22.2.5 includes all the code to support it but is missing the chip ID.
The device ID was included in upstream mesa 22.3.1.
[ Test Plan ]
* Verify that VA-API works using "mpv" or a similar tool that uses VA-API
*
At least from AMD's tests, backported mesa stack is working properly
with RDNA3. Adjusting tag accordingly.
** Tags removed: verification-needed verification-needed-jammy
** Tags added: verification-done verification-done-jammy
--
You received this bug notification because you are a member of
Just to correct a few of the targets on this issue.
* The reverts mentioned in #30 need to be pulled into linux-firmware for focal.
* They're already included in jammy.
** Changed in: amd
Status: New => Fix Released
** No longer affects: mesa (Ubuntu)
** Also affects: linux-firmware
with Intel Kabylake GT2 (UHD graphics 630) as server
display gpu and AMD Radeon Pro 560 (Polaris 11) render offload gpu. I
assume many of the new Laptops with Intel + AMD will benefit from this
fix as well.
Thanks for consideration
-mario
** Affects: psychtoolbox-3 (Ubuntu)
Importance:
Verified on YC with the following combination all from -proposed:
# dpkg -l | grep "linux-firmware\|linux-image-5.14.0-1005-oem\|21.0.3-0ubuntu0."
ii libegl-mesa0:amd64 21.0.3-0ubuntu0.3~20.04.3
amd64free implementation of the EGL API -- Mesa vendor
With manually placing firmware in /lib/firmware (since SRU not started
for that) and using 5.14 kernel confirmed that mesa looks good. Since
we don't have linux-firmware SRU package yet and they are combined on
this bug report I will not add "verification-done-focal".
# glxinfo | grep "OpenGL
Here's a PPA build with the mesa fix Alex mentioned backported:
https://launchpad.net/~superm1/+archive/ubuntu/lp1928393
If you can follow the directions to add that PPA and upgrade to that
mesa package you can see if that indeed fixes it.
** Also affects: mesa (Ubuntu)
Importance: Undecided
Public bug reported:
Hi
1)
$ lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04
2)
$ apt-cache policy xorg
xorg:
Installed: 1:7.7+19ubuntu14
Candidate: 1:7.7+19ubuntu14
Version table:
*** 1:7.7+19ubuntu14 500
500 http://cl.archive.ubuntu.com/ubuntu
Thanks so much!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
https://bugs.launchpad.net/bugs/1822394
Title:
[Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530 2-in-1]
laptop keyboard & touchpad not working at
Thanks Joe! By chance can you upgrade to current BIOS too and get that
dump again? There is that workaround now (blacklist intel-vbtn) which
you should be able to use now if you have no other problems with current
firmware.
--
You received this bug notification because you are a member of
To anyone who has been affected - there is a discussion going on the
kernel mailing lists regarding this issue and it would be helpful if you
can provide an acpidump. You can attach it to this bug (or file a
kernel bugzilla and attach it there).
Desired would be the 1.2.0 firmware (which some
Looking at the dmesg from #30, it's actually intel-hid. Here is how to
blacklist: https://askubuntu.com/questions/110341/how-to-blacklist-
kernel-modules
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libinput in Ubuntu.
Can you check if you have intel-vbtn or intel-hid driver loaded? I would
think intel-vbtn.
Whichever it is a good experiment with the above comment is to blacklist
the module, rebuild initramfs and reboot. See if this helps.
If it does then it's likely a situation of this driver starting in
Public bug reported:
Received during focal apt dist-upgrade
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: libxvmc-dev 2:1.0.12-0ubuntu2
ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
Uname: Linux 5.4.0-12-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
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
5530 2-in-1 also isn't available for purchase with Ubuntu, so same boat.
It's (confusingly) a very different system than 5530 which /is/
available with Ubuntu.
** Summary changed:
- [Dell BIOSes dated 27 Mar 2019, XPS 9575, Precision 5530] laptop keyboard &
touchpad not working at gdm screen
XPS 9575 isn't (currently) available for purchase with Ubuntu. So yes,
it's below the radar for something that is typically tested, tracked, or
fixed from a BIOS or validation team perspective.
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to
That's interesting to me. Yes the EC will emulate an PS2 mouse until the
OS brings up the I2C controller. I would think you can accomplish a
similar result by blacklisting psmouse potentially.
Is this discussion in IRC or a mailing list?
--
You received this bug notification because you are a
Public bug reported:
.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-54.58-generic 4.15.18
Uname: Linux 4.15.0-54-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CompizPlugins: No
FWIW a few other messages pop up to me in the above logs as suspicious
to the described symptoms, especially with keyboard working in
cryptsetup.
Mar 31 10:34:45 taplop org.gnome.Shell.desktop[5876]: libinput error: client
bug: timer event25 debounce: offset negative (-111ms)
Mar 31 10:34:45
Public bug reported:
57Y6kpFYMVG4JPr
ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-146.172-generic 4.4.177
Uname: Linux 4.4.0-146-generic i686
.tmp.unity_support_test.0:
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
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
This is still failing for me,
3.66s$ sudo apt-get purge -y libxfont1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer
required:
xfonts-encodings xserver-common
Use 'sudo apt autoremove'
May I ask when was this Fix released? Is this fix landing at Xenial? If
yes, with which version?
Thanks!
--
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to libxfont in Ubuntu.
https://bugs.launchpad.net/bugs/1818428
Title:
bdftopcf: bdf input,
** Bug watch added: Red Hat Bugzilla #1241939
https://bugzilla.redhat.com/show_bug.cgi?id=1241939
** Also affects: libxfont (Nexenta Operating System) via
https://bugzilla.redhat.com/show_bug.cgi?id=1241939
Importance: Unknown
Status: Unknown
--
You received this bug
Public bug reported:
Compiling the xorg Test Suite called XTS (https://github.com/freedesktop
/xorg-test-xts) on TravisCI (https://travis-ci.org/mjtrangoni/nx-
libs/jobs/501145999), I am running on this Bug,
-
/usr/bin/bdftopcf -t -o xtfont0.pcf xtfont0.bdf
/usr/bin/bdftopcf -t
** 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
A) sudo cat /var/lib/whoopsie/whoopsie-id
126a6c719bcce7c3ad86f82dbca39dc81524233531d72481f4d5a2a4f2fac31510f8ea9e7daf5748cbe4667770413d4cc3e5644d79f968c0df829149ea1011b5
B) At the moment it is not possible to reinstall Ubuntu. I'm able to
work more less fine as is, with the issue occurring. When
Since I've reinstalled the ubuntu 16.04, the problem persists, but the
kernel parameter (radeon.runpm=0) is no longer present. I'll provide
another log dump, when as soon as the problem occurs again.
mc
--
You received this bug notification because you are a member of Ubuntu-X,
which is
1)
```
$ls -la /var/crash/
total 8080
drwxrwsrwt 2 root whoopsie4096 Jun 7 01:30 .
drwxr-xr-x 14 root root4096 Ago 1 2017 ..
-rwxrwxrwx 1 root whoopsie 0 Jun 7 01:17 .lock
-rw-r- 1 root whoopsie 8265453 Jun 7 01:28 _usr_lib_xorg_Xorg.0.crash
-rw-r--r--
Hi, thanks for you promptly response, unfortunately only now I had the
time to check the things above.
The HWE is the latest:
```
~$ sudo apt-get install --install-recommends linux-generic-hwe-16.04
xserver-xorg-hwe-16.04
Reading package lists... Done
Building dependency tree
Reading
Honestly, I think it got worst at some point, after some update or after
I changed from Unity to Gnome. Unfortunately I don't really have any
additional info.
Why do you "say" that the bios is outdated ? It is the last from the
manufacturer, HP Elite Book 840 G1.
```
# dmidecode 3.0
Getting
Public bug reported:
When I try to use ubuntu with dual desktop display it crashes
continuously, and entering into login mode.
I cannot use dual display.
To use an external monitor, I have to start the laptop with the computer closed.
It seems to be related to the graphic card, maybe dual
** 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
1 - 100 of 382 matches
Mail list logo
