You were correct, I saw it within 26 minutes of the upload :P Thanks for the long-term review and kind words :) Great video as usual. The reason why -wlr does not have window share is because wlr does not have a protocol for sharing a window buffer, and even worse, with the current architecture, you could only have hope for that even being doable if the compositor is not using a custom renderer (so e.g. sway, but not wf or hl) :) Bugs in screencopy are not a pw issue, not a wlr issue, they are my issue as "with speed come mistakes" and especially in C (and especially when working with code you did not write, xdph is a fork of xdpw) those mistakes can go unnoticed easily. Regarding screenshots - I fixed this by making a script that runs `hyprpicker -r -z` a moment before grim, freezing the displays and _then_ allowing me to screenshot :P A fun note: on -git I did some HEAVY optimizations over the past 2 days and now Hyprland with effects is lighter on my gpu than sway :P - Staged for 0.28.0 - stay tuned :) Some people report 3x GPU usage improvements which aligns with my profiling Another fun note: you didn't mention our amazing new mascot or the cool hidden easter egg :P
Hey vaxryy, please ignore this question if it is of any bother, but I used Hyprland for several months and I absolutely love everything about it. The only reason I stopped using it is because any sort of video playback was just burning up my CPU. I don't experience this with the same device on other DEs or WMs. I'm sure it was something specific to my configuration or other apps. But if you have any ideas what could be causing it, or point me in the direction to fix it, I would love to head back to using Hyprland. Thanks in advance
@@Lognodotdev That's unrelated to hyprland. It depends on your graphics card, what application you used the play the video and the configurations in that application. You should look at how you enable hardware video encoding in the application you used to play the video. Mpv does this out of the box well. If you use nvidia then wayland has performance problems in general anyways.
10:30 One other problem Hyprland specifically has is that it sets inactive window FPS to 1 and some games are really not happy about it. In Elden Ring, when the game runs at the low framerate it kicks you into the main menu because "FPS is insufficient for online play"
This is an issue with Wayland as a whole - there have been attempts to make protocols to fix it, and so far the accepted solution is to let Mesa tell the game it still has a consistent refresh rate. When a protocol is added, expect it to work better.
@@Mallchad Oh this issue has been mentioned on Discord several times. I just think the dev prob has more important stuff to work on, I don't want to distract him.
Gamescope hosts an xwayland session (including a virtual screen) for the games and flips their output directly to the screen, reducing the amount of buffer copies and latency. It also has it's own input handling.
that's not really the whole thing going on here with it - gamescope does do all of that, yes, but that's not why it "Just Works" for most things. It creates a normal Wayland (or Xwayland, depending on SDL2 configs) and draw the currently "focused" X window from the nested Xwayland instance to that. It solves so many focus and input bugs by telling apps "hey, you're focused, you will always have focus, don't worry about it" and that works. It's not quite perfect yet (it's missing borderless fullscreen afaik, and I've made an issue about it - it also can reduce the amount of copies if it used wlroots backends, or their own, instead of SDL2) but it's useful for so may use cases and fixes so many issues, all without introducing too many new bugs; it's amazing.
For screenshots, I made a little script, that let's me select a window or region. It then displays a notification. If i rightclick it, it uploads it to my paste service, if i middleclick it, I can edit it with swappy and shows another notification, where I can right click it to upload. mako and dunst both support mouse actions for their notifications The screenshots are saved in my Screenshots folder and the image data is sent to clipboard so I can paste it into applications. The link to uploaded Screenshots is put into primary selection.
I did something similar, except the screenshot just goes in the clipboard, and then I have keybinds for uploading the contents of the clipboard, because that works very nicely for files and text as well 👌
The mouse-snapping glitch doesn't only affect games. I regularly crash Blender when I click into the 3D viewport - the selection tool thinks that I started dragging a rectangle from way off-screen and the process segfaults. I'm not familiar with how events are handled, but it seems like the compositor sends the mouse-down event to the client before it actually tells it where the pointer is located relative to the client, and glitches ensue. GameScope seems to use a software pointer that is independent from the one provided by Hyprland (which would make sense, since GS itself is an independent compositor), which never actually moves outside GS's window. Other than that, my main gripe is that I can't write scripts inside Hyprland's config file and have to use the exec dispatcher and hyprctl or the IPC sockets. It's like going cold turkey after Qtile's pure python config.
Had to watch this again, great resource, needed to jog memory of issues and fixes, because some of these I still run into... some have been solved. Wayland feels like frontier exploration and mapping of places to safely ford rivers and where good berry patches are... less edge running, and more crumb leaving for others who come after. Thanks again @BrodieRobertson all-killer-no filler as usual brother!
I am literally screwing around with nix right this moment, trying to install hyprland after watching your talk with Chris Titus ... and you drop this gem on my noggin.
I really wanted to get into nix... and hyperland. But i really don't know whether it's worth my time... (after started using wayland, i haven't gone back to twm.. wasted years overconfiguring arch and twms...)
hey brodie! now i can finally understand what you were talking about! since first mentioning this many moons ago... you can in fact do even more sophisticated (to nth degree better control) in kde... along with many other ways too. it just requires going into kde system settings --> shortcuts --> right click mouse --> new --> global shortcut --> send keyboard input many thanks for missing that one. but it's probably been there for a while already. just hard to find / a bit more clunky to get to and setup. of course the other requirement on kde is a properly working bismuth. (or alternative kwin scripts). which is now partially broken sometimes on the current plasma 5.27+ and will most likely remain in flux until plasma 6+ ...however am pretty certain that too many people would miss all of these tiling feature on kde bismuth for it to ever remain permanently cut from kde. so these tiling feature disruptions they seem to be a transitional thing. (and still using bismuth here, albeit somewhat less reliable)
The dmenu issue can be fixed by setting it's layer to 'overlay' using layerrule in the config, I did the same with wofi when it wasn't popping up whilst another window was fullscreen
@@travis1240And they were still right. X11 has been around longer than linux itself, so it's gonna take a long time for Wayland to get as stable as X11. Still, slowly, it has gotten better.
8:26 you can use grimblast for that, it’s a script in the hyprland’s “contrib” repo, very nice, and freezes the screen and all It does that by somehow running the color picker made by the hyprland author, but doesn’t actually pick colors, just freezes the screen for grim to capture it
The reason Gamescope works so well is because while it is technically a Wayland compositor, it only implements support for fullscreen XWayland. In a sense it is the most lightweight X server + compositor possible.
I love window managers, and I was testing Hyprland, the truth is that it is an incredible and beautiful project, it looks quite polished, but it was not to my taste, I was looking for something more similar to openbox and for now the projects I have seen about this seems that they still need some work. I'm also a fan of retro style but I guess that will be after a while (imagine amiga's workbench in wayland) XD
concerning your dmenu issue: you can (asymetrically) exclude space at the edge of the screen via "hyprctl keyword monitor, addreserved, " I have no idea if that fixes the issue. I made a custom toolbar with eww and when I start it with a script I add the reserved space for it and when I close the bar I unreserve it.
opentabletdriver is one of the best pieces of software ive used for ny tablet. as an osu player, it has low latency and it is easy to configure. and i can change it to be pressure sensitive so i can use my tablet for art as well. its really nice
though i can't really play osu on wayland. you can feel the latency at higher level play. and i have a 165hz monitor. so until the tearing protocol gets implemented in wlroots and compositors support it, i have to switch to another tty and use x11 if i want to use wayland but also play osu.
Thank you! I wondered if I was the only one that couldn't get Flameshot to work right on Hyprland?! I switched to Ksnip about a year and a half ago (pre WM for me) and like it better. I like how multiple captures go into tabs, very handy for what I use it for - but I couldn't get it to work quite right either. I cared more about the editing after the screen shot than the actual action of taking the screen shot, so what I ended up doing is using grim, but launching it into Ksnip for annotations. I also miss the freeze while screen shot feature, but I saw the Hyprland Dev's comment about his work around so I'll give that a shot. The only major issue for me is that I use Teams for work and often have to screen share - which apparently doesn't work. Although from what I understand that's a Wayland issue, but its still a pain. I want to give a shout out to another wayland wm, Wayfire (fork of Hyprland? they are very similar). Super key in Wayfire zooms out to a grid of your workspaces on that monitor, I use that all the time. It also has some other cool "compiz-like" animations. I find myself bouncing between the two. For anyone using Hyprland, I'd recommend joining their Discord channel, the dev updates it regularly with updates and other helpful info. Great video!
I have a KDE wayland Desktop on my laprop that has wacom pen support and it just workswith the built in drivers of Feodora and in KDE's setting can i configure it
When your system locks up (becomes unresponsive) and the CPUs are maxed out, it's worth it to try the kernel's manual OOM killer before a hard reset. It's triggered with Alt+SysRq+F if it's enabled.
The mouse-snapping thing is something I notice touchpad and tablet input devices being present and older games. Touchpad and tablet devices present conflicting input that is sometimes treated by libraries as mouse input, and games not knowing how to tell with it, ends up throwing the game to the view limits (up and down). It doesn't affect horizontal as bad because it has full 360 view limits. This also sometimes happens with older game libraries that had some certain ideas about how a mouse device should work, and throws a fit if presented software cusor data, instead of raw mouse iput. I've not really found any consistent fix but it can be fixed on a case-by-case basis by modifying the presenting input devices to play nicely (probably what Valve is doing).
The only thing keeping me from switching to Hyperland is that manual tiling support is marked as low priority (not yet implemented) and the docking system is buggy (e.g. docking multiple widgets to multiple edges). I could probably make do with the master layout, but I want my widgets to work as expected.
I had to rebuild my desktop a few weeks ago and decided to give Wayland a shot due in large part to your videos. I'm using Plasma (previously used XFCE) and haven't had any notable issues so far outside of Wayland not properly detecting the available resolution for one of my monitors - a problem that Windows 10 also has with that monitor, but xorg does not. But I had another monitor laying around and swapped them so everything is working fine. I've got an Nvidia graphics card and was worried the experience would suffer as a result, but so far it's fine. And not needing to mess around with trying to get xorg and nvidia-settings to properly save/load my monitor configuration is quite nice.
may I ask what distro and nvidia card do you have? I was trying today to install debian dual boot on my main pc and run into some issues installing the non-free drivers (I deleted the whole distro to reinstall it later, I f up really bad so I thought it was faster reinstalling rather than fixing it), did you use commands or something else? srry for the long text
@@chocolat5804 I'm using Garuda and have a 750 Ti. Garuda uses xorg by default, so I had to install the relevant wayland packages, and then I needed to add nvidia_drm.modeset=1 ibt=off to my grub config. I believe that's it though.
For me, the GW2/FFXIV mouse issue was because those games were running in xwayland, which has a different multi monitor layout than wayland (including a different primary monitor). They have as part of their "click and move the camera around" logic a bit for "snap the mouse to the center of the screen so the mouse doesn't move off the monitor". So when you click, the mouse centers to a completely different xwayland monitor and things get wonky. Gamescope fixes this by limiting the game to thinking it is a single monitor setup, so the current monitor is the primary monitor. Alternatively, I have had this snippet in my sway config for a super long time: exec_always xrandr --output "$(xrandr --listactivemonitors | grep 1920+0 | head -n1 | cut -d' ' -f6)" --primary --pos 1920x0 It just runs xrandr inside xwayland, finds which monitor is at 1920+0 (the middle monitor of my triple monitor setup), and sets that one as the primary. So now my middle monitor is the primary monitor even in xwayland, and when a game runs, it doesn't feel the need to snap the mouse to a different screen.
At the pace it's evolving, I'd say in one 6 months-1 year most bugs are gonna be gone. The community is super active in comparison with sway, which haven't seen many updates during the last year. I'd like that project to revive. It's pretty good. To say the truth I have less bugs on sway, but I stay on hyprland because browsing on the internet and watching videos with vrr working correctly feels awesome.
Why not, when spawning dmenu, kill waybar then restart it when dmenu despawns? I have a keybind to cycle waybar on and off on those occasions I need that space for something else.
X11 is already deprecated, nobody wants to work on it anymore. The codebase is getting *very few* changes, most of which are only from a few weeks ago; Wayland has improvements coming from *hours* ago. Not to mention the available resources Wayland frees up, and the battery life improvements. And apps can't keylog you without explicit permission anymore. Give dwl a try, it's the Wayland equivalent of dwm - it'll feel familiar. Most issues you might have are either due to it being so bare, or have changes waiting to trickle down to you.
@@Mariuspersem I'm well aware of what it means. The developers of it have since moved onto Wayland, and suggest not using Xorg. If that isn't what deprecation means, then I have to ask what fucked up variant of English you're using.
@12:18, Have you tried sshing into your system from another computer? then using your method of choice of process terminal process viewer (I like using bashtop) but just ps -A then using kill to end offending process number works too. This can save you from a hard reset, its saved me. I like using Termux on my android to ssh into my system to kill the offending process.
Have been using Hyprland for the past few months - it's amazing. The only thing is that I never figured out is the screen sharing on zoom and instructions in wiki didn't really fix it for me. In general, I wish wiki was a bit more actively updated. But a great project indeed :)
8:46 In my experience, latency is REALLY noticeable on integrated graphics, which is annoying is you're on a laptop like me and want the gestures and the better battery life, I am putting the blame on Wine here since most of my library are windows games and the linux-native stuff is just as responsive as X11 with no composition... ok maybe not that much. I just switch to X11 when I'm not doing work or have access to an outlet, but generally that isn't the idea. Oh and let's not talk about the proprietary comunication apps not supporting Wayland propperly.
I'm using an old Thinkpad (E550) with a 60Hz display, and I can't see a noticeable difference in latency compared to my desktop (5500XT) system, with a 165Hz monitor. At most, the thinkpad feels less smooth, but that's a refresh rate thing. I don't really get why people complain about latency. All it takes is a few minutes to get used to different refresh rates or internals and it's all sunshine and rainbows. Most chat applications also either support PipeWire capture indirectly (via the browser), or their app can be updated to use a version of Electron which supports it. Worst case, use the xwaylandvideobridge.
bro if u plug your laptop off and then u need battery life u need some power saving things like tlp and when u will use them the latency will increase very much@@oro6768
For me gaming actually had noticeably more latency up until I started capping my framerate and manually set my vulkan presentation mode. Now it's indistinguishable
I've been daily driving it on my laptop (Intel integrated graphics) for a couple of months now. I use it mostly for web browsing and terminal and I had absolutely no issues with it :D
1. It's a shame that dmenu can't have a z-level. 2. It would be even better IMHO for dmenu to appear below the panel in the y dimension so both would be visible and just the top of the windows are obscured. 3. The missing feature is choice. 4. My issue with tillers is that I like to have gkrellm running as a dock and I'm unfamiliar with how to do that, the support I've been given is don't run a system visualizer. I see the panel applets that perform this function, my apprehension is size/relestate. I like gkrellm and even though I'm open to other solutions I haven't seen anything that looks like a good fit for me, keeping me on gnome(because of it's hot corner).
If we could get xwayland OBS to work with Nvidia drivers for obs that would be great. Obs will only use cpu and launch with Mesa driver instead of Nvidia with xwayland. Or if obs would make twitch integration and custom docks work on wayland, that would be great.
I just started to setup an Artix, dinit, Hyprland system. It generally runs completely fine. But I do have an error where one of my monitors doesn't get a signal when booting into hyprland. Exitting hyprland and logging back in fixes it, but it still is very annoying. I opened an issue., let's see if it can be fixed.
I use wayland on my work daily driver --- for the only reason being that it handles mutliple screen resolutions better. I've done my head in over the years getting compositors to handle this and was done.. But the big downside is in screen sharing, screen recording and just some apps that don't play nice (especially like the global protect vpn client I need for work... but I've just decided to tunnel through a windows vm instead.....) My work machine is not something I want to go chopping and changing with but yeah-- occasionally if doing a big presentation I may shut down the second monitor (not enough room for 2 * 4k monitors) and switch back to xorg. My other machine is also a work machine. It's a dedicated DAW.. Ardour/Mixbus is still Maybe I'll wait a while and see if hyprland can cut it, when it's more stable.
Just a question: why does reducing one key press make a window manager looker "better"? What's wrong with an extra key if you want to specify where the new window is going to appear?
Wait, why would it be the compositor's job to handle drawing tablets anyways? Shouldn't it be compositor-agnostic? Same with keybinds, why is it the compositor's job? Shouldn't that be part of wayland, or just a separate program? Is the compositor just responsible for way way more than a window manager on X? If that's true, is that a flaw of Wayland that's gonna be fixed or is it a design decision?
I wish the dev would write tutorial / documentation how to write compositor with wlroots, there are mostly no docs how to do so, and everything is like "read our code, deal with it". Not to mention creating custom renderer
I just started using hyprland about a week ago and its amazing, however the battery consumption isnt. Hyprland is still the best wm for beginners imo, i tried to start with fluxbox and then openbox but they always got messed up for me, Hyprland hasnt broken yet and im pretty happy with my config :)
I am working on optimization on -git and during the last 2 days there has been a chonker of commits to address performance. You should try that :) Staged for 0.28.0, so you can also wait for that, but some people report 3x gpu usage improvements and idle cpu usage drop of around 20%
X also has the thing where basically any program running could keylog any other program. Or other 69420 security black holes, which just cannot be solved. Do we really want to have a windowing system then fucking windows?
@@no_name4796 "X also has the thing where basically any program running could keylog any other program." sounds like a feature. id love to have some windows interract with others. like overlays and screen recorders if you install a program that keylogs stuff its mostly your fault. i mean, software installed on your machine can do worse things than just keylogging if they felt like it lmao. youre blaming x for something that isnt even the main issue
I am using Hyprland now, migrating from KDE. I definitely like Hyprland better, despite the quirks. And I was able to launch Steam and play my favourite game, Path of Exile. Mostely playable, though sometimes I get stutter on the frames. Then again, I am playing this on an old laptop. It was top of the line when I purchased it 8 years ago, but now it is starting to show its age. 32 Gigs of RAM is nothing today.
As someone who plays some precision demanding games (osu!, geometry dash, etc), wayland wasn't an option until i got a high refresh rate display. The input delay was just too much it was absolutely unplayable for me. I was waiting for the implementation of the tearing control protocol, but the MR was just not beeing touch at all and nothing was moving in the wlroot side. I do think the merge of tearing control will probably help a lot of 60hz gamers to try to switch to wlroot-based compositors and try out wayland, i hope it lands soon !
@@シミズルリ sane developers. Tearing is not fun, and it's something that other platforms have been handling just fine - Android doesn't tear, Windows only tears when gaming, and macOS doesn't tear *at all*. Wayland does what's sane, and fit the most with their design - commit-based and frame-perfect compositing. Tearing is mostly waiting on other improvements in the stack, specifically your in-kernel GPU drivers. I do hope the tearing protocol is more widely supported, even if just for fullscreen windows. That, at least, would give a decent balance of a tear-free experience and latency.
Hyperland may be a good future option for next 3-5 years, especially if hyperland is as hackable as xmonad or dwm, and has no preinstalled bs features. There is no beauty about disabling features, transitions and transformations. The coolest stuff, to my opinion, is to write and tweak your own designs for the twm. If there will be clean and well documented version of the hyperland, alongside with plug and play version I think that must be a banger.
If I ever find a jackpot winning lottery ticket and can therefore afford large 4K monitors, I'll probably give a tiling WM some time, but other than that, I'm damn near always using full screen, so it's just not worth the effort (after 30 years of floating).
I had a issue with hyprland and pipewire. When i watch videos via firefox, the audio plays normally. But when i playing games(csgo etc), the audio got chopped, it plays 1 second of audio, then no sound for 5 or 10 seconds. Don't know why.
I've daily driven hyprland for a couple months now and all I can say is that it's flawless. Every problem I had was my fault and now it's completely untouchable by competitors, imo.
These are some of the main reasons why I don't use Wayland at all, video production is still not stable enough on Wayland for me to use and I also have a NVIDIA card and as we all know that Wayland support on NVIDIA is hit or miss. So until we have a good way to capture screens and windows and video editors that don't crash as often on Wayland it's Xorg/X11 for me!
Hyprland works well even on reasonably low performance hardware (Core 2 Duo, 4 GB DDR2, AMD graphics card). There are a few issues though. The Dolphin file manager doesn't show the file and folder icons, and since the thing is running on NixOS I don't know how to fix this - the general consensus is that I need to add QT5, somehow. A mix of Hyprland problems and myself not knowing how to configure NixOS properly.
Sway's default config is your best bet but pretty much everything you're going to want to configure. Maybe check out the configs that Arco Linux provides
The screen having the zoomies was an issue in Elite Dangerous too, when I'd go to the map and try to right click spin the camera or pan around with the mouse, it'd spin at mach 9 or snap to the edge of the map. I think I fixed it by changing an option in game about which mouse I wanted to use, something about either the systems mouse or a rendered mouse.
Not a big fan of tiling window managers, the openbox wayland alternative labwc interested me but it lacks one of the most important features of openbox, smart window placement, so it will just place windows directly on top of each other, so you still don't have many options when it comes to wayland if you don't like tiling window managers and want smart window placement, your only option is plasma, we really need lxqt and xfce to support wayland, I suspect lxqt will get there before xfce does.
I have been using hyprland for a few months now and I want tab groups and stacking like how i3 does it. That was one of the reasons I didn't switch to it for so long, but I eventually decided I would just use it and wait.
Also qt theming on hyprland doesn't work for me. I use qt5ct but it always complains about that system variable though it is set and works fine on other WMs ¯\_(ツ)_/¯
I've heard FAR TOO MANY complaints against wayland and that it is STILL NOT STABLE---- but I LOVE this dynamic tling window manager... and would love to run this-- ALSO-- I have one eye now and am old- so I HATE command line crap... how close is this to being GUI ONLY????? (not knocking CL or anything like that- as many accuse me of-- I just don't use it because it BOTHERS MY ONE GOOD EYE).. I absolutley HATE key anything... other than normal typing... PERIOD.. so- how close is this to GUI ONLY???
Yeah unfortunately wayland is still unusable with nvidia hardware, despite what others say. Tons of crashes in software, xwayland flickering like crazy and repeating frames, egl xwayland fallback to software rendering (which means that applications such as firefox default to software rendering opengl, as if you have no graphics card at all), pipewire capture not working (for me at least), so I cant use most screen recording software. Hyprland has a section about nvidia on how to workaround the flickering, however none of those options has worked for me.
I had to use Sol Does Tech's install script here on youtube. If you search "arch hyprland install" he comes in top 10 searches. Right now he's got four versions of install scripts. I checked the script and it turned out I don't know that much about arch and linux in general because I was did not install some libraries in order for hyprland to work. I highly recommend his script!
ปีที่แล้ว
Hyprland is really nice. I gave it a try, but I can't live without DWM/DWL's tags.
have been using KDE Wayland for a good while and I feel like games are a lot better on Wayland. On X11, if you want low latency, you disable compositing but then you have unavoidable tearing unless you use vsync in your games... Though, Wayland compositing on KDE is mostly indistinguishable in latency from X11 with compositing disabled. Also, gamescope does support Wayland yes... but it is an X11 compositor by default, unless you specify you want it to run a Wayland session. I don't know what makes it have less issues with cursor capture than XWayland but it does and it's basically necessary to play War Thunder.
Gamescope *is* a Wayland compositor, it just embeds an Xwayland instance. It gets the niceties that come from being a dedicated compositor purely for gaming, including input handling. Gamescope has absolutely no native X11 support, that's all done in Xwayland. Set SDL_VIDEODRIVER=wayland if you want to run gamescope outside of Xwayland, if that's what you want.
You were correct, I saw it within 26 minutes of the upload :P Thanks for the long-term review and kind words :) Great video as usual.
The reason why -wlr does not have window share is because wlr does not have a protocol for sharing a window buffer, and even worse, with the current architecture, you could only have hope for that even being doable if the compositor is not using a custom renderer (so e.g. sway, but not wf or hl) :)
Bugs in screencopy are not a pw issue, not a wlr issue, they are my issue as "with speed come mistakes" and especially in C (and especially when working with code you did not write, xdph is a fork of xdpw) those mistakes can go unnoticed easily.
Regarding screenshots - I fixed this by making a script that runs `hyprpicker -r -z` a moment before grim, freezing the displays and _then_ allowing me to screenshot :P
A fun note: on -git I did some HEAVY optimizations over the past 2 days and now Hyprland with effects is lighter on my gpu than sway :P - Staged for 0.28.0 - stay tuned :) Some people report 3x GPU usage improvements which aligns with my profiling
Another fun note: you didn't mention our amazing new mascot or the cool hidden easter egg :P
@brodie... pin this...
the goat is here
Wouldn't exporting a dma buf for windows be possible for both sway and hyprland? or how does the custom render prevent that?
Hey vaxryy, please ignore this question if it is of any bother, but I used Hyprland for several months and I absolutely love everything about it. The only reason I stopped using it is because any sort of video playback was just burning up my CPU. I don't experience this with the same device on other DEs or WMs. I'm sure it was something specific to my configuration or other apps. But if you have any ideas what could be causing it, or point me in the direction to fix it, I would love to head back to using Hyprland. Thanks in advance
@@Lognodotdev That's unrelated to hyprland. It depends on your graphics card, what application you used the play the video and the configurations in that application. You should look at how you enable hardware video encoding in the application you used to play the video. Mpv does this out of the box well. If you use nvidia then wayland has performance problems in general anyways.
10:30
One other problem Hyprland specifically has is that it sets inactive window FPS to 1 and some games are really not happy about it. In Elden Ring, when the game runs at the low framerate it kicks you into the main menu because "FPS is insufficient for online play"
There's a workaround by having obs capture their specific window if you're using the hyprland portal, but it depends on the game tho
its open source, ykyk
This could be fixed with a 1 line toggle if you reported it
This is an issue with Wayland as a whole - there have been attempts to make protocols to fix it, and so far the accepted solution is to let Mesa tell the game it still has a consistent refresh rate.
When a protocol is added, expect it to work better.
@@Mallchad Oh this issue has been mentioned on Discord several times. I just think the dev prob has more important stuff to work on, I don't want to distract him.
Gamescope hosts an xwayland session (including a virtual screen) for the games and flips their output directly to the screen, reducing the amount of buffer copies and latency. It also has it's own input handling.
that's not really the whole thing going on here with it - gamescope does do all of that, yes, but that's not why it "Just Works" for most things.
It creates a normal Wayland (or Xwayland, depending on SDL2 configs) and draw the currently "focused" X window from the nested Xwayland instance to that. It solves so many focus and input bugs by telling apps "hey, you're focused, you will always have focus, don't worry about it" and that works.
It's not quite perfect yet (it's missing borderless fullscreen afaik, and I've made an issue about it - it also can reduce the amount of copies if it used wlroots backends, or their own, instead of SDL2) but it's useful for so may use cases and fixes so many issues, all without introducing too many new bugs; it's amazing.
For screenshots, I made a little script, that let's me select a window or region. It then displays a notification. If i rightclick it, it uploads it to my paste service, if i middleclick it, I can edit it with swappy and shows another notification, where I can right click it to upload. mako and dunst both support mouse actions for their notifications
The screenshots are saved in my Screenshots folder and the image data is sent to clipboard so I can paste it into applications. The link to uploaded Screenshots is put into primary selection.
tip: launch hyprpicker -r -z right before grim to freeze displays. Don't forget to kill it after you select the area tho :P
@@vaxryy nice one
I did something similar, except the screenshot just goes in the clipboard, and then I have keybinds for uploading the contents of the clipboard, because that works very nicely for files and text as well 👌
can you send me/post that script? thanks
For the F4 being stucked with obs
You can try using `bindn` instead of `bind`, which does a "non-capturing' bind
also for the dmenu being at the bottom of the layer, you can put "layer": "bottom" in waybar config, then it will appear below any other window
You could also create a submap, in case you do want it to be captured.
I would strongly suggest you have a look at river. It's a significantly more sane tiling window manager with a focus on correctness and stability.
The mouse-snapping glitch doesn't only affect games. I regularly crash Blender when I click into the 3D viewport - the selection tool thinks that I started dragging a rectangle from way off-screen and the process segfaults. I'm not familiar with how events are handled, but it seems like the compositor sends the mouse-down event to the client before it actually tells it where the pointer is located relative to the client, and glitches ensue. GameScope seems to use a software pointer that is independent from the one provided by Hyprland (which would make sense, since GS itself is an independent compositor), which never actually moves outside GS's window.
Other than that, my main gripe is that I can't write scripts inside Hyprland's config file and have to use the exec dispatcher and hyprctl or the IPC sockets. It's like going cold turkey after Qtile's pure python config.
Had to watch this again, great resource, needed to jog memory of issues and fixes, because some of these I still run into... some have been solved. Wayland feels like frontier exploration and mapping of places to safely ford rivers and where good berry patches are... less edge running, and more crumb leaving for others who come after. Thanks again @BrodieRobertson all-killer-no filler as usual brother!
I tested out hyperland and absolutely fell in love with it. Been using it for a few months 😊
should i use it as well? i am using i3 rn
Up to you, it has an easy config, ive been my main WM since this comment i love it and im even on nividia with 0 issues @ItsBarmanji
and you uploaded this exactly the day my hyprland installation stopped working after a kernel update...
I am literally screwing around with nix right this moment, trying to install hyprland after watching your talk with Chris Titus ... and you drop this gem on my noggin.
Just worked with .enable for me. That’s with gdm running as I spend some time in gnome too
@@billeterk I feel so dumb, thanks! 😂
I really wanted to get into nix... and hyperland. But i really don't know whether it's worth my time...
(after started using wayland, i haven't gone back to twm.. wasted years overconfiguring arch and twms...)
@@BannedEvECharacter don't worry -- I'm there too with NixOS web dev atm!
hey brodie! now i can finally understand what you were talking about! since first mentioning this many moons ago... you can in fact do even more sophisticated (to nth degree better control) in kde... along with many other ways too. it just requires going into kde system settings --> shortcuts --> right click mouse --> new --> global shortcut --> send keyboard input
many thanks for missing that one. but it's probably been there for a while already. just hard to find / a bit more clunky to get to and setup.
of course the other requirement on kde is a properly working bismuth. (or alternative kwin scripts). which is now partially broken sometimes on the current plasma 5.27+ and will most likely remain in flux until plasma 6+ ...however am pretty certain that too many people would miss all of these tiling feature on kde bismuth for it to ever remain permanently cut from kde. so these tiling feature disruptions they seem to be a transitional thing. (and still using bismuth here, albeit somewhat less reliable)
I'm still considering KDE, maybe I'll have to hop onto that one sometime after plasma 6
I switched from awesomewm to Hyprland about 5 months ago and I couldn't be happier with it. I run it on a desktop and two different laptops. Love it!👍
how you manage the workspaces? Awesomewm gives you independent workspaces for each monitor. Did you solve that?
I've been using it for about the same time and it's REALLY nice, also switched to NixOS along side it
Same here, I've been daily driving Hyprland since I saw Brodie's video on it.
The dmenu issue can be fixed by setting it's layer to 'overlay' using layerrule in the config, I did the same with wofi when it wasn't popping up whilst another window was fullscreen
it's only getting better.
Yep. People were saying the same thing 10 years ago.
@@travis1240 ?
@@travis1240 and it was true and still is. But by now it reached a quite good level already.
@@travis1240And they were still right.
X11 has been around longer than linux itself, so it's gonna take a long time for Wayland to get as stable as X11. Still, slowly, it has gotten better.
Maybe that should be Todd Howards slogan.
Great in-depth review, very enlightening, thanks!
8:26 you can use grimblast for that, it’s a script in the hyprland’s “contrib” repo, very nice, and freezes the screen and all
It does that by somehow running the color picker made by the hyprland author, but doesn’t actually pick colors, just freezes the screen for grim to capture it
Thats because hyprpicker has an option to freeze screens, and also an option to not show the color picker, both of which the script uses
The reason Gamescope works so well is because while it is technically a Wayland compositor, it only implements support for fullscreen XWayland. In a sense it is the most lightweight X server + compositor possible.
I love window managers, and I was testing Hyprland, the truth is that it is an incredible and beautiful project, it looks quite polished, but it was not to my taste, I was looking for something more similar to openbox and for now the projects I have seen about this seems that they still need some work.
I'm also a fan of retro style but I guess that will be after a while (imagine amiga's workbench in wayland) XD
You need Wayfire in your life.
concerning your dmenu issue: you can (asymetrically) exclude space at the edge of the screen via "hyprctl keyword monitor, addreserved, " I have no idea if that fixes the issue. I made a custom toolbar with eww and when I start it with a script I add the reserved space for it and when I close the bar I unreserve it.
opentabletdriver is one of the best pieces of software ive used for ny tablet. as an osu player, it has low latency and it is easy to configure. and i can change it to be pressure sensitive so i can use my tablet for art as well. its really nice
though i can't really play osu on wayland. you can feel the latency at higher level play. and i have a 165hz monitor. so until the tearing protocol gets implemented in wlroots and compositors support it, i have to switch to another tty and use x11 if i want to use wayland but also play osu.
Been on Hyprland on 2 systems since November. I love it & can't go back to anything else now.
1 year today I've been running Hyprland
@@A_G420 r u enjoyin it?
@@ItsBarmanji yeah, have it installed on 3 systems now
Thank you! I wondered if I was the only one that couldn't get Flameshot to work right on Hyprland?! I switched to Ksnip about a year and a half ago (pre WM for me) and like it better. I like how multiple captures go into tabs, very handy for what I use it for - but I couldn't get it to work quite right either. I cared more about the editing after the screen shot than the actual action of taking the screen shot, so what I ended up doing is using grim, but launching it into Ksnip for annotations. I also miss the freeze while screen shot feature, but I saw the Hyprland Dev's comment about his work around so I'll give that a shot. The only major issue for me is that I use Teams for work and often have to screen share - which apparently doesn't work. Although from what I understand that's a Wayland issue, but its still a pain. I want to give a shout out to another wayland wm, Wayfire (fork of Hyprland? they are very similar). Super key in Wayfire zooms out to a grid of your workspaces on that monitor, I use that all the time. It also has some other cool "compiz-like" animations. I find myself bouncing between the two. For anyone using Hyprland, I'd recommend joining their Discord channel, the dev updates it regularly with updates and other helpful info. Great video!
IIRC as per the latest update, the Waybar package from the Arch repos now works with Hyprland.
Oh I'll have to check that out
Hyprland is the solution for me. I hope this project will be evolving and have support. My best wishes to creators and contributors
I have a KDE wayland Desktop on my laprop that has wacom pen support and it just workswith the built in drivers of Feodora and in KDE's setting can i configure it
When your system locks up (becomes unresponsive) and the CPUs are maxed out, it's worth it to try the kernel's manual OOM killer before a hard reset. It's triggered with Alt+SysRq+F if it's enabled.
The mouse-snapping thing is something I notice touchpad and tablet input devices being present and older games.
Touchpad and tablet devices present conflicting input that is sometimes treated by libraries as mouse input, and games not knowing how to tell with it, ends up throwing the game to the view limits (up and down). It doesn't affect horizontal as bad because it has full 360 view limits.
This also sometimes happens with older game libraries that had some certain ideas about how a mouse device should work, and throws a fit if presented software cusor data, instead of raw mouse iput. I've not really found any consistent fix but it can be fixed on a case-by-case basis by modifying the presenting input devices to play nicely (probably what Valve is doing).
One month now on Hyprland, zero issues. Except Zoom screen sharing being a bit buggy.
That's related to the problem I was dealing with
The only thing keeping me from switching to Hyperland is that manual tiling support is marked as low priority (not yet implemented) and the docking system is buggy (e.g. docking multiple widgets to multiple edges). I could probably make do with the master layout, but I want my widgets to work as expected.
Whats manual tiling?
@@remz02 Where you are free to manipulate windows within the tile grid and are not conformed to a "layout."
I had to rebuild my desktop a few weeks ago and decided to give Wayland a shot due in large part to your videos. I'm using Plasma (previously used XFCE) and haven't had any notable issues so far outside of Wayland not properly detecting the available resolution for one of my monitors - a problem that Windows 10 also has with that monitor, but xorg does not. But I had another monitor laying around and swapped them so everything is working fine.
I've got an Nvidia graphics card and was worried the experience would suffer as a result, but so far it's fine. And not needing to mess around with trying to get xorg and nvidia-settings to properly save/load my monitor configuration is quite nice.
may I ask what distro and nvidia card do you have? I was trying today to install debian dual boot on my main pc and run into some issues installing the non-free drivers (I deleted the whole distro to reinstall it later, I f up really bad so I thought it was faster reinstalling rather than fixing it), did you use commands or something else? srry for the long text
@@chocolat5804 I'm using Garuda and have a 750 Ti. Garuda uses xorg by default, so I had to install the relevant wayland packages, and then I needed to add nvidia_drm.modeset=1 ibt=off to my grub config. I believe that's it though.
For me, the GW2/FFXIV mouse issue was because those games were running in xwayland, which has a different multi monitor layout than wayland (including a different primary monitor). They have as part of their "click and move the camera around" logic a bit for "snap the mouse to the center of the screen so the mouse doesn't move off the monitor". So when you click, the mouse centers to a completely different xwayland monitor and things get wonky.
Gamescope fixes this by limiting the game to thinking it is a single monitor setup, so the current monitor is the primary monitor.
Alternatively, I have had this snippet in my sway config for a super long time:
exec_always xrandr --output "$(xrandr --listactivemonitors | grep 1920+0 | head -n1 | cut -d' ' -f6)" --primary --pos 1920x0
It just runs xrandr inside xwayland, finds which monitor is at 1920+0 (the middle monitor of my triple monitor setup), and sets that one as the primary. So now my middle monitor is the primary monitor even in xwayland, and when a game runs, it doesn't feel the need to snap the mouse to a different screen.
I hadn't considered that possibility, I'll give it a look
At the pace it's evolving, I'd say in one 6 months-1 year most bugs are gonna be gone. The community is super active in comparison with sway, which haven't seen many updates during the last year. I'd like that project to revive. It's pretty good.
To say the truth I have less bugs on sway, but I stay on hyprland because browsing on the internet and watching videos with vrr working correctly feels awesome.
I guess I'll ask since it's 6 months later. Has it improved? I'm using kde right now because I was nervous at first.
Why not, when spawning dmenu, kill waybar then restart it when dmenu despawns?
I have a keybind to cycle waybar on and off on those occasions I need that space for something else.
obs-vkcapture may be useful as an alternative for game capture. I also still use wlrobs, because it remembers which display it was capturing.
Im at the point where I have modified dwm to my liking. Unless X11 for some reason gets deprecated or something I really don't see a need to change
X11 is already deprecated, nobody wants to work on it anymore. The codebase is getting *very few* changes, most of which are only from a few weeks ago; Wayland has improvements coming from *hours* ago. Not to mention the available resources Wayland frees up, and the battery life improvements. And apps can't keylog you without explicit permission anymore.
Give dwl a try, it's the Wayland equivalent of dwm - it'll feel familiar. Most issues you might have are either due to it being so bare, or have changes waiting to trickle down to you.
@@oro6768 I don't think you know what deprecated means
@@Mariuspersem I'm well aware of what it means. The developers of it have since moved onto Wayland, and suggest not using Xorg. If that isn't what deprecation means, then I have to ask what fucked up variant of English you're using.
@12:18, Have you tried sshing into your system from another computer? then using your method of choice of process terminal process viewer (I like using bashtop) but just ps -A then using kill to end offending process number works too. This can save you from a hard reset, its saved me.
I like using Termux on my android to ssh into my system to kill the offending process.
I would love to switch to a wlroots compositor but my nvidia GPU isn't letting me.
There's a community version of hyprland setup for NVIDIA, I can't comment on how well it works though
Have been using Hyprland for the past few months - it's amazing. The only thing is that I never figured out is the screen sharing on zoom and instructions in wiki didn't really fix it for me. In general, I wish wiki was a bit more actively updated. But a great project indeed :)
Zoom works for me, slack doesn't. I'm on dwl though.
I don't use waybar but 2 days ago i was testing waybar and mainline waybar had workspace support for hyprland, i might be wrong here
Someone else told me the fork changes recently got merged into the main project
8:46
In my experience, latency is REALLY noticeable on integrated graphics, which is annoying is you're on a laptop like me and want the gestures and the better battery life, I am putting the blame on Wine here since most of my library are windows games and the linux-native stuff is just as responsive as X11 with no composition... ok maybe not that much.
I just switch to X11 when I'm not doing work or have access to an outlet, but generally that isn't the idea.
Oh and let's not talk about the proprietary comunication apps not supporting Wayland propperly.
I'm using an old Thinkpad (E550) with a 60Hz display, and I can't see a noticeable difference in latency compared to my desktop (5500XT) system, with a 165Hz monitor. At most, the thinkpad feels less smooth, but that's a refresh rate thing. I don't really get why people complain about latency. All it takes is a few minutes to get used to different refresh rates or internals and it's all sunshine and rainbows.
Most chat applications also either support PipeWire capture indirectly (via the browser), or their app can be updated to use a version of Electron which supports it. Worst case, use the xwaylandvideobridge.
bro if u plug your laptop off and then u need battery life u need some power saving things like tlp and when u will use them the latency will increase very much@@oro6768
For FF, I fix this by enabling FF's option to capture the mouse (not letting the mouse leave the window). This is on Gnome/Wayland though, so YMMV
For me gaming actually had noticeably more latency up until I started capping my framerate and manually set my vulkan presentation mode. Now it's indistinguishable
Hyprland looks really cool and I did set up up once, but now I’m back to my stock Ubuntu gnome desktop and a fullscreen terminal running tmux lol
yes.. i am back in fedora kde...
I don't like flameshot. I've always thought it was unnecessary to have a daemon running in the background for screenshots.
I've been daily driving it on my laptop (Intel integrated graphics) for a couple of months now. I use it mostly for web browsing and terminal and I had absolutely no issues with it :D
I literally don’t care about any of the features you listed… except the drawing tablet support, and I’m pretty happy with the Wacom driver, thanks.
using hyprland on my work pc provided by my workplace like a madlad, awesome experience!
1. It's a shame that dmenu can't have a z-level. 2. It would be even better IMHO for dmenu to appear below the panel in the y dimension so both would be visible and just the top of the windows are obscured. 3. The missing feature is choice. 4. My issue with tillers is that I like to have gkrellm running as a dock and I'm unfamiliar with how to do that, the support I've been given is don't run a system visualizer. I see the panel applets that perform this function, my apprehension is size/relestate. I like gkrellm and even though I'm open to other solutions I haven't seen anything that looks like a good fit for me, keeping me on gnome(because of it's hot corner).
You should make a tutorial video for hyprland/tiling WMs. I've used traditional DEs, and it's initimidating to learn a new way of doing things.
I don't even have a choice. Multiple refresh rate monitors; I *need* to use Wayland, and Hyprland has been my favorite WM.
If we could get xwayland OBS to work with Nvidia drivers for obs that would be great. Obs will only use cpu and launch with Mesa driver instead of Nvidia with xwayland. Or if obs would make twitch integration and custom docks work on wayland, that would be great.
I just started to setup an Artix, dinit, Hyprland system. It generally runs completely fine. But I do have an error where one of my monitors doesn't get a signal when booting into hyprland. Exitting hyprland and logging back in fixes it, but it still is very annoying. I opened an issue., let's see if it can be fixed.
for the dmenu being at the bottom of the layer, you can put "layer": "bottom" in waybar config
yes but things like nm applets and etc when click on them they appear in background of the window
I use wayland on my work daily driver --- for the only reason being that it handles mutliple screen resolutions better. I've done my head in over the years getting compositors to handle this and was done.. But the big downside is in screen sharing, screen recording and just some apps that don't play nice (especially like the global protect vpn client I need for work... but I've just decided to tunnel through a windows vm instead.....)
My work machine is not something I want to go chopping and changing with but yeah-- occasionally if doing a big presentation I may shut down the second monitor (not enough room for 2 * 4k monitors) and switch back to xorg.
My other machine is also a work machine. It's a dedicated DAW.. Ardour/Mixbus is still
Maybe I'll wait a while and see if hyprland can cut it, when it's more stable.
Just a question: why does reducing one key press make a window manager looker "better"?
What's wrong with an extra key if you want to specify where the new window is going to appear?
Wait, why would it be the compositor's job to handle drawing tablets anyways? Shouldn't it be compositor-agnostic? Same with keybinds, why is it the compositor's job? Shouldn't that be part of wayland, or just a separate program? Is the compositor just responsible for way way more than a window manager on X? If that's true, is that a flaw of Wayland that's gonna be fixed or is it a design decision?
12:15 so i take it not even sysrq REISUB works?
I HIGHLY recommend hyprshot for screenshots
I wish the dev would write tutorial / documentation how to write compositor with wlroots, there are mostly no docs how to do so, and everything is like "read our code, deal with it". Not to mention creating custom renderer
So it’s sway ++? I could give it a shot
Is there a compositor that supports pointy or Lys français styled window corners? Like Barocke decor.
I just started using hyprland about a week ago and its amazing, however the battery consumption isnt. Hyprland is still the best wm for beginners imo, i tried to start with fluxbox and then openbox but they always got messed up for me, Hyprland hasnt broken yet and im pretty happy with my config :)
tiling window manager for beginners???
I am working on optimization on -git and during the last 2 days there has been a chonker of commits to address performance. You should try that :)
Staged for 0.28.0, so you can also wait for that, but some people report 3x gpu usage improvements and idle cpu usage drop of around 20%
Nah beginners should stay away from Wayland outside of gnome or KDE, especially hyprland with it's weird hard dependency on systemd
@@darthvader1191 i tried i3 and bspwm but i couldnt get it to work
@@vaxryy thats awesome
They're called "F" keys because of what you say when your Numpad doesn't work.
Can we pls all agree that X has had it all from the very start?
Yea
X also has the thing where basically any program running could keylog any other program. Or other 69420 security black holes, which just cannot be solved.
Do we really want to have a windowing system then fucking windows?
@@no_name4796 "X also has the thing where basically any program running could keylog any other program."
sounds like a feature. id love to have some windows interract with others. like overlays and screen recorders
if you install a program that keylogs stuff its mostly your fault. i mean, software installed on your machine can do worse things than just keylogging if they felt like it lmao. youre blaming x for something that isnt even the main issue
I am using Hyprland now, migrating from KDE. I definitely like Hyprland better, despite the quirks. And I was able to launch Steam and play my favourite game, Path of Exile. Mostely playable, though sometimes I get stutter on the frames. Then again, I am playing this on an old laptop. It was top of the line when I purchased it 8 years ago, but now it is starting to show its age. 32 Gigs of RAM is nothing today.
I'm confused about bindings on this. A common thing I expect is Alt + Tab to swap focus between programs. How is that handled?
I had the mouse-snapping problem on Ark as well and I think Valheim
You can use submap to pass all keys to specific app only.
As someone who plays some precision demanding games (osu!, geometry dash, etc), wayland wasn't an option until i got a high refresh rate display. The input delay was just too much it was absolutely unplayable for me. I was waiting for the implementation of the tearing control protocol, but the MR was just not beeing touch at all and nothing was moving in the wlroot side. I do think the merge of tearing control will probably help a lot of 60hz gamers to try to switch to wlroot-based compositors and try out wayland, i hope it lands soon !
YES! 60fps gaming is a joke on wayland. who tf decided that it's a good idea to not let people have their tearing??
@@シミズルリ sane developers. Tearing is not fun, and it's something that other platforms have been handling just fine - Android doesn't tear, Windows only tears when gaming, and macOS doesn't tear *at all*.
Wayland does what's sane, and fit the most with their design - commit-based and frame-perfect compositing. Tearing is mostly waiting on other improvements in the stack, specifically your in-kernel GPU drivers.
I do hope the tearing protocol is more widely supported, even if just for fullscreen windows. That, at least, would give a decent balance of a tear-free experience and latency.
Hyperland may be a good future option for next 3-5 years, especially if hyperland is as hackable as xmonad or dwm, and has no preinstalled bs features.
There is no beauty about disabling features, transitions and transformations. The coolest stuff, to my opinion, is to write and tweak your own designs for the twm.
If there will be clean and well documented version of the hyperland, alongside with plug and play version I think that must be a banger.
if qtile was written in c++ I'd probably use it over hyprland since that's more customizable I've heard
@Brodie Robertson is there any way I can get you confit and setup up for hyprland. (Can figure out how to do this myself for the life of me)
If I ever find a jackpot winning lottery ticket and can therefore afford large 4K monitors, I'll probably give a tiling WM some time, but other than that, I'm damn near always using full screen, so it's just not worth the effort (after 30 years of floating).
I had a issue with hyprland and pipewire. When i watch videos via firefox, the audio plays normally. But when i playing games(csgo etc), the audio got chopped, it plays 1 second of audio, then no sound for 5 or 10 seconds. Don't know why.
I've daily driven hyprland for a couple months now and all I can say is that it's flawless. Every problem I had was my fault and now it's completely untouchable by competitors, imo.
These are some of the main reasons why I don't use Wayland at all, video production is still not stable enough on Wayland for me to use and I also have a NVIDIA card and as we all know that Wayland support on NVIDIA is hit or miss. So until we have a good way to capture screens and windows and video editors that don't crash as often on Wayland it's Xorg/X11 for me!
it is nice until I start using electron apps and ibus (some electron apps cannot work with flags, some crack after few update ...)
my wayland issue is that I can't put qt undockables (like "Scenes", "Sources" in obs studio) back into window
Hyperland seams nice but I wonder if it will support all my applications? Tex LinkStage3 branch of FreeCAD (Appimage) and KiCAD?
Hyprland works well even on reasonably low performance hardware (Core 2 Duo, 4 GB DDR2, AMD graphics card). There are a few issues though. The Dolphin file manager doesn't show the file and folder icons, and since the thing is running on NixOS I don't know how to fix this - the general consensus is that I need to add QT5, somehow. A mix of Hyprland problems and myself not knowing how to configure NixOS properly.
Is there a tiling desktop that "just works" without having to create yet another 100 lines config file?
technically dwm?
Sway's default config is your best bet but pretty much everything you're going to want to configure. Maybe check out the configs that Arco Linux provides
The screen having the zoomies was an issue in Elite Dangerous too, when I'd go to the map and try to right click spin the camera or pan around with the mouse, it'd spin at mach 9 or snap to the edge of the map. I think I fixed it by changing an option in game about which mouse I wanted to use, something about either the systems mouse or a rendered mouse.
I've been running into issues with Hyprland - especially with SDL games, so I switched back to sway a while back.
Not a big fan of tiling window managers, the openbox wayland alternative labwc interested me but it lacks one of the most important features of openbox, smart window placement, so it will just place windows directly on top of each other, so you still don't have many options when it comes to wayland if you don't like tiling window managers and want smart window placement, your only option is plasma, we really need lxqt and xfce to support wayland, I suspect lxqt will get there before xfce does.
On Linux I always seem to end back to WindowMaker, there just isn't any better GUI out there.
You absolutely should switch to Hyprland. It's absolutely amazing
I have been using hyprland for a few months now and I want tab groups and stacking like how i3 does it. That was one of the reasons I didn't switch to it for so long, but I eventually decided I would just use it and wait.
Hyperland is running on my system even with official nvidia drivers on arch :O
Do i already benefit from Nvidia's support in wlroots?
Atm I'm only held back because nvidia support on wayland is lacking. I really love all the eye candy on this wm.
Also qt theming on hyprland doesn't work for me. I use qt5ct but it always complains about that system variable though it is set and works fine on other WMs ¯\_(ツ)_/¯
I haven't done much research but why are you using dmenu instead of bemenu? you did a video on it and it is wayland native so why dmenu?
you should do this challange. you should use nixos as a daily driver for a month and see how it goes.
I've heard FAR TOO MANY complaints against wayland and that it is STILL NOT STABLE---- but I LOVE this dynamic tling window manager... and would love to run this-- ALSO-- I have one eye now and am old- so I HATE command line crap... how close is this to being GUI ONLY????? (not knocking CL or anything like that- as many accuse me of-- I just don't use it because it BOTHERS MY ONE GOOD EYE).. I absolutley HATE key anything... other than normal typing... PERIOD.. so- how close is this to GUI ONLY???
id like to try it, but haven’t been able to on arch with nvidia for months after a million different fixes
:O Sewerslvt fan!!
Yeah unfortunately wayland is still unusable with nvidia hardware, despite what others say. Tons of crashes in software, xwayland flickering like crazy and repeating frames, egl xwayland fallback to software rendering (which means that applications such as firefox default to software rendering opengl, as if you have no graphics card at all), pipewire capture not working (for me at least), so I cant use most screen recording software.
Hyprland has a section about nvidia on how to workaround the flickering, however none of those options has worked for me.
I had to use Sol Does Tech's install script here on youtube. If you search "arch hyprland install" he comes in top 10 searches. Right now he's got four versions of install scripts. I checked the script and it turned out I don't know that much about arch and linux in general because I was did not install some libraries in order for hyprland to work.
I highly recommend his script!
Hyprland is really nice. I gave it a try, but I can't live without DWM/DWL's tags.
hyperlandr seems like a good choice for windows tilling but overall it doesn't is non-programmer friendly.
I’ve been using the nvidia-hidpi aur package and it’s working good so far. I haven’t tried video editing yet.
have been using KDE Wayland for a good while and I feel like games are a lot better on Wayland. On X11, if you want low latency, you disable compositing but then you have unavoidable tearing unless you use vsync in your games... Though, Wayland compositing on KDE is mostly indistinguishable in latency from X11 with compositing disabled. Also, gamescope does support Wayland yes... but it is an X11 compositor by default, unless you specify you want it to run a Wayland session. I don't know what makes it have less issues with cursor capture than XWayland but it does and it's basically necessary to play War Thunder.
Gamescope *is* a Wayland compositor, it just embeds an Xwayland instance. It gets the niceties that come from being a dedicated compositor purely for gaming, including input handling. Gamescope has absolutely no native X11 support, that's all done in Xwayland.
Set SDL_VIDEODRIVER=wayland if you want to run gamescope outside of Xwayland, if that's what you want.