Requests for current-next (15.0-->15.1)

Jeebizz · 07-17-2026, 09:32 AM

Since KDE and even XFCE support wayland (XFCE being rather experimental still), can xwmconfig be updated to have wayland sessions added when choosing the DE/WM that support it?

LuckyCyborg · 07-17-2026, 09:48 AM

Quote:

Originally Posted by Jeebizz

Since KDE and even XFCE support wayland (XFCE being rather experimental still), can xwmconfig be updated to have wayland added when choosing the DE/WM ?

The Wayland sessions does not uses /etc/X11/xinit/xinitrc.* scripts and neither a ~/.xsession script, because they are specific to the X11 sessions. So, how will handle xwmconfig the Wayland sessions?

In practice, all you have for the Wayland sessions are some .desktop files located in the folder /usr/share/wayland-sessions (making them available in SDDM and XDM) and the console scripts like startkwayland or startlxqtwayland (cough! cough! self-advertising here). Maybe someone will invent also a startxfce4wayland script.

Regarding the startkwayland script, once Plasma6 become Wayland-only in October, for convenience may be renamed (or maybe symlinked) to /usr/bin/startkde, to have this command like in the old days. Anyway the Plasma6 uses startup programs named like startplasma-wayland and startplasma-x11 . This could be considered like a little request for -current.

LuckyCyborg · 07-17-2026, 09:51 AM

Quote:

Originally Posted by AlleyTrotter

COSMIC Desktop
Please

Great idea! I subscribe to this.

And while we are at it, maybe we will get also GNOME5, Pantheon and the new Cinnamon 6.8 (with full Wayland support). I will not say no!

BTW, in the attached screenshot is Pantheon. Looks like the XFCE4 if was written in GTK4 and with GNOME themes support.

Jeebizz · 07-17-2026, 10:05 AM

Quote:

Originally Posted by LuckyCyborg

The Wayland sessions does not uses /etc/X11/xinit/xinitrc.* scripts and neither a ~/.xsession script, because they are specific to the X11 sessions. So, how will handle xwmconfig the Wayland sessions?

In practice, all you have for the Wayland sessions are some .desktop files located in the folder /usr/share/wayland-sessions (making them available in SDDM and XDM) and the console scripts like startkwayland or startlxqtwayland (cough! cough! self-advertising here). Maybe someone will invent also a startxfce4wayland script.

Regarding the startkwayland script, once Plasma6 become Wayland-only in October, for convenience may be renamed (or maybe symlinked) to /usr/bin/startkde, to have this command like in the old days. Anyway the Plasma6 uses startup programs named like startplasma-wayland and startplasma-x11 . This could be considered like a little request for -current.

So how does one start a wayland session for xfce or say cinnamon ? startkwayland is for kde which I figured out on my own - but also what if one is booting to init 4 - I would imagine the rc.4 will have to be adjusted - login manager will be be x11 , but i choose to from there to start a wayland kde session - so now all these combinations also have to be accounted for i would think?

LuckyCyborg · 07-17-2026, 10:12 AM

Quote:

Originally Posted by Jeebizz

So how does one start a wayland session for xfce or say cinnamon ? startkwayland is for kde which I figured out on my own - but also what if one is booting to init 4 - I would imagine the rc.4 will have to be adjusted - login manager will be be x11 , but i choose to from there to start a wayland kde session - so now all these combinations also have to be accounted for i would think?

Good question! Right now we can start them only from runlevel 4 and i.e. SDDM - and it can start quite well either a X11 or Wayland session. Proved myself since many years. Also yourself you can try this in Slackware 15.0 because natively you have a Wayland session of Plasma5.

On the runlevel 4 there's no need for changes. Everything works already.

But, like I've said in the previous post, we need someone to write a startxfce4wayland script. Cinnamon also does not have console scripts too and we will need something if we want to start it from console.

For startxfce4wayland probably would be need something like below

/usr/bin/startxfce4wayland

Code:

#!/bin/sh

# Start XFCE4 Wayland session
/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startxfce4 --wayland

or maybe something like below?

/usr/bin/startxfce4wayland

Code:

#!/bin/sh

# Start XFCE4 Wayland session
dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 --wayland

I'll leave to you guys to consider.

willysr · 07-17-2026, 10:41 AM

For cinnamon it's just
cinnamon-session-cinnamon --wayland

LuckyCyborg · 07-17-2026, 10:50 AM

Quote:

Originally Posted by LuckyCyborg

or maybe something like below?

/usr/bin/startxfce4wayland

Code:

#!/bin/sh

