[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Please also try to keep each bug report concise and on a single topic. You can log as many different bugs as you like. -- 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/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Sorry to hear you're still having problems. Since the new issue has different symptoms on a different Ubuntu release we should track it in a different bug. If you are still willing to use Ubuntu then please open a new bug about the new issue. If the machine is not booting (black screen) then try accessing the grub menu (tap Escape or hold Shift during early boot) and select recovery mode. In recovery mode please then run: journalctl -b-1 > prevboot1.txt journalctl -b-2 > prevboot2.txt and attach the resulting text files to the new bug, not this one. -- 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/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-01.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688204/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-01.png -- 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/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Screenshots: Ubuntu 22.04.2 LTS, partial upgrade option after Nvidia driver 535 went live. ** Attachment added: "Bildschirmfoto vom 2023-07-25 05-42-07.png" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+attachment/5688203/+files/Bildschirmfoto%20vom%202023-07-25%2005-42-07.png -- 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/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023776] Re: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions
Hello Daniel, I apologize for the huge delay, but I have been experiencing a number of show stopping issues that I have yet to recover from. As written above: After all the issues that I had with Ubuntu 23.04, I decided to "downgrade" to Ubuntu 22.04.2, which was working just fine at first, see comment above. I was using the recommended and "tested" Nvidia driver 525, which was the one that the Ubuntu additional drivers tool suggested. Recently Nvidia released the proprietary Nvidia driver version 535, which was made available via Ubuntu 22.04.2. So I ran the Ubuntu system updates utility like I usually would, in the hopes of Ubuntu picking up the newest Nvidia driver automatically, like it has always done in the past. Ubuntu did find and suggest to install the new Nvidia driver, but... Just like on Ubuntu 23.04, Ubuntu 22.04.2 also mentioned something about a "partial upgrade", see attached screenshots below. Trying to click on "continue" instead didn't offer any updates, so I went back to the "partial upgrade" option, because my system wasn't getting any updates whatsoever ever since this "issue" appeared out of nowhere. In the middle of the "partial upgrade" my 22.04.2 system went black, meaning all of my screens turned off randomly, and the computer would not react to any user input whatsoever. After being forced to perform a hard reboot, the computer did not want to boot, spitting out several "journal errors" during the boot process. I would like to mention that this was a fresh install of 22.04.2 - not a single ppa etc. was added manually - just a handful of native apps installed as Snap via the official Ubuntu Software Center (including Steam, also installed via the Ubuntu Software Center). I hardly used the system, because I was still in the process of transferring over the data that I had to recover from my busted 23.04 install. A few notes here: - this happened totally randomly - previous system updates were completed without any issues whatsoever - there were no issues whatsoever before the new Nvidia driver 535 - the partial upgrade option mentioned a bunch of Nvidia 535 modules to be installed - and the old 530 driver to be removed - and it also mentioned a ton of other things to be updated as well, including the kernel and a bunch of Ubuntu desktop files Digging around I found out that both this and the low latency kernel subject is a common and repeating issue: - https://askubuntu.com/questions/1443779/why-doesnt-this-software- updater-warning-tell-me-what-is-going-to-be-installed - https://www.reddit.com/r/Kubuntu/comments/14ndb7a/why_do_i_keep_getting_these_oracle_and_lowlatency/ - https://askubuntu.com/questions/1334791/not-all-updates-can-be- installed-in-software-updater - https://askubuntu.com/questions/725481/ubuntu-software-updater-not- all-updates-can-be-installed - https://www.google.com/search?channel=fs=ubuntu- sn=ubuntu+nvidia+partial+upgrade Verdict: Now I have to recover my freshly installed 22.04.2 system again, just like I did with 23.04 a few days ago. Since I don't have the time to troubleshoot this yet again, I am now forced to go for a clean install again, but I will be using a different distro this time around as it seems that even Ubuntu LTS has become highly unstable / unusable for Nvidia users. This is extremely aggravating to say the least. This entire ordeal will set me back another one or two weeks at the very least. Been an Ubuntu user for decades now, and recently switched from AMD to Nvidia gpu, and it's been nothing but trouble thus far, sadly. Using an AMD gpu was flawless for the most part, but on Nvidia it's one headache after another on Ubuntu. -- 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/2023776 Title: Ubuntu 23.04 + Gnome + Nvidia 525 + Vsync = low fps in Xorg sessions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023776/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2015577] Re: middle click to lower window no longer works for xwayland windows
** 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/2015577 Title: middle click to lower window no longer works for xwayland windows To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2015577/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028610] Re: bring-to-front and send-to-back not working for some apps
*** This bug is a duplicate of bug 2015577 *** https://bugs.launchpad.net/bugs/2015577 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 2015577, 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. ** Tags added: regression-release ** This bug has been marked a duplicate of bug 2015577 middle click to lower window no longer works for xwayland windows -- 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/2028610 Title: bring-to-front and send-to-back not working for some apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028610] [NEW] bring-to-front and send-to-back not working for some apps
Public bug reported: Since I upgraded to Ubuntu 23.04, a number of my applications have stopped accepting bring-to-front (right click on the title bar) and send-to-back (middle click on the title bar). On the other hand, other apps (native Gnome apps seemingly) do still seem to work. Note I'm using X11 not Wayland. A set of apps I know do not work anymore, that used to work with Ubuntu 22.10 and below: * xterm * Emacs * Chrome * Slack * Spotify * VirtualBox manager Some apps that do still work: * Remmina * File Manager * gnome-terminal * Gnome Settings * Ubuntu Software There are many more in both categories. Please fix things so that I can use bring-to-front and send-to-back on all my apps again. Thanks! ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: mutter 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 5.14.0-1054.61-oem 5.14.21 Uname: Linux 5.14.0-1054-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 24 23:31:31 2023 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2022-12-02 (234 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 SourcePackage: mutter UpgradeStatus: Upgraded to lunar on 2023-06-04 (50 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- 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/2028610 Title: bring-to-front and send-to-back not working for some apps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2028610/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Upstream has already "fixed" it by reverting the change in a later release: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3030 Although this seems to be because they were waiting on a fix in Xwayland version 23.1.0 which Ubuntu 22.04 doesn't have yet. It looks like the downside they were trying to avoid was: > sending modifiers to clients prevents direct scanout for DRI3 clients via Xwayland so it was just to make full screen gaming performance better. If you can live without that optimization then you should keep MUTTER_DEBUG_SEND_KMS_MODIFIERS=1. Starting in 23.10 we have the best of both worlds so you won't need to choose anymore. ** Changed in: mutter (Ubuntu) Importance: Undecided => Medium ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2020782] Re: Xdcv: Changing display scale setting and reverting it fails
I just tested Ubuntu 22.04 and I can confirm it fixes the issue. First, used 22.04 with the current mutter version available in jammy- updates: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu1 Candidate: 42.9-0ubuntu1 Version table: *** 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 100 /var/lib/dpkg/status 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And I do hit the error when trying to revert after changing the scale: Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use linear monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Failed to use fallback monitor configuration: Invalid mode 800x600 (-nan) for monitor 'unknown unknown' Jul 24 17:03:37 U-20CG3JVH1ALS3 gnome-shell[3048]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:03:38 U-20CG3JVH1ALS3 gnome-shell[3048]: Xlib: extension "DPMS" missing on display ":1". Then, I upgraded to package from -proposed: user1@U-20CG3JVH1ALS3:~$ sudo apt-cache policy mutter-common libmutter-10-0 gir1.2-mutter-10 [sudo] password for user1: mutter-common: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages libmutter-10-0: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages gir1.2-mutter-10: Installed: 42.9-0ubuntu4 Candidate: 42.9-0ubuntu4 Version table: *** 42.9-0ubuntu4 500 500 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 42.9-0ubuntu1 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 42.0-3ubuntu2 500 500 http://sa-east-1.ec2.archive.ubuntu.com/ubuntu jammy/main amd64 Packages And now the error is no longer logged and I can successfully revert: Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 59 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 59 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 61 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 61 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 63 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 63 at 1.00 failed Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Impossible to set scaling on crtc 65 to 1.00, error id 2 Jul 24 17:07:49 U-20CG3JVH1ALS3 gnome-shell[3166]: Window manager warning: Scalig CRTC 65 at 1.00 failed Scalig CRTC 65 at 1.00 failed (The errors above can be ignored for now as their are a known problem with Xdcv, which is further explained in comment #16) Marking as verification-done ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- 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/2020782 Title: Xdcv:
[Bug 2028469] Re: Use less generic name for monitors.xml to avoid clashing with other desktops
** Summary changed: - monitors.xml is incompatible with MATE (and vice versa) + Use less generic name for monitors.xml to avoid clashing with other desktops -- 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/2028469 Title: Use less generic name for monitors.xml to avoid clashing with other desktops To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2028469/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026886] Re: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2
Hi Daniel, sorry for the delayed response. MUTTER_DEBUG_SEND_KMS_MODIFIERS=1 fixes the issue. I can now use chrome with hardware acceleration enabled without rendering problems. Is there any long-term downside with leaving this flag set? Or should I drop the environment entry when upstream has fixes? Thanks again for your help :-) -- 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/2026886 Title: [amdgpu] google chrome hardware acceleration broken on 42.9-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028553] Re: hardware not detected
*** This bug is a duplicate of bug 2028071 *** https://bugs.launchpad.net/bugs/2028071 That page does not exist. Can you provide an alternate solution -- 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/2028553 Title: hardware not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2028553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028553] Re: hardware not detected
*** This bug is a duplicate of bug 2028071 *** https://bugs.launchpad.net/bugs/2028071 Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #2028071, so 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. Please continue to report any other bugs you may find. ** Attachment removed: "CoreDump.gz" https://bugs.launchpad.net/bugs/2028553/+attachment/5688070/+files/CoreDump.gz ** Attachment removed: "ProcMaps.txt" https://bugs.launchpad.net/bugs/2028553/+attachment/5688072/+files/ProcMaps.txt ** Attachment removed: "ProcStatus.txt" https://bugs.launchpad.net/bugs/2028553/+attachment/5688073/+files/ProcStatus.txt ** This bug has been marked a duplicate of private bug 2028071 ** Information type changed from Private to Public ** Tags removed: need-amd64-retrace -- 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/2028553 Title: hardware not detected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-software/+bug/2028553/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2028311] Re: 22.04 : Default screenshot utility can be triggered from login-screen but useless.
In the eventuality it happens, ok. Might be interesting though to know how / why it happened. -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers fai
Hi Steve Langasek, I reinstalled today my PC with Ubuntu Desktop IOT. And i use latest packages from proposed repository. This issue is now resolved. My PC now running this: Kernel version: 5.15.0-1035-intel-iotg #40-Ubuntu SMP Fri Jul 14 08:03:36 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux Mutter version: dpkg -l | grep mutter ii gir1.2-mutter-10:amd64 42.9-0ubuntu4 amd64GObject introspection data for Mutter ii libmutter-10-0:amd64 42.9-0ubuntu4 amd64window manager library from the Mutter window manager ii mutter-common 42.9-0ubuntu4 all shared files for the Mutter window manager Thank you Daniel and Unnikrishnan for your support. A good day. -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers fai
** Tags removed: block-proposed -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026887] Re: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers fai
Test environment OS: Ubuntu 22.04.02 kernel: 5.15.0-76 Processor: 12th Gen Intel(R) Core(TM) i7-1270P mutter-common: 42.9-0ubuntu1 Problem: Stuck at a black screen after entering hard disk encryption password. Not getting any login screen for entering username/password Tried proposed fix by installing 42.9-0ubuntu4 from Jammy-proposed Rebooted machine Now login screen is loaded after entering hard disk encryption password ** Tags removed: verification-needed-jammy ** Tags added: block-proposed verification-done-jammy -- 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/2026887 Title: gnome-shell 42.9 Wayland sessions fail to start on Intel 12th gen or later if running 5.15/5.17 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2026887/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated
Verified fixed on jammy in 42.9-0ubuntu4. Tested using the test plan at the top of the page and a 1000Hz mouse. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy -- 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/2023766 Title: Mouse cursor stutters over GUI elements that are animated To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023766/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
