[Bug 1980718] Re: External monitor not working on Wayland
Hi Daniel, Thank you for your reply Before checking your solution I tested again to be sure the issue still exists and it seems that the issue has been fixed. Since the bug submission there were a few updates that might have fixed it directly or indirectly: * a kernel update * a thunderbolt (docking related) firmware update from Dell Is there any further action required from me to close this issue? Regards -- 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/1980718 Title: External monitor not working on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1980718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980718] [NEW] External monitor not working on Wayland
Public bug reported: When I connect the external monitor the image is shown on the external display but it freezes (on both displays); after I unplug the external display the following errors are logged (not sure it is related to the freeze): Jul 5 09:19:39 xps gnome-shell[10252]: meta_display_get_monitor_in_fullscreen: assertion 'monitor >= 0 && monitor < n_logical_monitors' failed Jul 5 09:19:39 xps gnome-shell[10252]: meta_monitor_manager_get_logical_monitor_from_number: assertion '(unsigned int) number < g_list_length (manager->logical_monitors)' failed Jul 5 09:19:39 xps gnome-shell[10252]: meta_workspace_get_work_area_for_monitor: assertion 'logical_monitor != NULL' failed The external display is connected via a thunderbolt port and an adapter to HDMI. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.2-0ubuntu0.2 ProcVersionSignature: Ubuntu 5.15.0-40.43-generic 5.15.35 Uname: Linux 5.15.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jul 5 09:21:33 2022 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-07 (696 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 42.2-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (68 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy third-party-packages wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1980718 Title: External monitor not working on Wayland To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1980718/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1980667] Re: ubuntu-desktop-minimal install fails - libmutter-10-1 broken with phased dependency
*** This bug is a duplicate of bug 1979244 *** https://bugs.launchpad.net/bugs/1979244 Hi Jeremy! Is there any workaround for this issue? I have a laptop that is not starting the gmd session anymore and on with gdm3 reconfigure I get the same broken package error. -- 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/1980667 Title: ubuntu-desktop-minimal install fails - libmutter-10-1 broken with phased dependency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1980667/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]
Setting MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 also works for me (XPS 9500). Furthermore, it fixes also the Night Light feature. Thank you Daniel! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1968040 Title: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1968040/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
Thank you Daniel! I have added the bug information here: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534 -- 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/1967274 Title: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1978534] [NEW] Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument]
Public bug reported: Screen wont wake up using mouse or keyboard. The only way to wake it up is to use CTRL+ALT+F1. The behavior is similar to the one for this bug: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1967274 The following is the log while this situation occurs: Jun 14 10:30:13 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:13 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument [ X 300+ of the first 2 lines] Jun 14 10:30:18 xps gnome-shell[3623]: JS ERROR: Failed to open reauthentication channel: Gio.IOErrorEnum: Error receiving data: Connection reset by peer#012_promisify/proto[asyncFunc]/ Warning: Unsupported maximum keycode 708, clipping. Jun 14 10:30:36 xps gnome-shell[12148]: > X11 cannot support keycodes above 255. Jun 14 10:30:36 xps gnome-shell[12148]: Errors from xkbcomp are not fatal to the X server Jun 14 10:30:36 xps gnome-shell[3623]: Failed to post KMS update: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Page flip discarded: drmModeAtomicCommit: Invalid argument Jun 14 10:30:36 xps gnome-shell[3623]: Object .MetaInputDeviceNative (0x7fb97014c200), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Jun 14 10:30:36 xps gnome-shell[3623]: == Stack trace for context 0x56180bd0f4b0 == Jun 14 10:30:36 xps gnome-shell[3623]: #0 56180f536160 i resource:///org/gnome/shell/ui/keyboard.js:1216 (2e077f8a62e0 @ 56) Jun 14 10:30:36 xps gnome-shell[3623]: #1 56180f5360b8 i resource:///org/gnome/shell/ui/keyboard.js:1222 (2e077f8a6330 @ 94) Jun 14 10:30:36 xps gnome-shell[3623]: #2 7ffe1f7901c0 b self-hosted:1181 (10952b4b0a10 @ 454) Jun 14 10:30:36 xps dbus-daemon[3485]: [session uid=1000 pid=3485] Activating service name='org.gnome.ArchiveManager1' requested by ':1.147' (uid=1000 pid=12112 comm="gjs /usr/share/gnome-shell/extensions/ding@rasters" label="unconfined") Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). Jun 14 10:30:36 xps gnome-shell[3623]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). Jun 14 10:30:37 xps gnome-shell[3623]: DING: Detected async api for thumbnails Jun 14 10:30:37 xps gnome-shell[3623]: DING: GNOME nautilus 42.1.1 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.1-0ubuntu0.1 ProcVersionSignature: Ubuntu 5.15.0-37.39-generic 5.15.35 Uname: Linux 5.15.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jun 14 10:32:00 2022 DisplayManager: gdm3 EcryptfsInUse: Yes InstallationDate: Installed on 2020-08-07 (675 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) RelatedPackageVersions: mutter-common 42.1-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-04-27 (47 days ago) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1978534 Title: Screen sometimes can't update [Failed to post KMS update: drmModeAtomicCommit: Invalid argument] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1978534/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1967274] Re: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found]
I am using kernel v5.15.0-37 but I am still affected by this bug on my XPS 15 (9500). Installed mutter is 42.1. Also, the Night Light is not working (I saw some references in this thread about this feature). Is there anything else I must update on my system to have it working properly? 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/1967274 Title: Screen sometimes can't update [Failed to post KMS update: CRTC property (GAMMA_LUT) not found] To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1967274/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1963264] Re: Gnome screen recorder doesn't work on dist-upgraded jammy systems
Hi, I have encountered the same issue after upgrading to Ubuntu 22.04. For me the fix was to reinstall the `gstreamer1.0-pipewire` package. `sudo apt reinstall gstreamer1.0-pipewire` Regards -- 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/1963264 Title: Gnome screen recorder doesn't work on dist-upgraded jammy systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1963264/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1666681] Re: Restore interactive_search.patch (type-ahead search)
OMFG, being an Ubuntu (patched Nautilus that is) user for more than 9 years I thought this was a bug with 17.10 and patiently waited for a fix ... can't agree more with "complete idiots" This is not a huge, complex and hard to maintain feature that you just decide it is too difficult to support. Is this a mirror of the next "de- generation" of products? OMFG -- 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/181 Title: Restore interactive_search.patch (type-ahead search) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/181/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
