You are not logged in.
Pages: 1
In an effort to run a pure wayland system you can follow where I am at here:
https://bbs.archlinux.org/viewtopic.php?id=286901
I now want to set up a greeter for wayland and need some help.
What I have working on my system is plasma-wayland, sway, wayfire
What I want is to have a greeter menu that I can choose between which one i want to start with instead of using tty.
Right now at tty I login and then I use a script to launch startplasma-wayland.
I have installed greetd, tuigreet, wlgreet, gtkgreet
I have read all the wikis and I must have some mental block that I cant get through the understanding of how to do this.
I have this in my /etc/greetd/config.toml:
[terminal]
# The VT to run the greeter on. Can be "next", "current" or a number
# designating the VT.
vt = 1
# The default session, also known as the greeter.
[default_session]
# `agreety` is the bundled agetty/login-lookalike. You can replace `/bin/sh`
# with whatever you want started, such as `sway`.
#command = "agreety --cmd /bin/sh"
command = "tuigreet --cmd startplasma-wayland"
# The user to run the command as. The privileges this user must have depends
# on the greeter. A graphical greeter may for example require the user to be
# in the `video` group.
user = "greeter"What I want to do is after I boot into my system I am sitting at a greeter like sddm but not sddm that has the login and password window and I can choose which dm I want to go into : sway . plasma, wayfire
Thanks guys
another piece of info:
[demo@archlinux ~]$ systemctl get-default
multi-user.targetMore info:
[demo@archlinux ~]$ loginctl session-status
1 - demo (1000)
Since: Thu 2023-07-06 08:14:44 EDT; 1h 26min ago
Leader: 526 (login)
Seat: seat0; vc1
TTY: tty1
Service: login; type tty; class user
State: active
Unit: session-1.scope
├─526 "login -- demo"
├─556 -bash
├─573 -bash
└─574 startplasma-waylandLast edited by MAYBL8 (2023-07-06 17:42:08)
Offline
What I want to do is after I boot into my system I am sitting at a greeter like sddm but not sddm that has the login and password window and I can choose which dm I want to go into : sway . plasma, wayfire
Why not sddm? As far as I can see you use plasma, and sddm is the standard greeter for KDE plasma. You can configure it to run on Wayland; the Archwiki page on SDDM has instructions.
In any case for a graphical greeter you need to boot into graphical.target; multi-user.target isn't enough.
Offline
SDDM pulls in an xorg package and I want to avoid as much xorg as possible.
[demo@archlinux ~]$ sudo pacman -S sddm
resolving dependencies...
looking for conflicting packages...
Packages (2) xorg-xauth-1.1.2-1 sddm-0.20.0-1
Total Installed Size: 4.57 MiBOffline
In any case for a graphical greeter you need to boot into graphical.target; multi-user.target isn't enough.
That's not entirely true. That may be the case for a couple of the biggest / most common DMs, but there is no technical reason it must be so. One can set a given service to run for whichever target they like and it's common to configure auto-login to a tty and autostart of a graphical session in a shell profile all to run under multi-user.target.
Last edited by Trilby (2023-07-06 15:07:09)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
So do plasma-workspace and greetd-gtkgreet, even sway transitively pulls X11 libraries, and you likely need xwayland anyway at some point, because wayland support is far from ubiquitous yet… I am not sure what you're trying to achieve here. You're making your life harder than it needs to be, just to avoid a 60kb package?
But as said, if you'd like to use greetd you have to change your default target into "graphical.target", and enable "greetd.service". What's the actual problem?
Offline
... and you likely need xwayland anyway at some point, because wayland support is far from ubiquitous yet
Nonsense. I've been using wayland exclusively for years and have never had xwayland installed on any of my computers. (edit: okay, I have breifly installed it a few times to test specific code, but I've never kept it around for my own use).
And while I can't speak to the OPs motivation, committing to sticking with one set of tools creates incentive to learn about those tools as well as to expand on and improve them. I beleive wayland may not be as well developed as you would need in order to be satisfied with it ... and it never will be if everyone just keeps relying on the xwayland crutch. Xwayland was a necessary and useful crutch in the early days of wayland, but it needs to go away now and take along the misinformation it carries with it.
Last edited by Trilby (2023-07-06 15:25:56)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Guys thanks for weighing in on a philosophical discussion about wayland.
I appreciate all the different viewpoints.
So a far as I'm concerned with what I am doing. I have set up a partition on my laptop for using, learning and testing wayland.
As far as my greeter issue it sounds like my main problem is setting it to use a graphical.target.
I will reread how to set this from being a multi-user.target.
Hopefully my problem will be solved then.
I will post back if I have solved it or still have problems.
Thanks
Dan
Offline
The default target of a fresh installation is "graphical.target"; if you're booting into "multi-user.target" you must have changed the default target at some point, perhaps via systemctl set-default or with a kernel parameter. You'll need to undo this configuration; perhaps "systemctl set-default graphical.target" works already.
Alternatively you can also install greetd into "multi-user.target" with "systemctl add-wants multi-user.target greetd.target", but I'd not recommend that. This moves your configuration even farther away from the the defaults, so you need to keep even more things in mind when searching the internet for help, reading the Arch Wiki, or asking for help.
Offline
I am happy to report I have greetd working.
Changed the target to graphical.target
Enabled the greetd.service
Now I just need to configure plasma, sway, and wayfire.
Offline
Xwayland was a necessary and useful crutch in the early days of wayland, but it needs to go away now and take along the misinformation it carries with it.
If Tcl/Tk/tkinter applications would work under pure wayland, I could dump Xwayland, too.
Eenie meenie, chili beanie, the spirits are about to speak -- Bullwinkle J. Moose
It's a big club...and you ain't in it -- George Carlin
Registered Linux user #149839
perl -e 'print$i=pack(c5,(41*2),sqrt(7056),(unpack(c,H)-2),oct(115),10); '
Offline
I call xwayland a crutch as it is a bit of a double-edged sword. It allows for things like tk and freeglut applications to continue running under wayland, which is great. But it's ongoing presence has allowed for the tk and freeglut communities to not bother putting forth any effort in porting to wayland. There was a wl-shell port for freeglut made by one guy, but it was never updated to work with xdg-shell (wl-shell is deprecated and not supported by any major compositor). Wayland support has come up in the tk community a couple of times, but at least once the response was quite litterally "why should we even bother if xwayland will be around forevery anyways".
Xwayland carries costs (anyone who has looked at compositor code or considered implementing xwayland in a compositor will know this). There should be incentives to move away from it over time.
Last edited by Trilby (2023-07-07 01:34:26)
"UNIX is simple and coherent" - Dennis Ritchie; "GNU's Not Unix" - Richard Stallman
Offline
Pages: 1