I just did an online fresh install of Cinnamon on a x86_64 device.
On x11, everything works properly. On Wayland after login, you get a black screen, then black screen that flashes the panel and an arrow cursor, then back to black screen.
Tried with LTS kernel, same results.
Fresh installs on RPi 4b, and RPI 5 with Cinnamon exhibit the exact same symptoms, so I don’t think this is hardware related.
Getting late, so I will investigate further tomorrow.
Anyone else having this problem?
Pudge
I got basically the same thing, with multiple coredumps starting with Xwayland. I wonder if there are packages missing that the stock Cinnamon install doesn’t include for Wayland.
Is Cinnamon ready for Wayland already? I thought it isn’t … 
As far as I know the Wayland session on Cinnamon is still experimental, so no surprise if something doesn’t work.
https://forums.linuxmint.com/viewtopic.php?t=411761
AFAIC Wayland backend of Cinnamon has been worked on a lot for the past 2 years, hopefully it will be ready for the next major release of Mint.
Apr 24 14:22:16 joe-standardpc systemd-coredump[4398]: Process 4108 (Xwayland) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Apr 24 14:22:16 joe-standardpc systemd[1]: Started Process Core Dump (PID 4398/UID 0).
Apr 24 14:22:16 joe-standardpc systemd-coredump[4399]: Process 4108 (Xwayland) of user 1000 dumped core.
Stack trace of thread 4108:
#0 0x00007f2a06498a2c n/a (libc.so.6 + 0x98a2c)
#1 0x00007f2a0643e1a0 raise (libc.so.6 + 0x3e1a0)
#2 0x00007f2a064255fe abort (libc.so.6 + 0x255fe)
#3 0x000055cf518ef5ab n/a (/usr/bin/Xwayland + 0x18c5ab)
#4 0x000055cf518ef8ff n/a (/usr/bin/Xwayland + 0x18c8ff)
#5 0x000055cf518e6b64 n/a (/usr/bin/Xwayland + 0x183b64)
#6 0x00007f2a0643e2d0 n/a (libc.so.6 + 0x3e2d0)
#7 0x000055cf5179a95b n/a (/usr/bin/Xwayland + 0x3795b)
#8 0x000055cf5185dc26 n/a (/usr/bin/Xwayland + 0xfac26)
#9 0x000055cf5185fa5b n/a (/usr/bin/Xwayland + 0xfca5b)
#10 0x000055cf5180ae69 n/a (/usr/bin/Xwayland + 0xa7e69)
#11 0x000055cf51809b94 n/a (/usr/bin/Xwayland + 0xa6b94)
#12 0x000055cf51780645 n/a (/usr/bin/Xwayland + 0x1d645)
#13 0x00007f2a064276c1 n/a (libc.so.6 + 0x276c1)
#14 0x00007f2a064277f9 __libc_start_main (libc.so.6 + 0x277f9)
#15 0x000055cf51782085 n/a (/usr/bin/Xwayland + 0x1f085)
ELF object binary architecture: AMD x86-64
Apr 24 14:22:16 joe-standardpc systemd[1]: systemd-coredump@8-5-4398_4399-0.service: Deactivated successfully.
Apr 24 14:22:16 joe-standardpc cinnamon-session-binary[3588]: WARNING: t+1.88924s: App 'cinnamon-wayland.desktop' respawning too quickly
Apr 24 14:22:16 joe-standardpc cinnamon-session-binary[3588]: CRITICAL: t+1.88929s: Unable to start session: A program required by the session failed to start. App ID: 'cinnamon-wayland.desktop'. Startup ID: '10a1d25f68a59ceaeb177703333480865000000035880000'.
https://dpaste.com/DGYVBDXUL
bootlog ..
so same as with arch/based ?
i know wayland session was starting properly before on my tests in VMs too.. now its failing the same all over the place, and it had even keymap set from what i remember?
I played with cin in vms for a while tried downgrading muffin / mesa and using git versions with no change on the issue. No checking on real hardware too..
Thanks everyone for the feedback.
After reading all the posts, I think this is a hunker down and wait for the fix situation.
Pudge
it looks exactly the same everywhere i can see cinnamon panel and desktop flickering and it crashes to black screen ..
archinstall has the same outcome..
I remember having run Cinnamon Wayland on Mint when it had its debut.
No problems with flickering, but the session kept freezing after some time, to the extent I was able to un-freeze it only with REISUB.
Correct. The title of this post was my conclusion after 15 minutes on EOS Cinnamon Wayland.
So never looked back or tried it again.
The title of the post was also my conclusion on EOS 10.10.2 budgie but by then I could work with it (the “broken”) and really wound up liking it
