Trying to run wayland again, but...

[RayDude]

Wayland has never worked for me. There are always a few gotchas that get me.

Let's deal with the media server's issue(s) first.

On my media server, I login as mythtv which is an old habit from the 2000s. I have no desire to change it now, but might have to if I can't figure this out.

Right now if I login with Plasma (X) it works great!

But if I login with Plasma (Wayland) it runs mythfrontend as the only application with no plasma, not GUI, nothing. And I can't figure out why. I don't know where that configuration file is.

I keep googling wayland startup files and I can't find anything ...

Anyone know how wayland works?

[Zucca]

Right now if I login

"login" how?
Which command did you run, if any? Do you have any logs?

If you use some login manager, then there should exist some .desktop files inside a session directory (/usr/share/wayland-sessions), from where you can see what command is being run.
By editing the command you can perhaps redirect all of its output to a log file.
Before that, I'd suspect that since it's plasma session I'd first assume it produces some sort of log file already.

[rab0171610]

Does the mythtv even work in Wayland yet? There seems to be conflicting information out there.
The Arch Linux wiki for mythtv doesn't mention Wayland or Xwayland at all. It only says that you must have a working X installation.
The only things that I can think of . . .

Does running the mythtv frontend with the '--platform xcb' option work while using Wayland? 'xcb' would force X11. I don't know if that works while using Wayland or not. It may be that you need to try setting it to 'wayland'.
I don't know what command you are using to launch mythfrontend. But let's say:

Code: Select all

mythfrontend --platform xcb

or

Code: Select all

mythfrontend --platform wayland

Are those valid options and do either of those work for you in Wayland? I don't know as I don't use mythtv. I have no way of experimenting with it and would need for you to try it and let me know.

Does trying to force Xwayland work with mythtv? I don't know if mythtv is written in QT or GTK. I assume from the xcb in the option above that it might be QT.
If QT:

Code: Select all

QT_QPA_PLATFORM=xcb  mythfrontend

or you could experiment and explicitly set it to wayland:

Code: Select all

QT_QPA_PLATFORM=wayland  mythfrontend

Monitor the results.

If by some odd chance it is GTK:

Code: Select all

GDK_BACKEND=x11 mythfrontend

The only other thing I would suggest is asking over at the mythtv forums if other mythtv users are able to get mythtv working in Wayland and if so, how?

[RayDude]

Hi Zucca,

Right now if I login

"login" how?
Which command did you run, if any? Do you have any logs?

If you use some login manager, then there should exist some .desktop files inside a session directory (/usr/share/wayland-sessions), from where you can see what command is being run.
By editing the command you can perhaps redirect all of its output to a log file.
Before that, I'd suspect that since it's plasma session I'd first assume it produces some sort of log file already.

Part of the problem is: I can't find any logs. For X /usr/log/Xorg.0.log exists and I've parsed a thousand times in the last two decades.

Plasma is not starting. It looks like XWayland is handling mythfrontend, but I have no idea how mythfrontend is running. I don't want it to run. I can't use it right now because mythfrontend is not even compatible with the latest version of X, let alone Wayland. I used Kodi for a while, but alas it has problems with my hard drive raid array and crashes during playback sometimes. So I end up looking up the file name for the recording I want to watch and use mpv to watch it. No timeout issues there.

I didn't communicate my problem well enough. Wayland is starting a single application, mythfrontend. I suspect that's because I have a user named mythtv which gentoo assumes is for running mythtv applications and some configuration file got changed. But I have no idea how wayland determines what it does on startup.

I found /usr/share/wayland-sessions/plasma.desktop and it has these first few lines:

[Desktop Entry]
Exec=/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland
TryExec=/usr/bin/startplasma-wayland
DesktopNames=KDE
Name=Plasma (Wayland)

I don't think startplasma-wayland has been changed, but what ever it uses for config files may be the culprit. I just need to know what it does to figure out why it's running mythfrontend.

Thanks for taking the time to reply, I really appreciate it.

[RayDude]

Does the mythtv even work in Wayland yet? There seems to be conflicting information out there.
The Arch Linux wiki for mythtv doesn't mention Wayland or Xwayland at all. It only says that you must have a working X installation.
The only things that I can think of . . .

