Allow multiple UI packages to be installed

Currently multiple postmarketos-ui-* packages can't be installed at the same time because the 60-autologin.conf file conflicts. If this file is renamed to something else for every UI package they can at least co-exist. This would lead to less problems when trying to switch UI with the package manager and it would make it possible to select the UI on boot if there's a greeter that supports a mobile screen.

For example gdm can be installed on postmarketos and enabled, and then lightdm disabled. gdm works reasonably well on the pinephone (and probably crashes on most other postmarketOS devices) and can select the desktop to boot in to.

An example of GDM running on the pinephone: https://youtu.be/YTtDk6EsH7k?t=34

Related (kinda): #320 (closed)

By Dolphin von Chips on 2020-03-26T06:30:06

added discussion type::feature + 1 deleted label

and probably crashes on most other postmarketOS devices

Oh, I got kinda excited about it yesterday when you mentioned it, not so much now...

Ideally we have a DM which allows switching UI's, like GDM, but it should work on every device with working screen really. I've been meaning to look into using SDDM for it but haven't gotten the chance yet.

By Bart Ribbers on 2020-03-26T21:50:16

Well, for me GNOME was working on samsung-j1mini3g with X11 backend, so in theory GNOME can work on all the other devices that can run X11 DEs.

By Dolphin von Chips on 2020-03-26T21:50:16

if there's a greeter that supports a mobile screen.

We could make something with the webkit greeter (but it could probably be incredibly slow and it doesn't seem to be packaged in Alpine yet) or fork an existing one and attempt to modify it.

gdm works reasonably well on the pinephone (and probably crashes on most other postmarketOS devices)

On the 2 Samsung devices I tried it with, it worked, but it was painfully slow (especially the keyboard, which seems to need to be restarted once?)

By knuxify on 2020-03-29T17:18:12

We could make something with the webkit greeter (but it could probably be incredibly slow and it doesn't seem to be packaged in Alpine yet) or fork an existing one and attempt to modify it.

Ewww, let's not use the webkit greeter. This should be a simple task that some lightweight software can do, having a whole browser in there is the opposite.

@Raatty's custom mobile greeter is more lightweight, although still depending on python: !1017 (merged)

It's probably not so hard to add multiple UI selection to it.

By Oliver Smith on 2020-03-29T17:18:12

i planned to rewrite in rust after i was happy with functionallity lolz

By Raatty on 2020-03-29T21:07:03

no, not Rust please? C is not that hard

By Alexey Min on 2020-03-29T21:13:33

We could also say that C is not that safe. When starting a new project, there is almost never a good reason to use C if you can use Rust.

By Fabrice Desré on 2020-04-04T03:32:24

Rust has million problems with packaging currently

By Alexey Min on 2020-04-04T15:14:27

Maybe, but that's a different issue. Also didn't !845 (closed) help?

By Fabrice Desré on 2020-04-04T16:22:22

Rustwashing is off-topic on every forum on which it's raised. C is a suitable langauge for new projects and if the community does not wish to use Rust, I will thank you for holding your tongue.

By Drew DeVault on 2020-04-04T16:36:54

As much as C washing, yes. I haven't seen a community opinion here, just an individual one.

By Fabrice Desré on 2020-04-04T16:49:26

Have you ever heard of the C evangelism strike force? Give me a break. Quit this off-topic nonsense.

By Drew DeVault on 2020-04-04T16:50:30

You're the one driving this discussion off topic. Have a nice day!

By Fabrice Desré on 2020-04-04T17:04:54

Maybe !845 (closed) did help in some way, but #407 (closed) is still a thing.

(And now my offtopic opinion that I'm not qualified enough to say: there's no need to overcomplicate and use Rust. Considering that we are going to do, good old C (or good not so old C++ if we are going to write one in Qt) would fit our needs. And if you are suggesting us to use Rust because muh MeMoRy SaFeTy, well, feature just for feature is not always good and you really need to mess something up in your C/C++ code to get problems with memory.)

By Dolphin von Chips on 2020-04-04T17:29:49

mentioned in issue #566 (closed)

By Antoine Fontaine on 2020-05-01T10:31:00

mentioned in merge request !1238 (merged)

By Raatty on 2020-05-16T05:59:52

closed via merge request !1238 (merged)

By Bart Ribbers on 2020-05-25T08:41:58