All applied upstream.

phog Debian release 0.1.4-1

Arnaud Ferraris authored 1 year ago and Arnaud Ferraris committed 1 year ago

This was needed for greetd v0.8, but we now have v0.9 in Debian, so
let's drop that one.

Arnaud Ferraris authored 1 year ago and Arnaud Ferraris committed 1 year ago

Update to upstream version '0.1.4'
with Debian dir e5dcfaf95e98229eea6be45b4d3e0b77d032bff7

Add forwarded/greetd-Handle-unset-last-session-gracefully.patch: <REASON>
Add forwarded/greetd-Ignore-entries-without-DesktopNames.patch: <REASON>
Add forwarded/greetd-Don-t-crash-on-NULL-socket.patch: <REASON>

Rather check it early

If a user was never logged in there's no last session so just
assume the first one listed.

Otherwise there's just

```
(phog:21054): GLib-CRITICAL **: 13:00:29.716: g_str_has_suffix: assertion 'str != NULL' failed
```

with little way for the user to figure out what file caused the problem.

The locked case is the interesting part for testing the greeter ;)

According to the greetd docs, this is the right path.

See https://man.sr.ht/~kennylevinsen/greetd/#setting-up-greetd

Closes: #1033282

`greetd` now ships those, so we should get rid of them. Add a versioned
dependency on `greetd` to ensure we have the proper configs.

Closes: #1032914

This allows to use phosh-osk-stub instead of squeekboard

Arnaud Ferraris authored 2 years ago and Arnaud Ferraris committed 2 years ago

Update to upstream version '0.1.3'
with Debian dir 53553203ab8493f0e3ded97a364c170df6c0e81d

Arnaud Ferraris authored 2 years ago and Arnaud Ferraris committed 2 years ago

It's extracted from a Desktop Entry file, in which the various values
must be separated with semicolons. However, the env var should use a
colon as the delimiter.

Update to upstream version '0.1.2'
with Debian dir 8bf1d0dd91d1b9f033d9da379f1ea6d1c35f041e

On some occasions, the user authenticates properly, but the session
startup fails for some reason (or there's a communication error leading
us to believe something went wrong). Both cases were handled the same
way, giving the user identical feedback in both cases, leading to
legitimate confusion.

Let's decouple authentication and session startup so we can handle both
cases appropriately.

Users are confused that they can swipe up on the default page but are
unable to login unless they actually click on the user button. Let's fix
this bad UX by creating the greetd session only by the time we changed
pages, and using the first username in the list (selected by default) as
the default value.

`phog` needs to store data into a folder named `/var/lib/phog`. As this
folder is not under the user's home directory, we must create it and
ensure the user `phog` will run as (`_greetd` here) has R/W permissions
on it.