As i not have two GPU’s just asking that it is clear, Device-1 is the integrated?
Yes, Device-1 is the integrated one.
Hi everybody,
to rule out this issue, does everybody here, that is affected by the reported issue use mutter-44.1?
mutter-44.1 (the compositor library for g-s, that provides the content for the screencast stream for gnome-remote-desktop (g-r-d)) contains Screencast fixes, a variety of (!2804) · Merge requests · GNOME / mutter · GitLab.
This MR appears to have a high negative impact on screencast streams, where MemFds are used instead of DmaBuf buffers, leading to most frames being not recorded to PipeWire (PW) buffers, so they could not be picked up by g-r-d.
The upstream issue for that is Since 44.1, sometimes frame updates are only occasionally pushed to the client (both X11 and Wayland), breaking GNOME Remote Desktop (#2783) · Issues · GNOME / mutter · GitLab and was fixed in screen-cast/src: Never dequeue pw_buffer's we refuse to record to (!2987) · Merge requests · GNOME / mutter · GitLab.
The fix was cherry-picked to the gnome-44 branch and mutter-44.2 will carry it.
Could try either to build mutter from the upstream gnome-44 branch or downgrade mutter to version 44.0 (because the MR, that introduced the issue, was merged for mutter-44.1) and then report here back, whether that got rid of your issue?
You need to restart your session (logout + login) after exchanging the installed mutter build.
How can one switch to a specific integrated video card, which in this case is Device 1? Is that a setting we choose? Thanks.
It should be mentioned that there are some very useful alternatives to remote desktop: IDE’s that use a web browser for display. Examples include Rstudio-server (which now adds a terminal and a Python IDE to the Rstudio IDE) and jupyter notebook (offers a terminal and notebook style IDE for Python, R, Julia, etc).
1 Like
It works for me in Fedora 38, but, only under Wayland. I always used to have my RDP working up until Fedora 37 with X11. The RDP still does not work for me under x11.
System:
Host: l-fedora Kernel: 6.2.14-300.fc38.x86_64 arch: x86_64
bits: 64 Desktop: GNOME v: 44.1 Distro: Fedora release 38 (Thirty Eight)
Machine:
Type: Laptop System: Dell product: Inspiron 15 3511 v: N/A
serial: <superuser required>
Mobo: Dell model: 0042CN v: A00 serial: <superuser required> UEFI: Dell
v: 1.21.0 date: 03/08/2023
Battery:
ID-1: BAT0 charge: 34.6 Wh (100.0%) condition: 34.6/40.3 Wh (85.8%)
CPU:
Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
cache: L2: 5 MiB
Speed (MHz): avg: 1656 min/max: 400/4200 cores: 1: 2400 2: 2400 3: 640
4: 2400 5: 954 6: 973 7: 1086 8: 2400
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
Display: wayland server: X.Org v: 22.1.9 with: Xwayland v: 22.1.9
compositor: gnome-shell driver: X: loaded: modesetting unloaded: fbdev,vesa
dri: iris gpu: i915 resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Xe Graphics (TGL GT2)
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-300.fc38.x86_64 status: kernel-api
Server-1: PipeWire v: 0.3.70 status: active
Network:
Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
driver: ath10k_pci
IF: wlp2s0 state: up mac: 4c:d5:77:5f:e1:3b
Bluetooth:
Device-1: Qualcomm Atheros type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
---
Partition:
---
Swap:
---
Sensors:
System Temperatures: cpu: 63.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 296 Uptime: 7m Memory: 15.35 GiB used: 3.24 GiB (21.1%)
Shell: Bash inxi: 3.3.26
The moment, I login back with my X11 windowing, RDP immediately breaks down in Fedora 38 as before. Which is:
- On login, the
RDPscreen becomes black. You press theEnterkey at this point. - You get the last visible screen on the desktop, totally frozen, where you cannot really do much, except to close your
RDPsession.
So, RDP works in Fedora 38 under Wayland, but, not on X11. Here is my inxi details for X11 session.
System:
Host: l-fedora Kernel: 6.2.14-300.fc38.x86_64 arch: x86_64
bits: 64 Desktop: GNOME v: 44.1 Distro: Fedora release 38 (Thirty Eight)
Machine:
Type: Laptop System: Dell product: Inspiron 15 3511 v: N/A
serial: <superuser required>
Mobo: Dell model: 0042CN v: A00 serial: <superuser required> UEFI: Dell
v: 1.21.0 date: 03/08/2023
Battery:
ID-1: BAT0 charge: 34.6 Wh (100.0%) condition: 34.6/40.3 Wh (85.8%)
CPU:
Info: quad core model: 11th Gen Intel Core i5-1135G7 bits: 64 type: MT MCP
cache: L2: 5 MiB
Speed (MHz): avg: 1892 min/max: 400/4200 cores: 1: 2400 2: 1089 3: 2400
4: 2400 5: 2400 6: 1185 7: 2400 8: 862
Graphics:
Device-1: Intel TigerLake-LP GT2 [Iris Xe Graphics] driver: i915 v: kernel
Device-2: Microdia Integrated_Webcam_HD type: USB driver: uvcvideo
Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 22.1.9 driver: X:
loaded: modesetting unloaded: fbdev,vesa dri: iris gpu: i915
resolution: 1920x1080~60Hz
API: OpenGL v: 4.6 Mesa 23.0.3 renderer: Mesa Intel Xe Graphics (TGL GT2)
Audio:
Device-1: Intel Tiger Lake-LP Smart Sound Audio driver: snd_hda_intel
API: ALSA v: k6.2.14-300.fc38.x86_64 status: kernel-api
Server-1: PipeWire v: 0.3.70 status: active
Network:
Device-1: Qualcomm Atheros QCA9377 802.11ac Wireless Network Adapter
driver: ath10k_pci
IF: wlp2s0 state: up mac: 4c:d5:77:5f:e1:3b
Bluetooth:
Device-1: Qualcomm Atheros type: USB driver: btusb
Report: rfkill ID: hci0 state: up address: see --recommends
Drives:
---
Partition:
---
Swap:
---
Sensors:
System Temperatures: cpu: 71.0 C mobo: N/A
Fan Speeds (RPM): N/A
Info:
Processes: 310 Uptime: 18m Memory: 15.35 GiB used: 3.99 GiB (26.0%)
Shell: Bash inxi: 3.3.26
Can you please give us the output of the following command:
sudo dnf list mutter
@rexarul I honestly don’t understand why you are still fiddling with that, when an upstream dev already told you the reason and how to mitigate it (and included the upstream references):
Either you build mutter from the (gnome-44 branch where [gnome-44] screen-cast/src: Never dequeue pw_buffer's we refuse to record to (!2988) · Merge requests · GNOME / mutter · GitLab is included or you temporary downgrade the mutter package to mutter-44.0 until mutter-44.2 is released.
The issue literally only happens in situation, where DmaBufs cannot be used for screencasting (like mentioned in my previous post, containing links to the upstream issue and upstream MR containing the fix).
DmaBuf buffers can only be used on Wayland (which is why the issue happen 100% of the time in x11, but not necessarily in Wayland), and only if the GPU driver supports DmaBufs (which is why the issue 100% of the time with NVIDIA drivers, because they don’t support DmaBufs).
Intel drivers support DmaBufs though.
See my previous post here for details.
1 Like
Please take in consideration that we are a wide range of audience. Not everyone who posts here a problem has the same technically background.
This keeping in mind, I asked about the mutter version @rexarul uses, to propose a downgrade. Step by step 
Apropos, you know “Mutter” in German means Mother. The name for this app could not been better chosen as it is. If a mother is missing or sick in a household mostly things get upside down. We are taking the “mutter” for granted that she works well, without taking in consideration that there can be a relation between “her” and Remote Desktop !
Mutter description
Source: GitHub - GNOME/mutter: Read-only mirror of https://gitlab.gnome.org/GNOME/mutter
Mutter
Mutter is a Wayland display server and X11 window manager and compositor library.
When used as a Wayland display server, it runs on top of KMS and libinput. It implements the compositor side of the Wayland core protocol as well as various protocol extensions. It also has functionality related to running X11 applications using Xwayland.
When used on top of Xorg it acts as a X11 window manager and compositing manager.
It contains functionality related to, among other things, window management, window compositing, focus tracking, workspace management, keybindings and monitor configuration.
Internally it uses a fork of Cogl, a hardware acceleration abstraction library used to simplify usage of OpenGL pipelines, as well as a fork of Clutter, a scene graph and user interface toolkit.
Mutter is used by, for example, GNOME Shell, the GNOME core user interface, and by Gala, elementary OS’s window manager. It can also be run standalone, using the command “mutter”, but just running plain mutter is only intended for debugging purposes.
2 Likes
+1 also experiencing this issue
sudo dnf downgrade mutter should be command in Fedora to downgrade the mutter version (to downgrade to mutter-44.0-1)
1 Like
Sure. Noted. It just was a bit over my head to perform the downgrade, but, what I tried to point out was that the issue does not exist with Wayland, while it exists with X11. That is all. Thank you.
Here is what I have and thanks @ilikelinux:
Copr repo for qgis-ltr owned by dani 1.3 kB/s | 341 B 00:00
Last metadata expiration check: 1:14:11 ago on Tue 16 May 2023 10:33:36 AM EDT.
Installed Packages
mutter.x86_64 44.1-1.fc38 @updates
Available Packages
mutter.i686 44.1-1.fc38 updates
Thank you very much, @pnowack, once I did as you suggested, am hunky-dory. After the downgrade, it is now:
Installed Packages
mutter.x86_64 44.0-1.fc38 @fedora
Available Packages
mutter.i686 44.1-1.fc38 updates
mutter.x86_64 44.1-1.fc38 updates
If you do now a update like sudo dnf upgrade, it will upgrade mutter back to the newer version.
To avoid this you can use the /etc/dnf/dnf.conf file and add on the end
exclude=mutter
As soon as we announce here that the newer version is available you can remove the command or just make a comment out of it while putting a # character in front.
like:
# exclude=mutter
Save it and do the update again.
1 Like
Thank you very much for that HT, @ilikelinux as that was the first thing I searched after the downgrade and set it up on the /etc/dnf/dnf.conf file already. 
Yes, understood… Thank you, very much. 
Come update mutter 44.2. Fix it on my machine.
You remove exclude=mutter in /etc/dnf/dnf.conf file, dnf update.
1 Like