unique_hemp

joined 1 year ago
[–] unique_hemp@discuss.tchncs.de 1 points 15 hours 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.

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

There's nothing to prevent data races. I myself have fallen into the trap of using the same list from multiple threads.

[–] unique_hemp@discuss.tchncs.de 22 points 1 month ago

There's a difference between source available and open source. For example, actually being allowed to distribute modified versions is pretty damn important:

Restrictions

  • No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form.
  • No Forking: You may not create, maintain, or distribute a forked version of the software.
  • Official Distribution: Only the maintainers of the official repository are allowed to distribute the software and its modifications.
[–] unique_hemp@discuss.tchncs.de 4 points 3 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 1 points 3 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 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 1 points 7 months ago

Maybe the kernel version on Debian lacks hardware support fixes?

[–] unique_hemp@discuss.tchncs.de 2 points 8 months ago

I saw a comment from an nvidia dev somewhere that XWayland support is enough to resolve the flickering, but compositor support is needed for best performance.

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

Maybe if your games are Wayland native or you're still running the 535 driver? I saw fbdev=1 as a workaround, but that made things very jello-y.

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

Plasma 6 X11, 550 proprietary driver.

233
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 ›