I was able to install EndevourOS on the rasberry pi 4B 8GB on a usb drive. It boots fine and seems to run fine, however I wanted to use the welcome screen however it’s not working. Welcome application opens but displays a mess of colors and not interactable. No clue what caused this since it’s a fresh install. Any Ideas?
1 Like
Latest image release for the Raspberry Pi 4b.
Known problems:
KDE Plasma with Wayland. yad and Wayland have a compatibility problem so must use x11 to utilize the
Welcome screen and most other EnOS apps.
GNOME: Welcome screen and other EnOS apps work, but cannot utilize the Dark theme.
Work around: Launch "Tweaks" then click "Appearance" then "Legacy Applications" and change to Arc-Dark
ref: " https://github.com/endeavouros-arm/images/releases "
that be my guess… hope it help
2 Likes
Oh snap, yeah I recall reading that there were some issues regarding wayland and yad…slipped my mind…and forgot to swap to x11. Thanks 
Nothing like reading information and then not actually using it
Welcome to the EndeavourOS forum. I hope you enjoy your time here.
Wait until you get to be my age. 
Thanks for the feed back. I have not been able to figure out why yad does not work with RPI 4b and RPi 5 yet. On a RPi, yad works with wayland with Gnome and Cinnamon, but not Plasma. GO figure.
Pudge
EDIT:
Speaking of known problems. I recently discovered that on all platforms LXQT would not start sddm.
Also, on the Odroid N2 platform,
Odroid N2
Known problems:
KDE Plasma with Wayland. Cannot login with sddm.
After entering password, the cursor goes away and the computer freezes.
x11 works as expected. Upon first boot, switch to x11 before logging in.
I have figured out what was wrong with both issues and will be issuing new images for all devices tomorrow or the next day.
Thanks! I’ve been really enjoying EndeavourOS on my VM, and thought it would be an alright OS for my Raspberry Pi 4B, granted it probably would preform better on Raspberry Pi5 or an X86 SBC. Now that I’ve resolved this…my next task is try and figure out how to get NexDock XL to function with only 2 cables, instead of 3+…sadly they dont have a large forum yet and I don’t think they are well known. Awesome item to have though…works great for steamdeck, samsung Galaxy S2x phones…etc.
1 Like
The new images have been issued.
@joekamprad
I finally figured out the problem with Odroid N2, KDE Plasma, and wayland.
Odroid N2 (+) now works with x11 and Wayland.
installing the two following packages fixed the problem.
libmd
libbsd
Pudge
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.
I will see to test asap… still busy with things and heat waves burning over my office …
1 Like
could be some dependency missing on arm packages at archarm repo?
1 Like
Or should we add the needed architecture related dependencies into a package we deliver?
1 Like
In the course of trouble shooting this, I tried several things that didn’t work. Finally installing libmd & libbsd made it work. However, maybe the fix needed three packages and the first package didn’t fix the problem by itself and the last two packages fixed it. One could walk away from that thinking the last two packages was the total fix not realizing a third package was involved.
A neat experiment, IF you still have the uSD card that has the old Plasma install, try booting it up and simply installing libmd & libbsd, reboot and see if you can log into Wayland.
The biggest mystery to me is, how did the Doktor not realize that lib MD was missing? 
Pudge
In this case, libmd & libbsd are available in both the Archlinux x86_64 repo and the Archlinux ARM aarch64 repos.
To fix this, I added libmd and libbsd to the base install package list so they get installed on every combination of options. They are relatively small packages and if they are needed, they are there, and it doesn’t hurt anything if they are not needed.
libmd 96 KiB
libbsd 336 KiB
Pudge
Did you add them in PKGBUILD’s
depends_<architecture>
array?
Sorry, read your post too quickly…
1 Like
i had running i3 install on the odroid and simply install the default EndeavourOS packages list on top … changed to sddm and create a new user to not mess with the configs … it was able to run wayland session without issues… and also i do not explicitly added the two packages these was installed… could be simply arch arm had some dependency missing and it is resolved with an update… i can do some test installs to check…
I am fairly confident the two additional libs fixed the problem,
Pudge
yea but seems they got installed as dependencies now …
So as of right now, when any platform is installed libmd and libbsd gets installed as part of the base install. Then if any DE needs them they are there.
Pudge
Really not clear why it is needed to run wayland session…
$ pactree -r libmd
libmd
└─libbsd
├─libwbclient
│ ├─cifs-utils
│ │ └─smbclient
│ │ ├─gvfs-smb
│ │ └─kio-extras
│ │ ├─dolphin
│ │ │ └─dolphin-plugins
│ │ └─plasma-workspace
│ │ ├─eos-plasma-sddm-config
│ │ ├─eos-settings-plasma
│ │ ├─kdeplasma-addons
│ │ ├─plasma-desktop
│ │ ├─plasma-nm
│ │ ├─plasma-pa
│ │ ├─powerdevil
│ │ │ └─plasma-desktop
│ │ └─xdg-desktop-portal-kde
│ │ └─plasma-integration
│ │ └─plasma-workspace
│ └─smbclient
├─smbclient
└─talloc
├─cifs-utils
├─ldb
│ └─smbclient
├─smbclient
└─tevent
├─ldb
└─smbclient
So samba and dolphin needs them…
yea missed the -r 
still unclear why it let the wayland session fail