[Bug 1826543] Re: [Wayland] Support multiple monitors with different scaling factors
[Expired for gnome-shell-extension-ubuntu-dock (Ubuntu) because there has been no activity for 60 days.] ** Changed in: gnome-shell-extension-ubuntu-dock (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/1826543 Title: [Wayland] Support multiple monitors with different scaling factors To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-ubuntu-dock/+bug/1826543/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] Re: SRU the current 2.48.7 stable update
Attaching a debdiff for the SRU, please sponsor. ** Attachment added: "librsvg-focal.debdiff.gz" https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+attachment/5385451/+files/librsvg-focal.debdiff.gz -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Maybe I should add that I qualify the OSK appearing in laptop mode under X as "Success" because: -This is how it behaved until 19.10 both under X and Wayland -In the upstream bug it was mentioned that the laptop vs tablet mode detection would not work under X and so the new behavior under Wayland (no OSK in laptop mode) could not (yet) be duplicated -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1866556] Re: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal
Fix released, see the new bug #1880596. Should this one be marked a duplicate of bug #1880596? -- 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/1866556 Title: On-screen keyboard (OSK) on touch screen does not seem to work at all under Xorg in Focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1866556/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
Installed mutter 3.36.3-0ubuntu0.20.04.1 from -proposed. This fixes the bug for me on the Dell XPS 9575 (could not test on the Asus Zenbook) Tested: 1. Logged into Xorg session 2. In laptop mode (physical keyboard enabled): - Touch Activities > Search: Success, OSK appears - Touch Show Applications > Search: Success, OSK appears - Open gnome-term > touch input area: Success, OSK appears - Open gedit > touch test areas: Success, OSK appears - Open Firefox > touch search box: Success, OSK appears - Open GnuCash (gtk application) > touch: OSK appears, but is flakey. This is as I remember it always to be - Swiped up from bottom of screen to summon OSK as needed: Success, OSK appears - In all test cases: touched DownArrow button on OSK: Success, OSK disappears 3. Folded display to tablet mode (physical keyboard disabled): - Same tests, same behavior 4. Log out and into Wayland session: - Same tests and successes in tablet mode. In laptop mode, the OSK never appears as expected due to the design decision mentioned above* * Still rather infuriating that you can touch a textfield but are not allowed to enter anything ** Tags removed: verification-needed ** Tags added: verification-done-focal ** Tags removed: verification-needed-focal -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1880596] Re: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled
And thank you! -- 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/1880596 Title: [Focal regression] On-screen keyboard (OSK) does not appear on touch under Xorg on convertible laptops in tablet mode when physical keyboard disabled To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1880596/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884326] [NEW] SRU the current 2.48.7 stable update
Public bug reported: * Impact That's the current GNOME stable update, which fixes a number of issues: https://gitlab.gnome.org/GNOME/librsvg/-/blob/librsvg-2.48/NEWS * Test case The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME Smoke testing by opening SVG images with eog or importing them with gimp can be performed to ensure there are no regressions. * Regression potential This is a bugfix-only stable micro-release, however librsvg is a core component with a number of reverse dependencies. A combination of autopkgtests and manual smoke testing to try and detect SVG rendering issues should be performed. ** Affects: librsvg (Ubuntu) Importance: High Assignee: Olivier Tilloy (osomon) Status: Fix Released ** Affects: librsvg (Ubuntu Focal) Importance: High Assignee: Olivier Tilloy (osomon) Status: In Progress ** Changed in: librsvg (Ubuntu) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu) Importance: Undecided => High ** Changed in: librsvg (Ubuntu) Status: New => Fix Released ** Also affects: librsvg (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: librsvg (Ubuntu Focal) Assignee: (unassigned) => Olivier Tilloy (osomon) ** Changed in: librsvg (Ubuntu Focal) Importance: Undecided => High ** Changed in: librsvg (Ubuntu Focal) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1884326 Title: SRU the current 2.48.7 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1884326/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
So, the new builds are new enough versions but libimobiledevice is still built against gnutls and so file transfers don't work. If I build my own library at the 1.3.0 version against openssl and drop it in, then it all works fine. The new builds of libplist and libusbmuxd are very helpful as they make it easy to rebuild libimobiledevice, but until the build is switched to openssl, it'll be broken no matter the version. And so yes, focal is broken too. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1882462] Re: Displays wake up pre-maturely (likely driven by notification)
OK, I'm out of ideas. Using do not disturb and thereby eliminating notifications didn't help either. -- 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/1882462 Title: Displays wake up pre-maturely (likely driven by notification) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1882462/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878275] Re: [qxl] wayland session hard freezes on login from GDM (X11 session works fine)
I was unable to upload the videos to Launchpad, so I uploaded them to Youtube. Here are the links: Video from laptop: https://youtu.be/rPCjCMRwtoo Video from VM: https://youtu.be/9enU0jCbtVI -- 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/1878275 Title: [qxl] wayland session hard freezes on login from GDM (X11 session works fine) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1878275/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881971] Re: Update to 3.36.3 and SRU it
Mutter in proposed works properly both standalone and running gnome- shell mutter: Installato: 3.36.3-0ubuntu0.20.04.1 Candidato: 3.36.3-0ubuntu0.20.04.1 Tabella versione: *** 3.36.3-0ubuntu0.20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-3ubuntu3 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** 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 mutter in Ubuntu. https://bugs.launchpad.net/bugs/1881971 Title: Update to 3.36.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1881971/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881912] Re: SRU 1.64.3 to focal
Gjs in proposed works as expected, and no related issues have been noticed when running gnome-shell gjs: Installato: 1.64.3-1~ubuntu20.04.1 Candidato: 1.64.3-1~ubuntu20.04.1 Tabella versione: *** 1.64.3-1~ubuntu20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 1.64.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 1.64.1-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1881912 Title: SRU 1.64.3 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1881912/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881973] Re: Update to 3.36.3 and SRU it
Shell in proposed works properly ❯ apt-cache policy gnome-shell gnome-shell: Installato: 3.36.3-1ubuntu1~20.04.2 Candidato: 3.36.3-1ubuntu1~20.04.2 Tabella versione: *** 3.36.3-1ubuntu1~20.04.2 500 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.2-1ubuntu1~20.04.1 500 500 http://archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages ** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1881973 Title: Update to 3.36.3 and SRU it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1881973/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
** No longer affects: gnome-control-center (Ubuntu Focal) -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876502] Re: Elan Microelectronics Corp fingerprint reader not recognized
** Changed in: libfprint (Ubuntu) Status: Fix Released => Fix Committed ** Changed in: libfprint (Ubuntu) Status: Fix Committed => 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/1876502 Title: Elan Microelectronics Corp fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1876502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1 --- libfprint (1:1.90.2+tod1-0ubuntu1) groovy; urgency=medium * New upstream release - Fixed crash in VFS0050 (LP: #1876502) - Enrollment fails with UPEK reader (LP: #1881380) - Lots of various drivers fixes - As per a patch for nbis required for some sensors that was accidentally dropped in an earlier release. Users of sensors/drivers aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll * d/p/git_reading_pointer.patch: - Dopped (applied upstream) * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267) * debian/rules: Be strictier about symbol changes * libfprint-2-tod1.symbols: Add new TOD symbols -- Marco Trevisan (Treviño) Fri, 19 Jun 2020 17:38:55 +0200 ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Released ** Changed in: libfprint (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884267] Re: TOD build dependencies are missing packages
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1 --- libfprint (1:1.90.2+tod1-0ubuntu1) groovy; urgency=medium * New upstream release - Fixed crash in VFS0050 (LP: #1876502) - Enrollment fails with UPEK reader (LP: #1881380) - Lots of various drivers fixes - As per a patch for nbis required for some sensors that was accidentally dropped in an earlier release. Users of sensors/drivers aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll * d/p/git_reading_pointer.patch: - Dopped (applied upstream) * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267) * debian/rules: Be strictier about symbol changes * libfprint-2-tod1.symbols: Add new TOD symbols -- Marco Trevisan (Treviño) Fri, 19 Jun 2020 17:38:55 +0200 ** 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/1884267 Title: TOD build dependencies are missing packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1884267/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1 --- libfprint (1:1.90.2+tod1-0ubuntu1) groovy; urgency=medium * New upstream release - Fixed crash in VFS0050 (LP: #1876502) - Enrollment fails with UPEK reader (LP: #1881380) - Lots of various drivers fixes - As per a patch for nbis required for some sensors that was accidentally dropped in an earlier release. Users of sensors/drivers aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll * d/p/git_reading_pointer.patch: - Dopped (applied upstream) * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267) * debian/rules: Be strictier about symbol changes * libfprint-2-tod1.symbols: Add new TOD symbols -- Marco Trevisan (Treviño) Fri, 19 Jun 2020 17:38:55 +0200 ** Changed in: libfprint (Ubuntu) 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/1881380 Title: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1881380/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876502] Re: Elan Microelectronics Corp fingerprint reader not recognized
This bug was fixed in the package libfprint - 1:1.90.2+tod1-0ubuntu1 --- libfprint (1:1.90.2+tod1-0ubuntu1) groovy; urgency=medium * New upstream release - Fixed crash in VFS0050 (LP: #1876502) - Enrollment fails with UPEK reader (LP: #1881380) - Lots of various drivers fixes - As per a patch for nbis required for some sensors that was accidentally dropped in an earlier release. Users of sensors/drivers aes1610, aes2501, aes2550, aes1660, aes2660, elan, upektc_img) need to re-enroll * d/p/git_reading_pointer.patch: - Dopped (applied upstream) * debian/control: Add missing libfprint-2-tod-dev dependencies (LP: #1884267) * debian/rules: Be strictier about symbol changes * libfprint-2-tod1.symbols: Add new TOD symbols -- Marco Trevisan (Treviño) Fri, 19 Jun 2020 17:38:55 +0200 ** Changed in: libfprint (Ubuntu) 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/1876502 Title: Elan Microelectronics Corp fingerprint reader not recognized To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1876502/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881380] Re: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader
** Description changed: + [ Impact ] + The fingerprint reader is an UPEK TCRE3C usb fingerprint reader. It was working fine with ubuntu 16.04 and 18.04. + + [ Test case ] + + With an UPEK fingerprint reader run: + - fprintd-enroll + + Enrollment should work properly + + [ Regression potential ] + + Fingers are not enrolled (not that now they are :)) + + lsusb shows: 0483:2016 STMicroelectronics Fingerprint Reader - user@xubuntu:~$ fprintd-enroll + user@xubuntu:~$ fprintd-enroll Using device /net/reactivated/Fprint/Device/0 failed to claim device: Open failed with error: transfer timed out user@xubuntu:~$ fprintd-list user found 1 devices Device at /net/reactivated/Fprint/Device/0 Using device /net/reactivated/Fprint/Device/0 User user has no fingers enrolled for UPEK TouchStrip. - This bug is probably the same as: https://bugzilla.redhat.com/show_bug.cgi?id=1832229 ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Status: New => Fix Committed ** Changed in: libfprint (Ubuntu) Status: In Progress => Fix Committed ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => High ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- 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/1881380 Title: fprintd-enroll fails on fresh install of xubuntu 20.04 with an USB UPEK reader To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1881380/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
** Description changed: + [ Impact ] + When I try to setup my fingerprint in gnome-control-center, I first have to choose which finger I would use, and when I press the "next" button, it crashes : "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". - For information, my fingerprint sensor is : - lsusb Bus 001 Device 005: ID 138a:0050 Validity Sensors, Inc. Swipe Fingerprint Sensor + [ Test case ] + + With a fingerprint reader 138a:0050: + - Open gnome-control-center user-accounts + - Select the fingeprint row to enroll a finger + - Follow the procedure and the finger should be enrolled + - Verify with: +fprintd-list $USER + + [ Regression potential ] + + - The fingerprint is not read by the sensor + + + --- Ubuntu 20.04 gnome-control-center: - Installé : 1:3.36.1-1ubuntu5 - Candidat : 1:3.36.1-1ubuntu5 - Table de version : - *** 1:3.36.1-1ubuntu5 500 - 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages - 100 /var/lib/dpkg/status + Installé : 1:3.36.1-1ubuntu5 + Candidat : 1:3.36.1-1ubuntu5 + Table de version : + *** 1:3.36.1-1ubuntu5 500 + 500 http://be.archive.ubuntu.com/ubuntu focal/main amd64 Packages + 100 /var/lib/dpkg/status - - What I expected to happen, is that everything works and that I can set up my finger for unlocking. + What I expected to happen, is that everything works and that I can set + up my finger for unlocking. What happened instead : it crashes with the information "Unable to access device "Validity VFS0050" GDBus.Error:org.freedesktop.DBus.Error.NoReply:Message recipient disconnected from message bus without replying". - ProblemType: Bug - DistroRelease: Ubuntu 20.04 + ProblemType: BugDistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.1-1ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia wl ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 22:00:30 2020 InstallationDate: Installed on 2020-05-11 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: - LANGUAGE=fr_BE:fr - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=fr_BE.UTF-8 - SHELL=/bin/bash - SourcePackage: gnome-control-center + LANGUAGE=fr_BE:fr + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_BE.UTF-8 + SHELL=/bin/bashSourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Changed in: libfprint (Ubuntu) Status: Triaged => In Progress ** Also affects: gnome-control-center (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: libfprint (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: libfprint (Ubuntu Focal) Status: New => In Progress ** Changed in: libfprint (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: libfprint (Ubuntu Focal) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) ** Changed in: libfprint (Ubuntu) Importance: Low => Medium -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
Great, you're in! You can disable proposed repositories if you want now, as you prefer :). ** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883902] Re: rhythmbox ignores pulseaudio default sink and outputs sound on random device
crvi : did you use RAOP sink as networks sinks ? I don't know if it matters, but my 2 networks sinks are both RAOP. Anyway, I have some more information : I can totally reproduce the problem with latest Fedora Live USB (Fedora-WS-Live-32-1-6), so it's not OS specific. I also tried Ubuntu 19.10 on live USB : the problem is not here. To be specific, in this situation : the 1st time I launch rhythmbox, it ignores my default sink. But with pavucontrol I can remap it to my local sink (my soundcard). Then I quit and relaunch rhythmbox : this time it remembers the last sink used and outputs sound on my local soundcard. My humble analysis : - it's probably an upstream problem - rhythmbox never took the default sink defined in pulseaudio into account - In version 3.4.3 and before, rhythmbox remembers last sink used and reconnects to it for next launch - this "save" function broke in 3.4.4 - specific conditions to trigger the problem are still to be defined, RAOP sinks may have a role -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1883902 Title: rhythmbox ignores pulseaudio default sink and outputs sound on random device To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1883902/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1884267] [NEW] TOD build dependencies are missing packages
Public bug reported:
Compiling a TOD package from source by build-depending only on
libfprint-2-tod-dev, does not work, as the tod-dev package has misses
the .pc dependencies.
❯ less /usr/lib/x86_64-linux-gnu/pkgconfig/libfprint-2-tod-1.pc
prefix=/usr
libdir=${prefix}/lib/x86_64-linux-gnu
includedir=${prefix}/include
tod_driversdir=${libdir}/libfprint-2/tod-1
Name: libfprint-2-tod
Description: Private Libfprint Touch Drivers API
Version: 1.90.1+tod1+tod1
Requires.private: gio-unix-2.0 >= 2.56, glib-2.0 >= 2.56, gusb >= 0.2.0,
pixman-1, nss, gmodule-2.0 >= 2.56, libfprint-2
Libs: -L${libdir} -lfprint-2-tod
Libs.private: -lm
Cflags: -I${includedir}/libfprint-2/tod-1
[ Impact ]
No possible to compile TOD packages without manual depenencies
[ Test case ]
Try with this driver https://gitlab.freedesktop.org/3v1n0/libfprint-tod-
vfs0090/-/tree/tod-deps-test
git clone https://gitlab.freedesktop.org/3v1n0/libfprint-tod-vfs0090 -b
tod-deps-test
gbp buildpackage -b
Should work
[ Regression potential ]
Installed dependencies may cause a conflict
** Affects: libfprint (Ubuntu)
Importance: Medium
Assignee: Marco Trevisan (Treviño) (3v1n0)
Status: 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/1884267
Title:
TOD build dependencies are missing packages
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1884267/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1242966] Re: Image viewer doesn't save image rotation changes
Hi, I have a fresh installation of Ubuntu 20.04 with Gnome Image Viewer version 3.36.2 and I have the same issue. When I rotate a single image and exit, a confirmation dialog appears and clicking save result in the right behavior. Nevertheless if i rotate multiple images and then exit the program modify the images but finally they are not rotated at all. I hope this helps Juxmix -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to eog in Ubuntu. https://bugs.launchpad.net/bugs/1242966 Title: Image viewer doesn't save image rotation changes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eog/+bug/1242966/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
p-i@asus-b450-f:~$ apt-cache policy gnome-shell gnome-shell: Installed: 3.36.3-1ubuntu1~20.04.2 Candidate: 3.36.3-1ubuntu1~20.04.2 Version table: *** 3.36.3-1ubuntu1~20.04.2 500 500 http://se.archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 500 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages 100 /var/lib/dpkg/status 3.36.2-1ubuntu1~20.04.1 500 500 http://se.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 3.36.1-5ubuntu1 500 500 http://se.archive.ubuntu.com/ubuntu focal/main amd64 Packages p-i@asus-b450-f:~ Den fre 19 juni 2020 kl 16:05 skrev Marco Trevisan (Treviño) < 1877...@bugs.launchpad.net>: > Please, ensure the version with the command I gave to you > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877760 > > Title: > gnome-shell crashed with SIGSEGV in __strncmp_avx2() from > g_str_has_prefix() from _st_theme_node_ensure_background() from > st_theme_node_paint_equal > > Status in GNOME Shell: > Unknown > Status in gnome-shell package in Ubuntu: > Fix Released > Status in gnome-shell source package in Focal: > Fix Committed > > Bug description: > [ Impact ] > > GNOME shell crashes on extensions loading / updates > > [ Test case ] >- No clear test case, normally may happen during screen > locking/unlocking >- But crashes should be monitored at > > https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3 > > [ Regression potential ] > > Stylesheet memory could be leaked > > --- > > Started the computer from suspend. Started Gmail from Dash to Panel. > > ProblemType: CrashDistroRelease: Ubuntu 20.10 > Package: gnome-shell 3.36.2-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 > Uname: Linux 5.4.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu33 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 18:30:48 2020 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > InstallationDate: Installed on 2020-04-16 (23 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 > (20200415.2) > ProcCmdline: /usr/bin/gnome-shell > RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 > SegvAnalysis: >Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu > (%rdi),%ymm1 >PC (0x7fe9fdcc3e41) ok >source "(%rdi)" (0xf0250) not located in a known VMA region (needed > readable region)! >destination "%ymm1" ok > SegvReason: reading unknown VMA > Signal: 11SourcePackage: gnome-shell > StacktraceTop: >__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 >g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >_st_theme_node_ensure_background () from /usr/lib/gnome-shell/ > libst-1.0.so >st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so >?? () from /usr/lib/gnome-shell/libst-1.0.so > Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions > -- Skickat från min nya mailadress -- 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/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878285] Re: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050
** Summary changed: - gnome-control-center crashes on setting up fingerprint + gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 -- 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/1878285 Title: gnome-control-center / fprintd crashes on setting up fingerprint with vfs0050 To manage notifications about this bug go to: https://bugs.launchpad.net/libfprint/+bug/1878285/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1854403] Re: Need updated libimobiledevice and dependencies to access iOS 13 devices
Upstream rolled new versions and they landed in Debian and now Ubuntu https://bugs.launchpad.net/ubuntu/+source/libplist/2.2.0-3 https://bugs.launchpad.net/ubuntu/+source/libusbmuxd/2.0.2-2 https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/1.3.0-2 Could someone with access to a device try if things work well using those? Is focal buggy and needing an update? ** Changed in: libplist (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libusbmuxd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: libimobiledevice (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libimobiledevice in Ubuntu. https://bugs.launchpad.net/bugs/1854403 Title: Need updated libimobiledevice and dependencies to access iOS 13 devices To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1854403/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
Please, ensure the version with the command I gave to you -- 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/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1861332] Re: Bump version to 1.90 to add support for Synaptics 06cb:00bd
** 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/1861332 Title: Bump version to 1.90 to add support for Synaptics 06cb:00bd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1861332/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1878172] Re: FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not working
*** This bug is a duplicate of bug 1878285 *** https://bugs.launchpad.net/bugs/1878285 ** This bug has been marked a duplicate of bug 1878285 gnome-control-center crashes on setting up fingerprint -- 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/1878172 Title: FUJITSU LIFEBOOK U748: 138a:0050 Validity Sensors not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1878172/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1881458] Re: Playback aborts when a download is started, printing "server does not support seeking"
The URI you put up plays fine. Unfortunately, I ran into the same issue when I started a different stream. There were a few short skips at first but the player came back. Then it suddenly gave up completely with the error message mentioned in my opening post. I am including the log file. The issue appears to show up in lines 8492-8493. The lines further down show a recurring pattern so I assume that the player is stuck in a loop that prevents it from resuming. ** Attachment added: "rhythmbox.log" https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+attachment/5385346/+files/rhythmbox.log -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to rhythmbox in Ubuntu. https://bugs.launchpad.net/bugs/1881458 Title: Playback aborts when a download is started, printing "server does not support seeking" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/1881458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
No, this is noy groovy. I have downloaded Focal Daily from http://iso.qa.ubuntu.com/qatracker/milestones/408/builds some days ago and updates regularly and I think the developer option is set. After an update today the Gnome version is " Desktop: Gnome 3.36.3". I have made a couple of suspends and there is no crash.. Den fre 19 juni 2020 kl 12:30 skrev Marco Trevisan (Treviño) < 1877...@bugs.launchpad.net>: > > I'm now using the development version of 20.04.1. Will this fix be > included? > > What do you mean by that? Are you using groovy? > > However, to check, just look what version of gnome-shell you're running via > - apt-cache policy gnome-shell > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877760 > > Title: > gnome-shell crashed with SIGSEGV in __strncmp_avx2() from > g_str_has_prefix() from _st_theme_node_ensure_background() from > st_theme_node_paint_equal > > Status in GNOME Shell: > Unknown > Status in gnome-shell package in Ubuntu: > Fix Released > Status in gnome-shell source package in Focal: > Fix Committed > > Bug description: > [ Impact ] > > GNOME shell crashes on extensions loading / updates > > [ Test case ] >- No clear test case, normally may happen during screen > locking/unlocking >- But crashes should be monitored at > > https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3 > > [ Regression potential ] > > Stylesheet memory could be leaked > > --- > > Started the computer from suspend. Started Gmail from Dash to Panel. > > ProblemType: CrashDistroRelease: Ubuntu 20.10 > Package: gnome-shell 3.36.2-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 > Uname: Linux 5.4.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu33 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 18:30:48 2020 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > InstallationDate: Installed on 2020-04-16 (23 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 > (20200415.2) > ProcCmdline: /usr/bin/gnome-shell > RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 > SegvAnalysis: >Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu > (%rdi),%ymm1 >PC (0x7fe9fdcc3e41) ok >source "(%rdi)" (0xf0250) not located in a known VMA region (needed > readable region)! >destination "%ymm1" ok > SegvReason: reading unknown VMA > Signal: 11SourcePackage: gnome-shell > StacktraceTop: >__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 >g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >_st_theme_node_ensure_background () from /usr/lib/gnome-shell/ > libst-1.0.so >st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so >?? () from /usr/lib/gnome-shell/libst-1.0.so > Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions > -- Skickat från min nya mailadress -- 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/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1873692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591323] Re: No low battery notification, shutdown without warning
Could you add your 'journalctl' log after getting the issue? ** Changed in: gnome-power-manager (Ubuntu) Importance: High => Low ** Changed in: gnome-power-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1591323 Title: No low battery notification, shutdown without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1591323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718994] Re: gnome-software crashed with SIGSEGV in gtk_widget_unparent()
Thanks for reporting it upstream ** Changed in: gnome-software (Ubuntu) Status: Confirmed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1718994 Title: gnome-software crashed with SIGSEGV in gtk_widget_unparent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1718994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1718994] Re: gnome-software crashed with SIGSEGV in gtk_widget_unparent()
Still happens as of Ubuntu 20.04, I reported it to upstream now: https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1016 ** Changed in: gnome-software (Ubuntu) Status: Expired => Confirmed ** Bug watch added: gitlab.gnome.org/GNOME/gnome-software/-/issues #1016 https://gitlab.gnome.org/GNOME/gnome-software/-/issues/1016 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1718994 Title: gnome-software crashed with SIGSEGV in gtk_widget_unparent() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1718994/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1873692] Re: Do Not Disturb setting does not persist across login sessions
Hi, I have now installed gnome-shell/focal-proposed,now 3.36.3-1ubuntu1~20.04.2 amd64 [installed] and the patch works as expected. The setting of Do Not Disturb persists across login sessions. 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/1873692 Title: Do Not Disturb setting does not persist across login sessions To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1873692/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
> I'm now using the development version of 20.04.1. Will this fix be included? What do you mean by that? Are you using groovy? However, to check, just look what version of gnome-shell you're running via - apt-cache policy gnome-shell -- 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/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking
** 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-shell in Ubuntu. https://bugs.launchpad.net/bugs/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1838838] Re: username is not saved in openconnect connection dialog
@GeekSmith Thanks for sharing this working! Wonderful! -- 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/1838838 Title: username is not saved in openconnect connection dialog To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1838838/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Re: [Bug 1877760] Re: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal
I'm now using the development version of 20.04.1. Will this fix be included? Den fre 19 juni 2020 kl 07:55 skrev Timo Aaltonen < 1877...@bugs.launchpad.net>: > Hello Per-Inge, or anyone else affected, > > Accepted gnome-shell into focal-proposed. The package will build now and > be available at https://launchpad.net/ubuntu/+source/gnome- > shell/3.36.3-1ubuntu1~20.04.2 in a few hours, and then in the -proposed > repository. > > Please help us by testing this new package. See > https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how > to enable and use -proposed. Your feedback will aid us getting this > update out to other Ubuntu users. > > If this package fixes the bug for you, please add a comment to this bug, > mentioning the version of the package you tested, what testing has been > performed on the package and change the tag from verification-needed- > focal to verification-done-focal. If it does not fix the bug for you, > please add a comment stating that, and change the tag to verification- > failed-focal. In either case, without details of your testing we will > not be able to proceed. > > Further information regarding the verification process can be found at > https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in > advance for helping! > > N.B. The updated package will be released to -updates after the bug(s) > fixed by this package have been verified and the package has been in > -proposed for a minimum of 7 days. > > ** Changed in: gnome-shell (Ubuntu Focal) >Status: Fix Released => Fix Committed > > ** Tags added: verification-needed verification-needed-focal > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1877760 > > Title: > gnome-shell crashed with SIGSEGV in __strncmp_avx2() from > g_str_has_prefix() from _st_theme_node_ensure_background() from > st_theme_node_paint_equal > > Status in GNOME Shell: > Unknown > Status in gnome-shell package in Ubuntu: > Fix Released > Status in gnome-shell source package in Focal: > Fix Committed > > Bug description: > [ Impact ] > > GNOME shell crashes on extensions loading / updates > > [ Test case ] >- No clear test case, normally may happen during screen > locking/unlocking >- But crashes should be monitored at > > https://errors.ubuntu.com/problem/ed05979081de9b66eac4a9eaa25e51fac88e43a3 > > [ Regression potential ] > > Stylesheet memory could be leaked > > --- > > Started the computer from suspend. Started Gmail from Dash to Panel. > > ProblemType: CrashDistroRelease: Ubuntu 20.10 > Package: gnome-shell 3.36.2-1ubuntu1 > ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 > Uname: Linux 5.4.0-28-generic x86_64 > ApportVersion: 2.20.11-0ubuntu33 > Architecture: amd64 > CasperMD5CheckResult: skip > CurrentDesktop: ubuntu:GNOME > Date: Sat May 9 18:30:48 2020 > DisplayManager: gdm3 > ExecutablePath: /usr/bin/gnome-shell > InstallationDate: Installed on 2020-04-16 (23 days ago) > InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 > (20200415.2) > ProcCmdline: /usr/bin/gnome-shell > RelatedPackageVersions: mutter-common 3.36.2-1ubuntu1 > SegvAnalysis: >Segfault happened at: 0x7fe9fdcc3e41 <__strncmp_avx2+49>:vmovdqu > (%rdi),%ymm1 >PC (0x7fe9fdcc3e41) ok >source "(%rdi)" (0xf0250) not located in a known VMA region (needed > readable region)! >destination "%ymm1" ok > SegvReason: reading unknown VMA > Signal: 11SourcePackage: gnome-shell > StacktraceTop: >__strncmp_avx2 () at ../sysdeps/x86_64/multiarch/strcmp-avx2.S:101 >g_str_has_prefix () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 >_st_theme_node_ensure_background () from /usr/lib/gnome-shell/ > libst-1.0.so >st_theme_node_paint_equal () from /usr/lib/gnome-shell/libst-1.0.so >?? () from /usr/lib/gnome-shell/libst-1.0.so > Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() > UpgradeStatus: No upgrade log present (probably fresh install) > UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo > separator: > > To manage notifications about this bug go to: > https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions > -- Skickat från min nya mailadress -- 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/1877760 Title: gnome-shell crashed with SIGSEGV in __strncmp_avx2() from g_str_has_prefix() from _st_theme_node_ensure_background() from st_theme_node_paint_equal To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1877760/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1591323] Re: No low battery notification, shutdown without warning
Is there some progress? It's still there in 18.04 - I#ve upgraded from 16.04 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in Ubuntu. https://bugs.launchpad.net/bugs/1591323 Title: No low battery notification, shutdown without warning To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/1591323/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883118] Re: SRU the current 3.36.3 stable update
Hello Sebastien, or anyone else affected, Accepted evolution into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/evolution/3.36.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: evolution (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1883118 Title: SRU the current 3.36.3 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1883118/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883123] Re: SRU the current 3.36.2 stable update
Hello Sebastien, or anyone else affected, Accepted epiphany-browser into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/epiphany- browser/3.36.2-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: epiphany-browser (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to epiphany-browser in Ubuntu. https://bugs.launchpad.net/bugs/1883123 Title: SRU the current 3.36.2 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/epiphany-browser/+bug/1883123/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883116] Re: SRU the current 3.36.3 stable update
Hello Sebastien, or anyone else affected, Accepted evolution-data-server into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /evolution-data-server/3.36.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: evolution-data-server (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1883116 Title: SRU the current 3.36.3 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution-data-server/+bug/1883116/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking
JP, This crash does not affect 18.04. There have been ZERO cases of it from bionic. If you experience any problems with 18.04 then please open a new bug by running: ubuntu-bug gnome-shell -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking
Hello, will you solve the problem in Ubuntu 18.04.4 LTS too ? Gnome crashes when I lock my screen with gnome-shell 3.28.4. I have "dash to panel" extension on this computer too. -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877774] Re: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking
The package gnome-shell 3.36.3-1ubuntu1~20.04.2 (and gnome-shell-common) fixed the bug for me. On the previous version 3.36.2-1ubuntu1~20.04.1 locking the screen (unrelated to suspend) using Windows+L would directly crash gnome-shell and it would be restarted. The same now works again with the update. Thank you! -- 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/184 Title: gnome-shell crashed with SIGSEGV in _st_theme_node_ensure_background() from st_theme_node_paint_equal() from st_widget_recompute_style() from st_widget_style_changed() [when locking the screen] [usually due to dash-to-panel] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/184/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1876937] Re: Dock location reversed in RTL
Thank you Marco! Your effort is very important to a large community of RTL Ubuntu users. This is definitely bringing us one step closer to improving the overall usage experience for those crazy languages speakers :) -- 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/1876937 Title: Dock location reversed in RTL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1876937/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1883516] Re: display is freezing randomly
Dear Daniel, thank you for your assistance, unfortunately I cannot run anything when the display freezes. The system seems to run, since sound is playing, but the display does not update at all. I have to make a hard reset by pushing the power button for a while to get the system running again. However, it did not happen for a while now. I try to keep my system up to date, so maybe a kernel patch has fixed the issue. I will let you know if it happens again and try to disable shell extensions then. Best Regards, Gregor -- 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/1883516 Title: display is freezing randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1883516/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1882952] Re: SRU the current 0.30.10 stable version
Hello Sebastien, or anyone else affected, Accepted shotwell into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/shotwell/0.30.10-0ubuntu0.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: shotwell (Ubuntu Focal) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-focal -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to shotwell in Ubuntu. https://bugs.launchpad.net/bugs/1882952 Title: SRU the current 0.30.10 stable version To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/shotwell/+bug/1882952/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1793496] Re: scaling changes when closing/re-opening the lid
Hello Matthias, or anyone else affected, Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.4+git20200505-0ubuntu18.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: mutter (Ubuntu Bionic) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-bionic -- 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/1793496 Title: scaling changes when closing/re-opening the lid To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1793496/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1877075] Re: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed
Verified the fix is present in mutter_3.36.3.orig.tar.xz but as mentioned above, no known test case. ** Tags removed: verification-needed verification-needed-focal ** Tags added: verification-done verification-done-focal ** Description changed: [Impact] This is the #1 crasher of gnome-shell in Ubuntu 20.04, though it's duplicated across multiple problem reports according to locale: https://errors.ubuntu.com/problem/4de3d315d9df1c9699bda54beafa8d52053c https://errors.ubuntu.com/problem/2251b638f7a6167772f922dc5916740522c5c22b https://errors.ubuntu.com/problem/943838b8a80c1da4f8df584b7d2ad3a13361fdd7 https://errors.ubuntu.com/problem/4b78bc9730e8681f0c42fc2ecea14d03544394f0 [Test Case] None known. The plan is to just continue monitoring crash reports. Still, we are confident this is the fix because: * The offending source code in libx11 tells us it is :) and * The crash only started in Ubuntu with gnome-shell 3.34, which is the exact release in which XInitThreads was removed from mutter. [Regression Potential] Low. We add a single function call that tells libX11 to enable thread - safety. This same function call as one we had in bionic, cosmic and - disco. + safety. This is the same as what we had in bionic, cosmic and disco, so + it's well tested. -- 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/1877075 Title: gnome-shell crashed at xcb_io.c:260: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost'' failed To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1877075/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879234] Re: Clicking Activities does nothing - screen appears to freeze
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => Invalid -- 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/1879234 Title: Clicking Activities does nothing - screen appears to freeze To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1879234/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
