[Desktop-packages] [Bug 1998765] Re: libnl3 3.4.0 doesn't work with WCN3980
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libnl3 in Ubuntu. https://bugs.launchpad.net/bugs/1998765 Title: libnl3 3.4.0 doesn't work with WCN3980 Status in OEM Priority Project: New Status in libnl3 package in Ubuntu: New Bug description: When testing WCN3980 with 20.04 and UC20, WCN3980 is not able connect to an AP. I tried a different libnl3 from BSP and found that WCN3980 can work correctly. The version used in BSP is 3.5.0. I bisected the commits from 3.4.0 to 3.5.0 and found this commit[1] is the root cause. According to the commit, it seems that the flag should be set for kernel later than 5.2. [1] https://github.com/thom311/libnl/commit/7de65a051fb37ece16f896a7385073274b77a133 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1998765/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1985869] Re: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found]
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1985869 Title: Screen does not update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found and Page flip discarded: CRTC property (GAMMA_LUT) not found] Status in Mutter: New Status in OEM Priority Project: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: == ApportVersion = 2.20.11-0ubuntu82.1 == Architecture = amd64 == CasperMD5CheckResult = pass == Date = Fri Aug 12 16:01:31 2022 == Dependencies = accountsservice 22.07.5-2ubuntu1.3 acl 2.3.1-1 adduser 3.118ubuntu5 adwaita-icon-theme 41.0-1ubuntu1 alsa-topology-conf 1.2.5.1-2 alsa-ucm-conf 1.2.6.3-1ubuntu1 apg 2.2.3.dfsg.1-5build2 apport 2.20.11-0ubuntu82.1 apport-symptoms 0.24 apt 2.4.6 apt-utils 2.4.6 aptdaemon 1.1.1+bzr982-0ubuntu39 aptdaemon-data 1.1.1+bzr982-0ubuntu39 aspell 0.60.8-4build1 aspell-en 2018.04.16-0-1 at-spi2-core 2.44.0-3 avahi-daemon 0.8-5ubuntu5 avahi-utils 0.8-5ubuntu5 base-files 12ubuntu4.2 bash 5.1-6ubuntu1 bash-completion 1:2.11-5ubuntu1 bind9-host 1:9.18.1-1ubuntu1.1 bind9-libs 1:9.18.1-1ubuntu1.1 bluez 5.64-0ubuntu1 bolt 0.9.2-1 bsdextrautils 2.37.2-4ubuntu3 bubblewrap 0.6.1-1 ca-certificates 20211016 cheese-common 41.1-1build1 colord 1.4.6-1 colord-data 1.4.6-1 coreutils 8.32-4.1ubuntu1 cpp 4:11.2.0-1ubuntu1 cpp-11 11.2.0-19ubuntu1 cracklib-runtime 2.9.6-3.4build4 cups-pk-helper 0.2.6-1ubuntu5 [ 6902.723370] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7123.822417] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7123.823384] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7124.335913] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize fprintd service: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.reactivated.Fprint was not provided by any .service files asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7180.309459] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7180.311605] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7218.558479] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7218.559502] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7244.319195] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7244.320182] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7295.446436] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7295.447812] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7573.588299] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7573.590411] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7574.868039] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize fprintd service: Gio.DBusError: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name net.reactivated.Fprint was not provided by any .service files asyncCallback@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:114:23 [ 7654.509594] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7654.510955] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7751.955703] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7751.957582] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 7965.552231] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 7965.553842] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 8073.130242] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 8073.131334] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 8816.510259] ubuntu1 gnome-shell[2773]: Failed to post KMS update: CRTC property (GAMMA_LUT) not found [ 8816.511259] ubuntu1 gnome-shell[2773]: Page flip discarded: CRTC property (GAMMA_LUT) not found [ 8818.963154] ubuntu1 gnome-shell[2773]: JS ERROR: Failed to initialize fprintd
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Tags removed: verification-needed ** Tags added: verification-done -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980334] Re: Support Quectel's modem(EM120/160) firmware update, fwupd
** Changed in: oem-priority Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1980334 Title: Support Quectel's modem(EM120/160) firmware update, fwupd Status in OEM Priority Project: Fix Committed Status in fwupd package in Ubuntu: Fix Released Status in gnome-firmware package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in libxmlb package in Ubuntu: Fix Released Status in fwupd source package in Focal: Fix Committed Status in gnome-firmware source package in Focal: Fix Committed Status in gnome-software source package in Focal: Fix Committed Status in libxmlb source package in Focal: Fix Committed Status in fwupd source package in Kinetic: Fix Released Status in gnome-firmware source package in Kinetic: New Status in gnome-software source package in Kinetic: New Status in libxmlb source package in Kinetic: Fix Released Bug description: [Impact] * EM120/160 firmware update's fw can't get updated. [Test Plan] * Use a machine with EM120/160 and test fw upgrade or reinstall. For the rest of the SRU document, please check lp:1982103 Note: the SRU of fwupd is following the exception in https://wiki.ubuntu.com/firmware-updates. We also need to upgrade libxmlb due to fwupd is its only major consumer, and without that, we could not have the correct fwupd function on this one. -- The current fwupd packages in focal have to be rebuild with the latest 1.18.6 modem manager[1] in updates channel. In the modem-manager plugin of fwupd, there are several version check macros to determine the version of modem-manager, for instance: https://git.launchpad.net/ubuntu/+source/fwupd/tree/plugins/modem- manager/fu-mm-device.c?h=ubuntu/focal-updates#n22 #if MM_CHECK_VERSION(1, 17, 2) #include "fu-firehose-updater.h" #endif If the version is equal to or newer than 1.17.2, fwupd will have different behaviors. And the previous version in Focal is 1.16.6 so we have to rebuild or do a version bump to make sure it compile with the new modem manager. [1] https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969422] Re: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object(
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1969422 Title: gnome-shell crashed with SIGSEGV in gbm_surface_release_buffer() from meta_drm_buffer_gbm_finalize() from g_object_unref() from g_object_unref() from g_set_object() Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Jammy: Fix Committed Status in mutter source package in Kinetic: Fix Released Bug description: [ Impact ] On dual-GPU systems, gnome-shell may crash in gbm_surface_release_buffer() during display config changes, like when rearranging monitor positions. [ Test Plan ] 1. Find a dual GPU system where both use open source drivers (like Intel + AMD). 2. Ideally also attach one monitor to each GPU. 3. Open Settings and repeatedly change the monitor layout pressing Apply each time. Expect: System does not crash. [ Where problems could occur ] Anywhere to do with screen updates since the entire triple buffering patch has been updated. [ Other Info ] The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 42.0-1ubuntu1, the problem page at https://errors.ubuntu.com/problem/4fa0be3b67c650c621a425137efd7376c32451b4 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1980334] Re: Support Quectel's modem(EM120/160) firmware update, fwupd
with fwupd 1.7.5-3~20.04.1, and `fwupdmgr enable-remote lvfs-testing`. Can't see EM160R GL. After install fwupd 1.7.9-1~20.04.1 from the focal-proposed channel, Can see: > ├─EM160R GL: > │ Device ID: 60fd634d16e219aa0a142e9f00e9989654f48b60 > │ Summary:Mobile broadband device > │ Current version:EM160RGLAPR02A07M4G_15.015.15.015 Given so, mark verification done. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1980334 Title: Support Quectel's modem(EM120/160) firmware update, fwupd Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Fix Released Status in gnome-firmware package in Ubuntu: New Status in gnome-software package in Ubuntu: New Status in libxmlb package in Ubuntu: Fix Released Status in fwupd source package in Focal: Fix Committed Status in gnome-firmware source package in Focal: Fix Committed Status in gnome-software source package in Focal: Fix Committed Status in libxmlb source package in Focal: Fix Committed Status in fwupd source package in Kinetic: Fix Released Status in gnome-firmware source package in Kinetic: New Status in gnome-software source package in Kinetic: New Status in libxmlb source package in Kinetic: Fix Released Bug description: [Impact] * EM120/160 firmware update's fw can't get updated. [Test Plan] * Use a machine with EM120/160 and test fw upgrade or reinstall. For the rest of the SRU document, please check lp:1982103 Note: the SRU of fwupd is following the exception in https://wiki.ubuntu.com/firmware-updates. We also need to upgrade libxmlb due to fwupd is its only major consumer, and without that, we could not have the correct fwupd function on this one. -- The current fwupd packages in focal have to be rebuild with the latest 1.18.6 modem manager[1] in updates channel. In the modem-manager plugin of fwupd, there are several version check macros to determine the version of modem-manager, for instance: https://git.launchpad.net/ubuntu/+source/fwupd/tree/plugins/modem- manager/fu-mm-device.c?h=ubuntu/focal-updates#n22 #if MM_CHECK_VERSION(1, 17, 2) #include "fu-firehose-updater.h" #endif If the version is equal to or newer than 1.17.2, fwupd will have different behaviors. And the previous version in Focal is 1.16.6 so we have to rebuild or do a version bump to make sure it compile with the new modem manager. [1] https://launchpad.net/ubuntu/+source/modemmanager/1.18.6-1~ubuntu20.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984840] Re: bump libxml version for gnome-software and gnome-firmware
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority Status: In Progress => Confirmed ** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware Status in OEM Priority Project: Fix Committed Status in gnome-firmware package in Ubuntu: In Progress Status in gnome-software package in Ubuntu: In Progress Status in gnome-firmware source package in Focal: Fix Committed Status in gnome-software source package in Focal: Fix Committed Bug description: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984840] Re: bump libxml version for gnome-software and gnome-firmware
focal: (keep updating) after upgrade fwupd to 1.7.9-1~20.04.1, gnome-software to 3.36.1-0ubuntu0.20.04.1, and gnome-firmware to 3.34.0-2ubuntu1 from the proposed channel: gnome-software: upgrade test passed gnome-firmware: TODO -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware Status in OEM Priority Project: In Progress Status in gnome-firmware package in Ubuntu: In Progress Status in gnome-software package in Ubuntu: In Progress Status in gnome-firmware source package in Focal: Fix Committed Status in gnome-software source package in Focal: Fix Committed Bug description: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1990089] Re: Screen freeze when performing memory stress in Wayland mode
** Tags added: oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1990089
Title:
Screen freeze when performing memory stress in Wayland mode
Status in OEM Priority Project:
In Progress
Status in linux package in Ubuntu:
New
Status in mutter package in Ubuntu:
New
Bug description:
[Steps to reproduce]
(disable systemd-oomd or executing over ssh)
(below command allocates a lot of memory to stress kernel page fault)
1. stress-ng --stack 0 --timeout 300
2. check the screen
[Expected result]
Screen will update slowly when performing the stress-test.
but screen needs back to work after stress.
[Actual result]
Screen freeze after stress test.
[Additional information]
kernel version: vmlinuz-5.17.0-1017-oem
kernel version: vmlinuz-6.0.0-06rc4drmtip20220910-generic
Mesa version: 22.0.5-0ubuntu0.1
Mutter version: 42.2-0ubuntu1
Gnome-shell version: 42.2-0ubuntu0.2
* Issue happens in Wayland only
* gnome-shell keeps issuing ioctl()
```
(gdb) bt
#0 __GI___ioctl (fd=fd@entry=14, request=request@entry=3223348419) at
../sysdeps/unix/sysv/linux/ioctl.c:36
#1 0x7fcacab0eb4f in intel_ioctl (arg=0x7fffc5404d80,
request=3223348419, fd=14) at ../src/intel/common/intel_gem.h:75
#2 iris_wait_syncobj (timeout_nsec=140736502713808, syncobj=,
bufmgr=) at ../src/gallium/drivers/iris/iris_fence.c:229
#3 iris_wait_syncobj (bufmgr=, syncobj=,
timeout_nsec=timeout_nsec@entry=9223372036854775807) at
../src/gallium/drivers/iris/iris_fence.c:215
#4 0x7fcacab8beab in iris_get_query_result (result=0x7fffc5404e50,
wait=, query=0x55774159b800, ctx=) at
../src/gallium/drivers/iris/iris_query.c:635
#5 iris_get_query_result (ctx=, query=0x55774159b800,
wait=, result=0x7fffc5404e50) at
../src/gallium/drivers/iris/iris_query.c:601
#6 0x7fcaca405e89 in tc_get_query_result (_pipe=,
query=0x55774159b800, wait=, result=0x7fffc5404e50) at
../src/gallium/auxiliary/util/u_threaded_context.c:881
#7 0x7fcaca0f0e64 in get_query_result (pipe=pipe@entry=0x55773f87bad0,
q=q@entry=0x557741a0c790, wait=wait@entry=1 '\001') at
../src/mesa/main/queryobj.c:266
#8 0x7fcaca0f1b12 in _mesa_wait_query (q=0x557741a0c790,
ctx=0x55773f8af980) at ../src/mesa/main/queryobj.c:344
#9 get_query_object (ctx=0x55773f8af980, func=func@entry=0x7fcacaf28283
"glGetQueryObjecti64v", id=, pname=34918,
ptype=ptype@entry=5134, buf=0x0, offset=140736502714192)
at ../src/mesa/main/queryobj.c:1174
#10 0x7fcaca0f2d65 in _mesa_GetQueryObjecti64v (id=,
pname=, params=) at
../src/mesa/main/queryobj.c:1257
#11 0x7fcadfa39b90 in ?? () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#12 0x7fcadfa751b9 in cogl_frame_info_get_rendering_duration_ns () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#13 0x7fcadf8819c4 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#14 0x7fcadfa6e7a2 in _cogl_onscreen_notify_complete () from
/usr/lib/x86_64-linux-gnu/mutter-10/libmutter-cogl-10.so.0
#15 0x7fcadf969cdd in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#16 0x7fcadf96ec7b in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#17 0x7fcadf969601 in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#18 0x7fcadf98395e in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#19 0x7fcadf96962d in ?? () from /lib/x86_64-linux-gnu/libmutter-10.so.0
#20 0x7fcae0743c24 in g_main_context_dispatch () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#21 0x7fcae07986f8 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#22 0x7fcae0743293 in g_main_loop_run () from
/lib/x86_64-linux-gnu/libglib-2.0.so.0
#23 0x7fcadf8d0849 in meta_context_run_main_loop () from
/lib/x86_64-linux-gnu/libmutter-10.so.0
#24 0x55773f1a4f12 in ?? ()
#25 0x7fcadf429d90 in __libc_start_call_main
(main=main@entry=0x55773f1a4a70, argc=argc@entry=1,
argv=argv@entry=0x7fffc54053e8) at ../sysdeps/nptl/libc_start_call_main.h:58
#26 0x7fcadf429e40 in __libc_start_main_impl (main=0x55773f1a4a70,
argc=1, argv=0x7fffc54053e8, init=, fini=,
rtld_fini=, stack_end=0x7fffc54053d8)
at ../csu/libc-start.c:392
#27 0x55773f1a51b5 in ?? ()
```
Other discussion thread:
https://gitlab.freedesktop.org/drm/intel/-/issues/6851
https://gitlab.gnome.org/GNOME/mutter/-/issues/2431
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter (not installed)
Uname: Linux 5.18.0-rc2+ x86_64
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
CasperMD5json:
{
"result": "skip"
}
Date: Mon Sep 19 10:39:59 2022
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
[Desktop-packages] [Bug 1984840] Re: bump libxml version for gnome-software and gnome-firmware
** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => In Progress ** Changed in: gnome-firmware (Ubuntu) Status: New => In Progress ** Changed in: gnome-software (Ubuntu) Status: New => In Progress ** Tags added: fwupd libxmlb -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware Status in OEM Priority Project: In Progress Status in gnome-firmware package in Ubuntu: In Progress Status in gnome-software package in Ubuntu: In Progress Bug description: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1984840] [NEW] bump libxml version for gnome-software and gnome-firmware
Public bug reported: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) ** Affects: oem-priority Importance: High Assignee: Yuan-Chen Cheng (ycheng-twn) Status: In Progress ** Affects: gnome-firmware (Ubuntu) Importance: Undecided Status: In Progress ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: In Progress ** Tags: fwupd libxmlb oem-priority ** Information type changed from Proprietary to Public ** Also affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority ** Also affects: gnome-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware Status in OEM Priority Project: In Progress Status in gnome-firmware package in Ubuntu: In Progress Status in gnome-software package in Ubuntu: In Progress Bug description: We'll need to upgrade foacl/libxmlb to version 0.3.6 because of lp:1980334, which will bump the runtime from libxmlb1 to libxmlb2. Given so, we'll modify the control file to build-depend on the new focal/libxmlb so we'll be sure that it will have right dependency after focal/libxmlb is upgraded. [Impact] * need to upgrade libxmlb so that EM120/160 firmware update cound be upgraded. (lp:1980334) * Since after upgrade, libxmlb1 will become libxmlb2. So we need to bump version in the control file to make sure it build against the new libxmlb. [Test Plan] * install the upgraded fwupd/libxmlb and gnome-software and gnome-firmware. Find a machine that have pending firmware upgrade. 1. check if the device list is the same before/after upgrade 2. make sure those two app still could upgrade the firmware after upgrade. * other test on fwupd will be covered by their bugs. [Where problems could occur] * Given libxmlb is only used to do fw upgrade, if it pass the test above, I can't see other think could happen. [Other Info] * It will be better of the gnome-software / snap-store snap could be rebuilt after this is release (if they are build on focal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1868915] Re: [focal] nm-online -s --timeout=10 timeout every time
no activity for 2 years. ** Changed in: oem-priority Importance: Critical => Medium -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1868915 Title: [focal] nm-online -s --timeout=10 timeout every time Status in MAAS: Invalid Status in OEM Priority Project: New Status in network-manager package in Ubuntu: Triaged Bug description: Also created bug on upstream : https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/398 This issue will cause "NetworkManager-wait-online.service: Failed with result 'exit-code'." And cloud-init.service is counting on this service for network status. So this issue will finally cause MaaS deploying failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu1 [modified: lib/systemd/system/NetworkManager-wait-online.service] ProcVersionSignature: Ubuntu 5.4.0-1002.4-oem 5.4.8 Uname: Linux 5.4.0-1002-oem x86_64 ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 Date: Wed Mar 25 12:43:13 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200316-60+fossa-staging+X09 IfupdownConfig: source /etc/network/interfaces.d/*.cfg InstallationDate: Installed on 2020-03-25 (0 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200316-08:40 IpRoute: default via 192.168.101.1 dev eno1 proto static metric 100 10.101.46.0/24 via 192.168.101.1 dev eno1 proto static metric 200 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.101.0/24 dev eno1 proto kernel scope link src 192.168.101.85 metric 100 NetDevice.bonding_masters: Error: command ['udevadm', 'info', '--query=all', '--path', '/sys/class/net/bonding_masters'] failed with exit code 1: Unknown device "/sys/class/net/bonding_masters": No such device X: INTERFACE_MAC=Error: command ['cat', '/sys/class/net/bonding_masters/address'] failed with exit code 1: cat: /sys/class/net/bonding_masters/address: Not a directory SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-con: NAME UUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE FILENAME netplan-eno1 10838d80-caeb-349e-ba73-08ed16d4d666 ethernet 158577 廿廿年三月廿五日 (週三) 十二時39分37秒 yes 0 no /org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- /run/NetworkManager/system-connections/netplan-eno1.nmconnection nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected starting full enabled disabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1868915/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1875015] Re: Displaylink is extremely slow in Xorg sessions
** Tags added: jellyfish-edge-staging -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-video-amdgpu in Ubuntu. https://bugs.launchpad.net/bugs/1875015 Title: Displaylink is extremely slow in Xorg sessions Status in Nouveau Xorg driver: New Status in OEM Priority Project: New Status in xf86-video-amd: Fix Released Status in X.Org X server: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xserver-xorg-video-amdgpu package in Ubuntu: Fix Released Status in xserver-xorg-video-nouveau package in Ubuntu: In Progress Status in xorg-server source package in Focal: Fix Released Status in xorg-server source package in Hirsute: Won't Fix Status in xorg-server source package in Impish: Fix Released Status in xorg-server source package in Jammy: Fix Released Status in xserver-xorg-video-amdgpu source package in Jammy: New Status in xserver-xorg-video-nouveau source package in Jammy: New Bug description: Using ubuntu 20.04 on displaylink docking with external monitor is totally slow, unusable. The GUI responds very slow, if you click, the command of the click goes on after about 3 seconds... if you type, all the letters are with the same lag, so it is totally unusable. Was using displaylink without any problem on 19.10 until yesterday, when I upgraded to 20.04. It is terrific. If i plug out the usb for the displaylink docking station, than the speed is back, and the system is ok, if I connect it to the docking station again, everything extremely slow again. Please investigate this asap, as it is unusable on displaylink docking stations. To manage notifications about this bug go to: https://bugs.launchpad.net/nouveau/+bug/1875015/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1977790] Re: Window could be glitched with Intel + NVIDIA GPU laptops, and prime-select set to intel
** Changed in: oem-priority Importance: Undecided => High -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1977790 Title: Window could be glitched with Intel + NVIDIA GPU laptops, and prime- select set to intel Status in OEM Priority Project: New Status in firefox package in Ubuntu: New Bug description: [Summary] Firefox on Ubuntu 20.04 (99.0build2-0ubuntu0.20.04.2) window could be glitched with laptops with Intel + NVIDIA GPU, and prime-select set to intel. Either setting gfx.x11-egl-force-disabled to true in about:config, or setting prime-select to on-demand or nvidia, makes the issue unreproducible. Note that through nvidia-settings GUI, prime-select cannot be set to intel. Reproducibility: 1/8 [Reproduce Steps] 1. Run `sudo prime-select intel` in Terminal then reboot 2. Open Firefox window 3. Close Firefox window 4. Repeat until window is glitched (usually Firefox being transparent except the borders of the window) [Results] Expected: Firefox should not have its window glitched Actual: Firefox is glitched with window being transparent but the border, and every window on top of it draws on the Firefox window. Video attached. --- ProblemType: Bug AddonCompatCheckDisabled: False ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1753 F pulseaudio BuildID: 20220330194208 CasperMD5CheckResult: skip Channel: Unavailable DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-spearow-14p+X215 DistroRelease: Ubuntu 20.04 ForcedLayersAccel: False InstallationDate: Installed on 2022-05-25 (12 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 IpRoute: default via 10.102.142.1 dev enp0s31f6 proto dhcp metric 100 default via 10.102.136.1 dev wlp0s20f3 proto dhcp metric 600 10.102.136.0/22 dev wlp0s20f3 proto kernel scope link src 10.102.139.188 metric 600 10.102.142.0/23 dev enp0s31f6 proto kernel scope link src 10.102.142.246 metric 100 169.254.0.0/16 dev wlp0s20f3 scope link metric 1000 NoProfiles: True NonfreeKernelModules: nvidia_modeset nvidia Package: firefox 99.0+build2-0ubuntu0.20.04.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.14.0-1034.37-oem 5.14.21 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RunningIncompatibleAddons: False Tags: focal Uname: Linux 5.14.0-1034-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 05/16/2022 dmi.bios.release: 1.3 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.2 dmi.board.vendor: Dell Inc. dmi.chassis.asset.tag: RAID dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.2:bd05/16/2022:br1.3:svnDellInc.:pnPrecision3470:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr:sku0BC1: dmi.product.family: Precision dmi.product.name: Precision 3470 dmi.product.sku: 0BC1 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1977790/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962349] Re: Bolt doesn't work with native USB4 hosts
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bolt in Ubuntu. https://bugs.launchpad.net/bugs/1962349 Title: Bolt doesn't work with native USB4 hosts Status in OEM Priority Project: Fix Released Status in bolt package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in bolt source package in Focal: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux-oem-5.17 source package in Focal: Invalid Status in bolt source package in Impish: Fix Released Status in linux source package in Impish: Won't Fix Status in linux-oem-5.14 source package in Impish: Invalid Status in linux-oem-5.17 source package in Impish: Invalid Status in bolt source package in Jammy: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] * AMD Yellow Carp provides integrated USB4 host controllers * When plugging in a Thunderbolt3 or USB4 device, users are unable to authorize it using the GUI due to an error message: "parent not authorized, deferring" [Test Plan] AMD Yellow Carp Host (issue this bug is about) -- * Plug in USB4 device or TBT3 to AMD Yellow Carp host * Ensure that PCI topology has populated * Observe that /sys/bus/thunderbolt/devices/DEVICE/authorized is "0" * Try to run `boltctl enroll $UUID` Alpine Ridge / Titan Ridge host (discrete controller) -- Start out on a host with discrete controller (Alpine Ridge or Titan Ridge) 1. sudo boltctl forget -a 2. Plug in dock 3. Make sure 'boltctl list' enumerates dock. 4. Check /sys/bus/thunderbolt/devices/domain0/iommu_dma_protection (value dependent upon host) - If 0; try to manually enroll using 'boltctl enroll $UUID' - If 1; ensure that device automatically enrolled with bolt. GUI Check - Ensure that devices show up in the Settings GUI and are now able to authorize. Note: for AMD platforms enumerating PCIe devices is a separate problem from BOLT handled by kernel tasks. GUI check is only about "authorization". [Where problems could occur] * Intel USB4 or TBT3 hosts also use bolt. They could have a problem with the new version of bolt. * This is very unlikely however since there is a through test suite, and up until now the entire industry has been using bolt on Intel controllers for a long time. * There haven't been any significant bugs reported upstream or in Ubuntu since 0.9.1 release. [Other Info] * This bug also occurs on Intel controllers from ICL, TGL or ALD, but in many cases they are automatically authorized to an iommu DMA policy. * It is fixed in bolt 0.9.1 or later release. * To solve the SRU, will backport 0.9.1 release from Impish. * I did look into backporting just the commit(s) for fixing this, but it's not a trivial backport. Quoting the changelog (https://gitlab.freedesktop.org/bolt/bolt/-/blob/master/CHANGELOG.md): "Additionally the unique_id of said host controller changes with every boot, which breaks one of the fundamental assumptions in boltd". To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962349/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1968929] Re: Missing Wayland login option on NVIDIA systems
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems Status in OEM Priority Project: Fix Released Status in gdm3 package in Ubuntu: Fix Released Status in gdm3 source package in Jammy: Fix Released Bug description: Impact - Systems using Nvidia graphics drivers should have an option to use Wayland but Xorg should be the default. Hybrid systems using Nvidia graphics drivers should use Wayland by default. Test Case 1 --- Create a new user (since existing users can choose their own session). Restart your system after applying the update. Select your name on the login screen. A gear button should appear in the lower right of the screen. Click the gear button. Ubuntu should be selected. If you are using a system with only an Nvidia graphics card (so your system is not a hybrid), there should be an Ubuntu on Wayland option. Otherwise, there should be an Ubuntu on Xorg option. Test Case 2 --- Also verify that the behavior stays the same for systems that don't have Nvidia graphics. Create a new user (since existing users can choose their own session). Restart your system after applying the update. Select your name on the login screen. A gear button should appear in the lower right of the screen. Click the gear button. Ubuntu should be selected. There should also be an Ubuntu on Xorg option. What Could Go Wrong --- Hybrid systems should actually be using the Intel graphics for to run GNOME Shell so that's why it should be safe to use Wayland by default. There are some suspend & resume issues, an issue with gsync, etc. which is why Nvidia are requesting that we don't enable Wayland by default for systems that are only using the Nvidia graphics driver. We do still make it available in case someone really wants to try without needing to edit system files. Before last week, we were actually using Wayland by default for Nvidia systems so this upload returns most systems back to that status quo. Priority This is a high priority for the Desktop and OEM Teams and it's requested that this update be available as soon as possible after release. The desktop live session defaults to Xorg not Wayland so this doesn't impact that session at all. We are not going to delay the release to get this fix on the Ubuntu 22.04 desktop ISO. Original Bug Report --- I'm using Ubuntu 22.04 on a Dell G15 5511 laptop that have an NVIDIA 3060 GPU. I saw in the last update in the gdm3 package that Wayland will be disabled in machines with hybrid graphics. The question is: In this laptop I can enable optimus to use Intel and sometimes NVIDIA or keep only on NVIDIA (I use this option). So even it's detected two GPUs the Intel one is unused. I think the problem could extend for people with a desktop with an integrated intel GPU and a discrete NVIDIA GPU, since both will be present in the system. So maybe will be necessary to check with more accuracy to check if there are two GPUs, but only one is being used or have a documented option to force the enablement of Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957094] Re: on-demand mode doesn't work with nvidia-390
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1957094 Title: on-demand mode doesn't work with nvidia-390 Status in OEM Priority Project: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in ubuntu-drivers-common source package in Focal: Fix Released Status in nvidia-settings source package in Impish: Fix Released Status in ubuntu-drivers-common source package in Impish: Fix Released Status in nvidia-settings source package in Jammy: Fix Released Status in ubuntu-drivers-common source package in Jammy: Fix Released Bug description: [Impact] * In any Ubuntu series, if user using a old GPU (which supported by nvidia-390 only) then issuing glxinfo will get "Error: couldn't find RGB GLX visual or fbconfig". Which mean the Xorg doesn't load dri driver correctly. [Test Plan] * install nvidia-390 on nvidia-390 supported system. * prime-select on-demand * reboot * glxinfo * after applying this patch, it will fall back to "ON" mode after reboot. * install nvidia-450 on nvidia-450 supported system. * prime-select on-demand * reboot the system * prime-select query (and check that on-demand mode is still in use). [Where problems could occur] * Since nvidia-390 doesn't support on-demand mode (RTD3 either). If a user stays in on-demand mode with 390 without problem, the after upgrading u-d-c and reboot. The mode will fall back to "ON" mode. * From my point of view, it's fine because nvidia-390 doesn't support RTD3. Thus, the nvidia will always stay in "Active" stage no matter which mode it is. * While there is no way to inform the user about this change, changing to the only supported default will avoid breaking GLX. --- The regression from https://bugs.launchpad.net/ubuntu/+source/ubuntu- drivers-common/+bug/1942789. It impacts Jammy and Impish so far. [Steps to reproduce] 1. Find a GPU supports nvidia-390 2. ubuntu-drivers install nvidia:390 3. prime-select on-demand 4. glxinfo [Expected result] Shows intel or nvidia drives monitor [Actual result] Error: couldn't find RGB GLX visual or fbconfig Since we are all agree "on-demand" mode as default mode. Pre-talk with Alberto, on-demand doesn't support with nvidia-390 (no matter RTD3). We could consider to make it as performance mode and leave a note on nvidia-settings. I'll prepare some test packages. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1957094/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
** Changed in: oem-priority
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1967274
Title:
Screen sometimes can't update [Failed to post KMS update: CRTC
property (GAMMA_LUT) not found]
Status in Mutter:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in mutter package in Ubuntu:
Fix Released
Status in linux source package in Jammy:
Fix Released
Status in mutter source package in Jammy:
Fix Committed
Bug description:
Screen can't turn back on by clicking keyboard after screen off by meta + l
key.
Try to do VT switch can make the screen back, some error poped when I try to
wake up screen.
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: CRTC property (GAMMA_LUT) not
found
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[1666]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
GsettingsChanges:
b'org.gnome.shell' b'welcome-dialog-last-shown-version' b"'42.beta'"
b'org.gnome.desktop.input-sources' b'sources' b"[('xkb', 'us')]"
b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
b'org.gnome.desktop.privacy' b'report-technical-problems' b'true'
InstallationDate: Installed on 2022-03-31 (0 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326)
Package: gnome-shell 42~beta-1ubuntu3 [origin: unknown]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: wayland-session jammy third-party-packages
Uname: Linux 5.15.0-23-generic x86_64
UnreportableReason: This does not seem to be an official Ubuntu package.
Please retry after updating the indexes of available packages, if that does not
work then remove related third party packages and try again.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
==
SRU Justification
[Impact]
The backlight power won't come back after the meta + l to turn off the
display on ADL machines.
[Fix]
Below series of commits from v5.17 fix this issue
1c7ab5affa5e drm/i915/xelpd: Add Pipe Color Lut caps to platform config
17815f624a90 drm/i915/xelpd: Enable Pipe Degamma
e83c18cffaed drm/i915/xelpd: Enable Pipe color support for D13 platform
[Test]
Verified on at least 2 different machines, the backlight is on after the
screen dimmed with touchpad movement or key stroke.
[Where problems could occcur]
The patches only affect ADL-P and up.
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887910] Re: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1887910 Title: [bionic]blutoothd segfault when you cancel the keyboard pairing during the dialog for pairing code Status in OEM Priority Project: Fix Released Status in bluez package in Ubuntu: Fix Released Status in bluez source package in Bionic: In Progress Status in bluez source package in Eoan: Fix Released Status in bluez source package in Focal: Fix Released Status in bluez source package in Groovy: Fix Released Bug description: [Impact] This patch is for this issue: steps: 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. blutoothd segfault shows in dmesg after a while. 5. Bluetooth shows off on setting UI of right top corner. dmesg shows: [ 978.138593] bluetoothd[1569]: segfault at 0 ip 55564abe0a06 sp 7ffe4bec6410 error 4 in bluetoothd[55564ab77000+f3000] [Test Case] 1. pair bluetooth keyboard 2. see the dialog asking user input the code for pairing. 3. press "esc" to cancel it. 4. the bluetooth should still work to pair another bluetooth device. [Regression Potential] * This patch workaround the case that a queue node was created but not yet assigned function before user input pairing keycode. If the user cancel the paring before inputting pairing keycode then assign the function pointer a dummy 'direct_match'. * Bluetoothd responses to Bluetooth functions and "queue" is a shared common data structure, so in case of regression happens then blutoothd systemd service would be crashed. * We can verify this by operating add/remove BT devices to trigger queue operations. * I verified on target machine BIOS ID:0983 on BT mouse, keyboard, headset on pairing, remove and functionality checking. [Other Info] * NO. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1887910/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1920096] Re: Cursor bleeds on the platform with Mali armsoc driver
fix released in originated bug. ** Changed in: oem-priority/focal Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1920096 Title: Cursor bleeds on the platform with Mali armsoc driver Status in OEM Priority Project: Fix Released Status in OEM Priority Project focal series: Fix Released Status in xorg-server package in Ubuntu: Fix Released Status in xorg-server source package in Focal: Fix Released Bug description: [Impact] The cursor bleeds because of the bug in xorg which does not refresh the sprite background. (LP: #1911479) The issue happens to Xilinx zcu102/104/106 boards (arm64, mali gpu). [Test Case] Check if cursor is still bleeding with the patched xorg-server [ Regression potential ] The new function, miDCSaveUnderCursor2, is only used by Xilinx armsoc driver. It won't impact other platforms. --- Xilinx is trying to upstream the patch. It's still under review. https://lists.x.org/archives/xorg-devel/2021-March/058672.html To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1920096/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1896098] Re: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack
originate bug fixed ** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1896098 Title: Lenovo P1G3 - unable to select system speakers when headset plugged into audio jack Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Invalid Bug description: I suspect this is a pulseaudio or alsa bug. Our test team reported this: 1. Prepare Padme-3 machine and Install Ubuntu_20.04 OS . 2. Boot system. 3. Play audio or video file. 4. Open Settings > Sound. 5. Hot attach headset. 6. Notice that headset is selected as output device in sound settings and sound can be heard from headset => EXPECTED 7. While playback, select Internal Speaker as output device => KEYPOINT 9. Notice:SUT havo no sound from Internal Speakers => PROBLEM I was able to confirm this - it seems with the headphones connected that I can't select the system speakers. If I don't have headphones connected I can switch between dock audio and system speakers correctly - so it's just related to the audio jack Thanks Mark To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1896098/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908167] Re: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1908167 Title: [SRU] pulseaudio: the headset-mic or heapdhone-mic could not be selected automatically if there is no internal mic Status in HWE Next: New Status in OEM Priority Project: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Focal: Fix Released Status in pulseaudio source package in Groovy: Fix Released Status in pulseaudio source package in Hirsute: Fix Released Bug description: [Impact] On the Dell AIO machines, there is no internal mic, after plugging a headset, users expect the headset-mic or headphone-mic could be selected automatically. But with the current rule, the headset-mic/headphone-mic will not be selected automatically and even users manually select them, they will not show up in the gnome sound setting, and users could not record sound by headset-mic/headphone-mic. [Fix] backport a patch from pulseaudio mergerequest, the patch is going to be merged to pulseaudio 14.1. This patch could be backported to hirsute without any change, but need to be changed if backport it to groovy and focal. [Test] With the old pulseaudio (prior to 1:13.99.1-1ubuntu3.10), plugging in a headset to the problematic Dell AIO machine will not automatically select headset-mic/headphone-mic, and they also do not show up in Gnome sound settings, leading to failure to record any sound. With the new proposed package, on those Dell AIO, plug a headset, open the gnome sound setting, the headset-mic is selected automatically, use the headset-mic to record the sound, the sound could be recorded and the sound quality is good. [Where problems could occur] This patch could change the policy of audio device switching, it will not affect all audio devices, but only the devices which has AVAIL_UNKNOWN available status, that means it has possibility to introduce the regression on headphone-mic ,headset-mic, internal mic and internal speaker's switching since they all has AVAIL_UNKNOWN status. For example, after unpluging the headset, the input device will not switch to internal mic automatically or after unplug the headphone, the output device will not switch to internal speaker automatically. But this possibility is very low, we have tested the patch on many Dell and Lenovo machines, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908167/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967843] Re: cheese display corrupted under Ubuntu 22.04
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1967843 Title: cheese display corrupted under Ubuntu 22.04 Status in Cheese: Unknown Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: Triaged Status in clutter-gst-3.0 package in Ubuntu: Fix Committed Status in clutter-gst-3.0 source package in Jammy: In Progress Bug description: Impact == The cheese app is unusable with color bands showing in the main view. Test Case Install the update Run the cheese app Verify that the main view shows what your webcam can see normally. Click the camera button in the bottom toolbar area. Check if the photo looks normal. You can find it in ~/Pictures/Webcam What Could Go Wrong === Only 4 apps in Ubuntu use clutter-gst: empathy, cheese, lyricue, pinpoint clutter-gst has been archived by GNOME. (It's recommended for apps to use GTK4 instead of GTK3 + Clutter). That means it's not possible for this patch to be accepted upstream. Instead, distros like Arch Linux are applying this patch. This patch removes 2 renderers that don't work (RGBx and BGRx) but still keeps ones that do work: RGBA and BRGA. Original Bug Report === The cheese application produces a corrupted display under Ubuntu 22.04 with a Logitech C525 webcam. When started from the command line, cheese produces repeated warnings of the form... (cheese:4175): cheese-WARNING **: 05:15:48.706: A lot of buffers are being dropped.: ../libs/gst/base/gstbasesink.c(3143): gst_base_sink_is_too_late (): /GstCameraBin:camerabin/GstViewfinderBin:vf-bin/ClutterGstVideoSink:cluttergstvideosink0: There may be a timestamping problem, or this computer is too slow. Adding /etc/modprobe.d/uvcvideo.conf with 'options uvcvideo nodrop=1' doesn't solve the problem. This issue is not seen in either Ubuntu 21.10 or under Fedora-Workstation- Live-x86_64-36_Beta-1.4. The problem in Ubuntu 22.04 occurs under both Wayland and X11 displays with the Nvidia drivers. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: cheese 41.1-1build1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 5 05:15:35 2022 ExecutablePath: /usr/bin/cheese InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD ProcEnviron: SHELL=/bin/bash LANG=en_US.UTF-8 TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32 dmi.board.asset.tag: Default string dmi.board.name: X570 UD dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF32:bd01/18/2021:br5.17:svnGigabyteTechnologyCo.,Ltd.:pnX570UD:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnX570UD:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: X570 MB dmi.product.name: X570 UD dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu80 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-31 (4 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220326) MachineType: Gigabyte Technology Co., Ltd. X570 UD NonfreeKernelModules: nvidia_modeset nvidia Package: cheese 41.1-1build1 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 RelatedPackageVersions: cheese41.1-1build1 cheese-common 41.1-1build1 Tags: wayland-session third-party-packages jammy gstreamer-error Uname: Linux 5.15.0-25-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/18/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F32
[Desktop-packages] [Bug 1165609] Re: There is no apparent way to stop Orca
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-orca in Ubuntu. https://bugs.launchpad.net/bugs/1165609 Title: There is no apparent way to stop Orca Status in OEM Priority Project: Invalid Status in gnome-orca package in Ubuntu: Confirmed Bug description: The "Orca Screen Reader" icon in the Dash is a trap. If a user accidentally opens it, the only apparent recourse for the incessant jabber is to either mute the volume system-wide or log out. This makes for a very poor user experience. Orca could avoid this situation by providing at least one of the following: 1) A notification of how to stop it, if there is a way to stop it. 2) A confirmation prompt prior to starting. 3) A quit option in a standard location such as the indicator menu. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: gnome-orca 3.8.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.8.0-16.26-generic 3.8.5 Uname: Linux 3.8.0-16-generic x86_64 ApportVersion: 2.9.2-0ubuntu5 Architecture: amd64 Date: Sat Apr 6 18:35:02 2013 InstallationDate: Installed on 2013-04-06 (0 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130402.1) MarkForUpload: True PackageArchitecture: all ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-orca UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1165609/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969707] Re: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM).
just add "data-ciphers AES-128-CBC" into the config file, and then it will work. ** Changed in: oem-priority Status: New => Invalid ** Changed in: network-manager-openvpn (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969707 Title: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Status in OEM Priority Project: Invalid Status in network-manager-openvpn package in Ubuntu: Invalid Bug description: Try to enable vpn, but the vpn is not able to enable. The config file under /etc/NetworkManager input a deprecated option. Try to change cipher to data-cipher, the network can be enabled successfully. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:19:15 2022 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
I commented on the upstream bug. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in OEM Priority Project: New Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
** Tags added: wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in OEM Priority Project: New Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966629] Re: swipe up from the bottom of the touch monitor won't bring the OSK
** Tags added: wayland-session ** Tags removed: wayland-session ** Tags added: wayland -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the bottom of the touch monitor won't bring the OSK Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the bottom of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend Status in GNOME Shell: Unknown Status in Mutter: Unknown Status in OEM Priority Project: Confirmed Status in gnome-shell package in Ubuntu: Triaged Status in mutter package in Ubuntu: Triaged Status in nvidia-graphics-drivers-440 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-460 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-470 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-510 package in Ubuntu: Triaged Bug description: [Impact] The Nvidia driver corrupts and/or forgets its textures when resuming from suspend, by design. Documented here: https://www.khronos.org/registry/OpenGL/extensions/NV/NV_robustness_video_memory_purge.txt Although it's so awkward to implement everywhere that realistically compositors will never support it fully. Instead we're waiting for an Nvidia driver fix. *NOTE* that this is actually not a common problem because the system must be using Nvidia as the primary GPU to be affected. So generally only desktop users will encounter the bug, not laptops. And even then, only desktops that use suspend/resume and VT switching may trigger it, if ever. Even in development the bug cannot be reproduced reliably. [Workarounds] * Always log into a Xorg session and if corruption occurs then type: Alt+F2, R, Enter * https://download.nvidia.com/XFree86/Linux-x86_64/510.54/README/powermanagement.html#PreserveAllVide719f0 [Test Plan] [Where problems could occur] [Original Bug Report] I recently installed ubuntu 20.04 on my computer, and I am running into an issue when I do the following: * Login with a user on desktop * Select switch user, and login as second user * Switch user again, and return to original user At this point, text and icons in the menubar / sidebar are corrupted. Text and icons in normal windows appear correctly. I have attached a screenshot of what this looks like. Screenshots: https://imgur.com/a/3ZFDLMc ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..09.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:09:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun May 3 18:12:45 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP104 [GeForce GTX 1070] [1043:85a0] InstallationDate: Installed on 2020-05-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Gigabyte Technology Co., Ltd. AX370-Gaming ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-28-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/19/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F3 dmi.board.asset.tag: Default string dmi.board.name: AX370-Gaming-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: se1 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF3:bd06/19/2017:svnGigabyteTechnologyCo.,Ltd.:pnAX370-Gaming:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAX370-Gaming-CF:rvrse1:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AX370-Gaming dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1
[Desktop-packages] [Bug 1969707] Re: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM).
** Also affects: oem-priority Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1969707 Title: DEPRECATED OPTION: --cipher set to 'AES-128-CBC' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Status in OEM Priority Project: New Status in network-manager-openvpn package in Ubuntu: New Bug description: Try to enable vpn, but the vpn is not able to enable. The config file under /etc/NetworkManager input a deprecated option. Try to change cipher to data-cipher, the network can be enabled successfully. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: network-manager-openvpn 1.8.18-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Apr 21 10:19:15 2022 InstallationDate: Installed on 2022-04-21 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969707/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962277] Re: To support Synaptics fp device
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device Status in OEM Priority Project: Fix Released Status in libfprint package in Ubuntu: Fix Released Status in libfprint source package in Focal: Fix Released Status in libfprint source package in Impish: Fix Released Status in libfprint source package in Jammy: Fix Released Bug description: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/4d5e2775b23a65b6b7b41eb98fa5b2c68a805f33 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/128d809227bbef1d3bd8e7c7e1f9b68a335db252 https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3fb8860dc487568518d69e9074135041296d1e75 This ID is included in upstream. [Impact] * Devices have synaptics fingerprint component will get supported. * Supported list. [06cb:0100] [06cb:00f0] [06cb:0103] [06cb:0123] [06cb:0126] [06cb:0129] [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be more synaptics devices get supported. * 0xE7 is removed by Synaptics, so the user who is using this device will not be supported. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
Yes, it's not working in Wayland mode, and that's the issue. I don't know if gnome/nautilus have this feature (dnd file to move it by using touch monitor) Maybe it's not and just happened to partially work on x11 mode (if you check the video I upload, which is x11 mode) If gnome/nautilus does not have this feature, I think this is a good feature to have. (May need to think the proper way to) For the context menu in Wayland mode for the directory, I create lp:1964091. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
The output of "dpkg -l" as capture video in #2. ** Attachment added: "dpkg-l" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1966635/+attachment/5574005/+files/dpkg-l -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] Re: can't move file/directory by drag and drop by using touch monitor
video captured as running jammy, updated @ 2022/03/29, x11 mode. (can't drag and drop the file to move it around in Wayland mode) To move a file by drag and drop, need to move fast. If you check the video, if the finger moves too slow, it will show the context menu, and no longer be able to move the file around. ** Attachment added: "IMG_9158.mp4" https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1966635/+attachment/5573998/+files/IMG_9158.mp4 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: Incomplete Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965648] Re: Autorotate initiates but doesn't reset in Wayland sessions (Xorg sessions work fine)
** Tags added: 2-in-1 oem-priority
** Also affects: oem-priority
Importance: Undecided
Status: New
** Changed in: oem-priority
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1965648
Title:
Autorotate initiates but doesn't reset in Wayland sessions (Xorg
sessions work fine)
Status in Mutter:
Unknown
Status in OEM Priority Project:
New
Status in mutter package in Ubuntu:
Confirmed
Bug description:
In jammy I can get mutter's auto-rotate to switch to portrait mode
("right-up") by rotating the device (this only worked in impish if I
installed the autorotate gnome-shell extension).
However, putting it back into "normal" orientation doesn't put the
screen back in landscape mode. Flipping it around ("left-up") does
swap to the reverse portrait mode, but still can't get back to
"normal" afterward.
running `monitor-sensor` does show the accelerometer orientation
change events (including the "normal" ones) triggering properly, just
the desktop doesn't respond.
Plugging in an external monitor does seem to trigger the desktop to go
back to normal landscape mode.
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: mutter 42~beta-1ubuntu2
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
Uname: Linux 5.15.0-23-generic x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: GNOME
Date: Sat Mar 19 15:41:42 2022
InstallationDate: Installed on 2019-08-17 (945 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190305.1)
SourcePackage: mutter
UpgradeStatus: Upgraded to jammy on 2022-03-18 (1 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/mutter/+bug/1965648/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966637] Re: don't have good text copy method like on android / ios as using touch monitor, firefox
** Summary changed: - don't have good text copy method like on android / ios as using touch monitor + don't have good text copy method like on android / ios as using touch monitor, firefox ** Summary changed: - don't have good text copy method like on android / ios as using touch monitor, firefox + don't have good text copy method like on android / ios as using touch monitor, firefox snap -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966637 Title: don't have good text copy method like on android / ios as using touch monitor, firefox snap Status in OEM Priority Project: New Status in firefox package in Ubuntu: New Bug description: don't have a good text copy method like on android/ios as using a touch monitor OS: jammy update @ 2022/03/28 firefox snap: 98.0.2-1 r1154 it's not good on URL entry or text entry box on the HTML page. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966628] Re: touch on any place that can do text entry won't trigger OSK, libreoffice
** Summary changed: - touch on anyplace that can do text entry won't trigger OSK + touch on any place that can do text entry won't trigger OSK, libreoffice -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1966628 Title: touch on any place that can do text entry won't trigger OSK, libreoffice Status in OEM Priority Project: New Status in libreoffice package in Ubuntu: New Bug description: OS: jammy (fully updated on 2022/03/28) Libreoffice version: 1:7.3.2~rc1~0ubuntu2 Mode: wayland Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966642] [NEW] won't rotate back to landscape as come back to laptop mode
Public bug reported: For a 2-in-1 machine, as we flip more than 180 degrees between monitor and keyboard, then it goes to tablet mode. In table mode, if the orientation sensor is there, the monitor orientation will automatically rotate as we rotate the machine. As we flip the machine back to less than 180 degrees, in most cases, the user will want the monitor orientation to rotate back to landscape mode. It's not now per test on jammy update 2022/03/28, Wayland mode. gnome-shell version: 42~beta-1ubuntu3 ** Affects: oem-priority Importance: Wishlist Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 2-in-1 jammy oem-priority ** Description changed: For a 2-in-1 machine, as we flip more than 180 degrees between monitor and keyboard, then it goes to table mode. In table mode, if the orientation sensor is there, the monitor orientation will automatically rotate as we rotate the machine. - As we flip the machine back to less than 180 degrees, in most case, the + As we flip the machine back to less than 180 degrees, in most cases, the user will want the monitor orientation to rotate back to landscape mode. - It's not now per test on jammy update 2022/03/28, + It's not now per test on jammy update 2022/03/28, Wayland mode. gnome-shell version: 42~beta-1ubuntu3 ** Description changed: For a 2-in-1 machine, as we flip more than 180 degrees between monitor - and keyboard, then it goes to table mode. + and keyboard, then it goes to tablet mode. In table mode, if the orientation sensor is there, the monitor orientation will automatically rotate as we rotate the machine. As we flip the machine back to less than 180 degrees, in most cases, the user will want the monitor orientation to rotate back to landscape mode. It's not now per test on jammy update 2022/03/28, Wayland mode. gnome-shell version: 42~beta-1ubuntu3 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Wishlist ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966642 Title: won't rotate back to landscape as come back to laptop mode Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: For a 2-in-1 machine, as we flip more than 180 degrees between monitor and keyboard, then it goes to tablet mode. In table mode, if the orientation sensor is there, the monitor orientation will automatically rotate as we rotate the machine. As we flip the machine back to less than 180 degrees, in most cases, the user will want the monitor orientation to rotate back to landscape mode. It's not now per test on jammy update 2022/03/28, Wayland mode. gnome-shell version: 42~beta-1ubuntu3 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825299] Re: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard
Yes, I think it's fixed in jammy, update status as is. ** Changed in: oem-priority Status: New => Fix Released ** Changed in: gnome-shell (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825299 Title: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard Status in GNOME Shell: New Status in OEM Priority Project: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Focal: Triaged Bug description: I use a XPS 13 9380 laptop with Disco. The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard. To add this, will be a good user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966629] Re: swipe up from the bottom of the touch monitor won't bring the OSK
** Summary changed: - swipe up from the bottom of the touch monitor + swipe up from the bottom of the touch monitor won't bring the OSK -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the bottom of the touch monitor won't bring the OSK Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the bottom of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966629] Re: swipe up from the buttom of the touch monitor
Yes, typo updated ** Summary changed: - swipe up from the button of the touch monitor + swipe up from the buttom of the touch monitor ** Description changed: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK - 3. swipe up from the button of the touch monitor + 3. swipe up from the bottom of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. ** Summary changed: - swipe up from the buttom of the touch monitor + swipe up from the bottom of the touch monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the bottom of the touch monitor Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the bottom of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825297] Re: When OSK is present, typing on physical keyboard usually does not trigger the OSK to disappear (X11 only)
Per test on jammy, update on 2022/03/28, can also reproduce this issue in Wayland mode. Well, hard to say if this is good or bad behavior. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825297 Title: When OSK is present, typing on physical keyboard usually does not trigger the OSK to disappear (X11 only) Status in GNOME Shell: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Disco: Won't Fix Status in gnome-shell source package in Eoan: Won't Fix Status in gnome-shell source package in Focal: Triaged Bug description: I use a XPS 13 9380 laptop with Disco. When On-Screen-Keyboard is present, typing on physical keyboard usually doesn't trigger the OSK to disappear. The problem only happen on X11 not on Wayland. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825297/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966637] [NEW] don't have good text copy method like on android / ios as using touch monitor
Public bug reported: don't have a good text copy method like on android/ios as using a touch monitor OS: jammy update @ 2022/03/28 firefox snap: 98.0.2-1 r1154 it's not good on URL entry or text entry box on the HTML page. ** Affects: oem-priority Importance: Wishlist Status: New ** Affects: firefox (Ubuntu) Importance: Undecided Status: New ** Tags: 2-in-1 oem-priority ** Tags added: 2-in-1 ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Wishlist ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1966637 Title: don't have good text copy method like on android / ios as using touch monitor Status in OEM Priority Project: New Status in firefox package in Ubuntu: New Bug description: don't have a good text copy method like on android/ios as using a touch monitor OS: jammy update @ 2022/03/28 firefox snap: 98.0.2-1 r1154 it's not good on URL entry or text entry box on the HTML page. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966637/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966635] [NEW] can't move file/directory by drag and drop by using touch monitor
Public bug reported: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland ** Affects: oem-priority Importance: Wishlist Status: New ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: 2-in-1 jammy oem-priority ** Tags added: 2-in-1 jammy ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Wishlist ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1966635 Title: can't move file/directory by drag and drop by using touch monitor Status in OEM Priority Project: New Status in nautilus package in Ubuntu: New Bug description: Can't move file/directory by drag and drop by using a touch monitor OS: 22.04, up to date @ Mar 28, 2022. nautilus: 1:42~rc-1-ubuntu1 mode: wayland To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in OEM Priority Project: New Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966629] [NEW] swipe up from the button of the touch monitor
Public bug reported: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the button of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: 2-in-1 jammy oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the button of the touch monitor Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: OS: jammy update on 2022/03/28, Wayland mode, tablet or screen keyboard enable. Steps: 1. touch gnome-terminal and see OSK 2. hide OSK 3. swipe up from the button of the touch monitor Expected: OSK re-appears Actually: OSK does not re-appear. Is this by a design change, or a new bug? On focal, can't reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1914226] Re: Add option to enable screen-keyboard icon for panel
** Tags added: 2-in-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914226 Title: Add option to enable screen-keyboard icon for panel Status in gnome-shell package in Ubuntu: Triaged Bug description: Add option to enable screen-keyboard icon for panel - it help users to open screen keyboard only when necessary, not everytime when touch on text field or typing field. - furthermore sometimes we tap on certain areas for drag, move windows etc that may related to input fields and screen keyboard appear such times - Even if user mistake touch on certain areas and some third-party application then that gives trouble (Currently if enable it through universal access > screen keyboard then it makes quite annoying once again due pop up often) https://gitee.com/mHatsune/chaya/raw/master/disk/screenkeyboard.png To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1831039] Re: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome
per test on jammy updated on 2022/03/28, wayland mode, OSK works fine with firefox snap (v98.0.2-1, r1154) ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: 2-in-1 ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1831039 Title: When using Wayland, the onscreen keyboard does not open in text inputs for non-GTK applications such as Firefox or Chrome Status in OEM Priority Project: New Status in chromium-browser package in Ubuntu: Confirmed Status in firefox package in Ubuntu: Confirmed Status in gnome-shell package in Ubuntu: Confirmed Status in qtbase-opensource-src package in Ubuntu: Confirmed Bug description: When using wayland - onscreen keyboard not open in text inputs in many applications such as firefox or chrome. Ubuntu 18.04 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2015-06-09 (1455 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) Package: gnome-shell 3.28.3+git20190124-0ubuntu18.04.2 PackageArchitecture: amd64 ProcEnviron: LANG=cs_CZ.UTF-8 TERM=xterm-256color SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18 Tags: third-party-packages bionic Uname: Linux 4.15.0-50-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-05-31 (368 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825299] Re: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard
Re-test on a 2-in-1, wayland mode, Ubuntu jammy, tablet mode (flip more than 180 degrees between monitor and keyboard move focus to somewhere non-input, the OSK will disappear. ** Tags added: 2-in-1 ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825299 Title: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard Status in GNOME Shell: New Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: Triaged Status in gnome-shell source package in Bionic: Triaged Status in gnome-shell source package in Focal: Triaged Bug description: I use a XPS 13 9380 laptop with Disco. The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard. To add this, will be a good user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1854222] Re: Screen keyboard improperly appears on laptops with touchscreen
** Tags added: 2-in-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854222 Title: Screen keyboard improperly appears on laptops with touchscreen Status in gnome-shell package in Ubuntu: New Bug description: Release: Ubuntu 18.04.3 LTS gnome-shell version 3.28.4-0ubuntu18.04.2 Directions to produce bug: * Install Ubuntu 18.04 onto a laptop with a touchscreen. * Install uxterm package. * Upgrade software packages to most recent version. * Confirm "Screen Keyboard" and "Typing Assist" are disabled in Universal Access. * Reboot. * Log in and start "uxterm". * Switch focus to another window. * Touch the "uxterm" window. Expected proper behavior: "uxterm" window gets focus, no other actions. Actual inappropriate behavior: "uxterm" window gets focus, and screen keyboard appears in defiance of "Screen Keyboard: off" setting and presence of undetachable physical keyboard. Empirical testing indicates that the screen keyboard doesn't appear for every touch, but seems to appear for every touch to any area that accepts text input, or perhaps for all areas that aren't internally marked somehow as not accepting text. This is a reappearance of Bug #1723857. The reappearance was noted in comments 61 and 62 of that bug, but apparently ignored because the bug is closed. I am creating this as a new bug per the guidance in 1723857#60: "This bug is closed so if you experience any problem at all then please open a new one." by Daniel van Vugt (vanvugt). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854222/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966628] [NEW] touch on anyplace that can do text entry won't trigger OSK
Public bug reported: OS: jammy (fully updated on 2022/03/28) Libreoffice version: 1:7.3.2~rc1~0ubuntu2 Mode: wayland Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) ** Affects: oem-priority Importance: Undecided Status: New ** Affects: libreoffice (Ubuntu) Importance: Undecided Status: New ** Tags: 2-in-1 oem-priority ** Also affects: oem-priority Importance: Undecided Status: New ** Tags added: 2-in-1 ** Description changed: OS: jammy (fully updated on 2022/03/28) version: 1:7.3.2~rc1~0ubuntu2 mode: wayland - Screen Keyboard: On gnome-settings, goes Accessibility, goes Typing. - - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. + Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. + - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) ** Tags added: oem-priority ** Description changed: OS: jammy (fully updated on 2022/03/28) - version: 1:7.3.2~rc1~0ubuntu2 - mode: wayland + Libreoffice version: 1:7.3.2~rc1~0ubuntu2 + Mode: wayland Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/1966628 Title: touch on anyplace that can do text entry won't trigger OSK Status in OEM Priority Project: New Status in libreoffice package in Ubuntu: New Bug description: OS: jammy (fully updated on 2022/03/28) Libreoffice version: 1:7.3.2~rc1~0ubuntu2 Mode: wayland Screen Keyboard: On gnome-control-center, goes Accessibility, goes Typing. - or, on a 2-in-1 machines, flip more than 180 degree between keyboard and monitor. Touch any place that can do text input, can't see OSK appears. (OSK appears properly as touch on gnome-terminal) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
Hmm, weird that I can't reproduce this issue now. I'll set this to in- complete temporary. Btw, I try to add nomodeset to booting parameter, and I found that I can't run in Wayland mode. It's only x11 mode (and the icon to select between wayland and x11 mode is not there) ** Changed in: ibus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: Incomplete Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] Re: ibus input method not working
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1966356] [NEW] ibus input method not working
Public bug reported: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. ** Affects: ibus (Ubuntu) Importance: Undecided Status: New ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, then it works. ** Description changed: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. - Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, by modify /usr/lib/systemd/user/gnome-session.target.wants/org.freedesktop.IBus.session.GNOME.service, + Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. + + Note: per test, add --xim works for below cases: + + 1. x11 mode + 2. Wayland mode, x11 client, test by using microsoft edge. + 3. Wayland mode, Wayland client, tested by using gnome-terminal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1966356 Title: ibus input method not working Status in ibus package in Ubuntu: New Bug description: per test on jammy, config traditional Chinese and input method as ibus Chinese input method not working. Per check around, found that just force add "--xim" to /usr/bin/ibus-daemon, then it works. Note: per test, add --xim works for below cases: 1. x11 mode 2. Wayland mode, x11 client, test by using microsoft edge. 3. Wayland mode, Wayland client, tested by using gnome-terminal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1966356/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964923] Re: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages'
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1964923 Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' Status in OEM Priority Project: New Status in ubuntu-drivers-common package in Ubuntu: Confirmed Status in update-notifier package in Ubuntu: Confirmed Status in ubuntu-drivers-common source package in Jammy: Confirmed Status in update-notifier source package in Jammy: Confirmed Bug description: This bug occurred after install of Ubuntu Mate Jammy daily ISO 15-03-2022 Test machine Dell Optiplex 7060 in UEFI+secure boot mode. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: update-notifier-common 3.192.51 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Uname: Linux 5.15.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE Date: Tue Mar 15 10:21:14 2022 ExecutablePath: /usr/lib/update-notifier/list-oem-metapackages InstallationDate: Installed on 2022-03-15 (0 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220315) InterpreterPath: /usr/bin/python3.10 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/lib/update-notifier/list-oem-metapackages Python3Details: /usr/bin/python3.10, Python 3.10.2, python3-minimal, 3.10.1-0ubuntu1 PythonArgs: ['/usr/lib/update-notifier/list-oem-metapackages'] PythonDetails: N/A SourcePackage: update-notifier Title: list-oem-metapackages crashed with AttributeError in packages_for_modalias(): 'Cache' object has no attribute 'packages' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1964923/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
Yes, it is. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
I was testing in Wayland. Just test under X11, slightly better, but still not useable. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor
** Summary changed: - long touch/press a director won't trigger the context menu like file on empty space. on touch monitor + long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a directory won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format
cheese version 41 is release at 2021-Nov-15, https://download.gnome.org/sources/cheese/41/ quick check r40, it contains those patch in #6. and jammy have version 41.1-1 Given so, close this one. ** Changed in: oem-priority Status: Confirmed => Fix Released ** Changed in: cheese (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: Fix Released Status in cheese package in Ubuntu: Fix Released Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a director won't trigger the context menu like file on empty space. on touch monitor
** Tags added: 2-in-1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a director won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] Re: long touch/press a director won't trigger the context menu like file on empty space. on touch monitor
** Description changed: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 + mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a director won't trigger the context menu like file on empty space. on touch monitor Status in Nautilus: Unknown Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 mode: wayland With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964091] [NEW] long touch/press a director won't trigger the context menu like file on empty space. on touch monitor
Public bug reported: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Summary changed: - long touch/press a director won't trigger the context menu like file on empty space + long touch/press a director won't trigger the context menu like file on empty space. on touch monitor -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1964091 Title: long touch/press a director won't trigger the context menu like file on empty space. on touch monitor Status in nautilus package in Ubuntu: New Bug description: Long press/touch a directory won't trigger the context menu for it. OS: 22.04, up to date @ Mar 8, 2022. nautilus: 1:42~beta-1ubuntu1 With a touch monitor, it will be useful if we can do more operation with it. If I long press a file (for about 1 second), a context menu will appear just like we right-click mouse button on it. Then we can do file deleting, copy and move. We can also do the same as we long touch the empty space, and then we can create directory, etc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1964091/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958488] Re: [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia driver probe
** Summary changed:
- [nvidia][xorg] display hangs on boot LOGO
+ [nvidia][xorg] display hangs on boot LOGO due to race of gdm and nvidia
driver probe
** Tags added: gdm3
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in Ubuntu.
https://bugs.launchpad.net/bugs/1958488
Title:
[nvidia][xorg] display hangs on boot LOGO due to race of gdm and
nvidia driver probe
Status in OEM Priority Project:
Confirmed
Status in gdm3 package in Ubuntu:
New
Status in ubuntu-drivers-common package in Ubuntu:
In Progress
Status in gdm3 source package in Focal:
New
Status in ubuntu-drivers-common source package in Focal:
In Progress
Status in gdm3 source package in Impish:
New
Status in ubuntu-drivers-common source package in Impish:
In Progress
Bug description:
[Impact]
* In Ubuntu 20.04 (either impish, jammy, upstream gdm) (which using Xorg
with proprietary nvidia driver), in some cases, the nvidia driver will probe
later than launching gdm.
* If above race condition happens in iGPU + nvidia cases and monitor
connects to dGPU, which will cause gdm starts with wayland as opposed to Xorg.
Which may lead the monitor stuck in black-screen or boot LOGO.
[Test Plan]
* The environment:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary
nvidia driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
* Setup a cronjob,
e.g. @reboot /home/u/test.sh
* Have a test script in something like /home/u/test.sh as
#!/bin/bash
sleep 20
count="$(cat /home/ubuntu/count)"
count=$((count+1))
echo $count | tee /home/ubuntu/count
journalctl -b | grep -q -i wayland || sudo reboot
* the system will probably stuck in black-screen or boot LOGO.
* Before applying the fix, the fail rate is 6/24 (fail 6 time in 24 runs).
* After applying the fix, it got pass within 1000+ reboot cycles.
* Test PPA can be found here
https://launchpad.net/~os369510/+archive/ubuntu/lp1958488
[Fix]
* The patch makes gpu-manager to probe nvidia (if needed) first and waiting
for the /run/u-d-c-nvidia-drm-was-loaded be touched by
71-u-d-c-gpu-detection.rules.
* Also, the gdm is using 61-gdm.rules to configure the gdm mode by checking
the nvidia driver presents or not.
* gpu-manager is before display-manager. Thus, gpu-manager will wait for
nvidia uevent be processed and then continue to work. When gdm be launched, the
targeted nvidia uevent has been processed already.
(71-u-d-c-gpu-detection.rules is later than 61-gdm.rules）
[Where problems could occur]
* there is not potential regression from my mind but it will lead the boot
time be longer.
* In my test cycles, it leads extra 0~1000ms in boot time. Usually, 0~200ms.
Worst case, over 1 s in 8xx runs (of 1000).
* I think the stability is important than performance in this case.
[Other Info]
* For non-ubuntu-desktop (which doesn't have gpu-manager), which using gdm
will meet this issue still. The other potential fix (from either gdm or logind)
is under discussion in
https://gitlab.gnome.org/GNOME/gdm/-/issues/763#note_1385786.
* u-d-c upstream fix:
https://github.com/tseliot/ubuntu-drivers-common/pull/67
---
Test environment/steps:
1. A desktop or workstation which containing an iGPU.
2. Plug a nvidia graphic card to the system and installing proprietary nvidia
driver (470 in my case)
3. Attach a monitor to dGPU and leave iGPU connect to nothing.
(in my test environment, there is the other ethernet card and TBT4 cards)
4. Reboot system.
Based on:
$ cat /lib/udev/rules.d/61-gdm.rules
# disable Wayland on Hi1710 chipsets
ATTR{vendor}=="0x19e5", ATTR{device}=="0x1711",
RUN+="/usr/lib/gdm3/gdm-disable-wayland"
# disable Wayland when using the proprietary nvidia driver
DRIVER=="nvidia", RUN+="/usr/lib/gdm3/gdm-disable-wayland"
It will disable wayland by default if proprietary nvidia driver load.
But in some race condition cases, the nvidia probe is later than gnome
launches. (The fail rate is 6/24.)
Thus, ubuntu-gdm has a fix for Bug#1794280 to add
"ExecStartPre=@libexecdir@/gdm-wait-for-drm".
The gdm-wait-for-drm is intend to make sure all drm udev devices
enumerated before launching gdm.
It rely on at least one "master-of-seat" graphic card for gdm but it's not
rigorous enough.
Since most of graphic cards are own "master-of-seat"[1].
In my case, it detects the iGPU is probed but dGPU.
However, the display is attached to dGPU.
We need to make sure the targeted gpu (connecting to monitor) is probe
before launching gdm.
debian bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1004131
upstream bug: https://gitlab.gnome.org/GNOME/gdm/-/issues/763
[1]
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
** Changed in: oem-priority
Importance: Undecided => High
** Changed in: oem-priority
Assignee: (unassigned) => Yao Wei (medicalwei)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status in iio-sensor-proxy package in Ubuntu:
Fix Committed
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1292041] Re: Lockscreen doesn't turn off the screen
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen Status in OEM Priority Project: Fix Released Status in OEM Priority Project trusty series: Fix Released Status in Unity: Fix Released Status in gnome-screensaver package in Ubuntu: Invalid Status in unity package in Ubuntu: Fix Released Bug description: [ATTENTION] This bug report is strictly for lockscreen. When user activates lockscreen with Ctrl+Alt+L or Super+L shortcut or from indicator-session the screen should blank off after a couple seconds. The new Unity lock screen doesn't turn off the monitor screen. I can wait as long as 10 minutes after activating the lock screen and the monitor still doesn't turn off. Then when I unlock the screen and don't use mouse or keyboard monitor will turn off (it's about 5 seconds after unlocking). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 49579] Re: screen doesn't lock when some menu is open
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open Status in GNOME Screensaver: Expired Status in OEM Priority Project: Won't Fix Status in OEM Priority Project precise series: Won't Fix Status in Unity: Triaged Status in Unity 7.2 series: Triaged Status in X.Org X server: Invalid Status in gnome-screensaver package in Ubuntu: Triaged Status in gnome-shell package in Ubuntu: Confirmed Status in unity package in Ubuntu: Triaged Status in gnome-screensaver source package in Precise: Won't Fix Status in gnome-shell source package in Precise: Confirmed Status in unity source package in Precise: Won't Fix Status in gnome-screensaver source package in Xenial: Triaged Status in gnome-shell source package in Xenial: Confirmed Status in unity source package in Xenial: Triaged Status in xorg-server package in Debian: Confirmed Bug description: Binary package hint: gnome-screensaver I'm running a fresh install of Dapper with screensaver set to 'blank screen', and 'lock screen when screensaver is active' enabled. If a panel menu (e.g. Applications) is open and the machine is left idle, the screen fails to lock. It fades out after the time period as expected, but the desktop reappears after a few seconds. Ben (comments / criticism welcome, this is my first bug report) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1963628] Re: Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
** Also affects: oem-priority
Importance: Undecided
Status: New
** Tags added: oem-priority
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to iio-sensor-proxy in Ubuntu.
https://bugs.launchpad.net/bugs/1963628
Title:
Force IIO_SENSOR_PROXY_TYPE to iio-buffer-als for some Dell models
Status in OEM Priority Project:
New
Status in iio-sensor-proxy package in Ubuntu:
Fix Committed
Bug description:
We are encountering issues, that when enabling some Dell laptops, the readings
from iio-poll-als are unstable, or could freeze on certain value. On these
systems they have ENV{IIO_SENSOR_PROXY_TYPE}="iio-poll-als iio-buffer-als",
and
removing iio-poll-als makes reading stable.
This adds workaround to the affected Dell laptop models which may equip with
ALS.
[Impact]
* Only models matching the same device BIOS IDs are affected.
[Test Plan]
* Pick devices which BIOS IDs are listed in the patch, and test
whether it's ambient light sensors are working properly without
unexpected brightness flickers.
[Where problems could occur]
* Machines matching the same BIOS ID, either having ALS built-in or
not, but attached ambient light sensors externally (for example,
ColorHug ALS) might experience failures.
[Other Info]
* Upstream merge request:
https://gitlab.freedesktop.org/hadess/iio-sensor-proxy/-/merge_requests/352
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1949621] Re: modemmanager/libmbim cannot make use of Quectel EM120
For Today, the version of MondemManager in jammy 1.18.6 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to modemmanager in Ubuntu. https://bugs.launchpad.net/bugs/1949621 Title: modemmanager/libmbim cannot make use of Quectel EM120 Status in libmbim package in Ubuntu: New Status in modemmanager package in Ubuntu: New Bug description: As reported on https://gitlab.freedesktop.org/mobile- broadband/ModemManager/-/issues/402, this modem (shipped in many new Lenovo ThinkPad laptops) requires some specific handling as others new modems to performs FCC unlock procedure. A fix has been merged upstream: https://gitlab.freedesktop.org/mobile- broadband/libmbim/-/merge_requests/125/diffs Can we expect to see that merged in the current Ubuntu 21.10 ? I understand it might require a backport, since they merged it against 1.26 and it does not seems to apply cleanly on 1.24. I also suspect upgrading libmbim to 1.26 is not acceptable for impish release. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1949621/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
saw the new libgusb goes to jammy channel. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
I test the libgusb from jammy-proposed, and it fixed this issue on a machine that previously can reliably reproduce this issue. Guess it's on it's way to jammy or jammy-update channel. ** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: Fix Released Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Fix Released Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
debian sid now has libgusb version 0.3.10. And it's in jammy-proposed now. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libgusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: Invalid Status in libgusb package in Ubuntu: Confirmed Status in libusb package in Ubuntu: Invalid Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960768] Re: fwupd crash on stop
** Also affects: libusb (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libusb in Ubuntu. https://bugs.launchpad.net/bugs/1960768 Title: fwupd crash on stop Status in OEM Priority Project: In Progress Status in fwupd package in Ubuntu: New Status in libusb package in Ubuntu: New Bug description: I can reproduce crash with a similar stack as below as I stop fwupd service. https://errors.ubuntu.com/problem/4bfcf571c017010afe4775687ff2a9ca7ff79661 also test fwupd 1.7.5 (https://launchpad.net/~ycheng-twn/+archive/ubuntu/fwupd175) still can reproduce this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1960768/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959362] Re: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode)
** Tags added: oem-priority -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1959362 Title: "Launch using dedicated graphics card" option absent (nvidia, proprietary drivers, on-demand PRIME mode) Status in OEM Priority Project: New Status in gnome-shell package in Ubuntu: New Bug description: Device: Dell Precision 5500 with discrete nvidia Quadro T1000 Mobile GPU Image: Jammy daily (20220126 build) Test steps == Secure Boot enabled Installation options: - used ubiquity (not the new flutter installer) - normal installation - checked "Install third-party software for graphics and Wi-Fi hardware and additional media formats" - left "Configure Secure Boot" checked - Setup a password for Secure Boot MOK enrollment - Used "Erase disk and install Ubuntu" option After installation completes, the device reboots and I enroll the MOK in the UEFI BIOS. At first boot, the default GNOME session is "Ubuntu" (not "Ubuntu on Wayland"), which seems to be expected given that I am using NVidia proprietary drivers. Once logged in, nvidia-settings and GNOME Settings About screen both show that the GPU is available. It is set in "On-Demand" in nvidia- settings. $ switcherooctl Device: 0 Name:Intel® UHD Graphics Default: yes Environment: DRI_PRIME=pci-_00_02_0 Device: 1 Name:NVIDIA Corporation TU117GLM [Quadro T1000 Mobile] Default: no Environment: __GLX_VENDOR_LIBRARY_NAME=nvidia __NV_PRIME_RENDER_OFFLOAD=1 Expected result === When right-clicking on an icon in the launcher (for instance Firefox or Files), a "Launch using dedicated graphics card" option is available and launches the selected software using Nvidia GPU. Actual result = However, there is no "Launch using dedicated graphics card" option available when right-clicking on an application launcher on the left. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Jan 28 14:00:33 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-01-28 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220126) RelatedPackageVersions: mutter-common 41.3-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952083] Re: Add support for Beige Goby
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Released Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Released Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1952083] Re: Add support for Beige Goby
** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Changed in: oem-priority Status: New => Fix Committed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1952083 Title: Add support for Beige Goby Status in amd: New Status in OEM Priority Project: Fix Committed Status in mesa package in Ubuntu: Fix Released Status in mesa source package in Focal: Fix Committed Bug description: Impact] New hardware support for AMD's Beige Goby needs a commit backported to mesa. This is only needed on focal, skipping hirsute (no kernel support there). Fixed in impish and up. [Test plan] Install updates, boot a BG machine and check that the desktop has full hardware acceleration. [Where problems could occur] Mesa adds a single commit for enabling BEIGE_GOBY, hard to see what could go wrong. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1952083/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: Fix Released Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Hirsute: Fix Released Status in mutter source package in Impish: Fix Released Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plymouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: mutter (Ubuntu Hirsute) Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Released Status in mutter source package in Hirsute: Fix Released Status in mutter source package in Impish: Fix Released Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plymouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_star
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
I try to install impish and hirsute on the target machine, with the kernel from focal (so that it support the new ADL GPU, and then the monitor can be turned off so that the touchscreen will be detached, that's the way we reproduce this issue in focal) With that, with or without mutter from the proposed channel, I can't reproduce this issue. (We do see the backlight turned off and the touchscreen detached from kernel message.) Given this is a timing-sensitive issue, I think as long as there is no regression, then we can call that as verified done. I've dog food those, and can't find regression so far. So I'll tag verify done. ** Tags removed: verification-needed verification-needed-hirsute verification-needed-impish ** Tags added: verification-done verification-done-hirsute verification-done-impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: Fix Committed Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Focal: Fix Committed Status in mutter source package in Hirsute: Fix Committed Status in mutter source package in Impish: Fix Committed Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plymouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Description changed: [Impact] - * Gdm crashed and user need to be an expert to know how to work around, -or need to reboot to fix. + * Gdm crashed and user need to be an expert to know how to work around, + or need to reboot to fix. - * OEM projects got certain SKU that can reliably reproduce this issue. + * OEM projects got certain SKU that can reliably reproduce this issue. - * A merged patch in upstream fix the race condition. + * A merged patch in upstream fix the race condition. [Test Plan] - * Use the SKU that can reliably reproduce this issue. - * Do a cold boot, and wait for 5 mins. The monitor should turned-black -but showing the Machine Vendor logo that was previously -displayed by plythmouth. - * Try to dog-food the deb from the proposed channel and make sure -all input events still properly propagate. + * Use the SKU that can reliably reproduce this issue. + * Do a cold boot, and wait for 5 mins. The monitor should turned-black + but showing the Machine Vendor logo that was previously + displayed by plymouth. + * Try to dog-food the deb from the proposed channel and make sure + all input events still properly propagate. [Where problems could occur] - * If the patch is not properly working as expected, per the file this -patch touch, the user desktop session could stop responding to -mouse, keyboard, and touch screen input. + * If the patch is not properly working as expected, per the file this + patch touch, the user desktop session could stop responding to + mouse, keyboard, and touch screen input. [Other Info] - - * Can't think of any for now. + + * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Given ubuntu/impish is not exist in salsa, so I create it in my salsa git and another patch to include the change. https://salsa.debian.org/ycheng- guest/mutter/-/tree/salsa_wayland_race_fix_impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
MP for focal: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/78 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this issue. * A merged patch in upstream fix the race condition. [Test Plan] * Use the SKU that can reliably reproduce this issue. * Do a cold boot, and wait for 5 mins. The monitor should turned-black but showing the Machine Vendor logo that was previously displayed by plythmouth. * Try to dog-food the deb from the proposed channel and make sure all input events still properly propagate. [Where problems could occur] * If the patch is not properly working as expected, per the file this patch touch, the user desktop session could stop responding to mouse, keyboard, and touch screen input. [Other Info] * Can't think of any for now. This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list:
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Description changed: + [Impact] + + * Gdm crashed and user need to be an expert to know how to work around, +or need to reboot to fix. + + * OEM projects got certain SKU that can reliably reproduce this issue. + + * A merged patch in upstream fix the race condition. + + [Test Plan] + + * Use the SKU that can reliably reproduce this issue. + * Do a cold boot, and wait for 5 mins. The monitor should turned-black +but showing the Machine Vendor logo that was previously +displayed by plythmouth. + * Try to dog-food the deb from the proposed channel and make sure +all input events still properly propagate. + + [Where problems could occur] + + * If the patch is not properly working as expected, per the file this +patch touch, the user desktop session could stop responding to +mouse, keyboard, and touch screen input. + + [Other Info] + + * Can't think of any for now. + + + This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: In Progress Bug description: [Impact] * Gdm crashed and user need to be an expert to know how to work around, or need to reboot to fix. * OEM projects got certain SKU that can reliably reproduce this
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for focal. Note I back-port a chunk from the patch as hirsute. ** Patch added: "mutter_3.36.9-0ubuntu0.20.04.2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537413/+files/mutter_3.36.9-0ubuntu0.20.04.2.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for impish ** Patch added: "mutter_40.5-1ubuntu3~21.10.1_impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537406/+files/mutter_40.5-1ubuntu3~21.10.1_impish.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
add Bug-Ubuntu in salsa git, and re-upload jammy debdiff. ** Patch removed: "mutter_40.5-1ubuntu3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537386/+files/mutter_40.5-1ubuntu3.debdiff ** Patch added: "mutter_40.5-1ubuntu3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537405/+files/mutter_40.5-1ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for hirsute. Note I back-port a chunk from the patch. ** Patch added: "mutter_3.38.4-1ubuntu3_hirsute.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537401/+files/mutter_3.38.4-1ubuntu3_hirsute.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Patch removed: "mutter_40.5-1ubuntu3~21.04.1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537399/+files/mutter_40.5-1ubuntu3~21.04.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for impish ** Patch added: "mutter_40.5-1ubuntu3~21.04.1.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537399/+files/mutter_40.5-1ubuntu3~21.04.1.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Description changed: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. + + Note: this bug seems to be timing sensitive. I got an OEM project + machine that can reproduce this issue (reproducible on several machines + with the same HW design). The machine is using ADL CPU, which needs a + patched 5.14 kernel. So I can't reproduce this on impish. With the + backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. -Kernel message like: "usb 1-9: USB disconnect, device number 6" -as the screen turned black. + Kernel message like: "usb 1-9: USB disconnect, device number 6" + as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and -gnome-shell stop there for 30 more seconds. + gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) - at ../src/wayland-client.c:911 + at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, - target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 + target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` ** Description changed: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. - 2. wait for 5 mins, and the screen will be turned off. + 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Also create MP in https://salsa.debian.org/gnome- team/mutter/-/merge_requests/76 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for jammy. also uploaded to ppa: https://launchpad.net/~ycheng- twn/+archive/ubuntu/mutter-f3 AI: install jammy and do some quick trial use of desktop environment after the upgrade. Note: we'd need to SRU back to focal to fulfill the OEM project requirement. ** Patch added: "mutter_40.5-1ubuntu3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537386/+files/mutter_40.5-1ubuntu3.debdiff -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
Currently we are doing a little bit more test to make sure we this patch does work. For now, the versions of mutter: jammy: 40.5-1ubuntu2 impish: 40.5-1ubuntu2 Debian: sid: 41.0-5 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: Fix Committed Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
upstream bug: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 ** Tags added: oem-priority originate-from-1947739 somerville -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: New Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948894/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1948894] [NEW] Xwayland crash in gdm as screen off and touchscreen detach.
Public bug reported: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` ** Affects: oem-priority Importance: Critical Assignee: Yuan-Chen Cheng (ycheng-twn) Status: In Progress ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1947739 somerville ** Information type changed from Proprietary to Public ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in OEM Priority Project: In Progress Status in mutter package in Ubuntu: New Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in Abort
[Desktop-packages] [Bug 1915003] Re: SRU: Always update the initramfs when changing power profile
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1915003 Title: SRU: Always update the initramfs when changing power profile Status in NVIDIA Drivers Ubuntu: New Status in OEM Priority Project: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-prime source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in nvidia-prime source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Released Status in nvidia-prime source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Released Bug description: Since we introduced support for dynamic power management, on systems with hybrid graphics (LP: #1904583), the need to load drivers with different options has become more evident. We need to make sure that the files in the initramfs are in sync with the current user selection. This is also a chance to update the old nvidia-settings release in the archive. [Impact] * If the modules list is not in sync with the selected power profile, users may experience a black screen or increased power consumption. * Updating the initramfs can take a few seconds, and we need to provide users with some form of visual feedback. [Fix] * The prime-select tool shoud update the initramfs when switching between power profiles, and provide visual feedback. * The nvidia-settings panel should provide a progress dialog, since profile switching would otherwise freeze the UI until update-initramfs completes. [Test Case] Make sure a supported nvidia driver is installed (450, 460), then install nvidia-prime and nvidia-settings from proposed, and check the following: 1) prime-select query (to check your current profile) 2) sudo prime-select on-demand (or "intel", or "nvidia", depending on your current power profile) 3) Check that the operation completes successfully. 4) Reboot your system 5) Launch the nvidia-setting panel. 6) Select a different profile from the PRIME tab, and check that a progress dialog is correctly displayed. 7) Close the nvidia-settings panel, and reboot. [Regression Risk] Medium, while the changes in prime-select are trivial, nvidia-settings needs careful testing. To manage notifications about this bug go to: https://bugs.launchpad.net/nvidia-drivers-ubuntu/+bug/1915003/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1895855] Re: FFE: support for NVIDIA runtimepm (hybrid gfx)
** Changed in: oem-priority Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-prime in Ubuntu. https://bugs.launchpad.net/bugs/1895855 Title: FFE: support for NVIDIA runtimepm (hybrid gfx) Status in OEM Priority Project: Fix Released Status in nvidia-graphics-drivers-450 package in Ubuntu: Fix Released Status in nvidia-prime package in Ubuntu: Fix Released Status in ubuntu-drivers-common package in Ubuntu: Fix Released Status in nvidia-prime source package in Focal: Fix Released Bug description: The work that went into ubuntu-drivers-common and nvidia-prime is meant to enable RTD3 support on Intel/NVIDIA or AMD/NVIDIA hybrid systems, introduced by the NVIDIA 450 driver series. This allows the supported systems to make use of the integrated GPU (Intel or AMD) and to keep the discrete NVIDIA GPU powered down until needed. While powered down, the NVIDIA GPU can still detect any events, should external displays be plugged in. This brings hybrid graphics on Linux on par with Windows. Only the supported GPUs will be able to benefit from this change. This is why NVIDIA provides a hardware database (included in the nvidia packages), which gpu-manager can now parse. The ubuntu-drivers tool relies on that detection to enable this new feature when installing the NVIDIA driver. Another improvement is the ability of ubuntu-drivers to detect LTSB (Long term support branch), NFB (New feature branch), Legacy, Beta flags, which the NVIDIA drivers can have, and make informed detection choices. This work also includes a number of bug fixes reported on errors.ubuntu.com. Requirements: The new ubuntu-drivers-common: The new nvidia-prime: Changes to the NVIDIA drivers: To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1895855/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
** Tags added: fwupd -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store-desktop: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1869086] Re: Firmware upgrade always notifies to reboot the device even on immediate failure
I can't reproduce this. fwupd deb 1.3.11-1~focal1 snap-store, Version: 3.38.0-59-g494f078, Rev: 518 (latest/stable) Attached is the UI when AC is not plugged. ** Attachment added: "fwupd-test-no-ac-passed.png" https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+attachment/5500346/+files/fwupd-test-no-ac-passed.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1869086 Title: Firmware upgrade always notifies to reboot the device even on immediate failure Status in snap-store-desktop: Triaged Status in gnome-software package in Ubuntu: Triaged Status in gnome-software source package in Focal: Triaged Bug description: If the firmware update request fails because of a network error or because the AC power is not plugged, or any other problem, gnome- software shows an error in an in-app notification, while sends a resident notification to gnome-shell that requests the user to restart the system, even if this is not really required. See the attached screenshot. To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format
** Changed in: cheese (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: Confirmed Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1882896] Re: cheese not recognize resolution in MJPG format
The patch lives in https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 it's merged on Sep 21 2020. However, it does not exist in cheese-3.34.0 nor cheese deb 3.38.0-3 in debian/unstable. To really fix it, the first step is to land this change in debian. ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cheese in Ubuntu. https://bugs.launchpad.net/bugs/1882896 Title: cheese not recognize resolution in MJPG format Status in Cheese: Unknown Status in OEM Priority Project: Confirmed Status in cheese package in Ubuntu: Incomplete Bug description: reproduce step: - open cheese - open preferences -> resolution - only resolution from YUYV format in options the patches there works well and waiting for merge: https://gitlab.gnome.org/GNOME/cheese/-/merge_requests/17 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 ProcVersionSignature: Ubuntu 5.6.0-1008.8-oem 5.6.4 Uname: Linux 5.6.0-1008-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 10 15:23:02 2020 InstallationDate: Installed on 2020-04-12 (58 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200411) MachineType: Dell Inc. XPS 13 9380 RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/05/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.7.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.7.0:bd08/05/2019:svnDellInc.:pnXPS139380:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9380 dmi.product.sku: 08AF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/cheese/+bug/1882896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
