#sway — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #sway, aggregated by home.social.
-
I have released a small tool for Linux/Wayland to let you zoom the current screen and annotate it and have a few other features to make it easy when presenting. It's called shmooz and available on AUR and github https://github.com/chmouel/shmooz
-
I have released a small tool for Linux/Wayland to let you zoom the current screen and annotate it and have a few other features to make it easy when presenting. It's called shmooz and available on AUR and github https://github.com/chmouel/shmooz
-
I have released a small tool for Linux/Wayland to let you zoom the current screen and annotate it and have a few other features to make it easy when presenting. It's called shmooz and available on AUR and github https://github.com/chmouel/shmooz
-
I have released a small tool for Linux/Wayland to let you zoom the current screen and annotate it and have a few other features to make it easy when presenting. It's called shmooz and available on AUR and github https://github.com/chmouel/shmooz
-
I have released a small tool for Linux/Wayland to let you zoom the current screen and annotate it and have a few other features to make it easy when presenting. It's called shmooz and available on AUR and github https://github.com/chmouel/shmooz
-
Nouvelle release de #hyprland
https://hypr.land/news/update55/
et tout qui est à nouveau cassé, des adaptations de config à faire…C’est sympa mais un peu pénible ce manque de stabilité. Il faudrait peut être que je teste #sway à la place 🤔
-
Nouvelle release de #hyprland
https://hypr.land/news/update55/
et tout qui est à nouveau cassé, des adaptations de config à faire…C’est sympa mais un peu pénible ce manque de stabilité. Il faudrait peut être que je teste #sway à la place 🤔
-
Nouvelle release de #hyprland
https://hypr.land/news/update55/
et tout qui est à nouveau cassé, des adaptations de config à faire…C’est sympa mais un peu pénible ce manque de stabilité. Il faudrait peut être que je teste #sway à la place 🤔
-
Nouvelle release de #hyprland
https://hypr.land/news/update55/
et tout qui est à nouveau cassé, des adaptations de config à faire…C’est sympa mais un peu pénible ce manque de stabilité. Il faudrait peut être que je teste #sway à la place 🤔
-
Nouvelle release de #hyprland
https://hypr.land/news/update55/
et tout qui est à nouveau cassé, des adaptations de config à faire…C’est sympa mais un peu pénible ce manque de stabilité. Il faudrait peut être que je teste #sway à la place 🤔
-
Alors, on retourne tester Sway avec Endeavour OS! 🐧 💜
Mon experience pour les prochaines soirees sera de prendre les elements de sway et de les placer pour labwc afin d'avoir un systeme similaire mais sans utiliser des tuiles. Je garde Sway quand meme pour basculer en mode "tuiles" au besoin 🤓 .
L'image de droite est une image de reference car labwc tout nu tout nu, pas be bas, ca ressemble a ca!
Je rajoute un clavier francais aussi! 😉
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Solving the mystery of niri and swayidle—elogind
Based on the debug output from
swayidle, I started researching what the heckorg.freedesktop.login1.Managerwas doing. When usingsway, this was not used on my non-systemd system, andswayidleworks as expected.With
sway, the way it is working, from a casual user’s perspective:swayidleintercepts for an “idle state” message.swayidleruns the script that I have configured—swaylock-pluginlocks and the background is rotated continually.
Using
nirion my non-systemd system, there does seem to be this extra piece in the mix—logind. Or in my caseelogind.swayidleintercepts aPrepareForSleep signal...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Debug output from swayidle on both sway and niri
I captured debug output from swayidle for a period time when using sway and then when using niri, which helped me understand a bit more of what’s going on. It seems that when running sway, I am getting idle state events at the expected intervals (300s), but when I am running niri, I am getting sleep events at unexpected intervals.
In a screen recording, niri almost immediately sent the sleep within 2 minutes!
The difference seems to be that swayidle is receiving property changes from
org.freedesktop.login1.Managerwhen using niri, but a simple "idle state" when using sway.I think I will start...
-
Re: Why does niri stop network connection on idle while sway does not?
Since most of my posts about #niri here have been a bit scattered I thought I would take some time to document what I have setup on Slackware current (non-systemd).
My main problem with niri is that idle is not detected properly as it is with sway, and will kick in while I am typing, in a video call, or seemingly at random. I could live with this, but my network connection is disrupted each time niri launches swayidle unlike sway which does not exhibit this behavior.
Most of the way things are setup to launch is so that screen capture will work.
I don't think any of the configuration accurately...
-
Re: Why does niri stop network connection on idle while sway does not?
Since most of my posts about #niri here have been a bit scattered I thought I would take some time to document what I have setup on Slackware current (non-systemd).
My main problem with niri is that idle is not detected properly as it is with sway, and will kick in while I am typing, in a video call, or seemingly at random. I could live with this, but my network connection is disrupted each time niri launches swayidle unlike sway which does not exhibit this behavior.
Most of the way things are setup to launch is so that screen capture will work.
I don't think any of the configuration accurately...
-
Re: Why does niri stop network connection on idle while sway does not?
Since most of my posts about #niri here have been a bit scattered I thought I would take some time to document what I have setup on Slackware current (non-systemd).
My main problem with niri is that idle is not detected properly as it is with sway, and will kick in while I am typing, in a video call, or seemingly at random. I could live with this, but my network connection is disrupted each time niri launches swayidle unlike sway which does not exhibit this behavior.
Most of the way things are setup to launch is so that screen capture will work.
I don't think any of the configuration accurately...
-
Re: Why does niri stop network connection on idle while sway does not?
Since most of my posts about #niri here have been a bit scattered I thought I would take some time to document what I have setup on Slackware current (non-systemd).
My main problem with niri is that idle is not detected properly as it is with sway, and will kick in while I am typing, in a video call, or seemingly at random. I could live with this, but my network connection is disrupted each time niri launches swayidle unlike sway which does not exhibit this behavior.
Most of the way things are setup to launch is so that screen capture will work.
I don't think any of the configuration accurately...
-
I really want to love niri window manager, but I just can’t.
I could deal with niri and swayidle not working at all with seemingly randomly locking me when I am in the middle of typing something or on a video conference call if niri would NOT kill my network connection when it’s idle.
I don’t understand why this is even a feature? It does not happen with sway. In sway, when swayidle kicks in, I still have a network connection. But not in niri. Why? Is there a way to get it to not do that? Who knows? The documentation is terrible.
If it did not do that, then I could live with having idle kick in...
-
I really want to love niri window manager, but I just can’t.
I could deal with niri and swayidle not working at all with seemingly randomly locking me when I am in the middle of typing something or on a video conference call if niri would NOT kill my network connection when it’s idle.
I don’t understand why this is even a feature? It does not happen with sway. In sway, when swayidle kicks in, I still have a network connection. But not in niri. Why? Is there a way to get it to not do that? Who knows? The documentation is terrible.
If it did not do that, then I could live with having idle kick in...
-
I really want to love niri window manager, but I just can’t.
I could deal with niri and swayidle not working at all with seemingly randomly locking me when I am in the middle of typing something or on a video conference call if niri would NOT kill my network connection when it’s idle.
I don’t understand why this is even a feature? It does not happen with sway. In sway, when swayidle kicks in, I still have a network connection. But not in niri. Why? Is there a way to get it to not do that? Who knows? The documentation is terrible.
If it did not do that, then I could live with having idle kick in...
-
I really want to love niri window manager, but I just can’t.
I could deal with niri and swayidle not working at all with seemingly randomly locking me when I am in the middle of typing something or on a video conference call if niri would NOT kill my network connection when it’s idle.
I don’t understand why this is even a feature? It does not happen with sway. In sway, when swayidle kicks in, I still have a network connection. But not in niri. Why? Is there a way to get it to not do that? Who knows? The documentation is terrible.
If it did not do that, then I could live with having idle kick in...
-
I really want to love niri window manager, but I just can’t.
I could deal with niri and swayidle not working at all with seemingly randomly locking me when I am in the middle of typing something or on a video conference call if niri would NOT kill my network connection when it’s idle.
I don’t understand why this is even a feature? It does not happen with sway. In sway, when swayidle kicks in, I still have a network connection. But not in niri. Why? Is there a way to get it to not do that? Who knows? The documentation is terrible.
If it did not do that, then I could live with having idle kick in...
-
I'm thinking of re-installing FreeBSD on my Thinkpad T480s (Intel iGPU) and exploring Sway as my Wayland compositor. What is the state of Wayland support in FreeBSD?
