You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While running some tests I started a second wayfire session under my regular id from a linux console/tty.
In that second session I try to launch the drawer via the usual key combo and nothing happens.
So I fire up a terminal and I see this message:
INFO[0000] Showing resident instance (PID 2200)
Now I have made nwg-drawer resident so that there is no delay when I invoke it in the course of my wayfire session and It looks like a side-effect of this approach is that I can no longer invoke in it in a second wayfire session.
Is this to be expected... or is it a case of my not doing it right?
Among my wayfire session 'autostart commands' I have:
nwg-drawer -r
As to my wayfire bindings I have:
<Ctrl> <Alt> KEY_Y nwg-drawer
Not really relevant but the reason I'm doing this is that I'm trying to hunt down the applications that are not 'native-wayland-enabled' and have disabled XWayland before launching the second session (and I'm too lazy to clone my setup to another id :)
The text was updated successfully, but these errors were encountered:
While running some tests I started a second wayfire session under my regular id from a linux console/tty.
In that second session I try to launch the drawer via the usual key combo and nothing happens.
So I fire up a terminal and I see this message:
INFO[0000] Showing resident instance (PID 2200)
Now I have made nwg-drawer resident so that there is no delay when I invoke it in the course of my wayfire session and It looks like a side-effect of this approach is that I can no longer invoke in it in a second wayfire session.
Is this to be expected... or is it a case of my not doing it right?
Among my wayfire session 'autostart commands' I have:
nwg-drawer -r
As to my wayfire bindings I have:
<Ctrl> <Alt> KEY_Y nwg-drawer
Not really relevant but the reason I'm doing this is that I'm trying to hunt down the applications that are not 'native-wayland-enabled' and have disabled XWayland before launching the second session (and I'm too lazy to clone my setup to another id :)
The text was updated successfully, but these errors were encountered: