(03-09-2020, 06:00 AM)p3732 Wrote: Meanwhile ArchlinuxARM already has GNOME 3.36 landed (gotta love how fast Arch packages new releases <3) and it fixed the issues for me. I am sure Manjaro will soon have the packages too, if you don't want to wait you can swap out your mirrorlist with the one from Arch like I did.That's great for Arch/Manjaro users! Sadly I am not among the ranks anymore, since now I can not get any fresh installs of Arch/Manjaro to stay booting for me.
(03-09-2020, 06:00 AM)p3732 Wrote: That sucks, I am glad I installed Manjaro to the EMMC a long time ago and it never acted up like that.That's certainly possible, Hard to say for sure, as the drive was wiped since there was no way of recovering my lost data.
The system folder becoming files sounds like some messing around with flags (like missing x flag
(03-09-2020, 06:00 AM)p3732 Wrote: I don't have any such package installed, so I don't think that was the issue.It didn't show as a conflict in Fedora, either. A shame, but the glimmer of hope was worth it while it lasted.
EDIT: just ran into this issue on Fedora that may prove helpful, too. I saw many of the same errors given here, when troubleshooting this issue myself: https://bugzilla.redhat.com/show_bug.cgi?id=1762151#c20
Got a Manjaro install to stay booting, too. Switching to unstable repos will get you a working Gnome 3.36