unique_hemp

joined 1 year ago

Tuxedo is violating Linux's licence - driver modules use the kernel and therefore have to be released under a compatible licence. That's all.

Barely, going to be 17°C again this week.

[–] unique_hemp@discuss.tchncs.de 5 points 4 months ago (1 children)

Make sure that port forwarding is actually working - on ProtonVPN the port allocated to you can change regularly and QBittorent's settings need to be updated accordingly. Easiest way to check is to click through your active torrents and check if any peer has the I (incoming) flag.

If you have not set up something like this, port forwarding is probably not working: https://github.com/mjmeli/qbittorrent-port-forward-gluetun-server

I would personally just run the plain script as a cronjob on the host though, to not rely on some random docker image.

[–] unique_hemp@discuss.tchncs.de 2 points 4 months ago (1 children)

Hmm, I might try to make that. Any particular feature you are looking for, or is just displaying all the events in a table good 'nuff?

[–] unique_hemp@discuss.tchncs.de 21 points 4 months ago

The MSYS2 environment on Windows uses pacman as well.

[–] unique_hemp@discuss.tchncs.de 2 points 5 months ago* (last edited 5 months ago) (1 children)

Some distros have editions with a WM (usually i3) as a default, yes. These editions tend to come with some basic config so it's more usable out of the box. But you can also install WMs side by side with DEs and then switch in the login manager (GDM, SDDM), just the same as you can install multiple DEs on a system. You could also install a headless version of a distro first and then install only the WM and whatever other tools you want on top of that. Basically all system settings can be changed through config files or CLI programs, for some things like audio and bluetooth there are good DE-independent settings programs like pavucontrol.

You can also replace the WM built into KDE (kwin) with i3, for example, but that's pretty messy, IMO.

As for advantages, WMs are usually very keyboard driven, you pretty much never have to touch the mouse. They also tend to be fairly light weight and use little RAM. My favourite i3 feature is that workspaces are per-monitor, so I could easily move multiple windows between monitors and not lose the way they are set up.

As for disadvantages, changing any system settings tends to be a research project, because there is no centralized solution, it's even worse than Windows in this regard. Personally this is the main reason I switched back to KDE from i3. I could also never get theming to work quite right.

[–] unique_hemp@discuss.tchncs.de 6 points 5 months ago (3 children)

WMs typically do not include stuff like a custom GUI for system settings and do not have a suite of GUI software associated with it (think Kate, Konsole, Dolphin etc) - it is just a piece of software for managing windows, you have to put the rest of the desktop together yourself.

[–] unique_hemp@discuss.tchncs.de 1 points 6 months ago

It's fine with the beta driver, so still not fine by default.

[–] unique_hemp@discuss.tchncs.de 2 points 6 months ago (1 children)

I've seen enough blurry software on Windows to know this is not quite true 😅

[–] unique_hemp@discuss.tchncs.de 5 points 6 months ago (1 children)

Native games need to add client side decorations to be usable on Wayland Gnome. Currently most games just run in XWayland.

[–] unique_hemp@discuss.tchncs.de 5 points 6 months ago (1 children)

The way I see it, GTK is really a framework for building cross-platform GUI apps. Then handling display server compatibility makes perfect sense to me.

If this was meant to be a dig at Wayland, I'm pretty sure GTK also needs explicit and direct support for X11, Windows and MacOS. It just already exists.

[–] unique_hemp@discuss.tchncs.de 3 points 6 months ago

I'm pretty sure Louis is just another recipient of FUTO's funding, not "the" other partner to this dude.

361
submitted 8 months ago* (last edited 8 months ago) by unique_hemp@discuss.tchncs.de to c/linux@lemmy.ml
 

Since nvidia drivers do not properly implement implicit sync, this protocol not existing is the root cause of flickering with nvidia graphics on Wayland. This MR being merged means that Wayland might finally be usable with nvidia graphics with the next driver release.

EDIT: Nvidia dev posted that support is planned in the 555 driver, with beta release planned for May 15: https://github.com/NVIDIA/egl-wayland/pull/104#issuecomment-2010292221

view more: next ›