Closing terminal kills wayfire

S

Styrsven

While attempting to configure wayfire I have discovered a problem I have never seen before.
If I open a terminal under wayfire and then closes it wayfire exits.
It doesn't matter if it is Foot or Alacritty, it is the same resolt.
Has anyone had the same issue, and does anyone know a fix?
 
Styrsven said:
While attempting to configure wayfire
Click to expand...
Does the issue also occur with a unedited /usr/local/share/examples/wayfire/wayfire.ini under ~/.config/wayfire?

I do not experience such a problem with the example .ini file. Version: wayfire-0.9.0_2

Try the debug logging option, something like wayfire -d -c .config/wayfire/wayfire.ini >&2 wayfire.log

If debugging doesn't show anything of relevance to the issue, when configuring, you may want to specify only one configuration at a time, and test.
 
Not sure about wayfire, and I know it's not "X" but under X, you can start a terminal emulator from your .xinitrc. That gives you a window with no control. But you can then start a Window Manager (like twm) from that window. Killing the window kills everything.
Not sure how you you are starting wayfire, but if it's part of a shell init, that may be the reason
 
I'll break protocol and actuall get involved in a wayland centric discussion, but know that I have nothing but disdain for wayland...However, the compositor and its related window manager NEED a client to keep running. When the last client exits then the compositor will exit, so you need to be careful about what order things are started in:

root is compositor -> window manager is its direct child -> then any number of clients...

Since wayfire doesn't seem to be a "window manager" in the traditional sense...when the clients exit, it will exit.

The more direct solution is of course, to make sure the compositor client is a wayland conformant window manager, and then run your terminal under that WM.
 
You must log in or register to reply here.
Back
Top