Be pessimistic and assume failure when the pam handle did not get
cleanued up earlier.

Traces are still cut off

The files are even more imporatant then

We want to catch these early

Split Wayland registry code into separate class

Closes #26

See merge request Librem5/phosh!84

Split PhoshWayland out of PhoshShell where the former handles protocol
registration and the later all the surfaces and managers.

We can move PhoshShell into a separate file once we moved out the lock
screen handling to the lockscreen manager.

Closes: #26

Support org.gnome.Mutter.DisplayConfig.{Set,Get}CrtcGamma

Closes #13

See merge request Librem5/phosh!58

Only add outputs to the list of displays that are fully configured
(that received wl_output's done event). This prevents us to from
accessing half initialized monitors.

This allows us to listen for the done event.

This allows GNOME's redshift to work. Since wlroots gamma protocol
doesn't allow to read the gamma ramps fake empty ramps of the right
size. All users only use it to determin the gamma table's size.

Fixes #13

Use get_primary_monitor everywhere

Closes #20

See merge request Librem5/phosh!74

FIXME: check if we get the right widh/height after rotation

Closes: #20

Use valgrind in CI

See merge request Librem5/phosh!80

This will help us find leaks early

This allows us to archive the artifacts in CI

This will make is simple to integrate it into CI

Otherwise some of the call traces are cut off

Otherwise we can't determine the PID of the main process and
can't kill it properly during tests

Valgrind fixes

See merge request Librem5/phosh!81

panel: include gi18n.h for '_'

See merge request Librem5/phosh!79

Add smoketest

See merge request Librem5/phosh!78

This starts and stops phosh to make sure this still works. Future
additions will be screenshots, asan, valgrind, ...

We're using the CI packages of libhandy and wlroots for that.

Add Spanish translation

See merge request Librem5/phosh!77