Does running the mythtv frontend with the '--platform xcb' option work while using Wayland? 'xcb' would force X11. I don't know if that works while using Wayland or not. It may be that you need to try setting it to 'wayland'.
I don't know what command you are using to launch mythfrontend. But let's say:

Code: Select all

mythfrontend --platform xcb

or

Code: Select all

mythfrontend --platform wayland

Are those valid options and do either of those work for you in Wayland? I don't know as I don't use mythtv. I have no way of experimenting with it and would need for you to try it and let me know.

Does trying to force Xwayland work with mythtv? I don't know if mythtv is written in QT or GTK. I assume from the xcb in the option above that it might be QT.
If QT:

Code: Select all

QT_QPA_PLATFORM=xcb  mythfrontend

or you could experiment and explicitly set it to wayland:

Code: Select all

QT_QPA_PLATFORM=wayland  mythfrontend

Monitor the results.

If by some odd chance it is GTK:

Code: Select all

GDK_BACKEND=x11 mythfrontend

The only other thing I would suggest is asking over at the mythtv forums if other mythtv users are able to get mythtv working in Wayland and if so, how?

rab0171610,

Thanks for taking the time to respond to my post. I really appreciate it.

You are correct. mythfrontend is completely borked for both X and Wayland at the moment. It's ancient software, but the backend is still the best there is for recording over the air television.

I can run mythfrontend with --platform xcb, but it shows up as a 1080p window in the lower left corner of my 4K display. It's not useful. So I don't run it. I've been using mpv to watch recordings.

I don't actually care about mythfrontend. I want wayland to run plasma and let me see how well it works. The last time I tried it was not stable enough.

My problem is: I don't know where the configuration files are for wayland / plasma wayland and I don't know how to tell what it's doing or why it's doing it that way. I'm sure it's a text file, it always is, but I can't find it. I even tried searching the whole of /etc looking for mythfrontend, but didn't find it...

If anyone knows wayland's / plasma_wayland's guts, I'd appreciate a nudge in the right direction.

[Anon-E-moose]

