[Bug 2008746] Re: connected external monitor prevents automatic screen lock

** Tags added: amdgpu multimonitor ** Package changed: gdm3 (Ubuntu) => mutter (Ubuntu) -- 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/2008746 Title: connected external monitor

[Bug 1905186] Re: dock and top bar flashing non-stop at fullscreen in Xorg sessions

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1381 https://github.com/micheleg/dash-to-dock/issues/1381 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1381 Importance: Unknown Status: Unknown -- You received this bug notification

[Bug 1870519] Re: Ubuntu 20.04 Dock - Autohide not working

** Bug watch added: github.com/micheleg/dash-to-dock/issues #1938 https://github.com/micheleg/dash-to-dock/issues/1938 ** Also affects: dash-to-dock via https://github.com/micheleg/dash-to-dock/issues/1938 Importance: Unknown Status: Unknown ** Changed in: dash-to-dock Remote

[Bug 2008746] Re: connected external monitor prevents automatic screen lock

FYI I have installed amdgpu-install_5.4.50403-1_all.deb to get rid of crashes (not waking up from manual triggered suspends). It fixed this problem. I am not sure if that is important here as the behavior has been there before installing this package. I have hoped it might fix both bugs. -- You

[Bug 2008746] [NEW] connected external monitor prevents automatic screen lock

Public bug reported: when my laptop (Acer Swift 3 SF314-42, Ryzen 5 with AMD GPU) is connected to an external monitor automatic locking of the screen does no longer since a few weeks (since 22.4.2?). It shows the following behavior. 1. After the set idle time both screen blanks. 2. The builtin

[Bug 1999884] Re: gdm-smartcard not passing successful authentication to desktop at system logon

Is there any update on this particular issue? Rocky and RedHat version 8 systems can successfully use PIV authentication in conjunction with SSSD and can be used on Government systems. Ubuntu can not as of now. Jim Graham -- You received this bug notification because you are a member of

[Bug 2008613] ThreadStacktrace.txt

** Attachment added: "ThreadStacktrace.txt" https://bugs.launchpad.net/bugs/2008613/+attachment/5650359/+files/ThreadStacktrace.txt ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2008613/+attachment/5650075/+files/CoreDump.gz ** Changed in:

[Bug 2008613] StacktraceSource.txt

** Attachment added: "StacktraceSource.txt" https://bugs.launchpad.net/bugs/2008613/+attachment/5650358/+files/StacktraceSource.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.

[Bug 2008613] Stacktrace.txt

** Attachment added: "Stacktrace.txt" https://bugs.launchpad.net/bugs/2008613/+attachment/5650357/+files/Stacktrace.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/2008613

[Bug 2008613] gnome-shell crashed with SIGSEGV in meta_window_actor_queue_destroy(NULL) [ubuntu-d...@ubuntu.com/locations.js:370]

StacktraceTop: meta_window_actor_queue_destroy (self=0x0) at ../src/compositor/meta-window-actor.c:793 meta_compositor_real_remove_window (compositor=, window=) at ../src/compositor/compositor.c:540 meta_window_unmanage (window=0x55f3e993b320, timestamp=553254) at ../src/core/window.c:1464

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

** Attachment added: "after.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650348/+files/after.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

This may be a better one, no reboots or kernel changes between. ** Attachment added: "before.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650347/+files/before.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

** Attachment added: "after.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5650276/+files/after.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu.

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

I believe I just had this happen, though there was a reboot and kernel switch (bug #1988989...) in between before and after. gnome-shell was also topping out CPU. Maybe this helps. ** Attachment added: "before.txt"

[Bug 2008453] Re: Wrong trash icon on the desktop

** Summary changed: - Two different trash icons on screen at once + Wrong trash icon on the desktop ** No longer affects: gnome-shell-extension-ubuntu-dock (Ubuntu) ** Package changed: gnome-shell-extension-desktop-icons-ng (Ubuntu) => yaru-theme (Ubuntu) ** Bug watch added:

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

To anyone who can reproduce this bug, please help me to debug it by: 1. Remove the workaround. 2. Reboot. 3. Log in by ssh from another machine. 4. Run: drm_info > before.txt 5. Reproduce the bug by locking and trying to resume. 6. Run: drm_info > after.txt 7. Attach the two resulting