[Bug 1726224] Re: wacom invisible mouse pointer in wayland
Launchpad has imported 6 comments from the remote bug at https://bugzilla.gnome.org/show_bug.cgi?id=789754. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2017-11-01T09:27:49+00:00 Alessandro wrote: After log-in with Wacom tablet connected Gnome shows two cursors, one for the mouse and the other for the tablet's pen. I can normally control the pen's cursor. After a while the pen's cursor disappears (it is invisible, but I can still control it with the pen). If I reset the shell with "killall -HUP gnome-shell" and I log in again the cursor is back. Thanks Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/6 On 2017-11-01T10:09:58+00:00 Alessandro wrote: Additional info: the pen cursor disappears when I move in the same time both mouse and pen. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/7 On 2017-11-08T21:48:19+00:00 Alessandro wrote: Additionally if I press any of the Wacom Intuos Pen and Touch buttons the screen freezes completely and I have to restart the PC. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/13 On 2017-11-21T19:22:42+00:00 Schatzkin-o wrote: I'm having these problems too. In addition, I cannot open a dropdown menu using the pen. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/14 On 2018-01-14T03:04:36+00:00 Casey wrote: This seems to happen with applications running under XWayland. For pure Wayland applications the Wacom tablet's cursor behaves correctly. To see this, open for instance gnome-terminal (which uses Wayland) and Xournal (which uses XWayland) side by side. When moving the cursor from gnome-terminal to Xournal, the cursor does not change to a pen but instead remains whatever it was when it left the gnome-terminal window, such as an arrow or a text cursor. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/18 On 2018-02-01T04:49:15+00:00 Ian wrote: Aside from the drop-down menu and pen button problems, I have all of the issues above while using digimend drivers and a Huion tablet; this is probably not a problem with the Gnome Wacom drivers but rather an issue with XWayland, as Casey pointed out. Another thing worth mentioning is that on my system, after I switch off my pen with a button on the top, my regular pointer can't click anything. I need to either press alt-tab, change workspaces and switch back, or a few other options to restore the normal cursor. Reply at: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1726224/comments/19 ** Changed in: gnome-shell Status: Unknown => Confirmed ** Changed in: gnome-shell Importance: Unknown => 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/1726224 Title: wacom invisible mouse pointer in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1726224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1726224] Re: wacom invisible mouse pointer in wayland
This bug should have expired last year per comment #18. If anyone still experiences similar issues then please open a new bug by running: ubuntu-bug gnome-shell ** Bug watch added: bugzilla.gnome.org/ #789754 https://bugzilla.gnome.org/show_bug.cgi?id=789754 ** Changed in: gnome-shell Importance: Critical => Unknown ** Changed in: gnome-shell Status: Confirmed => Unknown ** Changed in: gnome-shell Remote watch: GNOME Bug Tracker #789754 => bugzilla.gnome.org/ #789754 ** Changed in: mutter (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: xorg-server (Ubuntu) Status: Incomplete => Won't Fix -- 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/1726224 Title: wacom invisible mouse pointer in wayland To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1726224/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916255] Re: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on
** Summary changed: - Caps Lock not detected properly by GNOME password dialogs + Caps Lock initially not detected in GNOME password dialogs if you logged in with it on ** Changed in: gnome-shell (Ubuntu) Status: New => Triaged ** Tags added: hirsute -- 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/1916255 Title: Caps Lock initially not detected in GNOME password dialogs if you logged in with it on To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916255/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915870] Re: gnome session not starting (segfault with r300_dri.so)
Actually it looks likely to be https://gitlab.freedesktop.org/mesa/mesa/-/issues/3990 so let's track that for now. ** Also affects: mesa via https://gitlab.freedesktop.org/mesa/mesa/-/issues/3990 Importance: Unknown Status: Unknown ** Bug watch added: Red Hat Bugzilla #1908448 https://bugzilla.redhat.com/show_bug.cgi?id=1908448 ** Also affects: mesa (Fedora) via https://bugzilla.redhat.com/show_bug.cgi?id=1908448 Importance: Unknown Status: Unknown ** No longer affects: gnome-shell (Ubuntu) ** Changed in: mesa (Ubuntu) Status: Incomplete => Confirmed -- 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/1915870 Title: gnome session not starting (segfault with r300_dri.so) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915870] Re: gnome session not starting
I should also note that we cannot read the crash file in comment #1. To have that analysed you should run: ubuntu-bug _usr_libexec_gnome-session-check-accelerated-gl- helper.126.crash It looks like it might be one of these crashes in the Mesa r300_dri.so driver: https://errors.ubuntu.com/problem/35e91e8a26a38f12a90e6fdca6b964b9a91889bf https://errors.ubuntu.com/problem/c7097de400ef4606fa71cc05b607d4f8d126838d https://errors.ubuntu.com/problem/d92b45e827f9a2ef27ecbd3039ee0d71134404df ** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Summary changed: - gnome session not starting + gnome session not starting (segfault with r300_dri.so) ** Bug watch added: gitlab.freedesktop.org/mesa/mesa/-/issues #3990 https://gitlab.freedesktop.org/mesa/mesa/-/issues/3990 -- 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/1915870 Title: gnome session not starting (segfault with r300_dri.so) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1915870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1909023] Re: package libfprint-2-2:amd64 1:1.90.3+tod1-0ubuntu1 failed to install/upgrade: installed libfprint-2-2:amd64 package post-installation script subprocess returned error exit status 1
This bug was fixed in the package libfprint - 1:1.90.7+git20210222+tod1-0ubuntu1 --- libfprint (1:1.90.7+git20210222+tod1-0ubuntu1) hirsute; urgency=medium * New upstream TOD release * Merge common packaging bits with debian * debian/libfprint-2-2.postinst: Devices triggers updated * debian/patches: Drop, they're all applied upstream * debian/libfprint-2-2.symbols: Update symbols * debian/update-udev-triggers.sh: Ignore udevadm trigger failures (LP: #1909023) * debian/libfprint-2-2.postinst: Regenerate as per generator changes (LP: #1909023) libfprint (1:1.90.7-3) experimental; urgency=medium * gbp.conf: Prepare for experimental branching * debian/patches: - Use hwdb to store device autosuspend rules and drop debian specifics. Upstream will use an hwdb to store the device autosuspend (that will be included in systemd also, so libfprint packagin may stop shipping it at later point), so use it earlier. Drop the debian specific rules to set the devices part of the `plugdev` group as such devices should not be ever readable by an user, but the access should be managed through a libfprint-based service (frpintd at the date). - Explicitly mark libfprint as a shared library * libfprint-2-2.install: Install hwdb file * debian/rules: - Do not autorename upstream rules file anymore. It's not there, while there's no point to rename the hwdb one. - Manually set udev hwdb directory (was rules dir before) - Don't remove the meson generated private values from pc file. This is now generated correctly by upstream, so no need to drop anything from it. * debian: Generate postinst devices list automatically at gbp import phase. Alternatively provide a script to keep the post-inst script updated * debian/libfprint-2-2.postinst: Upgrade as per upstream hwdb. Blacklisted devices can be now removed from the trigger list as we don't add them to plugdev anymore. libfprint (1:1.90.7-2) unstable; urgency=medium * debian/patches: Skip udev rules tests when not all drivers are compiled * debian/libfprint-2-2.postinst: Regenerate the udev list based on new IDs libfprint (1:1.90.7-1) unstable; urgency=medium * New upstream release: - vfs5011: Fix possible use-after-free - goodixmoc: Add two new PIDs (0x63AC, 0x639C) - goodixmoc: Support finger status API - synaptics: Only identify within provided prints - synaptics: Reject devices with old firmware during probe (#239) * debian/patches: - Refresh, dropping merged - Include upstream udev fixes and use hardcoded rules - Ensure that umockdev tests will pass with libusb 1.0.24 (Closes: #977848, #978256) -- Marco Trevisan (Treviño) Mon, 22 Feb 2021 21:39:04 +0100 ** 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/1909023 Title: package libfprint-2-2:amd64 1:1.90.3+tod1-0ubuntu1 failed to install/upgrade: installed libfprint-2-2:amd64 package post- installation script subprocess returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1909023/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 1. Isn't really important to the bug description. 2. Yeah, we know. That's why I removed mention of workspaces from the title for bug 1906792 yesterday and another user in the upstream bug already mentioned workspaces are not a factor (https://gitlab.gnome.org/GNOME/mutter/-/issues/1563). ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #1563 https://gitlab.gnome.org/GNOME/mutter/-/issues/1563 -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879122] Re: Cannot enable wifi hotspot on the first attempt
** Tags added: fixed-in-3.38.0 fixed-upstream -- 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/1879122 Title: Cannot enable wifi hotspot on the first attempt To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1879122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916390] Re: seeding a package that depends/recommends fuse3 causes livefs builds to fail
Looking at this better, this is unrelated to launchpad-buildd's dependency on fuse (which sits outside the chroot) and instead comes via the platform live-common seed which depends on ntfs-3g, which has a pre- depends on fuse. (which is wrong, it should be a dependency not a pre- dependency.) Reassigning this to fuse itself, since requiring parallel fuse and fuse3 daemons in the release should be addressed. ** Project changed: launchpad-buildd => fuse (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to sshfs-fuse in Ubuntu. https://bugs.launchpad.net/bugs/1916390 Title: seeding a package that depends/recommends fuse3 causes livefs builds to fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fuse/+bug/1916390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1865226] Re: gdm-smartcard pam config needs to be updated for Ubuntu and installed
** No longer affects: pam (Ubuntu) ** No longer affects: pam (Ubuntu Bionic) ** No longer affects: pam (Ubuntu Focal) ** No longer affects: pam (Ubuntu Groovy) ** Also affects: gdm3 (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953557 Importance: Unknown Status: Unknown ** Project changed: gdm => ubuntu-translations ** Changed in: ubuntu-translations Importance: Unknown => Undecided ** Changed in: ubuntu-translations Remote watch: Debian Bug tracker #953557 => None ** No longer affects: ubuntu-translations -- 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/1865226 Title: gdm-smartcard pam config needs to be updated for Ubuntu and installed To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-settings-daemon/+bug/1865226/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912060] Re: [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix) cause security issue for cinnamon
It appears that the Focal package has three separate patches for three different issues: - vala compilation - showing an 'e' submenu - undoing xf86 workaround, necessary after an xorg update and it appears that the Groovy package has these three same fixes but all squashed into one patch. Is this intentional? Normally it's better to keep separate fixes separate, so they can be more easily enabled/removed, or backed out when it's found they're not necessary years later. Thanks -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1912060 Title: [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix) cause security issue for cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1912060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1309531] Re: during distribution upgrade 13.10 -> 14.04 libfprint0 fails to confugure with: udevadm trigger is not permitted while udev is unconfigured.
** 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/1309531 Title: during distribution upgrade 13.10 -> 14.04 libfprint0 fails to confugure with: udevadm trigger is not permitted while udev is unconfigured. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1309531/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1822258] Re: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1
** Changed in: libfprint (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/1822258 Title: package libfprint-dev (not installed) failed to install/upgrade: tentative de remplacement de « /usr/include/libfprint/fprint.h », qui appartient aussi au paquet libfprint 0.0.6-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1822258/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1913895] Re: [6cb:00df ] Synaptics fingerprint sensor not working
I guess we can close as per https://askubuntu.com/a/1316326/7788 ** Changed in: libfprint (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/1913895 Title: [6cb:00df ] Synaptics fingerprint sensor not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/1913895/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Description changed: Original description: When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. --- Updates: - As for #1916458 this behaviour may happen also on the same workspace - + As for #1916458 this behaviour may happen also on the same workspace and with Google Chrome ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Description changed: - When using Chromium (snap) on Wayland (gnome-session), if I keep two - windows open on different workspaces, sometimes the current tab becomes - unusable as it freezes or is super-slow. + Original description: + When using Chromium (snap) on Wayland (gnome-session), if I keep two windows open on different workspaces, sometimes the current tab becomes unusable as it freezes or is super-slow. This usually happens with specific pages open, like youtube, mattermost, google drive. Minimizing one of the two windows makes the other work fine. The issues does not happen if both windows are on the same workspace. I've seen this issue in 20.04 and 20.10, always on Wayland sessions. The same behavior doesn't happen on a plain X11 session. + + --- + + Updates: + As for #1916458 this behaviour may happen also on the same workspace + ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-shell 3.38.1-1ubuntu1.1 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Fri Dec 4 09:39:08 2020 DisplayManager: gdm3 InstallationDate: Installed on 2020-10-18 (46 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Beta amd64 (20200930) RelatedPackageVersions: mutter-common 3.38.1-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916390] Re: seeding a package that depends/recommends fuse3 causes livefs builds to fail
The requirement for fuse comes from launchpad-buildd; because livefs builds happen inside a lxd container, fuse is required in order to be able to do mounts during the build. To support fuse3 we will need to arrange some sort of a migration. Why is fuse3 provided as a separate source, instead of being version 3 of the fuse package? If we are going to move to supporting fuse version 3 (i.e. migrating to having it in main), the preferred method is to make the fuse package version 3 so that upgrades work correctly. ** Project changed: ubuntu-cdimage => launchpad-buildd -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to sshfs-fuse in Ubuntu. https://bugs.launchpad.net/bugs/1916390 Title: seeding a package that depends/recommends fuse3 causes livefs builds to fail To manage notifications about this bug go to: https://bugs.launchpad.net/launchpad-buildd/+bug/1916390/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1912060] Re: [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix) cause security issue for cinnamon
(Yes the other commit is needed) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to caribou in Ubuntu. https://bugs.launchpad.net/bugs/1912060 Title: [SRU] caribou: Segfault (as regression of xorg CVE-2020-25712 fix) cause security issue for cinnamon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/caribou/+bug/1912060/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916512] [NEW] many fonts do not uninstall cleanly
Public bug reported: Many fonts do not uninstall cleanly. I verified this in the latest hirsute dev-release. There are .uuid files left behind which prevent removal of the font directory. dpkg: warning: while removing fonts-gargi, directory '/usr/share/fonts/truetype/Gargi' not empty so not removed dpkg: warning: while removing fonts-kalapi, directory '/usr/share/fonts/truetype/fonts-kalapi' not empty so not removed dpkg: warning: while removing fonts-nakula, directory '/usr/share/fonts/truetype/Nakula' not empty so not removed dpkg: warning: while removing fonts-navilu, directory '/usr/share/fonts/truetype/Navilu' not empty so not removed dpkg: warning: while removing fonts-sahadeva, directory '/usr/share/fonts/truetype/Sahadeva' not empty so not removed dpkg: warning: while removing fonts-samyak-deva, directory '/usr/share/fonts/truetype/samyak' not empty so not removed dpkg: warning: while removing fonts-samyak-taml, directory '/usr/share/fonts/truetype/samyak-fonts' not empty so not removed dpkg: warning: while removing fonts-sarai, directory '/usr/share/fonts/truetype/Sarai' not empty so not removed cat /usr/share/fonts/truetype/fonts-kalapi/.uuid 52eae14f-061f-48f2-8c9e-4a29c362316b ** Affects: fonts-navilu (Ubuntu) Importance: Undecided Status: New ** Affects: fonts-pagul (Ubuntu) Importance: Undecided Status: New ** Affects: fonts-samyak (Ubuntu) Importance: Undecided Status: New ** Tags: hirsute ** Also affects: fonts-navilu (Ubuntu) Importance: Undecided Status: New ** Also affects: fonts-samyak (Ubuntu) Importance: Undecided Status: New ** Description changed: Many fonts do not uninstall cleanly. I verified this in the latest hirsute dev-release. There are .uuid files left behind which prevent removal of the font directory. dpkg: warning: while removing fonts-gargi, directory '/usr/share/fonts/truetype/Gargi' not empty so not removed dpkg: warning: while removing fonts-kalapi, directory '/usr/share/fonts/truetype/fonts-kalapi' not empty so not removed dpkg: warning: while removing fonts-nakula, directory '/usr/share/fonts/truetype/Nakula' not empty so not removed dpkg: warning: while removing fonts-navilu, directory '/usr/share/fonts/truetype/Navilu' not empty so not removed dpkg: warning: while removing fonts-sahadeva, directory '/usr/share/fonts/truetype/Sahadeva' not empty so not removed dpkg: warning: while removing fonts-samyak-deva, directory '/usr/share/fonts/truetype/samyak' not empty so not removed dpkg: warning: while removing fonts-samyak-taml, directory '/usr/share/fonts/truetype/samyak-fonts' not empty so not removed dpkg: warning: while removing fonts-sarai, directory '/usr/share/fonts/truetype/Sarai' not empty so not removed + + cat /usr/share/fonts/truetype/fonts-kalapi/.uuid + 52eae14f-061f-48f2-8c9e-4a29c362316b -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to fonts-samyak in Ubuntu. https://bugs.launchpad.net/bugs/1916512 Title: many fonts do not uninstall cleanly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fonts-navilu/+bug/1916512/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1879122] Re: Cannot enable wifi hotspot on the first attempt
The issue has been fixed upstream in https://gitlab.gnome.org/GNOME /gnome-control-center/-/commit/9efe9eef and in GNOME 3.38 (so Ubuntu 20.10) ** Changed in: gnome-control-center (Ubuntu) Status: Triaged => 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/1879122 Title: Cannot enable wifi hotspot on the first attempt To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1879122/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] [NEW] Rendering problems with Khmer text containing U+17D2 and U+17C2
Public bug reported: gnome-terminal has some problems displaying Khmer text: The Khmer Sign Coeng (U+17D2) functions to indicate that the following Khmer letter is to be rendered subscripted. The Khmer Vowel Sign Ae (U+17C2) needs to be rendered in front of the preceding character. However, that doesn't work in gnome-terminal. See attached screenshots how things are supposed to look like (as rendered in gedit) and how they look in gnome-terminal: ខ្មែរ (U+1781 U+17d2 U+1798 U+17c2 U+179a) word fragments: ខ្ម (U+1781 U+17d2 U+1798) ខែ (U+1781 U+17c2) System information: $ lsb_release -rd Description:Ubuntu 18.04.5 LTS Release:18.04 $ apt-cache policy gnome-terminal gnome-terminal: Installed: 3.28.2-1ubuntu1~18.04.1 Candidate: 3.28.2-1ubuntu1~18.04.1 Version table: *** 3.28.2-1ubuntu1~18.04.1 500 500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 100 /var/lib/dpkg/status 3.28.1-1ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Expected rendering (gedit)" https://bugs.launchpad.net/bugs/1916493/+attachment/5465939/+files/Khmer-expected.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] Re: Rendering problems with Khmer text containing U+17D2 and U+17C2
** Attachment added: "Actual rendering in gnome-terminal" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+attachment/5465940/+files/Khmer-actual.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916493] Re: Rendering problems with Khmer text containing U+17D2 and U+17C2
** Attachment added: "Khmer text sample" https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+attachment/5465941/+files/Khmer.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/1916493 Title: Rendering problems with Khmer text containing U+17D2 and U+17C2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1916493/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916488] [NEW] SRU 1.64.5 to focal
Public bug reported: [ Impact ] That's the current GNOME stable update, including some performance improvements and crash fixes backported from the development branch. https://gitlab.gnome.org/GNOME/gjs/-/tags/1.64.5 [ Test case ] The update is part of GNOME stable updates https://wiki.ubuntu.com/StableReleaseUpdates/GNOME GNOME Shell and its components should continue working with no javascript related errors, as well other gjs based apps like polari [ Regression potential ] GJS based GTK4 should work properly, resolution of GI types was changed and so exported GI types should continue working. ** Affects: gjs (Ubuntu) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: Fix Released ** Affects: gjs (Ubuntu Focal) Importance: Medium Assignee: Marco Trevisan (Treviño) (3v1n0) Status: In Progress ** Also affects: gjs (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: gjs (Ubuntu) Status: In Progress => Fix Released ** Changed in: gjs (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: gjs (Ubuntu Focal) Status: New => In Progress ** Changed in: gjs (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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1916488 Title: SRU 1.64.5 to focal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1916488/+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
** Changed in: gjs (Ubuntu) Status: In Progress => 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/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 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 Hi, Daniel, I'm not sure if this is the same bug, because: 1. Minimizing one of the two windows doesn't always make the other work fine, only sometimes. 2. The issues DOES happen if both windows are on the same workspace. Especially point 2 makes me think it might be something different 樂 ** Description changed: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. - Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and - Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + Works fine on: + - Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) + - Firefox (85.0.1 (64-bit)) + - Microsoft Edge (Version 90.0.796.0 (Official build) dev (64-bit)) --- Affects: - Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) - Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) + - Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) + - Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 ** Description changed: If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + --- - - Chrome Version 88.0.4324.182 (Official Build) (64-bit) + Affects: + Chrome Stable: Version 88.0.4324.182 (Official Build) (64-bit) + Chrome Dev: Version 90.0.4421.5 (Official Build) dev (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1906792] Re: Chromium tabs freeze with two windows on Wayland (Xwayland)
** Summary changed: - Chromium tabs freeze with two windows on different workspaces on Wayland (Xwayland) + Chromium tabs freeze with two windows on Wayland (Xwayland) ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Medium ** Tags added: performance -- 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/1906792 Title: Chromium tabs freeze with two windows on Wayland (Xwayland) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1906792/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915870] Re: gnome session not starting
I used apport-cli -c to create Bug #1916463 as the suggested workaround did not really work out. I will add the other requested files there. Maybe then this bug can be closed as being a duplicate. -- 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/1915870 Title: gnome session not starting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915870/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 ** Description changed: - If I'm using Chrome under Wayland, and I pick a tab, and drag it out of - the current window, it correctly creates a new window. But this new - window has performance issues, and often freezes for a few seconds while - using it. The original window seems to be affected as well, but to a - lesser degree, in my experiments. Other windows seem to be unaffected. + If I'm using Chrome (Version 88.0.4324.182 (Official Build) (64-bit)) + under Wayland, and I pick a tab, and drag it out of the current window, + it correctly creates a new window. But this new window has performance + issues, and often freezes for a few seconds while using it. The original + window seems to be affected as well, but to a lesser degree, in my + experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. + + Chromium (Version 88.0.4324.182 (Official Build) snap (64-bit)) and + Firefox (85.0.1 (64-bit)) don't appear to have the same issue. + + + + Chrome Version 88.0.4324.182 (Official Build) (64-bit) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 1906792, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find. ** This bug has been marked a duplicate of bug 1906792 Chromium tabs freeze with two windows on Wayland (Xwayland) -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Chrome on Wayland: having more than one window makes it stutter
*** This bug is a duplicate of bug 1906792 *** https://bugs.launchpad.net/bugs/1906792 Update: Tested in Chromium (latest snap) and Firefox, no issue when opening multiple windows. -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916464] [NEW] Regression: auto-update notification and GUI doesn't allow installing updates without restart
Public bug reported: Linux is great and famous for being able to install most updates without Restart. However, recently Ubuntu started showing only "Update & Restart" button in GUI, even when no kernel packages are offered to be updated. There should be only "Update" button without restarting when no kernel updates are pending. Why do people now get Windows-like experience of always restarting? ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 22 11:56:42 2021 InstallationDate: Installed on 2019-11-29 (450 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-10-25 (119 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1916464 Title: Regression: auto-update notification and GUI doesn't allow installing updates without restart To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1916464/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] Re: Wayland: Using Chrome, taking a tab out in a new window makes it stutter
Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. ** Summary changed: - Wayland: Using Chrome, taking a tab out in a new window makes it stutter + Chrome on Wayland: having more than one window makes it stutter ** Description changed: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. + + Update: + Closing any additional window, makes Chrome work smoothly again. + + The same issue happens when opening a new window from the panel or from + the menu, so the issue appears to be about handling more than one + window. + + Doing the same on X doesn't result in any apparent performance + degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 -- 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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916458] [NEW] Chrome on Wayland: having more than one window makes it stutter
Public bug reported: If I'm using Chrome under Wayland, and I pick a tab, and drag it out of the current window, it correctly creates a new window. But this new window has performance issues, and often freezes for a few seconds while using it. The original window seems to be affected as well, but to a lesser degree, in my experiments. Other windows seem to be unaffected. I also checked it was not a one-session problem, so I logged-out and back in, tried again, same result. This behaviour renders Chrome very poorly usable when this happens. Update: Closing any additional window, makes Chrome work smoothly again. The same issue happens when opening a new window from the panel or from the menu, so the issue appears to be about handling more than one window. Doing the same on X doesn't result in any apparent performance degradation. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-shell 3.36.4-1ubuntu1~20.04.2 ProcVersionSignature: Ubuntu 5.4.0-65.73-generic 5.4.78 Uname: Linux 5.4.0-65-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Mon Feb 22 11:24:08 2021 DisplayManager: gdm3 InstallationDate: Installed on 2020-04-03 (324 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) RelatedPackageVersions: mutter-common 3.36.7+git20201123-0.20.04.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.apport.crashdb.conf: 2020-09-16T18:33:51.843197 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-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/1916458 Title: Chrome on Wayland: having more than one window makes it stutter To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1916458/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1916460] [NEW] Regression: upgrading of 3rd-party deb packages no longer works in GUI
Public bug reported: If you download an unofficial deb package and open it with gnome- software from the browser, it will let you to install it. However, if you already have an older version of the same package installed, it will offer to Remove only. Previously, it would offer to upgrade. This makes upgrading of 3rd-party software cumbersome. Tested with packages from here: https://angryip.org/download/#linux ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-software 3.38.0-2build1 ProcVersionSignature: Ubuntu 5.8.0-43.49-generic 5.8.18 Uname: Linux 5.8.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Feb 22 11:28:14 2021 InstallationDate: Installed on 2019-11-29 (450 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) InstalledPlugins: gnome-software-plugin-flatpak N/A gnome-software-plugin-snap3.38.0-2build1 SourcePackage: gnome-software UpgradeStatus: Upgraded to groovy on 2020-10-25 (119 days ago) ** Affects: gnome-software (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy -- 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/1916460 Title: Regression: upgrading of 3rd-party deb packages no longer works in GUI To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/1916460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1915681] Re: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384
Please also run: gsettings list-recursively org.gnome.shell > settings.txt and attach the resulting text file here. ** Changed in: gnome-shell (Ubuntu) Assignee: Daniel van Vugt (vanvugt) => (unassigned) -- 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/1915681 Title: Error in freeze/thaw accounting, GNOME Shell crashed with signal 5, resource:///org/gnome/shell/ui/windowManager.js:1384 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1915681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
