[Bug 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/-/issues #6831 https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6831 ** Also affects: gnome-shell via https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/6831 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
** Also affects: linux-hwe-5.19 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-hwe-5.19 (Ubuntu) Status: New => Fix Released ** Description changed: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. - [ Workaround ] + [ Workarounds ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment + + or upgrade to a newer kernel: + sudo apt install linux-generic-hwe-22.04 [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... For kinetic: The bug never existed in mutter 43.0 (it was introduced in 43.2) and was already fixed in the kernel anyway. For lunar and later: The bug was already fixed in the kernel. You would only ever encounter it in theory if you downgrade the kernel. -- 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 Alder Lake running 5.15 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 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
The kernel is only seeing the built-in display as "connected": /sys/class/drm/card0-DP-1/status:disconnected /sys/class/drm/card0-DP-2/status:disconnected /sys/class/drm/card0-eDP-1/status:connected If we assume one of those DP ports is actually the HDMI port then the problem would be a connector or cable issue. If however those DP ports are the USB-C ports then the HDMI port seems to be missing at the kernel level :( If the laptop has two GPUs then the second one would own the HDMI port, but I don't see a second GPU here. Unless it exists and is disabled in the BIOS? ** Package changed: mutter (Ubuntu) => linux-hwe-5.19 (Ubuntu) ** Changed in: linux-hwe-5.19 (Ubuntu) Status: Incomplete => 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/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.19/+bug/2027631/+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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
** No longer affects: mutter (Ubuntu Jammy) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mutter (Ubuntu Jammy) Status: New => In Progress ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => Critical ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: linux-intel-iotg (Ubuntu Jammy) Status: New => Confirmed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Won't Fix ** No longer affects: linux-intel-iotg (Ubuntu 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 Alder Lake running 5.15 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 2027617] Re: Can't change build-in display refresh rate
Thanks. The kernel is reporting only one official refresh rate for that monitor: │ │ ├───Modes │ │ │ └───3840x2160@60.01 preferred driver phsync nvsync So that's all you will see in Wayland sessions. To get more custom modes you can try logging into 'Ubuntu on Xorg' instead. There is an enhancement request being discussed to add the same to Wayland sessions: https://gitlab.gnome.org/GNOME/mutter/-/issues/2856 ** Bug watch added: gitlab.gnome.org/GNOME/mutter/-/issues #2856 https://gitlab.gnome.org/GNOME/mutter/-/issues/2856 ** Package changed: ubuntu => mutter (Ubuntu) ** Changed in: mutter (Ubuntu) Importance: Undecided => Wishlist ** Changed in: mutter (Ubuntu) Status: Incomplete => Triaged ** Also affects: mutter via https://gitlab.gnome.org/GNOME/mutter/-/issues/2856 Importance: Unknown Status: Unknown ** Summary changed: - Can't change build-in display refresh rate + Expose custom display modes in Wayland sessions like Xorg does -- 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/2027617 Title: Expose custom display modes in Wayland sessions like Xorg does To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/2027617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027617] [NEW] Can't change build-in display refresh rate
You have been subscribed to a public bug: I guess it is related to the latest updates. Before I can change refresh rate. As for now, the refresh rate is fixed (59.88Hz) and I don't have any option to change it. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:23:31 2023 DistUpgraded: Fresh install DistroCodename: lunar DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:3802] InstallationDate: Installed on 2018-09-15 (1760 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 80Y8 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=56a0d470-0b27-4743-8549-8b7195c884a1 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/23/2017 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: 5NCN28WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo YOGA 920-13IKB Glass dmi.ec.firmware.release: 0.29 dmi.modalias: dmi:bvnLENOVO:bvr5NCN28WW:bd08/23/2017:br1.28:efr0.29:svnLENOVO:pn80Y8:pvrLenovoYOGA920-13IKBGlass:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct31:cvrLenovoYOGA920-13IKBGlass:skuLENOVO_MT_80Y8_BU_idea_FM_YOGA920-13IKBGlass: dmi.product.family: YOGA 920-13IKB Glass dmi.product.name: 80Y8 dmi.product.sku: LENOVO_MT_80Y8_BU_idea_FM_YOGA 920-13IKB Glass dmi.product.version: Lenovo YOGA 920-13IKB Glass dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.114-1 version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~23.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1 version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-1ubuntu3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20210115-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 ** Affects: mutter (Ubuntu) Importance: Wishlist Status: Triaged ** Tags: amd64 apport-bug lunar ubuntu wayland-session -- Can't change build-in display refresh rate https://bugs.launchpad.net/bugs/2027617 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. -- 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
I'm still struggling to understand how gnome-shell is triggering the corruption. Maybe try switching between 42.5 and 42.9 a few times again and verify in both cases the mutter packages remain 42.9. Also can you find any other app affected? -- 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/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/gnome-shell/+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
** 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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+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
OK, thanks for the information. The one I had tested was 42.9-0ubuntu2 with Jammy. I'll test again when 42.9-0ubuntu3 is available in -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/2020782 Title: Xdcv: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027737] [NEW] Can't login to or add google accounts through control center
Public bug reported: My google account credentials say expired and the control center says I need to log in so I click on it, select to log in. A window for google sign in pops up with my email already entered and a next button. when you click the next button nothing happens. Ubuntu 23.04, gnome-control- center Installed: 1:44.0-1ubuntu5 I expected it to work it did not work ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-control-center 1:44.0-1ubuntu5 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 15:21:54 2023 ExecutablePath: /usr/libexec/gnome-control-center-goa-helper InstallationDate: Installed on 2023-07-11 (2 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, user) SHELL=/bin/bash XDG_RUNTIME_DIR= SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-control-center (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 gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/2027737 Title: Can't login to or add google accounts through control center To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2027737/+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
Actually, we're uploading a new version to jammy-proposed 42.9-0ubuntu3 so you can wait and test that version. -- 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: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+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
Fabio, just to be clear, could you be specific about what version of Ubuntu you were using and what version of mutter you had installed? If this update has fixed the issue here, you can also change the bug tag from verification-needed-jammy to 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: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Thank you for helping to make Ubuntu better. I have uploaded these fixes for Jammy and Lunar. They will need to be manually approved by a member of the Ubuntu SRU team before they will be made available as proposed updates. I am unsubscribing ubuntu-sponsors now. Feel free to resubscribe if you have something else that needs to be sponsored. ** Description changed: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example). 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] This only modifies the code related to mirror mode in Displays panel. For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha. - For Jammy, include the Lunar patch and modify the way to find cloning - mode. This second patch is backported from gnome-control-center 42. + For Jammy, include the Lunar patch and update the way to find cloning + mode. These 2 additional patches are backported from gnome-control- + center 43. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) -- 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/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026228] Re: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
** Description changed: [Impact] gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution [Test case] Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors. - 1. Connected monitors to system which don't have same resolution. + This particular bug requires two screens that have a screen resolution + that they don't both share. (See comment 12 for an example). + + 1. Connect the monitors 2. Open the GNOME Settings app (gnome-control-center) 3. On the left sidebar, click Displays to switch to the Display panel 4. Switch to mirror mode 3. gnome-control-center won't crash [Where problems could occur] - It only modified the code related to mirror mode in Displays panel. For KK and LL check variable (best_mode) before using it. For Jammy, modified the way to find cloning mode and check the variable (best_mode) . The second patch already included in gnome-42. The risk will be low. + This only modifies the code related to mirror mode in Displays panel. + + For Lunar, check variable (best_mode) before using it. This patch is + backported from GNOME 45 Alpha. + + For Jammy, include the Lunar patch and modify the way to find cloning + mode. This second patch is backported from gnome-control-center 42. [Other info] Two Merge Request are related 1. Check best_mode exist before adding flag (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1835) 2. Use virtual clone modes when mirroring (https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1376) ** Changed in: gnome-control-center (Ubuntu Lunar) Status: Confirmed => In Progress ** Changed in: gnome-control-center (Ubuntu Jammy) Status: New => In Progress ** Changed in: gnome-control-center (Ubuntu Jammy) Assignee: (unassigned) => Dirk Su (dirksu) -- 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/2026228 Title: gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2026228/+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've tested the mutter packages from -proposed in an AWS Workspace: https://pastebin.ubuntu.com/p/9Yvgfs7yZr/ And I'm able to successfully change the scale to 200% and then revert the setting. The following messages are logged when changing to 200%: https://pastebin.ubuntu.com/p/Y5QdXSqcsW/ And then when you try to revert: https://pastebin.ubuntu.com/p/cYP7JKryx9/ -- 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: Changing display scale setting and reverting it fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2020782/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2007621] Re: gio open exits with success even though the underlying exec failed
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glib2.0 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2007621 Title: gio open exits with success even though the underlying exec failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/2007621/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
Thank you! The Netplan build seems to be fixed now. Removing the tag. ** Tags removed: block-proposed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1794064] Re: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap
This bug was fixed in the package evince - 44.1-1ubuntu0.1 --- evince (44.1-1ubuntu0.1) lunar; urgency=medium * Allow evince to spawn browsers distributed as snaps (LP: #1794064) - debian/apparmor-profile: include snap-browsers abstracted profile and allow transitions to them in evince -- Georgia Garcia Mon, 05 Jun 2023 16:32:15 -0300 ** Changed in: evince (Ubuntu Lunar) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1794064 Title: Clicking a hyperlink in a PDF fails to open it if the default browser is a snap To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1794064/+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
Package version tested was 42.9-0ubuntu2 (replacing 42.9-0ubuntu1). Tested in a session running many active applications (Firefox, multiple windows with video, totem, Various chat applications, etc.) -- 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
[Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated
Fixed for me too. Also fixes drag and drop issues in many apps in where I would have to make multiple attempts before it would randomly succeed. -- 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
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
I've cherry-picked the !3498 upstream merge proposal for this issue. ** Changed in: glib2.0 (Ubuntu) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+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
Daniel van Vugt wrote: > On the slight chance this is related to another AMD GPU issue I've heard > about in 42.9, please try adding this to /etc/environment: > MUTTER_DEBUG_USE_KMS_MODIFIERS=0 This didn't help, unfortunately. What I did: - Re-enabled hardware acceleration in chrome - Confirmed rendering is broken - Added MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment - Rebooted - Confirmed rendering is still broken in chrome -- 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/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/gnome-shell/+bug/2026886/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027681] Re: On Home Folder when right click for context menu, if context option is on top of a file it cant be clicked
This is only happening on the home folder. I have tested other folders and they work properly. To replicate this, do the following steps 1 to 3 times. It will eventually happen. Sometimes on the first try or 2nd try, but I was able to confirm that up to a maximum of 3 tries are needed to always get the same result: 1. Right click empty space on the home folder while using nautilus and make sure for example the properties option in the context menu always lands on top of a file. 2. Try to click the properties option. If it works correctly, repeat step 1 at least 2 more times. 3. After the problem happens, it will keep on happening until nautilus is closed and reopened. -- 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/2027681 Title: On Home Folder when right click for context menu, if context option is on top of a file it cant be clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2027681/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027681] [NEW] On Home Folder when right click for context menu, if context option is on top of a file it cant be clicked
Public bug reported: When on home as seen on the image https://imgur.com/a/61q20OR if you right click for context menu, not right click on a file, but on the space between the files, after the context menu opens, if the context option you want to click is on top of a file it cant be clicked and it will resolve on closing the context menu and clicking on the file. On the image above you can see in red the files behind the context menu, those specific areas if clicked will close the context menu and end up clicking on the file. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: nautilus 1:44.2.1-0ubuntu1 Uname: Linux 6.3.7-060307-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 06:15:48 2023 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'small-plus'" b'org.gnome.nautilus.preferences' b'migrated-gtk-settings' b'true' b'org.gnome.nautilus.preferences' b'search-view' b"'icon-view'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1219, 879)' InstallationDate: Installed on 2023-04-20 (83 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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 nautilus-share0.7.5-0.3 ** Affects: nautilus (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 nautilus in Ubuntu. https://bugs.launchpad.net/bugs/2027681 Title: On Home Folder when right click for context menu, if context option is on top of a file it cant be clicked To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/2027681/+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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
I'm setting the importance to Critical per #6 at https://wiki.ubuntu.com/StableReleaseUpdates#Procedure ** Changed in: mutter (Ubuntu Jammy) Importance: High => Critical -- 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 Alder Lake running 5.15 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 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
** Changed in: glib Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
** Description changed: [ Impact ] gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder Lake systems running older kernels such as 5.15. [ Test Plan ] Try to log into gnome-shell. Verify there is a picture on the screen. [ Where problems could occur ] The offending code change relates to Intel-specific chip IDs so the change is limited to Intel systems. Although affected Intel systems worked perfectly before the change so we don't expect any problems in reverting the change. In theory the worst case is limited to more problems like that described in Impact above. [ Workaround ] Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment [ Other Info ] The log messages relating to this bug are: iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument iul 11 19:00:11 MY-PC gnome-shell[1040]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument ... + + For kinetic: The bug never existed in mutter 43.0 (it was introduced in + 43.2) and was already fixed in the kernel anyway. + + For lunar and later: The bug was already fixed in the kernel. You would + only ever encounter it in theory if you downgrade the kernel. -- 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 Alder Lake running 5.15 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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
Fix proposed: https://salsa.debian.org/gnome- team/mutter/-/merge_requests/100 -- 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 Alder Lake running 5.15 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 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
Daniel above are the txt files you've requested. Have tried 6.2 6.4 kernels in my previous installation with no success. That's when decided to reinstall and report the bug on clean system with supported kernel. Have also tried reinstalling gpu drivers with this guide no success, either https://dgpu-docs.intel.com/installation-guides/ubuntu/ubuntu-jammy-arc.html -- 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/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
connections.txt ** Attachment added: "connections.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+attachment/5686014/+files/connections.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/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
-- 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/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027631] Re: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port
drminfo.txt ** Attachment added: "drminfo.txt" https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+attachment/5686013/+files/drminfo.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/2027631 Title: [ASUS EXPERTBOOK B9400CBA] No signal to external monitor from HDMI port To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027631/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027645] Re: [Lenovo Legion 5] Brightness option is not working and not showing in system menu
See also: bug 1899626, bug 1944094, bug 1995173 ** Summary changed: - britness option is not working and not showing in system menu + [Lenovo Legion 5] Brightness option is not working and not showing in system menu ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Changed in: linux (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/2027645 Title: [Lenovo Legion 5] Brightness option is not working and not showing in system menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2027645/+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-0ubuntu2. Tested using the test plan at the top of the page and also a 1000Hz Microsoft Classic IntelliMouse. I actually don't think the bug was as visible in 42.x as it was in 44.x. The reason is likely because triple buffering in 42.x didn't rely on the problematic dynamic-max-render-time feature as much as newer releases do. Still, the fix was missing before and seems to be performing well in 42.9-0ubuntu2. ** Tags removed: verification-needed-jammy ** Tags added: verification-done-jammy ** Changed in: mutter (Ubuntu Jammy) Importance: Medium => Low -- 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
[Bug 2023766] Re: Mouse cursor stutters over GUI elements that are animated
> On test plans, I see both this bug and the other one will be individually > tested, > but what's the plan to ensure that other behaviour in mutter isn't regressed? Mutter and GNOME Shell are massive projects so the next bug is always somewhere you don't expect. I would not recommend focussing permanent test plans on any regressions that were found in 2023. Specifically addressing each one: Bug 2026887: Caused by a narrow hardware/kernel combination. No more important than any other CPU model or kernel release. Bug 2023759: Caused by a lack of testing remote desktop (upstream too). This could obviously be better tested but I argue the feature is too obscure to be a top-level test case we ask anyone to do on every update. Bug 2023363: Caused by 16 milliseconds being too small a difference for most to notice. Bug 2023766: Microstutters of a few milliseconds were a regression in 41.0 and went mostly unnoticed by everyone for several years because of how minor it is. Bug 2017097: Caused by a combination of being too hard to notice for people who did test Raspi, and me being only one person too busy dealing with a rewrite of triple buffering caused by a last-minute upstream API redesign in 44.0. Bug 2017137: Caused by a combination of being too hard to notice for people who did test Xorg, and me being only one person too busy dealing with a rewrite of triple buffering caused by a last-minute upstream API redesign in 44.0. To find future regressions more effectively we need both more people testing proposed for longer, and more hardware/software combinations. Perhaps slower phasing too since such obscure bugs are so easy to miss by most people. This isn't just a mutter issue. Almost every day I track obscure bugs back to the kernel caused by hardware combinations we simply can't expect to get tested exhaustively before every 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/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
Re: [Bug 2027645] Re: britness option is not working and not showing in system menu
On Thu, 13 Jul 2023 at 14:10, Daniel van Vugt <2027...@bugs.launchpad.net> wrote: > Please run: > > journalctl -b0 > journal.txt > > and attach the resulting text file here. > > ** Changed in: gnome-shell (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/2027645 > > Title: > britness option is not working and not showing in system menu > > Status in gnome-shell package in Ubuntu: > Incomplete > > Bug description: > The ubuntu version is automatic updated and then i am facing this > issue that there is not britness control is there in my system ment > and my briness key also not wokring > > ProblemType: Bug > DistroRelease: Ubuntu 23.04 > Package: gnome-shell 44.2-0ubuntu1 > ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 > Uname: Linux 6.2.0-25-generic x86_64 > ApportVersion: 2.26.1-0ubuntu2 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: ubuntu:GNOME > Date: Thu Jul 13 09:44:30 2023 > DisplayManager: gdm3 > InstallationDate: Installed on 2023-06-11 (32 days ago) > InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 > (20230418) > ProcEnviron: >LANG=en_US.UTF-8 >PATH=(custom, no user) >SHELL=/bin/bash >TERM=xterm-256color >XDG_RUNTIME_DIR= > RelatedPackageVersions: mutter-common 44.2-0ubuntu1 > SourcePackage: gnome-shell > UpgradeStatus: No upgrade log present (probably fresh install) > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027645/+subscriptions > > ** Attachment added: "journal.txt" https://bugs.launchpad.net/bugs/2027645/+attachment/5686012/+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/2027645 Title: britness option is not working and not showing in system menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027645/+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 Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid ar
** Description changed: - Hi Ubuntu Team, + [ Impact ] - MY ISSUE: - I installed today my PC with Ubuntu IOT Desktop(22.04.2 LTS (Jammy Jellyfish)). - But with updated for all packages and with reboot PC, i have error with starting gdm and access to /dev/dri/card0. + gnome-shell/mutter 42.9 fails to start (black screen) on Intel Alder + Lake systems running older kernels such as 5.15. - ERROR: - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:11 MY-PC gnome-session-binary[1022]: Entering running state - root@MY-PC:/home/tester# journalctl -b --no-pager | grep gnome- - iul 11 19:00:09 MY-PC systemd[1]: Mounting Mount unit for gnome-3-38-2004, revision 119... - iul 11 19:00:09 MY-PC systemd[1]: Mounted Mount unit for gnome-3-38-2004, revision 119. - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session[1022]: gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-session-binary[1022]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed - iul 11 19:00:10 MY-PC gnome-shell[1040]: Running GNOME Shell (using mutter 42.9) as a Wayland display server - iul 11 19:00:10 MY-PC gnome-shell[1040]: Device '/dev/dri/card0' prefers shadow buffer - iul 11 19:00:10 MY-PC gnome-shell[1040]: Added device '/dev/dri/card0' (i915) using atomic mode setting. - iul 11 19:00:10 MY-PC gnome-shell[1040]: Created gbm renderer for '/dev/dri/card0' - iul 11 19:00:10 MY-PC gnome-shell[1040]: Boot VGA GPU /dev/dri/card0 selected as primary - iul 11 19:00:10 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.a11y.Bus' requested by ':1.4' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using public X11 display :1024, (using :1025 for managed services) - iul 11 19:00:10 MY-PC gnome-shell[1040]: Using Wayland display name 'wayland-0' - iul 11 19:00:11 MY-PC gnome-shell[1040]: Unset XDG_SESSION_ID, getCurrentSessionProxy() called outside a user session. Asking logind directly. - iul 11 19:00:11 MY-PC gnome-shell[1040]: Will monitor session c1 - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.locale1' unit='dbus-org.freedesktop.locale1.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC /usr/libexec/gdm-wayland-session[1021]: dbus-daemon[1021]: [session uid=128 pid=1021] Activating service name='org.freedesktop.impl.portal.PermissionStore' requested by ':1.3' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.GeoClue2' unit='geoclue.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC polkitd(authority=local)[725]: Registered Authentication Agent for unix-session:c1 (system bus name :1.34 [/usr/bin/gnome-shell], object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) - iul 11 19:00:11 MY-PC dbus-daemon[693]: [system] Activating via systemd: service name='org.freedesktop.PackageKit' unit='packagekit.service' requested by ':1.34' (uid=128 pid=1040 comm="/usr/bin/gnome-shell " label="unconfined") - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension d...@rastersoft.com already installed in /usr/share/gnome-shell/extensions/d...@rastersoft.com. /usr/share/gnome-shell/extensions/d...@rastersoft.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-appindicat...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-appindicat...@ubuntu.com will not be loaded - iul 11 19:00:11 MY-PC gnome-shell[1040]: Extension ubuntu-d...@ubuntu.com already installed in /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com. /usr/share/gnome-shell/extensions/ubuntu-d...@ubuntu.com will not be
[Bug 2027645] Re: britness option is not working and not showing in system menu
Please run: journalctl -b0 > journal.txt and attach the resulting text file here. ** 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/2027645 Title: britness option is not working and not showing in system menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026887] Re: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
It's a regression introduced in mutter 42.9 by Intel: https://gitlab.gnome.org/GNOME/mutter/-/commit/1fd96e30f5f8a61d70d51f9012112e01818161a7 Although they would probably argue it's not a regression so long as you have a new enough kernel. Since we don't always have a new enough kernel in jammy we probably need to revert that commit. ** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Changed in: mutter (Ubuntu) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Mantic) Importance: Undecided Status: Fix Released ** Also affects: mutter (Ubuntu Mantic) Importance: High Assignee: Daniel van Vugt (vanvugt) Status: Confirmed ** Also affects: linux-intel-iotg (Ubuntu Mantic) Importance: Medium Status: Confirmed ** Also affects: linux (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: mutter (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-intel-iotg (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Jammy) ** No longer affects: linux (Ubuntu Kinetic) ** No longer affects: linux (Ubuntu Lunar) ** No longer affects: linux (Ubuntu Mantic) ** No longer affects: linux-intel-iotg (Ubuntu Jammy) ** No longer affects: linux-intel-iotg (Ubuntu Kinetic) ** No longer affects: linux-intel-iotg (Ubuntu Lunar) ** No longer affects: linux-intel-iotg (Ubuntu Mantic) ** Changed in: mutter (Ubuntu Jammy) Status: New => Confirmed ** Changed in: mutter (Ubuntu Jammy) Importance: Undecided => High ** Changed in: mutter (Ubuntu Jammy) Assignee: (unassigned) => Daniel van Vugt (vanvugt) ** Changed in: mutter (Ubuntu Kinetic) Status: New => Invalid ** Changed in: mutter (Ubuntu Lunar) Status: New => Invalid ** Changed in: mutter (Ubuntu Mantic) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu Mantic) Assignee: Daniel van Vugt (vanvugt) => (unassigned) ** Changed in: mutter (Ubuntu Mantic) Importance: High => Undecided ** Changed in: mutter (Ubuntu Jammy) Status: Confirmed => In Progress ** Summary changed: - [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) + gnome-shell 42.9 Wayland sessions fail to start on Intel Alder Lake running 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) -- 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 Alder Lake running 5.15 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: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Suggested workarounds: * Add MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment * sudo apt install linux-generic-hwe-22.04 -- 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: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 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: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Nevermind. This bug is affecting regular Ubuntu Desktop too, for those running the original 22.04 release. It shouldn't happen if you're using 22.04.2 though because that has a new enough kernel to support the hardware, in theory. ** Also affects: mutter (Ubuntu) Importance: Undecided Status: New ** Changed in: mutter (Ubuntu) Status: New => Confirmed ** Tags added: regression-update -- 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: [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 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 2027656] Re: blank screen after mutter update
*** This bug is a duplicate of bug 2026887 *** https://bugs.launchpad.net/bugs/2026887 Thanks. Merging into bug 2026887. ** This bug has been marked a duplicate of bug 2026887 [Intel Alder Lake] gnome-shell Wayland sessions fail to start on 5.15 kernels (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument) -- 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/2027656 Title: blank screen after mutter update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027645] Re: britness option is not working and not showing in system menu
** Package changed: ubuntu => gnome-shell (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/2027645 Title: britness option is not working and not showing in system menu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2027645/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027645] [NEW] britness option is not working and not showing in system menu
You have been subscribed to a public bug: The ubuntu version is automatic updated and then i am facing this issue that there is not britness control is there in my system ment and my briness key also not wokring ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-shell 44.2-0ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 09:44:30 2023 DisplayManager: gdm3 InstallationDate: Installed on 2023-06-11 (32 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 44.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- britness option is not working and not showing in system menu https://bugs.launchpad.net/bugs/2027645 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
** Bug watch added: gitlab.gnome.org/GNOME/glib/-/issues #3047 https://gitlab.gnome.org/GNOME/glib/-/issues/3047 ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/-/issues/3047 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027656] Re: blank screen after mutter update
At least one more colleague in my company just experienced the same issue after upgrading. -- 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/2027656 Title: blank screen after mutter update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027656] Re: blank screen after mutter update
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mutter (Ubuntu) Status: New => Confirmed -- 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/2027656 Title: blank screen after mutter update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1966808] Re: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (Failed to lock front buffer on /dev/dri/cardN: drmModeAddFB2WithModifiers failed: Invalid argument)
Hey Daniel, new bug opened: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656 thanks -- 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/1966808 Title: [radeon] gnome-shell Wayland sessions fail to start on legacy Radeon systems (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/mutter/+bug/1966808/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 2027656] [NEW] blank screen after mutter update
Public bug reported: Hey, running on Ubuntu 22.04.2 LTS. I upgraded mutter:amd64 (42.5-0ubuntu1 to 42.9-0ubuntu1) and suddenly experienced the problem described here: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1966808 black screen and logs like in #2 of above post. My own Logs: Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument Jul 12 11:35:16 xx gnome-shell[1464]: Failed to lock front buffer on /dev/dri/card0: drmModeAddFB2WithModifiers failed: Invalid argument After some investigation and finally finding the bug above here adding MUTTER_DEBUG_USE_KMS_MODIFIERS=0 to /etc/environment fixed it for me. Disabling wayland via /etc/gdm3/custom.conf worked as a workaround, too. Output of drm_info is attached. thanks ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: mutter 42.9-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 13 09:09:58 2023 SourcePackage: mutter UpgradeStatus: Upgraded to jammy on 2022-11-23 (231 days ago) ** Affects: mutter (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy regression-update wayland-session ** Attachment added: "drm_info.txt" https://bugs.launchpad.net/bugs/2027656/+attachment/5685973/+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/2027656 Title: blank screen after mutter update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2027656/+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
> On test plans, I see both this bug and the other one will be individually > tested, but > what's the plan to ensure that other behaviour in mutter isn't regressed? > https://wiki.ubuntu.com/DesktopTeam/TestPlans/Mutter exists, so would > following that be > appropriate, or do you want to do something else to verify this? I don't have a good answer to that, sorry. Mutter and GNOME Shell are very large projects and the desktop team only has between 1 and 3 people working on them at any given time. So we rely on community testing of proposed and careful monitoring of bug reports. -- 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
