[Bug 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
** Package changed: gnome-shell (Ubuntu) => ubuntu -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/2037599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Please provide a system log showing the errors: journalctl -b0 > journal.txt and attach the resulting text file here. -- 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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
** Description changed: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. + VNP on Alexandria Low SKU. + VNP on Luxor High SKU. + [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Please also try deleting locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then reboot. -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
add sosreport. ** Attachment added: "sosreport-u-OptiPlex-Micro-7020-2023-09-27-uuprzcb.tar.xz" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+attachment/5705032/+files/sosreport-u-OptiPlex-Micro-7020-2023-09-27-uuprzcb.tar.xz -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037599] Re: [D13.5 MFF Luxor Low] System didn't enter s0ix.
Add s0ix picture. ** Attachment added: "s0ix.PNG" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+attachment/5705030/+files/s0ix.PNG -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037599] [NEW] [D13.5 MFF Luxor Low] System didn't enter s0ix.
Public bug reported: [Reproduce Steps] 1. Manually Install Ubuntu 22.04 OS 2. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 3. Check the output. (please refer attached picture. 4. Put the system into suspend mode. 5. Resume system. 6. Input "cat /sys/kernel/debug/pmc_core/substate_residencies". 7. System didn't enter s0ix. --> issue occurs. [Results] Expected Result System can enter s0ix. Actual Result System didn't enter s0ix. VNP on Alexandria Low SKU. VNP on Luxor High SKU. [Additional Information] Test Vault ID: N/A Checkbox test case ID: N/A SKU:MFF MLK Luxor Low X00 BIOS Version:0.4.19 Image/Manifest:dell-bto-jammy-jellyfish-abra-X100-20230919-7 CPU i3-13100t GPU N/A WLAN: N/A Failure rate:(FR:5/5) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: jellyfish-abra odm-bug white-whale ** Tags added: jellyfish-abra odm-bug white-whale -- 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/2037599 Title: [D13.5 MFF Luxor Low] System didn't enter s0ix. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037599/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037182] Re: Restarting GNOME doesn't work
Please also try deleting locally installed extensions: cd ~/.local/share/gnome-shell/ rm -rf extensions and then reboot. -- 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/2037182 Title: Restarting GNOME doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037182] Re: Restarting GNOME doesn't work
Please follow steps 2 and 3 in comment #2. ** Tags added: hybrid i915 multigpu nvidia -- 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/2037182 Title: Restarting GNOME doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037182] Re: Restarting GNOME doesn't work
Here's the system logs, the restart occurred at 22:34 on Sep 27. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+attachment/5705029/+files/journal.txt -- 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/2037182 Title: Restarting GNOME doesn't work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037182/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely (Xorg session)
The foreground app. -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Please also check to see if the freeze is related to switching workspaces (bug 2000644). ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] Re: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely
When you say the workaround is to "kill the current program" do you mean the foreground app or the shell? ** Summary changed: - Dragging the top activities/time bar freezes GNOME completely + Dragging the top activities/time bar freezes GNOME completely (Xorg session] ** Summary changed: - Dragging the top activities/time bar freezes GNOME completely (Xorg session] + Dragging the top activities/time bar freezes GNOME completely (Xorg 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely (Xorg session) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1532508] Re: Screen contents revealed briefly on resume, before even unlocking
** Tags removed: mantic -- 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/1532508 Title: Screen contents revealed briefly on resume, before even unlocking To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1532508/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037191] Re: Lockscreen sometimes doesn't render
** This bug is no longer a duplicate of bug 1532508 Screen contents revealed briefly on resume, before even unlocking ** Summary changed: - Lockscreen sometimes doesn't render + Screen is sometimes not locked when opening the laptop lid ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New ** Summary changed: - Screen is sometimes not locked when opening the laptop lid + Lockscreen sometimes doesn't render (input is locked but desktop visible) ** Information type changed from Public to Public Security ** Summary changed: - Lockscreen sometimes doesn't render (input is locked but desktop visible) + Lock screen sometimes doesn't render (input is locked but desktop visible) -- 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/2037191 Title: Lock screen sometimes doesn't render (input is locked but desktop visible) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037191/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
** Summary changed: - [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland + [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 I can see three bugs there: 1. "bijiben-shell-s... segfault" -> bug 2012985 2. "org.gnome.Shell@wayland.service: Main process exited, code=killed, status=9/KILL" -> bug 2034619 3. "Cursor update failed: drmModeAtomicCommit: Invalid argument" though the shell kept running for hours after that so it wasn't fatal. I think most likely #2 is the main problem here. ** This bug has been marked a duplicate of bug 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037540] Re: system extension light style is not working
** Package changed: gnome-shell (Ubuntu) => gnome-shell-extensions (Ubuntu) -- 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/2037540 Title: system extension light style is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extensions/+bug/2037540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Hello. I seem to be hitting the same bug and I have attached the drm_info output while the screen is stuck in the off state. I see the the same Failed to post KMS update: drmModeAtomicCommit: Invalid argument and Page flip discarded: drmModeAtomicCommit: Invalid argument in my logs while the the monitor is stuck. It gets stuck when I turn my monitor off from inactivity or the monitor turns itself off after locking the computer. Putting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment fixed it for me. Rarely the screen also flickers at random moment, turns dark for a second, and then turns back on. When I checked the logs after it, I see the drmModeAtomicCommit: Invalid argument lines again. I have Ubuntu 22.04 with an external monitor Single display setup. Also Intel. ** Attachment added: "drm_info.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5705009/+files/drm_info.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/1968040 Title: [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037577] [NEW] [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect
Public bug reported: When the dconf parameter color-scheme in /org/gnome/shell/ubuntu/ is modified, the GNOME Shell theme remains in the default state, i.e. it switches between light and dark together with the ‘Dark Style’ toggle. It is impossible to set the Shell theme to be unconditionally dark or light. To reproduce: 1. Run command gsettings set org.gnome.shell.ubuntu color-scheme 'prefer-dark' or modify the parameter color-scheme in /org/gnome/shell/ubuntu/ to be equal 'prefer-dark' via the Dconf Editor GUI. 2. Make sure that the ‘Dark Style’ toggle is deactivated in the quick settings. What should happen: The Shell dialogs like the quick settings menu and the calendar-and-notifications menu should be rendered in dark style. What happens instead: The Shell dialogs are still light. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-shell 45.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 20:04:08 2023 DisplayManager: gdm3 InstallationDate: Installed on 2022-09-21 (371 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Alpha amd64 (20220829) RelatedPackageVersions: mutter-common 45.0-2ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to mantic on 2023-09-26 (1 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic 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/2037577 Title: [mantic] dconf parameter color-scheme in /org/gnome/shell/ubuntu/ has no effect To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
there's nothing in /var/crash or in errors.ubuntu.com ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => New -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
-b -1 ** Attachment added: "prevjournal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704967/+files/prevjournal.txt -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037460] Re: gnome-shell crash
-b 0 ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+attachment/5704966/+files/journal.txt -- 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/2037460 Title: gnome-shell crash To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037460/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037307] Re: Dragging the top activities/time bar freezes GNOME completely
The issue's really consistent and easy to reproduce thankfully. ** Attachment added: "journal.txt" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+attachment/5704945/+files/journal.txt -- 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/2037307 Title: Dragging the top activities/time bar freezes GNOME completely To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037307/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037540] Re: system extension light style is not working
The new light style extension is provided in the gnome-shell-extensions package. ** Tags added: mantic -- 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/2037540 Title: system extension light style is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2017498] Re: crashes trying to open the mouse screen
For me, the reason is the gstreamer playback plugin being blacklisted. To remove it from blacklist, you can run : sudo rm ~/.cache/gstreamer-1.0/registry* I have no idea why it was blacklisted in the first place. -- 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/2017498 Title: crashes trying to open the mouse screen To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2017498/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037540] [NEW] system extension light style is not working
Public bug reported: Trying to enable light style gnome shell system extension is not working. What should happen is that light style should be enabled: when pressing the super button, a light-not black background should be displayed. lsb_release -rd: Description:Ubuntu Mantic Minotaur (development branch) Release:23.10 apt-cache policy gnome-shell: gnome-shell: Installed: 45.0-1ubuntu1 Candidate: 45.0-1ubuntu1 Version table: *** 45.0-1ubuntu1 500 500 http://gr.archive.ubuntu.com/ubuntu mantic/main amd64 Packages 100 /var/lib/dpkg/status ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/2037540 Title: system extension light style is not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037540/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037538] [NEW] GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click.
Public bug reported: Ubuntu 22.04.3 LTS gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5db5c350] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe0d310] is on because it needs an allocation. gnome-shell[3218]: Can't update stage views actor [:0x555e5fe106d0] is on because it needs an allocation. gnome-shell[5794]: [5788:5825:0927/071652.214702:ERROR:nss_util.cc(357)] After loading Root Certs, loaded==false: NSS error code: -8018 Also, getting stack traces every time I open Activities by click or super button. I removed all User-Installed Extensions, and have also tried disabling the default System Extensions with no change. JS ERROR: TypeError: workspace is undefined#012_getSpacing@resource:///org/gnome/shell/ui/workspacesView.js:213:13#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:339:18#012vfunc_allocate@resource:///org/gnome/shell/ui/workspacesView.js:711:30#012removeWindow@resource:///org/gnome/shell/ui/workspace.js:855:29#012addWindow/<.destroyId<@resource:///org/gnome/shell/ui/workspace.js:806:22#012vfunc_hide@resource:///org/gnome/shell/ui/workspacesView.js:1016:38#012vfunc_unmap@resource:///org/gnome/shell/ui/overviewControls.js:715:33#012hideOverview@resource:///org/gnome/shell/ui/layout.js:347:28#012_hideDone@resource:///org/gnome/shell/ui/overview.js:641:32#012_animateNotVisible/<@resource:///org/gnome/shell/ui/overview.js:624:55#012onStopped@resource:///org/gnome/shell/ui/overviewControls.js:757:21#012_makeEaseCallback/<@resource:///org/gnome/shell/ui/environment.js:151:22#012_easeActorProperty/<@resource:///org/gnome/shell/ui/environment.js:317:60 gnome-shell[3218]: Object St.Button (0x555e5dc62c60), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:566 (20a2bc50b650 @ 10) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:567 (20a2bc50b650 @ 36) gnome-shell[3218]: == Stack trace for context 0x555e5d657170 == gnome-shell[3218]: #0 555e5deb4708 i resource:///org/gnome/shell/ui/windowPreview.js:570 (20a2bc50b650 @ 77) gnome-shell[3218]: Object St.Label (0x555e5df247a0), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. gnome-shell[3218]: Object .Gjs_ui_windowPreview_WindowPreview (0x555e5ed83d30), has been already disposed — impossible to get any property from it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-33.33~22.04.1-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 07:19:09 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-08-15 (42 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu4 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug gnome jammy -- 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/2037538 Title: GNOME Freezes, Alt+F2 not even responding. Mouse Cursor Tracks, but can't click. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037538/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037191] Re: Lockscreen sometimes doesn't render
*** This bug is a duplicate of bug 1532508 *** https://bugs.launchpad.net/bugs/1532508 https://bugs.launchpad.net/bugs/1532508 seems to be about the lockscreen only being invisible for a split second, but in this bug it stays invisible, activity preventing the user from logging in while revealing the desktop. -- 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/2037191 Title: Lockscreen sometimes doesn't render To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2037191/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1969140] Re: Window minimize animation flickers and appears in the wrong place in Xorg sessions
** Changed in: dash-to-dock Status: Unknown => New -- 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/1969140 Title: Window minimize animation flickers and appears in the wrong place in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/dash-to-dock/+bug/1969140/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037528] [NEW] every tab with touchscreen on a folder gives the context menu.
Public bug reported: Ubuntu installed on Chuwi u-book x pro (13 inch). CPU: Intel® Core™ i7-7Y75 × 4 GPU: Intel® HD Graphics 615 (KBL GT2) Tapping a folder in Nautilus always gives the context menu. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-33.33-generic 6.2.16 Uname: Linux 6.2.0-33-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 12:08:40 2023 GsettingsChanges: b'org.gnome.nautilus.preferences' b'click-policy' b"'single'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2023-09-19 (7 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: file-roller 43.0-1 nautilus-extension-gnome-terminal 3.48.0-1ubuntu1 ** Affects: nautilus (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session ** Attachment added: "Schermafdruk van 2023-09-27 12-14-03.png" https://bugs.launchpad.net/bugs/2037528/+attachment/5704881/+files/Schermafdruk%20van%202023-09-27%2012-14-03.png -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2037528 Title: every tab with touchscreen on a folder gives the context menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2037528/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2013083] Re: libwebp-dev doesn't install CMake configs
This is fixed in Debian sid/testing, will be fixed for mantic if bug: 2037527 is accepted, or to 24.04 otherwise. Setting right now as fix released. ** Changed in: libwebp (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2013083 Title: libwebp-dev doesn't install CMake configs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2013083/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037527] [NEW] [Ffe] libwebp
Public bug reported: - 9/13/2023: version 1.3.2 This is a binary compatible release. * security fix for lossless decoder (chromium: #1479274, CVE-2023-4863) - 6/23/2023: version 1.3.1 This is a binary compatible release. * security fixes for lossless encoder (#603, chromium: #1420107, #1455619, CVE-2023-1999) * improve error reporting through WebPPicture error codes * fix upsampling for RGB565 and RGBA in NEON builds * img2webp: add -sharp_yuv & -near_lossless * Windows builds: - fix compatibility with clang-cl (#607) - improve Arm64 performance with cl.exe - add Arm64EC support * fix webp_js with emcc >= 3.1.27 (stack size change, #614) * CMake fixes (#592, #610, #612) * further updates to the container and lossless bitstream docs (#581, #611) - 12/16/2022: version 1.3.0 This is a binary compatible release. * add libsharpyuv, which exposes -sharp_yuv/config.use_sharp_yuv functionality to other libraries; libwebp now depends on this library * major updates to the container and lossless bitstream docs (#448, #546, #551) * miscellaneous warning, bug & build fixes (#576, #583, #584) Moreover the LP: #2013083 can be closed in this release. The non-bugfix changes are related to a new library added, that is used probably by firefox and chromium (next releases? or maybe they are using the embedded library) ** Affects: libwebp (Ubuntu) Importance: Undecided Assignee: Ubuntu Release Team (ubuntu-release) Status: New ** Changed in: libwebp (Ubuntu) Assignee: (unassigned) => Ubuntu Release Team (ubuntu-release) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libwebp in Ubuntu. https://bugs.launchpad.net/bugs/2037527 Title: [Ffe] libwebp To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwebp/+bug/2037527/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland
** Description changed: + [ Workaround ] + + Add this to /etc/environment: + + MUTTER_DEBUG_KMS_THREAD_TYPE=user + + and then reboot. + + [ Original Description] + I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037520] Re: Locking screen causes logout in Wayland
*** This bug is a duplicate of bug 2034619 *** https://bugs.launchpad.net/bugs/2034619 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 2034619, 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 2034619 [amdgpu] gnome-shell gets SIGKILL'd when lock screen in Wayland -- 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/2037520 Title: Locking screen causes logout in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037520] [NEW] Locking screen causes logout in Wayland
Public bug reported: == Expected == When I lock the screen, the lock screen appears, and I can log in to return to my existing sessions. == Actual == When I lock the screen (Windows+L, Quick Settings or closing the laptop lid) it'll cause the session to logout and redirect me back to the login screen, which causes all running programs to close and starts a new session after login. == Additional details == This bug only happens on Wayland and is not present under xorg. I have confirmed (with top) that all the running programs are closed and the session itself is destroyed (Ctrl+Alt+F2 and other screens are all tty, except for the login screen at Ctrl+Alt+F1) == System details == ThinkPad E14 Gen 2 - AMD Ryzen 5500U Ubuntu 23.10 Mantic Minotaur (beta) ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-5.5-generic 6.5.0 Uname: Linux 6.5.0-5-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed Sep 27 11:06:43 2023 InstallationDate: Installed on 2022-04-23 (522 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-09-25 (2 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic -- 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/2037520 Title: Locking screen causes logout in Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2037520/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023572] Re: SRU gjs 1.72.4 to jammy
You still get The following packages have been kept back: gjs (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) libgjs0g (1.72.2-0ubuntu2 => 1.72.4-0ubuntu0.22.04.1) all the time. -- 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/2023572 Title: SRU gjs 1.72.4 to jammy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2023572/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037345] Re: error saving a new vpn
Thank you for your bug report. The GNOME report is from an opensuse user which suggests it's not distro specific. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => High ** Tags added: rls-mm-incoming -- 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/2037345 Title: error saving a new vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037345] Re: error saving a new vpn
Same as https://bugs.launchpad.net/ubuntu/+source/network-manager- openvpn/+bug/2037011 and the gnome bug report is https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #2668 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/2668 -- 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/2037345 Title: error saving a new vpn To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037345/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2030959] Update Released
The verification of the Stable Release Update for mutter has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2030959] Re: Cursor sometimes stutters after heavy shell animations in 42.9
This bug was fixed in the package mutter - 42.9-0ubuntu5 --- mutter (42.9-0ubuntu5) jammy; urgency=medium [ Daniel van Vugt ] * Drop clutter-frame-clock-Avoid-rapidly-toggling-dynamic-max-re.patch. It was never really required in mutter 42 but has caused some new stutter elsewhere (LP: #2030959) -- Marco Trevisan (Treviño) Mon, 11 Sep 2023 15:39:50 +0200 ** Changed in: mutter (Ubuntu Jammy) Status: Fix Committed => Fix Released -- 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/2030959 Title: Cursor sometimes stutters after heavy shell animations in 42.9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2030959/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2033719] Re: Mouse pointer stutters in gnome-shell 45
Also proposed a Debian patch: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/110 -- 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/2033719 Title: Mouse pointer stutters in gnome-shell 45 To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2033719/+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
gdm3 looks good to me, but I haven't accepted it yet as it depends on the gnome-settings-daemon patches and I think it's best to resolve those questions before accepting gdm3 into -proposed. -- 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/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 2037497] Re: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage()
** Tags added: regression-release -- 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/2037497 Title: gnome-shell crashed with SIGSEGV in ?? (iris_dri.so) from end_query() from cogl_gl_create_timestamp_query() from cogl_onscreen_egl_swap_buffers_with_damage() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/2037497/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036749] Re: Sudo gnome-terminal fails
having the same issue. Both `gnome-terminal` or `sudo gnome-terminal` doesn't work. However, when I changed to Linux 6.2.0-32-generic, gnome-terminal works again. -- 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/2036749 Title: Sudo gnome-terminal fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] Re: [jammy]backport #1453 from upstream
** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 + + I had to wait for this long because I expected a 42.x backport in the + backports repository of .1 release, but no one bothered to do such a + backport. -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2036749] Re: Sudo gnome-terminal fails
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-terminal (Ubuntu) Status: New => Confirmed -- 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/2036749 Title: Sudo gnome-terminal fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2036749/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2037503] [NEW] [jammy]backport #1453 from upstream
Public bug reported: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. The bug in question makes the gnome-control-center crash if an unsupported power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 I had to wait for this long because I expected a 42.x backport in the backports repository of .1 release, but no one bothered to do such a backport. ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: gnome-control-center (Debian) Importance: Undecided Status: New ** Tags: cherry-pick ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed ** Description changed: In some cases, it was possible for a profile to be set (directly, or through a hold) even though it wasn't supported. Don't assert in those cases. + The bug in question makes the gnome-control-center crash if an unsupported + power profile is set using, say, powerprofilesctl. Should be trivial to cherry-pick without breaking other components. https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1453 ** Also affects: gnome-control-center Importance: Undecided Status: New ** No longer affects: gnome-control-center ** Also affects: gnome-control-center (Debian) Importance: Undecided Status: New -- 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/2037503 Title: [jammy]backport #1453 from upstream To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2037503/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
