[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 Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1985869/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1980334 Title: Support Quectel's modem(EM120/160) firmware update, fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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() To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1969422/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1980334 Title: Support Quectel's modem(EM120/160) firmware update, fwupd To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1980334/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990089/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1984840 Title: bump libxml version for gnome-software and gnome-firmware To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1984840/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze and high CPU when a second monitor of different scaling factor is attached (but only if DING is active)
** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB + + Per further check, it will freeze only if the built-in and external + display has different scale factors. [Steps to reproduce] 1. Attact DA310 or WD19TB to DUT 2. Cold Boot into OS 3. Plug the DP/HDMI cable to DA310 or WD19TB 4. Check the external monitor has signal 5. Click keyboard or move mouse to check system can work well [Expected result] System won't be freeze with external monitor. [Actual result] Screen will freeze, but ssh can still reach out DUT. Keyboard and mouse don't work during the screen freeze. It can be recovered after unplug the external monitor sometime. [gnome-shell stack trace] 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). 五 27 22:12:31 ubuntu-XPS-9320 gnome-shell[1998]: meta_window_set_stack_position_no_sync: assertion 'window->stack_position >= 0' failed 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: ubuntu : TTY=pts/2 ; PWD=/home/ubuntu ; USER=root ; COMMAND=/usr/bin/dmesg 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session opened for user root(uid=0) by ubuntu(uid=1001) 五 27 22:12:55 ubuntu-XPS-9320 sudo[2916]: pam_unix(sudo:session): session closed for user root 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: == Stack trace for context 0x56156f8f04a0 == 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: The offending signal was window-added on MetaWorkspace 0x56156f916640. 五 27 22:12:56 ubuntu-XPS-9320 gnome-shell[1998]: Attempting to call back into JSAPI during the sweeping phase of GC. This is most likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be caused by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. - [What could go wrong] This 2 line bugfix maximizes the desktop icons window avoiding an infinite loop. This is a workaround for an apparent bug in mutter but fixing mutter is much more complicated. The Desktop Icons NG GNOME Shell extension is enabled by default on Ubuntu 22.04 LTS so a bug here could make desktops unusable. - --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-03-17 (75 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) Package: gnome-shell 42.1-0ubuntu0.1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-35.36-generic 5.15.35 RelatedPackageVersions: mutter-common 42.0-3ubuntu2 Tags: jammy wayland-session Uname: Linux 5.15.0-35-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1976204 Title: Screen freeze and high CPU when a second monitor of different scaling factor is attached (but only if DING is active) To manage notifications about this bug go to:
[Bug 1876632] Re: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend
** Tags added: jellyfish-edge-staging -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: Missing Wayland login option on NVIDIA systems To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1876632 Title: [nvidia] Corrupted/missing shell textures when switching users or resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1876632/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969707/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968929] Re: No Wayland support on my NVIDA laptop
** Tags added: oem-priority -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1968929 Title: No Wayland support on my NVIDA laptop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1968929/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1962277 Title: To support Synaptics fp device To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962277/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1965648/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966642/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the bottom of the touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825297/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1966629 Title: swipe up from the button of the touch monitor To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1966629/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1914226 Title: Add option to enable screen-keyboard icon for panel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1914226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825299/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1854222 Title: Screen keyboard improperly appears on laptops with touchscreen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1854222/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1831039/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1964091/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gdm3 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1958488/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1962523] Re: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed
** Tags added: gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1962523 Title: [Wayland][Nvidia] gdm default use Xorg in 22.04 if proprietary nvidia installed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1962523/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
** Tags added: gdm3 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963701] Re: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine
** Summary changed: - [NVIDIA][Wayland] graphic target not able to reach + [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1963701 Title: [NVIDIA][Wayland] graphic target not able to reach as the only monitor connect to NV GPU only on I+N machine To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963701/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-screensaver in Ubuntu. https://bugs.launchpad.net/bugs/1292041 Title: Lockscreen doesn't turn off the screen To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1292041/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/49579 Title: screen doesn't lock when some menu is open To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-screensaver/+bug/49579/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1963628/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1959362/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1869086/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard
** Changed in: oem-priority Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1845163 Title: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1845163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845163] Re: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard
** Tags added: hwe-bluetooth -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1845163 Title: The cancel button of the paring dialog does not work during pairing a bluetooth keyboard To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1845163/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878351] Re: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW
** Changed in: oem-priority Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1878351 Title: System shutdown directly by pressing power button and releasing immediately on Dell Vostro HW To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878351/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
Given the details in #11, yes with the new g-c-c, I can see the first profile auto-selected. Without updated g-c-c, it's not auto-selected. ** Tags removed: verification-failed verification-failed-focal ** Tags added: verification-done verification-done-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
I install a dell machine (still not disclosed), upgrade everything from updates channel, and install from focal-proposed Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 gnome-control-center-data all 1:3.36.4-0ubuntu2 [327 kB] Get:2 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 gnome-control-center amd64 1:3.36.4-0ubuntu2 [1,718 kB] Get:3 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 gnome-control-center-faces all 1:3.36.4-0ubuntu2 [1,216 kB] After that, I reboot the machine, plug hdmi, make sure hdmi output is selected in g-c-c. I still can see three items in the profile combo list. ** Tags removed: verification-done verification-done-focal ** Tags added: verification-failed verification-failed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1845801] Re: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login.
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1845801 Title: [nvidia] Automatic login fails and then all subsequent logins fail. Killing gnome-session-binary fixes it, or just not using automatic login. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1845801/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1896919] Re: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c
** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1896919 Title: [SRU] g-c-c: The hdmi/dp profiles are not set automatically in the combo list after selecting the hdmi/dp audio in the g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1896919/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1885673] Re: won't auto-select input when headset is plugged and selected in pop-up window
If we still need to land in focal, shall we affect focal series for g-c-c? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1885673 Title: won't auto-select input when headset is plugged and selected in pop-up window To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1885673/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
** Tags removed: focal ** Tags added: bionic ** Tags added: originate-1863700 ** Tags added: somerville -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864813] Re: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once.
bionic pactl log as just boot, after plug headset and remove headset. ** Summary changed: - As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c + As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. ** Description changed: - There will be an dummy output in gnome-contol-center (g-c-c) if + The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. - Reprudced in bionic and focal. + However, in bionic, it will disappear as the headset is plugged and selected. + After it disappears, a reboot won't make it appear again. - In Focal, As the earphone is plugged, dummy output disappears. - As it's unplugged, it appears again. + In Focal, dummy output won't disappear. - Per test in focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + focal: + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Description changed: The dummy output in gnome-contol-center (g-c-c) will exists if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. However, in bionic, it will disappear as the headset is plugged and selected. After it disappears, a reboot won't make it appear again. + bionic: + gnome-control-center: 1:3.28.2-0ubuntu0.18.04.6 + pulseaudio: 1:11.1-1ubuntu7.4 + In Focal, dummy output won't disappear. focal: - pulseaudio 1:13.0-3ubuntu2 - gnome-control-center 1:3.35.91-0ubuntu1 + pulseaudio 1:13.0-3ubuntu2 + gnome-control-center 1:3.35.91-0ubuntu1 ** Attachment added: "pactl-logs.tar" https://bugs.launchpad.net/oem-priority/+bug/1864813/+attachment/5331500/+files/pactl-logs.tar -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, the dummy output in g-c-c will disappear after plug headset once. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Yes, I think I have chance to access the HW and provide details soon. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864813] Re: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
In bionic, the dummy output disappears in certain case and never show up again in certain cases. I do like to know which is the *corrected* behaviors so I know which one we should work on. Agree that it’s not a major bug IMHO. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1864813] [NEW] As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c
Public bug reported: There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 ** Affects: oem-priority Importance: Medium Status: New ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Medium ** Description changed: - There will be an dummy output if + There will be an dummy output in gnome-contol-center (g-c-c) if - no built-in speaker - no headphone/earphone plugged - using display (like VGA, DVI) without audio out is plugged. Reprudced in bionic and focal. In Focal, As the earphone is plugged, dummy output disappears. As it's unplugged, it appears again. - Per test in focal: pulseaudio 1:13.0-3ubuntu2 gnome-control-center 1:3.35.91-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1864813 Title: As there is not built-in speaker, and not any output, there will be an dummy output in g-c-c To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1864813/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1827346] Re: Power: Fail to set delay time when the value is 90 minutes
** Changed in: oem-priority/xenial Status: Fix Committed => Fix Released ** Changed in: oem-priority/bionic Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1827346 Title: Power: Fail to set delay time when the value is 90 minutes To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1827346/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1809788] Re: Shell dialog messages are truncated and ellipsized...
** Changed in: oem-priority Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1809788 Title: Shell dialog messages are truncated and ellipsized... To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1809788/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1772811] Re: [SRU] different behaviors for switch display mode between xenial and bionic
** Changed in: oem-priority Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1772811 Title: [SRU] different behaviors for switch display mode between xenial and bionic To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1772811/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
per current oem project, we don't have this issue. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1811668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button/menu does nothing
@Sebastien, we use ubunquity with plugins for oem image. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715602 Title: ubiquity-dm / Install Ubuntu - Power button/menu does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1715602] Re: ubiquity-dm / Install Ubuntu - Power button does nothing
** Changed in: oem-priority Importance: High => Medium -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1715602 Title: ubiquity-dm / Install Ubuntu - Power button does nothing To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1715602/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled
** Changed in: oem-priority Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1817738 Title: Can't change virtual terminal on login screen or when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled
** Tags added: lp-1804607 somerville ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1817738 Title: Can't change virtual terminal on login screen or when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal on login screen or when auto-login is enabled
** Changed in: oem-priority Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1817738 Title: Can't change virtual terminal on login screen or when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1811668] Re: oem-config fails on Nvidia GPU machine on 18.04.1
** Changed in: oem-priority Status: Expired => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1811668 Title: oem-config fails on Nvidia GPU machine on 18.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1811668/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1817738] Re: Can't change virtual terminal when auto-login is enabled
** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1817738 Title: Can't change virtual terminal when auto-login is enabled To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1817738/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1766890] Re: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned
** Changed in: oem-priority Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-menus in Ubuntu. https://bugs.launchpad.net/bugs/1766890 Title: package gnome-menus 3.13.3-6ubuntu3.1 failed to install/upgrade: triggers looping, abandoned To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1766890/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
