This bug was fixed in the package mutter - 41.3-1ubuntu1

---------------
mutter (41.3-1ubuntu1) jammy; urgency=medium

  * Merge with debian, includes these upstream changes:
    - window: Don't change workspaces of unmanaged windows (LP: #1933996)
    - backend: Reset idletime when unplugging the power cable (LP: #1945121)
    - clutter/text: Invalidate actor paint volume when it has changed
      (LP: #1882291)
    - backends/native: Ensure pointer is onscreen in input thread (LP: #1933186)
    - OSK Enter, space and backspace keys don't work when typing in Greek
      (LP: #1820523)
    - window: Don't change workspaces of unmanaged windows (LP: #1932328)
  * Remainig changes with debian:
    - debian/gbp.conf: update upstream branch to point to ubuntu/master
    - debian/patches/x11-Add-support-for-fractional-scaling-using-Randr.patch:
      + X11: Add support for fractional scaling using Randr

mutter (41.3-1) unstable; urgency=medium

  * New upstream release:
    - Check keyboard serials for activation
    - Fix mixed up refresh rates in multi-monitor setups (LP: #1788535)
    - Allow disabling HW cursors
    - Improve damage handling (LP: #1872870)
    - Consider xrandr flags for advertised modes
    - Ensure constraints after client resize
    - window-group: Disable culling when rendinging clone to offscreen buffer
    - Fix workspace switch animation in default plugin
    - Fix unfullscreening of window that were mapped fullscreen
    - Fix DMA-BUF screencasts with unredirected fullscreen windows
    - Fix orientation changes on devices with 90°

mutter (41.2-2) unstable; urgency=medium

  * Team upload
  * d/p/Consistently-pass-timestamp-as-uint64-when-creating-MetaS.patch:
    Add proposed patch to fix FTBFS on 32-bit architectures
  * d/patches: Update to 41.2-6-g7b64c159a
    - Surface damage viewport improvements
  * Update patch metadata with upstream status

mutter (41.2-1) unstable; urgency=medium

  * Team upload

  [ Simon McVittie ]
  * New upstream release
  * d/patches: Drop patches that were applied upstream
  * d/patches: Update to upstream gnome-41 branch commit 41.2-3-g5d0c26631
    - wayland: Check keyboard serials for activation
    - Sync refresh rate to the correct monitor for maximized/full-screen
      apps in a multi-monitor layout
    - Add a debug environment variable to disable hardware cursors for
      faulty hardware and drivers

  [ Laurent Bigonville ]
  * debian/rules: Disable systemd support on non-linux architectures

mutter (41.1-1) unstable; urgency=medium

  * Team upload
  * New upstream release
  * Drop a patch that came from upstream
  * Update Lintian overrides
  * Replace patches for #995929 with the version that was applied upstream
  * Remove workaround for #994806
  * d/libmutter-9-0.symbols: Ignore removal of clutter_stage_capture_into.
    Nothing else in Debian references this symbol, except for forks of
    the mutter codebase.

mutter (41.0-5) unstable; urgency=medium

  * Team upload
  * Merge packaging from unstable
    - No changes relative to 41.0-4, except for the changelog
  * Close #995929 via changelog.
    The patches in 41.0-4 seem to have been successful.
  * Release to unstable (starts transition: #996607)

mutter (41.0-4) experimental; urgency=medium

  * Team upload
  * d/control.in: libmutter-test-9 Depends on mutter.
    It wants the libdefault.so plugin, which is in mutter.deb.
  * Update Lintian overrides for RUNPATH
  * d/patches: Another try at fixing #995929 (Closes: #995929)
  * d/rules: Disable gvfs when running unit tests

mutter (41.0-3) experimental; urgency=medium

  * Team upload
  * d/p/tests-Change-how-we-wait-for-an-orientation-change.patch:
    Add patch attempting to fix #995929
  * d/p/tests-Add-additional-debug-in-wait_for_orientation.patch,
    d/p/tests-Watch-the-orientation-manager-independently.patch:
    Try to diagnose what's going on if #995929 is still not fixed

mutter (41.0-2) experimental; urgency=medium

  * Team upload
  * Build-depend on libgl-dev instead of transitional libgl1-mesa-dev
  * (Build-)Depend on libgles-dev instead of transitional libgles2-mesa-dev
  * d/rules: Don't let log from flaky tests overwrite log from main tests
  * d/p/tests-dbus-runner-Make-sure-to-tear-down-even-on-test-fai.patch:
    Add patch from upstream to stop failing tests causing a timeout.
    Failing tests will generally still cause FTBFS, but failing immediately
    is more buildd-friendly than timing out.
  * d/p/tests-Don-t-use-TestEnvironment.patch,
    d/p/tests-Don-t-continue-if-setup-commands-fail.patch:
    Update patches for installed-tests to latest version submitted upstream
  * d/p/tests-Add-additional-debug-for-Debian-995929.patch:
    Add more debug logging to try to diagnose #995929

mutter (41.0-1) experimental; urgency=medium

  * Team upload

  [ Jeremy Bicha ]
  * debian/watch: Watch for stable releases

  [ Simon McVittie ]
  * New upstream release
  * Update package names for ABI break
  * Update build-dependencies
  * d/copyright: Update
  * Rebase patch series
  * Update symbols file
  * d/p/debian/synaptics-support.patch:
    Stop patching in Xorg synaptics driver support.
    Upstream rejected this patch back in 2018, but we continued to apply it
    as a transitional step for Ubuntu 18.04. Since then we've had stable/LTS
    releases of Debian 10, Ubuntu 18.04, Debian 11 and Ubuntu 20.04,
    libinput has improved, and both Debian and Ubuntu have switched to
    running GNOME in Wayland mode by default; let's have another try at
    following upstream on this. (Closes: #993171)
  * d/rules: Use upstream driver selection, except on 32-bit ARM.
    Specifying -Ddefault_driver=gl on x86 (and other architectures that are
    not 32-bit ARM) is no longer the same as the upstream default: the
    upstream default is now gl3, meaning modern OpenGL, whereas the gl driver
    is legacy (pre-3.2) OpenGL. Assume upstream are doing this for a reason.
    For now we continue to specify -Ddefault_driver=gles2 on 32-bit ARM, and
    apply the patch that adds the default_driver option, because 32-bit ARM
    has historically been an exception to the usual rules.
  * Add test-dependency on python3-dbus, python3-dbusmock
  * d/p/meta-dbus-runner-Import-importlib.util.patch:
    Add patch to fix test failure by working around #994806
  * d/p/tests-Don-t-use-TestEnvironment.patch,
    d/p/tests-Don-t-continue-if-setup-commands-fail.patch:
    Add patch to avoid using TestEnvironment.
    This works around a gnome-desktop-testing bug.
  * Add Lintian override for another RUNPATH in the tests.
    As with the existing tests, this is necessary to use mutter's fork of
    clutter and cogl.
  * Standards-Version: 4.6.0 (no changes required)
  * Put the new libmutter-test-9 in its own binary package.
    To avoid micro-packages, this includes the -dev files too; there is no
    explicit dependency on libmutter-9-dev, but packages compiling against
    this library are expected to build-depend on both. Outside mutter
    itself, it is only expected to be used by gnome-shell.

 -- Marco Trevisan (Treviño) <ma...@ubuntu.com>  Tue, 25 Jan 2022
04:07:12 +0100

** Changed in: mutter (Ubuntu)
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1945121

Title:
  Ubuntu auto-suspends when I unplug my laptop after not having used it
  for a few minutes.

Status in GNOME Settings Daemon:
  Unknown
Status in Mutter:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Invalid
Status in mutter package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 20.04.3 LTS

  I have my power settings so that Ubuntu will never auto-suspend if
  plugged in, but will do so after 20 minutes if on battery power.

  If I leave it plugged in but untouched for 20 minutes, and then unplug
  it (to move it to another room when I come back to it), then it
  suspends on the way there.

  It would seem more intuitive that unplugging/plugging in would be
  considered interaction, and would reset the delay. The expected
  behavior, in that case, would be that it gets unplugged, stays on, and
  then suspends after 20 minutes if there is no further interaction.

  I know any official fix would probably take a while, if one is even
  considered. Is there any workaround?

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.11.0-36.40~20.04.1-generic 5.11.22
  Uname: Linux 5.11.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
  .proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
  .proc.driver.nvidia.gpus.0000.01.00.0: Error: path was not a regular file.
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  460.91.03  Fri Jul  2 
06:04:10 UTC 2021
   GCC version:  gcc version 9.3.0 (Ubuntu 9.3.0-17ubuntu1~20.04)
  ApportVersion: 2.20.11-0ubuntu27.20
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: skip
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 26 14:35:33 2021
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 460.91.03, 5.11.0-34-generic, x86_64: installed
   nvidia, 460.91.03, 5.11.0-36-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA 
controller])
     Subsystem: ASUSTeK Computer Inc. UHD Graphics 630 (Mobile) [1043:18fe]
     Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] 
[1043:18fe]
  InstallationDate: Installed on 2021-02-21 (216 days ago)
  InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 
(20210209.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 13d3:5666 IMC Networks USB2.0 HD UVC WebCam
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 005: ID 1b1c:1b5c Corsair CORSAIR NIGHTSWORD RGB Gaming Mouse
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. TUF GAMING FX504GE_FX80GE
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-36-generic 
root=UUID=94577a37-4156-ac57-02e9-af5914abc257 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/19/2020
  dmi.bios.release: 5.13
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FX504GE.320
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: FX504GE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.ec.firmware.release: 1.16
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFX504GE.320:bd06/19/2020:br5.13:efr1.16:svnASUSTeKCOMPUTERINC.:pnTUFGAMINGFX504GE_FX80GE:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnFX504GE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: TUF GAMING
  dmi.product.name: TUF GAMING FX504GE_FX80GE
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.105-3~20.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1~20.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-settings-daemon/+bug/1945121/+subscriptions


-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to     : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to