Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Wayland phase 3 (Greeter) #440

Closed
6 tasks done
plfiorini opened this issue Jul 16, 2015 · 20 comments
Closed
6 tasks done

Wayland phase 3 (Greeter) #440

plfiorini opened this issue Jul 16, 2015 · 20 comments
Assignees
@plfiorini
Labels
feature

Comments

@plfiorini
Copy link
Member

plfiorini commented Jul 16, 2015 •
edited

Phase 1: #419
Phase 2: #426

  • Greeter: KeyboardBackend moved to its separate .cpp/.h files
  • Greeter: Wayland keyboard backend
  • Non X11 greeter requires Qt >= 5.5
  • Greeter: Make sure combo boxes do not create new windows
  • Greeter: Use QPA for the first iteration and in the next iteration use Green Island
  • Xorg user session
@plfiorini plfiorini self-assigned this Jul 16, 2015
@plfiorini plfiorini added this to the New 1.0 milestone Jul 16, 2015
@plfiorini plfiorini modified the milestones: 0.13, New 1.0 Sep 6, 2015
@plfiorini plfiorini mentioned this issue Sep 6, 2015
Closed
plfiorini added a commit that referenced this issue Sep 8, 2015
@plfiorini
Separate keyboard code into multiple files
4a90d4e 
We want to support multiple keyboard backends (Wayland and Xcb), but
in order to do this we first need to separate the code to make it
more manageable.

Issue: #440
@plfiorini plfiorini modified the milestones: 0.14, 0.13 Oct 19, 2015
@genodeftest
Copy link

As long as this issue is not closed, can you please clarify the short description of SDDM? It currently reads QML based X11 and Wayland display manager, but it should probably be more like QML based display manager for X11 and Wayland sessions

@plfiorini plfiorini modified the milestones: 0.15, 0.14 May 2, 2016
@plfiorini
Copy link
Member Author

Wait for #616

@plfiorini plfiorini modified the milestones: 0.16, 0.15 Apr 19, 2017
@woutermont
Copy link

Can I just ask if there is any progress on a wayland-backed greeter?

@plfiorini plfiorini removed this from the 0.16 milestone Nov 20, 2017
@sandersr
Copy link

What's the ETA on this issue? It seems it's been open for a very long time and it's almost done.

@cafehaine cafehaine mentioned this issue Mar 19, 2018
Closed
@ghost
Copy link

ghost commented Apr 21, 2018

I would like to request as well that we get a short update on the Wayland status. It seems like most of the tickets are addressed. I use Plasma-Wayland since a long time and SDDM is one of the last pieces on my systems without Wayland support. Can we expect a Wayland test build or what are the open points that must be addressed first?

@mispp
Copy link

mispp commented Jul 9, 2018

There wasn't any activity recently here, is this still planned or?

@majkrzak
Copy link

It seems that #673 and #616 just have to be merged

@sandy-8925
Copy link

So, I looked into #616 - that work uses the GreenIsland compositor. However, the GreenIsland compositor seems to be deprecated and doesn't work with newer Qt versions in it's present form.

I propose using wlroots instead - @plfiorini , @davidedmundson - do you guys think it's a good approach? I want to get sddm running on Wayland, so I'd like to take this up.

@davidedmundson
Copy link
Member

I don't think SDDM needs to "use" anything itself. From an SDDM POV we need to:

  1. not start X (depending on config)
  2. wrap sddm-greeter in a script that launches whatever
  3. detect if this has an issue and fallback to starting X and the greeter

@sandy-8925
Copy link

Right, but the greeter is just a normal QGuiApplication, and needs a Wayland compositor in order to display something - right?

@davidedmundson
Copy link
Member

Yes, by "launches whatever" I meant a compositor.

@majkrzak
Copy link

@plfiorini what's the current status? Are you alive?

@plfiorini
Copy link
Member Author

Let's see if I can continue working on it during Xmas vacations.

@ghost
Copy link

ghost commented Dec 17, 2018

I'm following this quite some time now and it would be great see some activities to get SDDM Wayland running! thanks

@kanyck
Copy link

kanyck commented Nov 16, 2019

Was there any progress on that?

@kanyck kanyck mentioned this issue Nov 16, 2019
Closed
@tpgxyz tpgxyz mentioned this issue Feb 11, 2020
Closed
@r3k2
Copy link

r3k2 commented Mar 22, 2020

Whats the progress on this?

@denisok denisok mentioned this issue Jun 1, 2020
Closed
2 tasks
@ghost
Copy link

ghost commented Oct 18, 2020

This issue seems abandoned. Will this be followed up eventually?

@sddm sddm deleted a comment from majkrzak Mar 13, 2021
aleixpol pushed a commit to aleixpol/sddm that referenced this issue Mar 19, 2021
@plfiorini @aleixpol
Wayland display server
565ba9c 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: sddm#440
@major-mayer
Copy link

Great to see some progress here ❤️
This lines up with the increased Wayland effort in this year for the rest of the KDE ecosystem.

aleixpol pushed a commit that referenced this issue Apr 20, 2021
@plfiorini @aleixpol
Wayland display server
34ecafa 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: #440
aleixpol pushed a commit that referenced this issue Apr 21, 2021
@plfiorini @aleixpol
Wayland display server
e9e5ca6 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: #440
@rooiratel rooiratel mentioned this issue May 18, 2021
Closed
plfiorini added a commit that referenced this issue Jun 8, 2021
@plfiorini
Wayland display server
fddaa65 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: #440
plfiorini added a commit that referenced this issue Jun 8, 2021
@plfiorini
Wayland display server
0b2e420 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: #440
peremen pushed a commit to peremen/sddm that referenced this issue Jun 30, 2022
@plfiorini @peremen
Wayland display server
7c16afd 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: sddm#440
@shmerl
Copy link

shmerl commented Aug 12, 2022 •
edited

Are there any plans to release a new version of sddm? It would be nice for distros to pick this feature of running sddm itself in Wayland mode.

@JJRcop
Copy link

JJRcop commented Aug 12, 2022

Are there any plans to release a new version of sddm?

There indeed appear to be plans! Take a look at the 0.20 milestone https://github.com/sddm/sddm/milestone/13

githubkusi pushed a commit to githubkusi/sddm that referenced this issue Jul 6, 2023
@plfiorini
Wayland display server
2e37c44 
Introduce a new display server option to run the greeter with.
In the future this will be the default display server.

This patch contains the most important parts to get the greeter running
on Wayland, but it's not possible to select a keyboard layout.

At the moment the Wayland socket is assumed to be "wayland-0" but in a
multi-seat configuration we would have more than one greeter running,
each with a diffent socket and the assumption won't work anymore.

In the future we will figure out how to do, after all at the moment this
is considered enough for most people.

Closes: sddm#440
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@plfiorini plfiorini

Labels
feature
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests