[Bug 2051074] Re: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking
** Tags added: originate-from-2048179 stella -- 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/2051074 Title: Mirror mode doesn't work when panel only supports one refresh rate with reduced blanking To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/2051074/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2031872] Re: Support Elan fp device [04F3:0C99]
** Changed in: oem-priority Assignee: (unassigned) => Yao Wei (medicalwei) ** Changed in: oem-priority Importance: Undecided => Critical ** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2031872 Title: Support Elan fp device [04F3:0C99] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2031872/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034121] Re: Support goodix fingerprint [27c6:633C]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034121 Title: Support goodix fingerprint [27c6:633C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930387] Re: The system voice doesn't change after disable "Over-Amplification"
** Also affects: gnome-settings-daemon via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/767 Importance: Unknown Status: Unknown ** No longer affects: gnome-control-center ** Also affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => Invalid ** Changed in: oem-priority Assignee: (unassigned) => Arturr (artur) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1930387 Title: The system voice doesn't change after disable "Over-Amplification" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1930387/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2042796] Re: Ubuntu 20.04 The four corners of the touchscreen are not sensitive
** Changed in: oem-priority Assignee: (unassigned) => Artur Pak (artur-at-work) ** Changed in: oem-priority Importance: Undecided => Critical -- 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/2042796 Title: Ubuntu 20.04 The four corners of the touchscreen are not sensitive To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042796/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930387] Re: The system voice doesn't change after disable "Over-Amplification"
Hi @seb128, Yes, my expectation is that if user disable over-amplification from UI, it'll be the value of 100% only. ** No longer affects: gnome-control-center ** Bug watch added: gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues #767 https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/767 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-settings-daemon/-/issues/767 Importance: Unknown Status: Unknown -- 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/1930387 Title: The system voice doesn't change after disable "Over-Amplification" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1930387/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930387] Re: The system voice doesn't change after disable "Over-Amplification"
https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2726 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2726 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2726 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2726 Importance: Unknown Status: Unknown ** Tags added: originate-from-2039792 -- 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/1930387 Title: The system voice doesn't change after disable "Over-Amplification" To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1930387/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995349] Re: [goodix] The enrolled finger is unknown to device
The fix is included in 1.94.6 (mantic). ** No longer affects: libfprint (Ubuntu Kinetic) -- 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/1995349 Title: [goodix] The enrolled finger is unknown to device To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1995349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034121] Re: Support goodix fingerprint [27c6:633C]
** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Lunar) Status: New => Confirmed -- 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/2034121 Title: Support goodix fingerprint [27c6:633C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034121/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
** Changed in: libfprint (Ubuntu Lunar) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: libfprint (Ubuntu Lunar) Status: Invalid => In Progress -- 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/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034481] Re: Cannot verify fingerprint if the storage is empty (Synaptics)
Enable -proposed on a HP laptop equip with Synaptics [06cb:00f0] fingerprint device and install libfprint version 1:1.94.3+tod1-0ubuntu2~22.04.06. Followed the steps to verify on it. [test] * Enroll one random finger * Reboot and enter BIOS to reset fingerprint device (HP laptops) * Boot into system and re-enroll the finger * Login system with enrolled finger I can login the system with re-enrolled finger. ** Changed in: libfprint (Ubuntu Lunar) Status: New => Invalid ** Changed in: libfprint (Ubuntu Lunar) Assignee: Andy Chi (andch) => (unassigned) ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2034481 Title: Cannot verify fingerprint if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034481] [NEW] Cannot verify print if the storage is empty (Synaptics)
Public bug reported: This patch is upstreamed: - https://gitlab.freedesktop.org/libfprint/libfprint/-/merge_requests/433 [Impact] * HP laptops provide clear fingerprint from BIOS, user can enroll finger on Synaptics device after clear from BIOS. [Test Plan] * Enroll one random finger * Reboot and enter BIOS to reset fingerprint device (HP laptops) * Boot into system and re-enroll the finger * Login system with enrolled finger [Where problems could occur] * The patch only fix the issue with clear fingerprint from BIOS on Synaptics device, won't impact other vendor. ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: Confirmed ** Affects: libfprint (Ubuntu) Importance: Medium Status: New ** Affects: libfprint (Ubuntu Jammy) Importance: Medium Assignee: Andy Chi (andch) Status: New ** Affects: libfprint (Ubuntu Lunar) Importance: Medium Assignee: Andy Chi (andch) Status: New ** Affects: libfprint (Ubuntu Mantic) Importance: Medium Status: New ** Tags: oem-priority originate-from-2018724 stella ** Also affects: libfprint (Ubuntu Mantic) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Assignee: (unassigned) => Andy Chi (andch) ** Changed in: libfprint (Ubuntu Lunar) Assignee: (unassigned) => Andy Chi (andch) ** Tags added: oem-priority originate-from-2018724 stella ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Mantic) Importance: Undecided => Medium -- 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/2034481 Title: Cannot verify print if the storage is empty (Synaptics) To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2034481/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293] Re: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1974293 Title: gnome-shell crashed on logout with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() To manage notifications about this bug go to: https://bugs.launchpad.net/gjs/+bug/1974293/+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)
** 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/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: https://bugs.launchpad.net/mutter/+bug/1976204/+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
** Tags added: originate-from-2019935 -- 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/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/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974293] Re: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl()
Hi @vanvugt, Sure, I changed this bug to public. ** Information type changed from Private to Public -- 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/1974293 Title: gnome-shell crashed with SIGSEGV in js::gc::Cell::storeBuffer() from js::gc::PostWriteBarrierImpl() To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974293/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008067] Re: To support Elan fp device [04F3:0C82]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/2008067 Title: To support Elan fp device [04F3:0C82] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+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
** Tags added: originate-from-2007815 -- 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/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/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008067] Re: To support Elan fp device [04F3:0C82]
This id is included in Lunar and Kinetic. ** Also affects: libfprint (Ubuntu Lunar) Importance: Medium Status: New ** Also affects: libfprint (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Kinetic) Status: New => Invalid ** Changed in: libfprint (Ubuntu Lunar) Status: New => Invalid -- 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/2008067 Title: To support Elan fp device [04F3:0C82] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2008067] [NEW] To support Elan fp device [04F3:0C82]
Public bug reported: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/2b760dfa380ceff152ff8105a2aad76d85ec1ddc This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C82] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C82] will be supported. ** Affects: oem-priority Importance: Undecided Status: New ** Affects: libfprint (Ubuntu) Importance: Medium Status: New ** Affects: libfprint (Ubuntu Jammy) Importance: Medium Status: New ** Tags: oem-priority originate-from-2007916 stella ** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => Medium ** No longer affects: libfprint (Ubuntu Lunar) ** No longer affects: libfprint (Ubuntu Kinetic) ** Changed in: libfprint (Ubuntu) Importance: Undecided => Medium ** Tags added: oem-priority originate-from-2007916 stella -- 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/2008067 Title: To support Elan fp device [04F3:0C82] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2008067/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
I found an easier way to reproduce this issue by the following steps: 1. Log out and select xorg 2. Log in and log out again to select wayland session 3. super + L to make screen blank. I can reproduce this issue easily. I tried the latest drm-tip/linux-next then I can't reproduce this issue. This kernel might help https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-intel-next/2023-02-22/ -- 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/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+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
** Tags added: originate-from-2006441 ** Tags added: originate-from-2006547 -- 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/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/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1995349] Re: [goodix] The enrolled finger is unknown to device
** Also affects: libfprint (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Kinetic) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Lunar) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Jammy) Importance: Undecided => Medium -- 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/1995349 Title: [goodix] The enrolled finger is unknown to device To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1995349/+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
** Tags added: originate-from-2000750 -- 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/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/mutter/+bug/1966635/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990209] Re: To support Goodix fp device [27C6:631C]
** Changed in: libfprint (Ubuntu) Status: New => 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/1990209 Title: To support Goodix fp device [27C6:631C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966911] Re: Cannot enroll finger on Jammy
** Changed in: libfprint-2-tod1-goodix Status: Fix Committed => 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/1966911 Title: Cannot enroll finger on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989313] Re: To support Goodix fp device [27C6:634C]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1989313 Title: To support Goodix fp device [27C6:634C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1990209] Re: To support Goodix fp device [27C6:631C]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1990209 Title: To support Goodix fp device [27C6:631C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989314] Re: To support Elan fp device [04F3:0C88]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1989314 Title: To support Elan fp device [04F3:0C88] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989314/+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: originate-from-1992399 -- 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/linux/+bug/1990089/+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: 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/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 1995349] [NEW] [goodix] The enrolled finger is unknown to device
Public bug reported: [Impact] * The enrolled finger is unknown to device [Test Plan] * Find a machine with Goodix fingerprint device * Clean up the storage of fp device by `manage-prints` * Launch `settings` and enable `Fingerprint Login` * Enroll left index finger and right index finger * Login with right index finger [Where problems could occur] * This is only affected goodix fingerprint device ** Affects: libfprint Importance: Unknown Status: Unknown ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: Confirmed ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1990344 somerville ** Tags added: oem-priority originate-from-1990344 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Bug watch added: gitlab.freedesktop.org/libfprint/libfprint/-/issues #511 https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/511 ** Also affects: libfprint via https://gitlab.freedesktop.org/libfprint/libfprint/-/issues/511 Importance: Unknown Status: Unknown -- 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/1995349 Title: [goodix] The enrolled finger is unknown to device To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1995349/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1988625] Re: Left-over cursor visible on second screen
Plug a 4k external monitor to XPS 9320, set the external monitor to 100% and set the internal monitor to 200%. Enable -proposed pocket and install mutter (42.5-0ubuntu1), wiggle mouse 20 times and no cursor left on my internal monitor. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1988625 Title: Left-over cursor visible on second screen To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1988625/+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: originate-from-1981168 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/1990089 Title: Screen freeze when performing memory stress in Wayland mode To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1990089/+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 added: originate-from-1989842 sutton -- 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 1990209] [NEW] To support Goodix fp device [27C6:631C]
Public bug reported: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/3a8299158600e06b126e72238ebd9156c7f59fc4 This ID is included in upstream. [Impact] * Devices have Goodix [27C6:631C] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [27C6:631C] will be supported. ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: Confirmed ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1980477 somerville ** Tags added: oem-priority originate-from-1980477 somerville ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1990209 Title: To support Goodix fp device [27C6:631C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1990209/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1956885] Re: Incorrect verify implementation, unable to verify on one finger
Hi Loic, I built a new deb here, please also check on your side. I can verify with one finger. fpritd-verify also works from my testing. https://launchpad.net/~andch/+archive/ubuntu/staging-fprint ** No longer affects: libfprint (Ubuntu) ** Changed in: oem-priority Status: Confirmed => In Progress ** Changed in: libfprint-2-tod1-broadcom Status: Confirmed => In Progress -- 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/1956885 Title: Incorrect verify implementation, unable to verify on one finger To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989313] [NEW] To support Elan fp device [04F3:0C88]
Public bug reported: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/7899bf4240819a28f3e29bd40d4e36aa432343b6 This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C88] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C88] will be supported. ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New -- 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/1989313 Title: To support Elan fp device [04F3:0C88] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1989313/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1989314] [NEW] To support Elan fp device [04F3:0C88]
Public bug reported: https://gitlab.freedesktop.org/libfprint/libfprint/-/commit/7899bf4240819a28f3e29bd40d4e36aa432343b6 This ID is included in upstream. [Impact] * Devices have Elan [04F3:0C88] fingerprint component will get supported. [Test Plan] * Find a machine with this fingerprint device * Launch `settings` and enable `Fingerprint Login` * Enroll finger and then logout * Login system with enrolled finger [Where problems could occur] * The only impact will be [04F3:0C88] will be supported. ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: In Progress ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1980183 somerville ** Tags added: oem-priority originate-from-1980183 somerville ** Changed in: oem-priority Status: New => In Progress ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1989314 Title: To support Elan fp device [04F3:0C88] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1989314/+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()
Hello @vanvugt, I tried with gnome-42.4 with steps below and gnome-shell works fine [Device] Laptop with iGPU (intel) and dGPU (amd) [steps] 1. Plug a monitor on iGPU (intel internal graphic) and plug the other monitor on dGPU (amd gpu) 2. Boot into system 3. Open gnome-settings-daemon and select `Displays` 4. Change the `Primary Display` to the other one [result] no crash with gnome-42.4 Test PPA: https://launchpad.net/~andch/+archive/ubuntu/experimental-package -- 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 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 Importance: High => Critical -- 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 1956885] Re: Incorrect verify implementation, unable to verify on one finger
** Changed in: libfprint-2-tod1-broadcom Status: New => Confirmed ** Changed in: libfprint-2-tod1-broadcom Importance: Undecided => Critical ** Changed in: libfprint-2-tod1-broadcom Assignee: (unassigned) => Andy Chi (andch) ** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags added: oem-priority originate-from-1985872 somerville -- 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/1956885 Title: Incorrect verify implementation, unable to verify on one finger To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1956885/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966911] Re: Cannot enroll finger on Jammy
** 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/1966911 Title: Cannot enroll finger on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+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 added: oem-priority originate-from-1981416 somerville ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Importance: Undecided => High -- 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 1981974] Re: FP identify is not working with broadcom sensor on Jammy
** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New -- 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/1981974 Title: FP identify is not working with broadcom sensor on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-broadcom/+bug/1981974/+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
** Tags added: originate-from-1982904 stella -- 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
** Tags added: originate-from-1981676 somerville -- 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 1936302] Re: To support elanmoc driver
** Changed in: libfprint (Ubuntu) Status: In Progress => 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/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+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)
** 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/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: https://bugs.launchpad.net/mutter/+bug/1976204/+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)
Enable -proposed on XPS9310(3456x2160), install gnome-shell-extension- desktop-icons-ng (43-2ubuntu1). [steps] 1. Plug type-c monitor to DUT 2. Cold Boot into OS 3. Check the external monitor has signal 4. Click keyboard or move mouse to check system can work well External and built-in monitor works fine. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Ubuntu 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: https://bugs.launchpad.net/mutter/+bug/1976204/+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)
Hello @vanvugt, I manually edit workspaces-only-on-primary false in /usr/share/glib-2.0/schemas/10_ubuntu-settings.gschema.override /usr/share/glib-2.0/schemas/00_org.gnome.shell.gschema.override Followed the steps in the bug description, my screen freeze after the external monitor plugged. Probably my setting is not correct? ** Attachment added: "20220627-gnome-shell.log.tar.gz" https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5599910/+files/20220627-gnome-shell.log.tar.gz -- 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: https://bugs.launchpad.net/oem-priority/+bug/1976204/+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)
Based on comment#57, I built a test deb for this issue. If anyone wants to test the patched gnome-shell-extension-desktop-icons-ng, please refer to https://launchpad.net/~andch/+archive/ubuntu/experimental-package. @vanvugt, thanks a lot! -- 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: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active
Tried with the newest mutter (42.2-0ubuntu1) and gnome-shell (42.2-0ubuntu0.2), the screen freeze after I plug external monitor. ** Attachment added: "gnome-shell-20220621.log" https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5598650/+files/gnome-shell-20220621.log -- 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 if a 4K monitor is added to a 4K laptop while DING is active To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze if a 4K monitor is added to a 4K laptop while DING is active
All the 4k eDP laptops will have this issue, I tried on HP ZBook (which includes nv card) and switch to wayland. Plug external 4k monitor can reproduce too. -- 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 if a 4K monitor is added to a 4K laptop while DING is active To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
If eDP is 4k or OLED (3456x2160), screen will freeze after plugging 4k external monitor. I switched to type-c to DP dongle, and the dongle works with other laptop with FHD eDP. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
Tried adding MUTTER_DEBUG_DISABLE_TRIPLE_BUFFERING=1 and screen freeze after plugging external monitor. I test with 2 different 4k monitor, one is ASUS and the other one is Benq. Both can cause this issue. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
timestamp of freeze time: 16:27:00 gnome-shell[1880]KMS: [atomic] Setting plane 31 (/dev/dri/card0) property 'rotation' (33) to 1 Unplug external monitor and screen does not freeze: 16:27:23 gnome-shell[1880]KMS: [atomic] Page flip callback for CRTC (98, /dev/dri/card0), data: 0x559af8d398890 ** Attachment added: "gnome-shell-enable-mutter-20220616.log" https://bugs.launchpad.net/oem-priority/+bug/1976204/+attachment/5597671/+files/gnome-shell-enable-mutter-20220616.log -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
Follow comment #19 to enable MUTTER_DEBUG=kms and get the sos report ** Attachment added: "sosreport-ubuntu-XPS-13-9310-2022-06-16-cypwmhe.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5597653/+files/sosreport-ubuntu-XPS-13-9310-2022-06-16-cypwmhe.tar.xz -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
Ubuntu-bug xxx.crash Bug #1978764 -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1936302] Re: To support elanmoc driver
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1936302 Title: To support elanmoc driver To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1936302/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
@vanvugt, Sure, but we don't have type-c monitor in Lab. I'm using a type-c to HDMI dongle. -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
Set the DUT back to X, plug external 4K monitor. I won't see the screen freeze. [DUT] XPS 9310 [Monitor] ASUS PA279CV [kernel] 5.15.0-35-generic [BIOS] 3.4.0 ** Attachment added: "dpkg.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5596187/+files/dpkg.txt -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: Screen freeze
Change the title to "Screen freeze" to avoid any confusion of "system hang" or "system freeze". Sure, I'll add the debug in the /etc/environment. Thanks. ** Summary changed: - System freeze + Screen freeze -- 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 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: System freeze
Sorry, connect type-c monitor directly without docking can also reproduce this issue. -- 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: System freeze To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [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] - System will be freeze. + 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. + 五 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.
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
I use `thread apply all bt full` to capture the gdb debug message and use `journalctl -b 0 /usr/bin/gnome-shell` to capture journal log. ** Attachment added: "gnome-shell-stack-trace-202206062108.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595073/+files/gnome-shell-stack-trace-202206062108.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
Hi @3v1n0, [steps] 1. Install gnome-shell-dbgsym_42.1-0ubuntu0.1_amd64.ddeb, libglib2.0-dev-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-test-10-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-0-dbgsym_2.72.1-1_amd64.ddeb, libglib2.0-tests-dbgsym_2.72.1-1_amd64.ddeb, mutter-10-tests-dbgsym_42.1-0ubuntu1_amd64.ddeb, libglib2.0-bin-dbgsym_2.72.1-1_amd64.ddeb, libmutter-10-0-dbgsym_42.1-0ubuntu1_amd64.ddeb and mutter-dbgsym_42.1-0ubuntu1_amd64.ddeb 2. Plug external monitor 3. Execute `sudo gdb -p $(pidof /usr/bin/gnome-shell) /usr/bin/gnome-shell` 4. Ctrl+C and `bt` 5. `call (void) gjs_dumpstack()` [journal log] 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: The offending callback was SourceFunc(). 六 06 16:23:27 ubuntu-XPS-13-9310 gnome-shell[1071]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter a ctor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked . ** Attachment added: "20220606-gnome-shell.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5595044/+files/20220606-gnome-shell.log.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
If I remove gnome-shell-extension-desktop-icons-ng, I can't reproduce this issue. Also I can't reproduce this issue under x-session. -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594178/+files/ShellJournal.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594177/+files/ProcEnviron.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594176/+files/ProcCpuinfoMinimal.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594175/+files/GsettingsChanges.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [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] System will be 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. + This system is using OLED (3456x2160) panel, and I can't reproduce this issue on FHD panel. + --- + 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 ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1976204/+attachment/5594174/+files/Dependencies.txt -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Attachment added: "syslog.log.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+attachment/5593680/+files/syslog.log.tar.gz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] Re: system freeze and gnome-shell reports multiple stack trace
** Tags added: oem-priority originate-from-1967530 somerville ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1976204] [NEW] system freeze and gnome-shell reports multiple stack trace
Public bug reported: [Summary] The system will run into freeze if I connect the external monitor through DP/HDMI with dongle DA310 or Docking WD19TB [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] System will be 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. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz" https://bugs.launchpad.net/bugs/1976204/+attachment/5593674/+files/sosreport-ubuntu-XPS-9320-2022-05-27-ouxfyjg.tar.xz -- 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/1976204 Title: system freeze and gnome-shell reports multiple stack trace To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1976204/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950244] Re: Cannot enroll fingerprint after re-install Focal
** Also affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Changed in: fprintd (Ubuntu) Status: New => Invalid -- 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/1950244 Title: Cannot enroll fingerprint after re-install Focal To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1950244/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] Re: gnome-shell crash when executing keys/media-control checkbox test job
Hi @vanvugt, Another bug is here Bug# 1974293 Thanks! -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] Re: gnome-shell crash when executing keys/media-control checkbox test job
-- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] ShellJournal.txt
apport information ** Attachment added: "ShellJournal.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591462/+files/ShellJournal.txt ** Tags added: oem-priority originate-from-1967555 somerville ** Changed in: oem-priority Status: New => Confirmed ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591461/+files/ProcEnviron.txt -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591460/+files/ProcCpuinfoMinimal.txt -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591459/+files/HookError_ubuntu.txt -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] GsettingsChanges.txt
apport information ** Attachment added: "GsettingsChanges.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591458/+files/GsettingsChanges.txt -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1974275/+attachment/5591457/+files/Dependencies.txt -- 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/1974275 Title: gnome-shell crash when executing keys/media-control checkbox test job To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1974275] [NEW] gnome-shell crash when executing keys/media-control checkbox test job
Public bug reported:
[Summary]
User will be logged out to landing page automatically when performing the Media
Control hotkey case.
[Steps to reproduce]
1. Boot into OS
2. Run "checkbox-cli com.canonical.certification::keys/media-control"
3. Press the "play & pause" hotkey (next to the microphone mute key)
4. Press left arrow button to move the focus to the "skip" button and then
press enter
Description:Ubuntu 22.04 LTS
Release:22.04
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5json: {
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistributionChannelDescriptor:
# This is the distribution channel descriptor for the OEM CDs
# For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X17
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2022-05-16 (4 days ago)
InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220425-25
Package: gnome-shell 42.0-2ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.15.0-9027.28+exp.26-generic 5.15.35
RelatedPackageVersions: mutter-common 42.0-3ubuntu2
Tags: wayland-session jammy
Uname: Linux 5.15.0-9027-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
** Affects: oem-priority
Importance: Critical
Assignee: Andy Chi (andch)
Status: Confirmed
** Affects: gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-collected jammy oem-priority originate-from-1967555 somerville
wayland-session
** Tags added: apport-collected jammy wayland-session
** Description changed:
[Summary]
User will be logged out to landing page automatically when performing the
Media Control hotkey case.
[Steps to reproduce]
1. Boot into OS
2. Run "checkbox-cli com.canonical.certification::keys/media-control"
3. Press the "play & pause" hotkey (next to the microphone mute key)
4. Press left arrow button to move the focus to the "skip" button and then
press enter
Description: Ubuntu 22.04 LTS
Release: 22.04
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu82
+ Architecture: amd64
+ CasperMD5json: {
+ CurrentDesktop: ubuntu:GNOME
+ DisplayManager: gdm3
+ DistributionChannelDescriptor:
+ # This is the distribution channel descriptor for the OEM CDs
+ # For more information see
http://wiki.ubuntu.com/DistributionChannelDescriptor
+ canonical-oem-somerville-jammy-amd64-20220425-25+jellyfish-tentacool+X17
+ DistroRelease: Ubuntu 22.04
+ InstallationDate: Installed on 2022-05-16 (4 days ago)
+ InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" -
somerville-jammy-amd64-20220425-25
+ Package: gnome-shell 42.0-2ubuntu1
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 5.15.0-9027.28+exp.26-generic 5.15.35
+ RelatedPackageVersions: mutter-common 42.0-3ubuntu2
+ Tags: wayland-session jammy
+ Uname: Linux 5.15.0-9027-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
--
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/1974275
Title:
gnome-shell crash when executing keys/media-control checkbox test job
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1974275/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
Enable -proposed and install gnome-control-center 1:3.36.5-0ubuntu4 on Focal. Test it on DUT which have HDMI port, plug HDMI monitor (ASUS PA279). External monitor with `Join Displays` works as expected. ** 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-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
Include this patch won't change the detection behavior, it will 'do it better' to set a preferred scale when monitor plugged. -- 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/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1951531] Re: Cannot copy file from Nautilus to desktop
** Changed in: oem-priority Status: Confirmed => Won't Fix ** Changed in: oem-priority Status: Won't Fix => Invalid ** Changed in: nautilus (Ubuntu) Status: Confirmed => Invalid -- 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/1951531 Title: Cannot copy file from Nautilus to desktop To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1951531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
** 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 gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1945296] Re: To support goodix fp device [27C6:639C]
** 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 libfprint in Ubuntu. https://bugs.launchpad.net/bugs/1945296 Title: To support goodix fp device [27C6:639C] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1945296/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1950438] Re: To support goodix fp device [27C6:63CC]
** 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/1950438 Title: To support goodix fp device [27C6:63CC] To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1950438/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** 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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] Re: External display will be `Single Display` when HDMI plugged
Upload debdiff for focal ** Patch added: "gnome-control-center_3.36.5-0ubuntu4.debdiff" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969428/+attachment/5581392/+files/gnome-control-center_3.36.5-0ubuntu4.debdiff ** Tags added: oem-priority originate-from-1967088 stella ** Tags added: originate-from-1966906 -- 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/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969428] [NEW] External display will be `Single Display` when HDMI plugged
Public bug reported: Upstream bug: https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1038 [Impact] * DUT will remain `Single Display` mode when 4k monitor is plugged. Not every 4K monitor will cause this issue. [Test Plan] * Find a 4k monitor (Philips 276E) * Plug HDMI cable to internal HDMI port on DUT [Where problems could occur] * This change makes DUT more stable when connecting external monitor. * This fix is also include in impish and jammy ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- 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/1969428 Title: External display will be `Single Display` when HDMI plugged To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1969428/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966911] [NEW] Cannot enroll finger on Jammy
Public bug reported: [Summary] Cannot enroll finger on Jammy. [Steps] 1. Install Jammy on XPS-9310 2. Open Gnome-control-center and select `User` 3. Enroll fingerprint [Expected] Enroll fingerprint without issue. [Actual] Cannot enroll fingerprint ** Affects: libfprint-2-tod1-goodix Importance: Critical Assignee: Andy Chi (andch) Status: Confirmed ** Affects: oem-priority Importance: Critical Assignee: Andy Chi (andch) Status: Confirmed ** Affects: libfprint (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1965879 somerville ** Attachment added: "fprintd.log" https://bugs.launchpad.net/bugs/1966911/+attachment/5574222/+files/fprintd.log ** Tags added: oem-priority originate-from-1965879 somerville ** Changed in: oem-priority Assignee: (unassigned) => Andy Chi (andch) ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Status: New => Confirmed ** Also affects: libfprint Importance: Undecided Status: New ** Project changed: libfprint => ubuntu ** Package changed: ubuntu => libfprint (Ubuntu) ** Changed in: libfprint-2-tod1-goodix Assignee: (unassigned) => Andy Chi (andch) ** Changed in: libfprint-2-tod1-goodix Importance: Undecided => Critical ** Changed in: libfprint-2-tod1-goodix Status: New => Confirmed -- 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/1966911 Title: Cannot enroll finger on Jammy To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1966911/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1944369] Re: Crash with fprintd 1.92.0
fprintd won't crash with new libfprint version on Jammy which is 1:1.94.3+tod1-0ubuntu1. ** 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/1944369 Title: Crash with fprintd 1.92.0 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint-2-tod1-goodix/+bug/1944369/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
