[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
^^^ Note bug 1933221 is really a duplicate of this one. That's why it's fix released. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.56-0ubuntu4.2 --- bluez (5.56-0ubuntu4.2) hirsute; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 08:07:12 + ** Changed in: bluez (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
This bug was fixed in the package bluez - 5.53-0ubuntu3.3 --- bluez (5.53-0ubuntu3.3) focal; urgency=medium * debian/patches/0001-fix-reading-from-rfkill-socket.patch: - fix reading from rfkill socket (lp: #1933221) -- Andy Chi Tue, 22 Jun 2021 14:27:12 +0800 ** Changed in: bluez (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off To manage notifications about this bug go to: https://bugs.launchpad.net/bluez/+bug/1926062/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1870736] Re: [nvidia] Screen scaling 125% gives 200%
I'm seeing the same symptoms, screen scaling 125% gives 200%, when accessing a Ubuntu 20.04 VMware system via xdrp from Windows 10. My graphics driver is root@geoff-ubuntu-2004:~# lshw -c video *-display description: VGA compatible controller product: SVGA II Adapter vendor: VMware physical id: f bus info: pci@:00:0f.0 version: 00 width: 32 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=vmwgfx latency=64 resources: irq:16 ioport:1070(size=16) memory:e800-efff memory:fe00-fe7f memory:c-d -- 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/1870736 Title: [nvidia] Screen scaling 125% gives 200% To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1870736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1934186] Re: gdm "New Window" popup won't go away
*** This bug is a duplicate of bug 1934185 *** https://bugs.launchpad.net/bugs/1934185 >Although I filed this bug once, using "ubuntu-bug", somehow it showed up on Launchpad twice, Unfortunatly that happens occasionally. Should be marked as a duplicate now. :) Btw, if you add a space between bug and # it will add an automatic link, like this: bug #1934185 ** This bug has been marked a duplicate of bug 1934185 Ubuntu Dock popup menu won't go away -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1934186 Title: gdm "New Window" popup won't go away To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1934186/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1931088] Re: boot-and-services tests fails in impish on armhf (248.3)
** Changed in: lxd (Ubuntu Impish) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1931088 Title: boot-and-services tests fails in impish on armhf (248.3) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1931088/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1871538] Re: dbus timeout-ed during an upgrade, taking services down including gdm
An interesting observation I made is that all journal logs (in this LP bug and the upstream systemd bug) show the "polkit.service: Unexpected error response from GetNameOwner(): Connection terminated" message, in addition to a bunch of other "Connection terminated" errors from changing services across the different installations (NetworkManager.service, accounts-daemon.service, systemd- logind.service, ...). I've also seen logs (from Gauthier) where only polkit.service is failing. The polkit.service "Unexpected error response from GetNameOwner()" message is a log from systemd effectively telling us that systemd cannot reach org.freedesktop.PolicyKit1 on DBus. But the root cause for that must be that polkitd is not running (or dbus is somehow stuck in a deadlock, not responding anymore). This gives a new twist to this issue, as we might be searching for a phantom in (lib-)systemd... PolicyKit is using glib's gdbus implementation. -- 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/1871538 Title: dbus timeout-ed during an upgrade, taking services down including gdm To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1871538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1917010] Re: Hard to detect double-clicks on the HiDPI touchscreen system
MR: https://gitlab.com/rastersoft/desktop-icons-ng/-/merge_requests/127 ** Also affects: gnome-shell-extension-desktop-icons-ng (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: Confirmed => Invalid -- 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/1917010 Title: Hard to detect double-clicks on the HiDPI touchscreen system To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1917010/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1930359] Re: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates
Are you sure that's the same bug as the original issue here? The original issue sounded plausibly related to the fix for bug 1905825 as you say. The diff between: ubuntu/3.36.7+git20201123-0.20.04.1 ubuntu/3.36.9-0ubuntu0.20.04.1 indeed shows no changes mentioning "schema" or "gsettings". The diff between: ubuntu/3.36.1-3ubuntu3 ubuntu/3.36.7+git20201123-0.20.04.1 does show some changes mentioning "schema" and "gsettings. So are you sure about the statement "the issue does not occur with 3.36.7+git20201123-0.20.04.1."? It's curious other people are not reporting this problem so I wonder what is unique about the customer's machines. Do they have any PPAs installed? I fear we might be onto a new separate issue now so reusing this bug might be confusing the situation. -- 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/1930359 Title: gdm fails to start in a VMware Horizon VDI environment with latest mutter 3.36.9-0ubuntu0.20.04.1 in focal-updates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1930359/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
