"For those who may be interested in trying to setupo & use SwayWM, I just updated & enhanced (?) my tutorial on the topic. The materials provided are all freely available and without copyright encumbrance."
After almost a year, I’ve released a new version of swaylock-effects, a fork of #swaylock with fancy effects and customization options. Swaylock is a screen locking utility for #Wayland compositors with ext-session-lock-v1 protocol support. #Linux
New features: unlock on SIGUSR1, allow to display image in indicator and change the state texts.
Thanks to all the contributors, especially @PeterCxy, who fixed a major bug that I couldn't fix myself!
I've used xterm for decades and I've found it to be fast and reliable. The default bitmap font always looks nice and sharp, too.
Does anyone know whether it could be ported to Wayland and remain just the same? Otherwise, can you recommend something similar - which I could at least configure to have the same fonts and select / paste behavior?
I probably ought to just start using Wayland and find out for myself :-)
- kernel 6.6.3
- nwg-panel 0.9.18 https://github.com/nwg-piotr/nwg-panel/releases/tag/v0.9.18;
- nwg-shell 0.5.23 https://github.com/nwg-piotr/nwg-shell/releases/tag/v0.5.23.
Or if VSCode was somehow successfully opened, change the setting "Title Bar Style" to custom.
It changes the window decoration, if applicable in your compositor of choice, to one similar to Windows. Kinda hacky, but ok.
Trying out #Wayland on #Fedora39 with an RTX 2070s, and the new #Nvidia 545 driver update actually makes it usable! 😮
It's still not as smooth as X11. Dragging windows around on the desktop feels a bit jittery (even at 144hz refresh rate) and elements of windows will just randomly flash transparency when moving or resizing, and my cursor leaves a white trail over certain #KDE UI elements, but I'm not getting horrible graphical glitches and I can actually game on this! Overall, I'm impressed.
I hope #Nvidia continues to make itself more compatible with Wayland before #Fedora40 releases, and that they add NV-Control support for Wayland so apps like #GWE will work. 🤞
But this is still experimental, as we're waiting for sctk-adwaita release, and winit update to support it.
You can try building `window-shadows` branch.
Damn. I decided to take the evening, sit down and actually try and setup #hyprland and get it to a spot where I could realistically use it for a project.
I think I might be somewhat of a Hyprland fan 😂 it’s definitely no qtile - the default config is a mess but that can easily be cleaned up. Until I can get Qtile #Wayland working, Hyprland will be an alright substitute.
@pete_wright -- there's waypipes, apparently? Which folks pro-offer as a substitute for #xpra. I use xpra and #barrier a lot for my machines to share input devices and pipe applications over the LAN. Haven't found a satisfactory way to do this with #Wayland, yet. A lot of good software is going to get depreciated at the same time that X gets the final kabosh from Redhat.
If you publicly declare that you don't want to use or support #Wayland because it doesn't suit your use cases, or it's incompatible with your hardware, or you disagree with how a protocol was designed, or some aspect is too low in quality, or you find it subjectively unpleasant, or you just plain don't want to: these are all valid, just know your mind and say so
If you assert that something is universally impossible under Wayland, when I've witnessed cross-compositor solutions on multiple computers for years, then this is going to pique my interest, because I want to understand what's missing/broken, and maybe even help advocate for these things to be improved
In future, I need to notice more quickly that someone is repeating absolutist assertions and isn't in a problem-solving state of mind
The plan is as usual: expose exciting technology to a great community of technical capable people -> improve quality, reliability and features (HDR...) -> get more companies to use it for products and invest into its development -> repeat -> #wayland world domination :P
Yeah, quite optimistic. Let's see how it goes. End 🧵
My personal vision with all of this is to see #wayland desktop technologies not only catching up with what other OSs offer, but becoming leading players - just like what other FLOSS projects already archived (or are in the process of becoming) in their areas. I'm thinking of #mesa, #pipewire, #gstreamer, #systemd, the kernel of course, and many others.
TL;DR: by making use of more modern hardware features we're finally in the position to catch up to other platforms with regards to energy efficiency. So let's do it!
#Cinnamon 6.0 Desktop Environment Arrives with Experimental #Wayland Session, Improved Sound Applet, New Gestures, and More https://9to5linux.com/cinnamon-6-0-desktop-environment-arrives-with-initial-wayland-support
Red Hat is removing all X servers except for Xwayland from Red Hat Enterprise Linux 10 and future releases, transitioning to a #Wayland ecosystem. The decision has garnered mixed reactions from users.
[Breaking News] RHEL 10 to drop X.Org server, but fear not my feline friends, Xwayland will remain like the purrfect backup cat! Meow-nificent! 😸 Time to embrace the Wayland ecosystem with more gestures, better hot-plugging, and increased security. Just remember, X11 is not out of the game yet, it's just taking a cat nap with Xwayland! 😼 #RHEL10 #Wayland #Xwayland
RHEL 10 kommt ohne X.Org-Server
So, please correct me if I'm wrong, but I think I'm discovering that if you use #Wayland and fractional scaling, there's no way to develop native #Android applications with a full blown IDE that isn't blurry (Android Studio doesn't support Wayland, and it seems nothing else matches it in terms of integration and functionality). WTF...
But my usage is 98% over Steam remote play (LAN), no direct interaction with this "server". That doesn't seem to work very well on #Wayland . Then I realized Fedora 40 will be dropping Xorg...
Any tips for Wayland Remote Play from the #linuxgaming folks?
#Wayland users: what do you use to take screenshots?
I'd ideally like to find a working version in the Debian repos, rather than pulling something in with git or whatever.
(The screenshot utility is to document a project. It is not a project in its own right.)
Red Hat’s RHEL 10 will Phase Out Xorg in Favor of Wayland
RHEL 10’s plan reveals Wayland’s dominance in future Linux releases, focusing on enhanced display features. Here’s more on that!
RHEL10 is planned to be all in on #wayland , with Xwayland for running xorg applications, and to not ship xorg server any more.
EDIT: text originally had 2x not..
folders under /var/run always gave me some issues, I had read it is supposed to be setup by pam,
set it to /tmp, or make a folder in your home and set the file permissions to 0700. (eg mkdir ~/.cache/run; chmod 0700 ~/.cache/run)
/var/run/user/1001 is a directory for temporary run data. You can safely remove it and create it under the ownership of your normal user again
Eben hatte ich einen echt krassen Nostalgie-Flashback!
Bis vor ca. 20 Jahren habe ich alles mit Emacs gemacht (Editor f. #TeXLaTeX, Programmeditor, Mail- und Newsgroups-Lesen, …). Ich muss glatt mal nachsehen, ob ich die alten .emacs-Files noch finde.
Irgendwann dann bin ich zum Feind übergelaufen und habe #Vi(m) genutzt.
Wait for wlroots™.
Non-logind TTY switching should work then
#sway #wayland #nwgshell
a single issue is capable of delaying my #nixos boot by minutes
having your runtime directory set up at login using something like dumb_runtime_dir.
#Linux Weekly Roundup for November 26th, 2023: #Firefox 120 adds new privacy features, #PipeWire reaches 1.0 milestone, EndeavourOS ditches #Xfce for #KDE Plasma, #OpenMandriva Lx 5.0, #OpenSSL 3.2, #NVK reaches #Vulkan 1.0 conformance, Firefox 121 promises #Wayland support by default, #TUXEDO Computers unveils their first all-AMD Linux #gaming laptop, and more https://9to5linux.com/9to5linux-weekly-roundup-november-26th-2023
PCSX2 Emulator Disables Wayland Support By Default
order of your packages matters. You have both pass and pass.withExtensions in your global packages defined. The order of packages is important, because who comes first - wins. #homemanager
all my #pass extensions work now, last bit is to add pass #wayland without collision
I have nothing against #Wayland and after it's ready for prime time I'm sure I'll use it. But it's not there, not for me anyway.
- If I lock my session and leave it locked for more than a few minutes, I can't unlock again. Instead I have a "black screen of death". X11 doesn't have this problem
- Numerous apps, especially flatpak and appimage based ones, don't have appropriate icons in the dock. X11 doesn't have this problem
- High DPI settings are not respected uniformly. X11 doesn't have this problem
- There's like a dozen more issues like this that I can't be bothered to list.
This is not a request for Google results about how to fix these issues. I know how to deal with all of them. That's not the point. The point is I shouldn't have to. In a mature, working window/desktop environment this stuff is settled. None of these issues arise with #X11 and they do arise with #Wayland. It's not ready.
Is it just me or does #Wayland piss everyone off? I am not a new #linux user, I have been at it since 1992. Every time I give Wayland a try, I find something that is broken. They have been at this for 15 years and it still feels like an early beta release. Maybe its time these guys gave it up and acknowledge this was not the way to go.
So happy to announce that finally, Swayora reached a usable state.
Keep in mind, that I was working on the installer more than the sway configuration itself.
So, keep checking it out for updates 😉
@ligthert I've honestly been quite happy with #fedora, the packages are up to date enough, they adopted things like #systemd, #wayland, #flatpak and #pipewire quite early (and yes, I think all of those have been good choices), the default setup is very well polished, and the packages that I prefer a rolling release for are installed in an #arch #distrobox
Elon Musk has lost tens of billions of dollars embracing the mediocrity of Brand X.
X is that person you vowed to never love again.
X means "DO NOT ENTER."
X is what you call a has-been.
Hell, even Linux is abandoning X for Wayland!
It is surely why more than a year later, people keep calling it "formerly known as Twitter." Elon is the only person who likes it being called X.
Apart from not fitting nicely UI wise, it prevents us from using the newly introduced #wayland hardware offloading (zero-copy playback) and, crucially, from (properly) supporting HDR content going forward.
I.e. we either need a port - or should consider making an alternative a core app to focus on.
Vulkan Support Begins Landing For Wine's Wayland Driver https://www.phoronix.com/news/Vulkan-Wine-Wayland-Part-1 #Vulkan #Wayland
VokoscreenNG is a screencasting tool with Wayland support that's easy to install on my Raspberry Pi 400 under 64-bit Raspberry Pi OS Bookworm. Wayland support is experimental and not all features are available but it works and does the job.
The required packages are in Debian, just execute:
sudo apt install vokoscreen-ng gstreamer1.0-pipewire
- Update tray icon: the check_updates() job from now on running on an async thread, in order not to lock the UI;
- screenshot tray applet added; it executes the screenshot command with relevant arguments; focused display and focused window screenshot delayed by 3 second, with a countdown timer in the tray icon.
With KDE Plasma: it's normal for the screen to lock when the computer sleeps.
With X11, and a keyboard and trackball as pictured at <https://mastodon.bsd.cafe/@grahamperrin/111377465852217006>: a lock will not occur. Anyone who wakes the computer will be able to use the desktop environment.
From <https://bugs.kde.org/show_bug.cgi?id=78871#c16> (2015-11-16):
❝… Plasma 5.5 comes with a Wayland session which does no longer expose this sever issue. … unfixable with X11, …❞
My FreeBSD case was a variation of duplicate bug 334051. Last week's photograph was tagged #cats because at home, with a laptop to the right of my main display, Bill and Pickle (to the left) habitually cause the keyboard to move, slowly, to the right. With the rear of the keyboard raised, on its feet, the top right underside of the keyboard occasionally leans sideways against a button on the side of the trackball device.
Defocusing from Plasma: <https://unix.stackexchange.com/a/355805/13260> refers to 'grab' in the X Window System core protocol, which I'll not attempt to understand.