The death watch for the X Window System has probably started
121–130 of 518 posts
Re: The death watch for the X Window System has probably started
#122Earlier quoted context omitted.
Which NVIDIA graphics card do you own? I’m surprised Sway doesn’t support certain graphics cards. I believe the goal of wlroots is to solve this problem: > wlroots provides backends that abstract the underlying display and input hardware https://github.com/swaywm/wlroots
Last I checked, sway detects if nvidia.ko is loaded (even if the nvidia gpu has no display) and errors out with some message to the effect of "f you for buying nvidia."
Re: The death watch for the X Window System has probably started
#123Earlier quoted context omitted.
>But I think it's a bonus that applications can't listen into keys when they're not in focus. There are applications that do not run as a window, in present I have a global shortcuts that run a bash or python script, I know I am a power user so I will need a way to whitelist my use case.
Then that should be done through a mechanism provided by the desktop environment. GNOME and I'm pretty sure KDE too has a method to set custom keyboard shortcuts that can execute commands.
Yeah, that is the problem with Wayland: the solution to many missing features you get out of the box with X largely depends on the environment you are using.
Re: The death watch for the X Window System has probably started
#124Earlier quoted context omitted.
Additionally, no alternative project is even providing close to the set of features that i.e. systemd or pulseaudio does, not even via modules. sysvinit for example is only an alternative to systemd the same way a SUV is an alternative to F1. (watch https://www.youtube.com/watch?v=o_AIw9bGogo if you don't know why)
> sysvinit for example is only an alternative to systemd the same way a SUV is an alternative to F1 Perhaps. But this is the same tired old argument that ignores the existence of any other init/daemon-manager aside from systemd. And I would use the same car metaphor for comparisons with some of the other options, esp. runit, except with systemd in the SUV slot (e.g. my runit systems all behave themselves; my systemd…
Do you mean openRC, s6 etc? They still all use bash scripts, (which as a result depend on the dev for quality and can vary quite a bit) vs systemd's clear, uniform service definitions. They don't provide much beyond starting services and are more like wrappers around sysvinit than anything else.
> my runit systems all behave themselves; my systemd systems frequently hang on reboot
Every time I've seen this in practice it turned out the system was actually not configured properly, (usually crypttab or something related), and systemd has a default 90s timer to try to wait for everything to dismount, shut down properly vs other init systems just yank the cord, but it seems faster, so I guess it's 'better', (in which case you can just shorten the systemd timer to like 1s and it would be even faster doing that - look for 'DefaultTimeoutStopSec' in /etc/systemd/system.conf).
Re: The death watch for the X Window System has probably started
#125I would use Wayland, but the most actively-developed tiling window manager, sway, doesn't work with the NVIDIA graphics card I own. And come to think of it, isn't that a really weird problem to have? On X, the compositor (responsible for actually drawing all the windows on the screen) and the window manager (responsible for deciding how to arrange the windows and what their title bars/borders should look like) can be…
Re: The death watch for the X Window System has probably started
#126Re: The death watch for the X Window System has probably started
#127Earlier quoted context omitted.
Last I checked, sway detects if nvidia.ko is loaded (even if the nvidia gpu has no display) and errors out with some message to the effect of "f you for buying nvidia."
I grepped wlroots for "nvidia" and got no hits.
Re: The death watch for the X Window System has probably started
#128I would use Wayland, but the most actively-developed tiling window manager, sway, doesn't work with the NVIDIA graphics card I own. And come to think of it, isn't that a really weird problem to have? On X, the compositor (responsible for actually drawing all the windows on the screen) and the window manager (responsible for deciding how to arrange the windows and what their title bars/borders should look like) can be…
I would love to use Wayland, currently I only use it to watch movies without tearing. Anecdotally, everything feels brittle when using Wayland, applications crash... I really hope it matures.
(This is on amdgpu and later intel. I had a lot of problems with nouveau.)
Re: The death watch for the X Window System has probably started
#129Sway has become one of my favorite pieces of software. The only issue is that Sway or Wayland seems to have trouble implementing an easy to use redshift/nightlight. Based on my research into eye strain and talking to my optometrist I keep redshift on 24/7 and I can’t go back.
If you call redshift before calling sway, it works for me. I have it always on and just give it a value. redshift -m drm -PO 3000 sway
It'll end up becoming just as convoluted as X and I don't understand why the devs don't see this.
Re: The death watch for the X Window System has probably started
#130I would use Wayland, but the most actively-developed tiling window manager, sway, doesn't work with the NVIDIA graphics card I own. And come to think of it, isn't that a really weird problem to have? On X, the compositor (responsible for actually drawing all the windows on the screen) and the window manager (responsible for deciding how to arrange the windows and what their title bars/borders should look like) can be…