# Start XFCE4 Wayland session
dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 --wayland

I've just tested this one practically and indeed it works. Now posting from a Wayland session of XFCE4, started from the Linux console.

Quote:

Originally Posted by willysr

For cinnamon it's just
cinnamon-session-cinnamon --wayland

Thanks! Hence, we will need also a script with the contents below.

Code:

#!/bin/sh

# Start Cinnamon Wayland session
dbus-launch --sh-syntax --exit-with-session /usr/bin/cinnamon-session-cinnamon --wayland

Jeebizz · 07-17-2026, 10:53 AM

Quote:

Originally Posted by AlleyTrotter

COSMIC Desktop
Please

Quote:

Originally Posted by LuckyCyborg

Good question! Right now we can start them only from runlevel 4 and i.e. SDDM - and it can start quite well either a X11 or Wayland session. Proved myself since many years. Also yourself you can try this in Slackware 15.0 because natively you have a Wayland session of Plasma5.

On the runlevel 4 there's no need for changes. Everything works already.

But, like I've said in the previous post, we need someone to write a startxfce4wayland script. Cinnamon also does not have console scripts too and we will need something if we want to start it from console.

For startxfce4wayland probably would be need something like below

Code:

#!/bin/sh

# Start XFCE4 Wayland session
/usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startxfce4 --wayland

or maybe something like below?

Code:

#!/bin/sh

# Start XFCE4 Wayland session
dbus-launch --sh-syntax --exit-with-session /usr/bin/startxfce4 --wayland

I'll leave to you guys to consider.

Quote:

Originally Posted by willysr

For cinnamon it's just
cinnamon-session-cinnamon --wayland

Quote:

Originally Posted by LuckyCyborg

I've just tested this one practically and indeed it works. Now posting from a Wayland session of XFCE4, started from the Linux console.

Hence, we will need also a script with the contents below.

Code:

#!/bin/sh

# Start Cinnamon Wayland session
dbus-launch --sh-syntax --exit-with-session /usr/bin/cinnamon-session-cinnamon --wayland

I am curious about cosmic so I would also like it added - and since I brought up the issue of xwmconfig - since cosmic is wayland only - it is just start-cosmic per the arch wiki - but again I am sure Luckycyborg can adjust accordingly if initab 4 is being used, and so forth...

and cinnamon too.

gcosbug · 07-17-2026, 10:53 AM

I just use:

Code:

startxfce4 --wayland

and it works!
If you have issues maybe you need?

Code:

dbus-run-session -- startxfce4 --wayland

Jeebizz · 07-17-2026, 10:56 AM

Quote:

Originally Posted by gcosbug

I just use:

Code:

startxfce4 --wayland

and it works!
If you have issues maybe you need?

Code:

dbus-run-session -- startxfce4 --wayland

How would you condense that? I know that Luckycyborg stated wayland doesn't use a .xinitrc - but you could put that in a file and reference that? I don't feel like having to do dbus-run-session --startxfce4 --wayland all the time, isn't there an easier way?

onebuck · 07-17-2026, 10:57 AM

As members should notice that infractions are given for off topic discussions within this thread. Anything that is not a 'Request for -current' is off topic. If you wish too discuss off topic subject matter then open a new thread for that topic.

Please stay on topic.

bigbadaboum · 07-17-2026, 01:21 PM

Quote:

Originally Posted by volkerdi
eLILO is going to be removed. I know of no situations where eLILO can boot but GRUB cannot. On the other hand, there are a huge number of machines out there where GRUB works fine, but eLILO fails to boot. And nearly every new machine coming out falls into this category.

Worse, a large portion of the people suffering from this issue refuse to believe that the problem is eLILO.

I use GRUB (BIOS-legacy), but I'm keeping LILO because I can't add a kernel when LILO is missing (error message), so I'm eagerly awaiting the official retirement of LILO.

sombragris · 07-18-2026, 10:16 AM

This might already have been considered here. In that case, my apologies.

Yesterday I installed Slackware on a new laptop, in a dual-boot setting with Win 11.

What I saw is that the installer still offers the option to install ELILO and does not install GRUB at all.

I think that removing the option to install ELILO (maybe) and add the option to install GRUB (definitely)) would be very welcome.

glennmcc · 07-18-2026, 11:08 AM

Yes, please.
We need the initial installer to offer to setup GRUB

khronosschoty · 07-18-2026, 11:22 AM

I would suggest (by implication request) the installer should have a "all defaults" "mode" that doesn't offer anything when selected. Then it should have its normal mode that it has now.