Try searching under your ~/.config dir for mythfrontend or possibly under ~/.local/*

[rab0171610]

Why don't you consider trying to login using the Wayland session. Give it a test run. Let us know when you have an issue and we can go from there. Provide specifics so we can help you.
Do you use systemd or openrc?
I use systemd so most of the logging I would need to read would be in the systemd journal.
I don't know how that works with openrc.
SDDM keeps a limited log when users log in that will probably not be of much help:
~ /.local/share/sddm/wayland-session.log
Usually that is only insightful if you cannot log into the Wayland session at all or have a black screen on login.
Aside from mythtv, if you log in to the wayland session, what other problems are you experiencing? Please provide specifics.

[RayDude]

Why don't you consider trying to login using the Wayland session. Give it a test run. Let us know when you have an issue and we can go from there. Provide specifics so we can help you.
Do you use systemd or openrc?
I use systemd so most of the logging I would need to read would be in the systemd journal.
I don't know how that works with openrc.
SDDM keeps a limited log when users log in that will probably not be of much help:
~ /.local/share/sddm/wayland-session.log
Usually that is only insightful if you cannot log into the Wayland session at all or have a black screen on login.
Aside from mythtv, if you log in to the wayland session, what other problems are you experiencing? Please provide specifics.

I use openRC.

Wayland session? I think that's what I'm doing from sddm, I'm choosing Plasma (Wayland) and that's when mythfrontend runs and nothing else. When I exist mythfrontend, it takes me back to sddm login.

Thanks for the wayland-sesson.log location I think that helps. It looks like there's a problem with wayland itself:

Code: Select all

X.Org X Server 1.21.1.20
X Protocol Version 11, Revision 0
Current Operating System: Linux server 6.18.6-gentoo #1 SMP PREEMPT_DYNAMIC Fri Jan 23 21:35:49 PST 2026 x86_64
Kernel command line: BOOT_IMAGE=/vmlinuz-6.18.6-gentoo root=PARTUUID=8e713e72-02a1-9b49-9b4c-c295620f36e0 ro initcall_blacklist=acpi_cpufreq_init amd_iommu=on sysrq_always_enabled=1 bdl_pos_adj=8,8 loglevel=8
 
Current version of pixman: 0.46.4
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
        (++) from command line, (!!) notice, (II) informational,
        (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/home/mythtv/.local/share/xorg/Xorg.1.log", Time: Sat Jan 24 16:01:42 2026
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86OK
> Warning:          Could not resolve keysym XF86GoTo
> Warning:          Could not resolve keysym XF86VendorLogo
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectProgramGuide
> Warning:          Could not resolve keysym XF86MediaSelectHome
> Warning:          Could not resolve keysym XF86MediaLanguageMenu
> Warning:          Could not resolve keysym XF86MediaTitleMenu
> Warning:          Could not resolve keysym XF86AudioChannelMode
> Warning:          Could not resolve keysym XF86MediaSelectPC
> Warning:          Could not resolve keysym XF86MediaSelectTV
> Warning:          Could not resolve keysym XF86MediaSelectCable
> Warning:          Could not resolve keysym XF86MediaSelectVCR
> Warning:          Could not resolve keysym XF86MediaSelectVCRPlus
> Warning:          Could not resolve keysym XF86MediaSelectSatellite
> Warning:          Could not resolve keysym XF86MediaSelectCD
> Warning:          Could not resolve keysym XF86MediaSelectTape
> Warning:          Could not resolve keysym XF86MediaSelectRadio
> Warning:          Could not resolve keysym XF86MediaSelectTuner
> Warning:          Could not resolve keysym XF86MediaPlayer
> Warning:          Could not resolve keysym XF86MediaSelectTeletext
> Warning:          Could not resolve keysym XF86MediaSelectAuxiliary
> Warning:          Could not resolve keysym XF86MediaPlaySlow
> Warning:          Could not resolve keysym XF86NumberEntryMode
> Warning:          Could not resolve keysym XF86RefreshRateToggle
> Warning:          Could not resolve keysym XF86Accessibility
> Warning:          Could not resolve keysym XF86DoNotDisturb
Errors from xkbcomp are not fatal to the X server
Failed to create wl_display (No such file or directory)
qt.qpa.plugin: Could not load the Qt platform plugin "wayland" in "" even though it was found.
xinit: connection to X server lost

waiting for X server to shut down XIO:  fatal IO error 4 (Interrupted system call) on X server ":1"
      after 498 requests (498 known processed) with 0 events remaining.
(II) Server terminated successfully (0). Closing log file.

TERM environment variable not set.

Looks like qtwayland is not working... I'll try re-emerging it.

[RayDude]

Try searching under your ~/.config dir for mythfrontend or possibly under ~/.local/*

I grepped for 'mythfrontend' in all of .config, but that never actually completed as I think there are recursive symlinks or something.

I'm tempted to blow away .config and see if that helps, but ... I'll have to setup everything all over again and I did that just a few months ago the last time I attempted to run Wayland.

[RayDude]

I'm having problems with emerge... Many files are not updated properly. Check this out:

Code: Select all

emerge -p qtwayland

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 9.18 s (backtrack: 0/20).

[ebuild  NS    ] dev-qt/qtwayland-6.10.1 [5.15.18] USE="qml%* -custom-cflags% -gnome%" 

Yet, when I attempt to emerge @world, I get this:

Code: Select all

emerge -puUD --backtrack=100 @world

These are the packages that would be merged, in order:

Calculating dependencies... done!
Dependency resolution took 56.71 s (backtrack: 4/100).


WARNING: One or more updates/rebuilds have been skipped due to a dependency conflict:

dev-python/msgpack:0

  (dev-python/msgpack-1.1.2:0/0::gentoo, ebuild scheduled for merge) USE="native-extensions -debug -test" ABI_X86="(64)" PYTHON_TARGETS="python3_12 python3_13 (-pypy3_11) -python3_11 -python3_14" conflicts with
    <dev-python/msgpack-1.1.2[python_targets_python3_12(-),python_targets_python3_13(-)] required by (app-backup/borgbackup-1.4.1-r1:0/0::gentoo, installed) USE="-debug -test" ABI_X86="(64)" PYTHON_TARGETS="python3_12 python3_13 -python3_11"
    ^                   ^^^^^                                                           


!!! The following update has been skipped due to unsatisfied dependencies:

www-client/firefox:rapid

  selected: (www-client/firefox-146.0.1:rapid/rapid::gentoo, installed)
  skipped: (www-client/firefox-147.0.1:rapid/rapid::gentoo, ebuild scheduled for merge) (see unsatisfied dependency below)

!!! All ebuilds that could satisfy ">=dev-libs/icu-78.1:=" have been masked.
!!! One of the following masked packages is required to complete your request:
- dev-libs/icu-78.2::gentoo (masked by: ~amd64 keyword)
- dev-libs/icu-78.1::gentoo (masked by: ~amd64 keyword)

(dependency required by "www-client/firefox-147.0.1::gentoo[system-icu]" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.



!!! The following update has been skipped due to unsatisfied dependencies:

sci-ml/caffe2:0

  selected: (sci-ml/caffe2-2.9.1-r1:0/0::gentoo, installed)
  skipped: (sci-ml/caffe2-2.9.1-r3:0/0::gentoo, ebuild scheduled for merge) (see unsatisfied dependency below)

!!! All ebuilds that could satisfy ">=sci-libs/hipBLASLt-6.3:=" have been masked.
!!! One of the following masked packages is required to complete your request:
- sci-libs/hipBLASLt-7.1.0-r2::gentoo (masked by: ~amd64 keyword)
- sci-libs/hipBLASLt-7.0.2-r2::gentoo (masked by: ~amd64 keyword)
- sci-libs/hipBLASLt-6.4.3::gentoo (masked by: ~amd64 keyword)
- sci-libs/hipBLASLt-6.3.3::gentoo (masked by: ~amd64 keyword)

(dependency required by "sci-ml/caffe2-2.9.1-r3::gentoo[rocm]" [ebuild])
For more information, see the MASKED PACKAGES section in the emerge
man page or refer to the Gentoo Handbook.

I'll try unmasking and see if it will run. The funny thing is I updated yesterday, had some trouble, but then it updated okay (over fifty packages, at least the linux kernel emerged) but I guess there are still issues.

It's not updating packages that need updated. That's why none of this works.

[Anon-E-moose]

Try searching under your ~/.config dir for mythfrontend or possibly under ~/.local/*

I grepped for 'mythfrontend' in all of .config, but that never actually completed as I think there are recursive symlinks or something.

I'm tempted to blow away .config and see if that helps, but ... I'll have to setup everything all over again and I did that just a few months ago the last time I attempted to run Wayland.

Basically you should look for anything with kde or plasma in it's name and then check those files.

You can temporarily make a tarball of .config, then delete the .config dir and see what happens.
Check to see if any files are left in the new .config subdirs and note them, then delete that .config and restore from the old config tarball.

Edit to add: Or instead of tar just rename .config to .config.save (or something) then make a new empty .config to test

[Havin_it]

Hi RayDude,

I am not sure why you are seeing what you are, but I do think it's possible that your running as the 'mythtv' user may play a part in the problems. User and group accounts that are intended for dedicated use by a particular app, known as system accounts, are subject to some loose conventions that govern how they are treated by the system and other apps. As such, most of them in modern Gentoo systems are created by dedicated ebuilds that are dependencies of whatever app: in your case, acct-user/mythtv and acct-group/mythtv. (It has only been done this way for the last few years though, and if your current box is older, I don't know how this transition process worked or whether it had a role to play in what's happening. AFAIK that was just splitting-off what the apps' ebuilds used to do for themselves, so it's probably not important ... probably)

System accounts normally have numeric IDs in the 1-999 range (1000 and above are for human users) and typically have no password, home directory, default shell and so on. The numbering convention is used to screen them out from things like display managers' user selection boxes. Normally you wouldn't even see 'mythtv' as a login option in SDDM or whatever. In its default state I wouldn't have thought you could even login to a terminal with it.

I am curious therefore about the history and current condition of this account. Did you create it yourself before even installing mythtv? If not, did you modify it manually?

Please can you show us the output of these commands:

Code: Select all

grep mythtv /etc/passwd
grep mythtv /etc/group
emerge -pv --nodeps mythtv

And if I can just get something straight: When you login to the Plasma (X11) session, does mythfrontend also autostart there?

Meanwhile, other places you could look for autostart config include /etc/xdg/autostart/, ~/.bash_profile, ~/.bashrc, ~/.xinitrc.

[RayDude]

~/.xinitrc was unique, owned by root and even after I changed ownership did not change.

rm worked though. I was able to login with wayland.

However, I have problems.

I use two output displays running replicas. I do this because this enabled me to send AC3 through HDMI to my stereo receiver (that can only do 60 Hz 4K) and DisplayPort to my TV @120Hz 4K.

This enables me to do dolby surround with my stereo and run 120Hz 4K to my TV.

I can't get dolby to my TV because AMD doesn't support AC3 out display port.

This causes a big problem. Once in a while the screen saver doesn't turn on and the display will burn in. It's OLED and my old TV was killed by this. X does not have this problem. The screensaver always works in X.

The other medium problem is glitching on the screen during youtube playback (stuttering is also a problem, but that was a problem with X as well).

There is also glitching in the 3D game I play.

Not blanking the screen is a show stopper for me because try as I might, I forget to turn off the TV when I walk away from it and when I come back the image is fixed, instead of black. I love the fact that I can do HDR... I really want to use Wayland.

On my laptop I also switched to wayland. Again, I have an odd configuration. Two DisplayPort monitors on a single USBC connector. In this case, I have the screens set to power off, but while one screen works, the other screen gets stuck in a loop: BLACK --> announce loss of signal --> switch off --> BLACK --> a few minutes go by --> WAKE UP! ->> Start the whole process again. I sleep in this room and the monitor turning on and off all night is an absolute no go. I turned off the power down and turn off both monitors at night. That's my work around, but it's not ideal.

I doubt anyone knows anything because these are highly unique circumstances, but I just thought I'd update everyone. If you have ideas though, I'm all ears.

[Havin_it]

There's more symptoms here than I want to even try diagnosing especially as it goes into hardware I've no experience with, so I'll sideline myself but to suggest one thing:

I strongly suggest you create a new user account, either in KDE System Settings or using `adduser` in the console, and leave the mythtv system account to be used only as its packager intends. If you are not using mythfrontend any more anyway, then I don't see that you lose anything from this. Any important configs/documents can be transferred to your new home directory as needed, though initially I would recommend just starting with the homedir completely bare in order to test how things are working.

The issues you're having may have other causes, but you have been using an account that is not meant to be used interactively by a human user (except, as far as I can tell from the files in portage, to run mythfrontend standalone without any DE/WM). Running a desktop under such an account may cause all kinds of unexpected issues because it breaks the common assumptions that this or that component may make about the properties of a "live" user account. It's worth at least trying to take that factor out of the equation.

[RayDude]

Thanks Havin_it.

When the gentoo mythtv maintainer attempted to take over the account a long time ago, I immediately filed a bug and told them I'd been using /home/mythtv for a decade before and they fixed their scripts to check to see if the account exists and to not touch it. I had to rebuild the mythtv home directory, but I got everything back.

Interesting. I just checked and the mythtv maintainer owns the file at fault:

Code: Select all

server ~ # equery b /home/mythtv/.xinitrc
 * Searching for /home/mythtv/.xinitrc ... 
media-tv/mythtv-35.0_p20250723 (/home/mythtv/.xinitrc)

I guess they forgot my bug complaint from years ago.

I think you are right. I need to create a new user. It's going to be a pain in the ass to redo the configuration, but I really have no choice.

Thanks for making me dig deeper. The fact that mythtv owns that file means it's going to come back. I'll change users.

[Hu]

As I read the ebuild, that file is only installed if you USE=autostart. The underlying files/xinitrc-r1 has been untouched since Gentoo moved to git in 2015. Its contents look to me like it would disable screen blanking from the X server, though an independent screensaver that you start could still override that. You could also choose to invoke the X server in a way that ~mythtv/.xinitrc is not read.

Code: Select all

       To  determine  the  client  to run, startx first checks the environment
       variable XINITRC for a filename. If that variable is unset, or does not
       contain a filename, it looks for a file called .xinitrc in  the  user’s
       home  directory.

I think you have several options that are easier than abandoning this user account. However, this is just what I was able to quickly discover. I haven't tested any of it.

I'd be a bit surprised if your Wayland compositor even noticed an xinitrc file though.

[Anon-E-moose]

Wayland doesn't care about the xinitrc file. Not sure about xwayland, but I don't think it uses it either, when I was running xwayland, it didn't care about it.
But since xinitrc is an executable script, you could certainly put "exit" on a line by itself at the beginning of the file, then it won't do anything.

[RayDude]

All I can say is that sddm or some other component was reading ~/.xinitrc and not starting plasma because of it, once I removed it, it ran plasma but with issues.

I created a new user and set up the account. It took a while to get everything back, but I got it.

It is behaving much better. The screen saver seems to be reliable now and I'm able to use high refresh and HDR. It's like a whole new machine, for free!

Thanks so much for your help!

[Anon-E-moose]

All I can say is that sddm or some other component was reading ~/.xinitrc and not starting plasma because of it, once I removed it, it ran plasma but with issues.

I created a new user and set up the account. It took a while to get everything back, but I got it.

It is behaving much better. The screen saver seems to be reliable now and I'm able to use high refresh and HDR. It's like a whole new machine, for free!

Thanks so much for your help!

So the problem was sddm, did you tell it to start wayland in it's configuration file?

[Havin_it]

I noticed that the ebuild also makes the mythtv user's ~/.bash_profile like this:

Code: Select all

case "`tty`" in
    *tty8) startx; logout ;;
esac

...which is supposed to launch mythfrontend via the user's .xinitrc.

I don't understand enough about the process to draw a clear line between that and what actually happened with the Wayland session, but with this being a rather vintage ebuild perhaps it does not consider the Wayland context at all :shrugs:

[Ralphred]

I don't understand enough about the process

In ye olde times, we used to have mythtv autologin on tty8 with

Code: Select all

c8:45:respawn:/sbin/mingetty --autologin mythtv tty8

which in turn invoked startx for the bashrc edit you noticed, which again in turn invoked ~/.xinitrc.
I still do this to an extent, because some kodi plugins are "dodgy" and it lets you lock down the mythtv user more than you would "your non-root user" that you use to do sysadmin type stuff. If you are set-up for it, it also allows you a greeter, like sddm, sitting idle on tty7 for "sysadmin type stuff" should you want to use a GUI/desktop.

Considering the number of times I've had to stop etc-update/dispatch-conf overwriting my inittab I'd guess that RayDude's is "clean", but the bashrc snippet is/was still there. Which tty sddm uses has been "devoid of config file control" for some time (it might have been fixed, but I have a working workaround so CBA to test it TBH) it's feasible that wayland was being started on tty8 and sucking in this now redundant xinitrc via that bashrc snippet, but I don't know enough about wayland to make a definitive statement.

[Havin_it]

I've only seen Plasma-wayland session run on tty7 but who knows. If it does somehow run tty8, then I figure the .bash_profile gets exec'd and startx gets in front of the wayland session launch.

[MaDDeePee]

All I can say is that sddm or some other component was reading ~/.xinitrc and not starting plasma because of it, once I removed it, it ran plasma but with issues.

I created a new user and set up the account. It took a while to get everything back, but I got it.

It is behaving much better. The screen saver seems to be reliable now and I'm able to use high refresh and HDR. It's like a whole new machine, for free!

Thanks so much for your help!

So the problem was sddm, did you tell it to start wayland in it's configuration file?

i am on sddm as well and cant login to wayland either.
There is just is no option to choose wayland in the login screen.
I think i configured sddm right to be able to use it but it seems i am missing smth.
To bad that there isnt any one by one guide for wayland with sddm

i gave up long time ago on this, lol

[Anon-E-moose]

man sddm.conf

[MaDDeePee]

man sddm.conf

nice, thanks!
i didn't know of man pages as a whole thing...

srsly, i tried everything in /etc/sdd.conf.d/ and its settings and i even got custom scripts in /usr/share/sddm/scripts for kde startup und shutdown.

I am either missing a package or smth general is missing to bring wayland up with sddm. Its just not yet barrier free as it should be to push things forward. I dont know where to start at, without kicking sddm out of my system.