Comment by ~rhysperry111 on ~kennylevinsen/greetd
Just bumping this as (as I seem to do every few months) I've started looking into it again. This time I moved from my odd sway-as-a-service config to using greetd to hopefully move to a more standard way of doing things.
As far as I can tell, the black screen in this case is simply the time it takes for greetd to run and sway to start presenting to the screen (as plymouth quits as soon as greetd starts).
Not sure if it helps, but if you can work out a way to get greetd/sway running in the background, then running
plymouth quit
afterwards, this should work pretty nicely. It probably won't be smooth (I believe GDM has worked out a fade) but it's better than nothing.
Ticket created by ~rhysperry111 on ~scoopta/wofi
When running wofi (v1.2.4) on sway (1.5.1) in dmenu mode, it hangs upon startup. The issue is intermittent (maybe happening 1/4 to 1/8 of the time), and the wofi window gets to the point of showing and grabbing input, but then hangs for ~10-20 seconds, not allowing any other applications to receive input.
When this happens, I can usually see the first few items in the menu, but it appears to hang while trying to get through them all.
Comment by ~rhysperry111 on ~scoopta/wofi
I can confirm that this does work with Intel+Nouveau
Comment by ~rhysperry111 on ~scoopta/wofi
I would be able to do testing. My current setup is Intel Graphics + NVidia 1050Ti
Ticket created by ~rhysperry111 on ~scoopta/wofi
In the recent update to the freedesktop specification they added the key
PrefersNonDefaultGPU
which is used to select which GPU to start an application. I am not sure how this would be implemented, but do you have any plans to do so?