Hi. I’m an online tutor using Xournal++ on Fedora 44. Recently, after an update, I find anytime I enable screen sharing regardless of the browser (Chrome/Firefox) or the online platform (Google Meet/Zoom), the moment I bring my stylus to my Wacom tablet, the entire display manager crashes and lands me back into the login screen.
I am on AMD Ryzen AI Pro 7 based Lenovo Thinkpad laptop with Wayland. I have no clue how to go about troubleshooting this further. I would greatly appreciate any help from the community. Thank you.
Can you somehow pinpoint what changed between now (not working) and then (working)? In particular, does xournalpp play a role here, or does the same happen with any shared window receiving stylus focus?
Besides the app, it’s gnome and the portals which may or may not have changed during the update.
Thank you for the reply.
The crash happens as long as I share my screen or window of any app, not necessarily Xournal++. The moment I bring my stylus to close proximity of the tablet, the display manager crashes.
With this experience, I have learned the hard way to setup BTRFS snapshots. I reinstalled fedora 44 but with BTRFS snapshots enabled now.
I just learned about this. I’m sorry I can’t tell what updates took place - as I just click the update button on the GUI, software manager.
Does mutter crash when you try to use the tablet?
Could be this issue https://gitlab.gnome.org/GNOME/mutter/-/work_items/4909
Recompile mutter with MR5169, I think downgrading mutter to version 50.1 should also work for now.
Thank you for the reply.
Will this be a safe procedure to follow to downgrade mutter to 50.1?
which one? All I see is a pre-filled google page with search results…
sudo dnf downgrade mutter will downgrade to 50.0 ( from the initial fedora repository) .
50.1 is available in updates-archive repository or directly from koji, e.g.
sudo dnf install fedora-repos-archive
sudo dnf config-manager setopt updates-archive.enabled=0
sudo dnf downgrade mutter --enable-repo updates-archive
Would you be willing to test ‘mutter-50.3’ using the merge request mentioned? I can have this compiled later, ( I’m busy atm).
Update: the merge request is for mutter 51 and the code has undergone some refactoring. This needs to be back ported to mutter 50 first.
Please open a new bugreport on bugzilla.redhat.com for Fedora / mutter
This is a known issue with Mutter. See: #4908 and #4909.
They seem to be working on it !5169.
In the mean time, here’s the workaround I’m using:
systemctl --user edit org.gnome.Shell@user.service
Paste the following:
[Service]
Environment=MUTTER_DEBUG_DISABLE_HW_CURSORS=1
Then save, logout and log back in.
Seems to have solved it for me until we have the official fix.
Thank you 
Thank you dear Sir
I’m just curious - what should I do when the official fix has been incorporated into the code base? Will the regular updates that I execute thereafter, undo this workaround or need I explicitly run a manual procedure to disable this workaround?
I’m not that familiar with the code management and deployment procedures, so please bear with me.
You can revert the edit by running:
systemctl --user revert org.gnome.Shell@user.service
Then logging out and logging back in.
I’m sorry, this workaround procedure did not work. The issue is still there, the display is still crashing when I share the screen and attempt to use the graphics tablet.
Yes, I’ve noticed that it doesn’t solve the problem on all screen sharing. For example, the workaround works when I’m using the Zoom app on Linux, but not when using Microsoft Teams for Linux (which is a web app).
So I’m afraid we’re going to have to wait for the official fix. 
I understand. Thank you so much for trying though. I appreciate it.
Thankfully I haven’t updated my desktop PC yet with the new mutter version; that’s kept me going.
As an alternative, I’ve temporarily downgraded Mutter and pinned the older version, which did not have this issue. On Fedora 44:
Fedora 44: downgrade Mutter 50.3 to 50.1 and pin it
Download the historical Fedora Koji packages:
mkdir -p /var/tmp/mutter-50.1-rollback
curl -fLO --output-dir /var/tmp/mutter-50.1-rollback \
https://kojipkgs.fedoraproject.org/packages/mutter/50.1/1.fc44/x86_64/mutter-50.1-1.fc44.x86_64.rpm \
https://kojipkgs.fedoraproject.org/packages/mutter/50.1/1.fc44/noarch/mutter-common-50.1-1.fc44.noarch.rpm
Downgrade both packages together:
sudo dnf install --nogpgcheck \
/var/tmp/mutter-50.1-rollback/mutter-50.1-1.fc44.x86_64.rpm \
/var/tmp/mutter-50.1-rollback/mutter-common-50.1-1.fc44.noarch.rpm
--nogpgcheck is necessary because these raw historical Koji artifacts are unsigned. They are downloaded directly from Fedora’s HTTPS Koji package store.
Pin the installed versions:
sudo dnf versionlock add mutter mutter-common
Verify the versions and locks:
rpm -q mutter mutter-common
dnf versionlock list
dnf upgrade --assumeno mutter mutter-common
Expected versions:
mutter-50.1-1.fc44.x86_64
mutter-common-50.1-1.fc44.noarch
Finally, log out and back in or reboot so GNOME Shell loads the downgraded Mutter libraries.
To remove the pin later:
sudo dnf versionlock delete mutter mutter-common
sudo dnf upgrade mutter mutter-common
You’re a gem! Thank you so much for the interim solution 
This works like a charm!
So when the permanent solution is out in the fedora codebase, I just run the below two commands?
sudo dnf versionlock delete mutter mutter-common
sudo dnf upgrade mutter mutter-common
May I know where/how do I check whether solution has been implemented in the code base?
Yep!
I’m keeping an eye on it myself. The fix has already been merged into the GNOME 51 development branch, but hasn’t been backported to GNOME 50. So I’m afraid it’s a case of watching the gnome-50 branch to wait for a backport, or wait for GNOME 51.
@rameshkumar the solution has been implemented and backported to Fedora 44. You can remove the version lock and download the latest mutter and mutter-common (50.3-3.fc44) by using dnf update.
I’ve tested it with Zoom and MS Teams, and both are working fine for me now.
Yes, I just did the unlocking. It is working fine now. No crashes when during the google meet sharing session. Thank you very much sir!