#wayland — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #wayland, aggregated by home.social.
-
[Astuce] #Firefox #Librewolf
Avant, sous #linux, quand on voulait lancer une instance de Firefox avec son icône dédiée, on passait un paramètre '--class' pour définir WM_CLASS (sous #gnome, permet de distinguer des autres instances du navigateur).
Ça ne marche plus sous #wayland ; il faut maintenant passer le paramètre '--name'.
Exemple d'utilisation dans un fichier .desktop pour lancer une application / site #web avec son icône dédiée:
-
[Astuce] #Firefox #Librewolf
Avant, sous #linux, quand on voulait lancer une instance de Firefox avec son icône dédiée, on passait un paramètre '--class' pour définir WM_CLASS (sous #gnome, permet de distinguer des autres instances du navigateur).
Ça ne marche plus sous #wayland ; il faut maintenant passer le paramètre '--name'.
Exemple d'utilisation dans un fichier .desktop pour lancer une application / site #web avec son icône dédiée:
-
[Astuce] #Firefox #Librewolf
Avant, sous #linux, quand on voulait lancer une instance de Firefox avec son icône dédiée, on passait un paramètre '--class' pour définir WM_CLASS (sous #gnome, permet de distinguer des autres instances du navigateur).
Ça ne marche plus sous #wayland ; il faut maintenant passer le paramètre '--name'.
Exemple d'utilisation dans un fichier .desktop pour lancer une application / site #web avec son icône dédiée:
-
For those 4 of us who are going to use the Steam Controller under GNOME Wayland, consider preloading Extest library
-
For those 4 of us who are going to use the Steam Controller under GNOME Wayland, consider preloading Extest library
-
For those 4 of us who are going to use the Steam Controller under GNOME Wayland, consider preloading Extest library
-
For those 4 of us who are going to use the Steam Controller under GNOME Wayland, consider preloading Extest library
-
For those 4 of us who are going to use the Steam Controller under GNOME Wayland, consider preloading Extest library
-
Archcraft Prime aggiorna la sua ISO con nuovi compositor Wayland, Hyprland v55 e miglioramenti per Openbox, bspwm e i3wm. #Linux #ArchLinux #Archcraft #Wayland #Hyprland #Openbox #Bspwm #i3wm
-
#dankmaterialshell die meisten Maschinen auf noctalia umgestellt.
Allerdings vermisse ich zwei Dinge:
- Desktop Widgets immer im Vordergrund - praktisch wenn man seine Tageszeitung im Vollbild-Modus liest und trotzdem noch die Uhrzeit einblenden kann
- Wetteranzeige ist bei dms viel detaillierter (stündlich). Bei noctalia hat man nur die tägliche Angabe. -
Plasma 6.6.5 porta una lunga serie di correzioni dedicate a stabilità, accessibilità e supporto hardware. KWin riceve molti interventi su Wayland, multi-monitor e GPU NVIDIA, mentre Spectacle e Discover #KDE #Plasma #LinuxDesktop #OpenSource #Wayland #KWin
-
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
-
Has anyone able to change a font on #krita 6.0.1? Before, I couldn't open the dropdown menu. Now I can see my fonts, but cannot change the font of the text by selecting any of the fonts.
Operating System: #EndeavourOS
#KDE #Plasma Version: 6.6.4
KDE Frameworks Version: 6.25.0
#Qt Version: 6.11.0
Graphics Platform: #Wayland -
🚀 New Phantom Player 2.1.0 release!
#PhantomPlayer is a smart media player for local videos, offering a smooth, streaming-like experience with your own media.
Supported platforms:
+ #Debian #Ubuntu
+ #ArchLinux
+ #Fedora (now officially supported)
+ #Windows
+ #FreeBSD (partial support)#VLC replaced with #GStreamer for #Wayland support and #GTK4 transition.
-
-
KDE Frameworks 6.26 migliora KIO, Kirigami e Baloo con nuove funzioni, fix per Wayland, supporto Python 3.15 e ottimizzazioni UI. #KDE #Linux #OpenSource #Qt #KIO #Kirigami #Baloo #Kate #Wayland #Frameworks
-
KDE Frameworks 6.26 migliora KIO, Kirigami e Baloo con nuove funzioni, fix per Wayland, supporto Python 3.15 e ottimizzazioni UI. #KDE #Linux #OpenSource #Qt #KIO #Kirigami #Baloo #Kate #Wayland #Frameworks
-
KDE Frameworks 6.26 migliora KIO, Kirigami e Baloo con nuove funzioni, fix per Wayland, supporto Python 3.15 e ottimizzazioni UI. #KDE #Linux #OpenSource #Qt #KIO #Kirigami #Baloo #Kate #Wayland #Frameworks
-
KDE Frameworks 6.26 migliora KIO, Kirigami e Baloo con nuove funzioni, fix per Wayland, supporto Python 3.15 e ottimizzazioni UI. #KDE #Linux #OpenSource #Qt #KIO #Kirigami #Baloo #Kate #Wayland #Frameworks
-
KDE Frameworks 6.26 migliora KIO, Kirigami e Baloo con nuove funzioni, fix per Wayland, supporto Python 3.15 e ottimizzazioni UI. #KDE #Linux #OpenSource #Qt #KIO #Kirigami #Baloo #Kate #Wayland #Frameworks
-
@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.
-
@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.
-
@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.
-
@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.
-
@rl_dane @sashin The problem is that #fuckFedora HAS taken a stand, a principled stand. They want to force #systemd, #gnome, #wayland down your throat. They have become the #microsoft of the #linux world. #dumpFedora and #goBSD.
-
Even in the era where all major desktop environments are going Wayland-only, web browsers will ensure we never get rid of X11's traumatic memory, huh? 🫠 https://bugzilla.mozilla.org/show_bug.cgi?id=2027556
Par for the course for the ecosystem where everybody pretends to be everybody because the web is a never-ending collection of hacks…
-
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...
