edinbruh

joined 2 years ago
[–] [email protected] 33 points 1 week ago (7 children)

Orcas will also jump on the beach to catch a moose and then squirm back into the water

[–] [email protected] 8 points 1 week ago

Dr. Pepper is actually Kurisu Makise

[–] [email protected] 1 points 1 week ago

GNOME tries to set a high standard of polishedness, look-and-feel, and simplicity of design. This is not wrong and makes GNOME good looking and easy to use for a less savvy user. But this has some drawbacks.

For a more savvy user that knows what he wants to do, the simplistic interface gets in the way and wastes time. In contrast KDE Will hold your hand less, and get less in your way. Though, when you drop these requirements GNOME becomes very pleasant to use, especially on laptops, which is why I use it on my laptop.

Another drawback is that GNOME developers will not ship something that doesn't fig their standards of usability. This adds to the polishing, but it means you will miss out on features, for reasons like "the options in the settings would be confusing for the users" until they are satisfied. E.G.: fractional scaling and vrr. On the other hand, KDE Will ship things that are less polished, but at least you have it.

Also some applications will work suboptimally on GNOME with Wayland, because of client side decorations.

[–] [email protected] 8 points 1 week ago (1 children)

Pigeons' nests aren't made to keep stuff inside, they just need to prevent the eggs from rolling off.

[–] [email protected] 6 points 1 week ago (2 children)

Hi, I'm hijacking this thread to answer your other questions. Xpadneo is the correct answer, it will work with any desktop environment (xorg or Wayland) and all reasonable distros. It's also the driver used by the steam deck, so go with that. But I suggest you read the troubleshooting section for two things: fixing input latency (if you experience it) and secure boot (more on that later).

I use both KDE and GNOME (on different computers, for different reasons), but in general I suggest you use KDE.

Now I will explain secure boot:

You can use third party drivers with secure boot on any distro that supports secure boot. Here's how it works. Secure boot means that the bios checks that the kernel and requires that the kernel checks that all kernel drivers are signed with a key that it recognizes.

Now, either using a second bootloader (like redhat's shim) signed by Microsoft, or either directly getting Microsoft's signature, you get secure boot support on distros like Fedora or Ubuntu. So your kernel and all your included drivers are signed by Fedora with a key they got from Microsoft.

Other drivers (like Nvidia's and this) aren't signed, so secure boot will not accept those. But, secure but supports MOKs (machine owner keys), which are keys for signing drivers that you manage yourself and you installed on your bios, and secure boot will accept drivers signed with those.

Now, external drivers can be installed using two systems: akmod (used mostly by Fedora and redhat derivatives) and dkms (used by anyone else). These two are not in conflict and will work on the same system at the same time, it's just preference. The Nvidia drivers you installed used akmod, xpadneo uses dkms.

Both these systems support setting up a key for signing, you should then register that key on your bios. When you installed your Nvidia drivers a little interface made by Fedora for those drivers helped you to set up your key for akmods, and now you can use any akmod driver with secure boot. You could always do it manually and you can do it on any distro, Fedora just adds the graphical interface.

To use xpadneo you need to do basically the same thing but for dkms, and you need to do it manually, it's very easy, the troubleshooting section should direct you here for instructions, you will recognize some of the steps of registering the key.

If you feel a little adventurous, you can find which key akmod uses, and set dkms to use the same, so you don't need to register another one.

Also, I strongly discourage this, but you can technically remove Microsoft's key and sign everything with your own key if you really hate Microsoft. Please please please don't do it, you will screw up and break your system badly, and it's also a lot of work. Places like datacenters and such do this. Because they want total control on what goes on those machines. Also they don't sign stuff on the machine themselves, but they sign on a more secure one and then deploy the signed stuff.

[–] [email protected] 6 points 2 weeks ago

The code for the peeler is stale, it stopped working three carrot seasons ago, but no one wants to rewrite the PeelerBladeRdge class.

[–] [email protected] 11 points 2 weeks ago* (last edited 2 weeks ago)

A quantum computer doesn't just calculate every possibility simultaneously, it's much more limited. It "calculates more things at once" in some cases.

Generally speaking, some things that are hard for a regular computer are easy quantum computers. So if an encryption algorithm is based on the difficulty of those things (e.g. RSA is based on the difficulty of factoring a semiprime number), and the thing is easy for a quantum computer (e.g. factoring a semiprime), then you could defeat the algorithm with a quantum computer.

How do you protect yourself? You base the algorithm on something that is difficult for both a regular and quantum computer, that's what post-quantum algorithms do.

But quantum computers have one last ace up their sleeve. There is a sure-fire algorithm (Grover's algorithm) to speed up any situation where you need to find an unknown value of a known length (in this case the secret key). To keep it simple, if to find the key a traditional computer would need N steps (because there are N possible keys), a quantum computer would need just √N, which is much less. Now, this sounds massive, and it is, but if you consider that with M bits there are 2^M keys, then if you just need to check √(2^M) keys, it's like using keys of M/2 bits, so to defend against this you just need to make the key twice as long.

Lastly, as a footnote: quantum computers can be faster than regular computers, but strictly speaking, regular computers are more powerful, that is to say they can do more things. We say that traditional computers are turing-complete, which means that they can compute anything that is computable, that is not the case for quantum computers, which means that some things (even easy things) that a computer can do, cannot be done on a quantum computer. For example, there is no way to implement regular expressions in quantum computers, it's impossible. I know regex look difficult, but in computation theory they are among the easiest things a computer can do.

Edit: one quick addition to the paragraph about Grover's algorithm. If a quantum computer really just tried all the solutions at once it would be much faster than that. It would be (may my professor forgive me for saying this) "like if it guessed the bits of the key one at a time and were right on the first try", so if you had your M bits key, you would need just M steps instead of the 2^(M/2) steps of Grover's algorithm (this is like the difference speed difference between "checking if a word is palindrome" and "calculating who will win a game of chess when using a perfect strategy"). A computer that works like that... doesn't (and probably will never) exist. But in literature they are called non-deterministic Turing machines. They would be powerful like a regular computer (not more) but unreasonably faster.

[–] [email protected] 6 points 2 weeks ago

mumble mumble mumble Helvetica Scenario mumble mumble

[–] [email protected] 3 points 3 weeks ago

I'm gonna cause him a Helvetica Scenario

[–] [email protected] 3 points 3 weeks ago (1 children)

First guess is "the Nile" second guess is "denial" , third guess is Sinai. Also, what the hell is that, an AI catcher?

[–] [email protected] 9 points 3 weeks ago

Depends. Generally English, unless they are "directed" to one specific person like the professor who's gonna grade it. But even then I might go with English anyway.

Oh I also use my language when I'm leaving an important warning to myself in a config file, like "this is needed because X! don't touch it! If you touch it do Y!"

[–] [email protected] 14 points 1 month ago
 
 

I'm using sunshine for remote gaming on my Linux PC. Because I use Wayland and don't have an Nvidia I use kmsgrab for capture (under the hood sunshine uses ffmpeg).

I have noticed that I can enter tty and kmsgrab will capture it as well. If it just captured after logging in my user I wouldn't be surprised, but it also captures the login screen.

I autostart it at login using my systemd user configuration (not systemwide) so it should just have my user's permission level. I get the same results if I put it in KDE's autostart section, so it's not a systemd thing.

Why does that work? Shouldn't you need special privileges to capture everything?

The installation instructions tells you to do sudo setcap -r $(readlink -f $(which sunshine)) is this the reason why it works? What does the command do exactly?

 

SOTTR can now run in proton-experimental (it used to crash due to a missing vulkan feature), but how does it compare to the native version?

Normally I would just use the native version, but got the game from epic, which doesn't provide the native build. So if I wanted to run native I would have to acquire the game from other sources (keep in mind that I own the game on epic), which is less than ideal. But I wouldn't do it if there's no advantage.

 

SOTTR can now run in proton-experimental (it used to crash due to a missing vulkan feature), but how does it compare to the native version?

Normally I would just use the native version, but got the game from epic, which doesn't provide the native build. So if I wanted to run native I would have to acquire the game from other sources (keep in mind that I own the game on epic), which is less than ideal. But I wouldn't do it if there's no advantage.

 

This is a short appreciation/user experience story. Tl;Dr I'm enjoying my time on linux

I have been using Linux for a while (gnome for a year with an Intel UHD gpu, and KDE for a couple of months on a recent AMD gpu), and till now there was no brightness slider. Moreover, I have used the same display with windows for several years and there was no slider as well.

As far as I know (I looked up online some years ago, but this info is sometimes hard to find) my display supports DDC/CI but doesn't expose brightness (haven't actually tried).

For some reason, about a week ago a brightness slider appeared on KDE but it didn't do anything. Yesterday while updating some unrelated stuff I noticed the slider again and moved it for shit and giggles, and the brightness actually changed...

I have several questions... and I don't even know which piece of software is responsible for this... but thanks

I have been using Linux on and off for several years, often alongside windows, but I have entirely switched to it (almost, I still have a windows PC that I use once in a while) about 16 months ago. I have to say that Linux does take a lot more effort in getting some things to work, but when everything goes smoothly it's sooo good, and improves every month.

In the span of a year my desktop experience has only got better. But the shock was when I booted up an Ubuntu 16.04 cd I had lying around to fix grub on a dual boot machine and it was barely usable. Now instead it's almost "plug and play". Plus Nvidia cards are getting more and more usable with every update, explicit sync is almost merged, and prime works fine already.

There won't be a year of the Linux desktop anytime soon (there's still too much that needs improvement), but the next years will definitely be exciting.

P.s.: does any of you know why display brightness works now?

 

I have a Nvidia gpu with the latest proprietary drivers, and I'm trying to play BAA from egs (using heroic) but physX doesn't work.

I have run the automatic winetricks (I don't know which ones because heroic doesn't tell) and I have tryed this also the environment variable PROTON_ENABLE_NVAPI=1, but it still doesn't run on the gpu, even if the message "no hardware physx detected" stopped showing.

And if hardware acceleration doesn't work, I get the same behaviour on arkham city, but the game runs at double the framerate, even if using the cpu. Would it be possible to get asylum to run like city? I have tried swapping some dlls but nothing.

 

I don't like my ssh keys being stored in plain sight, I also don't like having to type a passphrase to use them.

On windows, once you run ssh-add, the key is stored in a secure way and managed by some kind of session manager (source), at that point you can delete the key file and go about your life knowing that the key is safe and you won't need to type a password again.

I would like something similar on linux, like storing the key via libsecret as you do with git, so that you can access your servers without having a key in plain text.

I think it's possible to generate a key with a passphrase and have gnome-keyring or kwallet remember the passphrase, but it would be nicer to just securely store the key itself.

Can that be done?

 

I have a projector that needs limited rgb range, but for some reason (maybe a faulty hdmi-vga dongle) the intel driver selects full range. I want to force the limited rgb range when I plug the projector, but I need it set to auto normally, because my usual monitor needs full range.

I read this guide that explains how to use proptest to switch mode when in wayland. The problem is that running the command when the gnome session is open doesn't work and returns an error 243 (I can't find it in errno.h, but google says its EACCESS). The guide deals with this by launching the command with systemd before gdm starts, but as I said, I only want to force the limited range when using the projector.

I noticed that I can switch to a tty, set the range, and switch back to gnome while everything is still running and it works, which is my current "workaround", and I'd like to automate it. So I thought that there's a moment when gnome "takes control" of a screen where this can be set. I tried to use a udev rule to switch as soon as a monitor is plugged, but it exits with 243 as usual. I suspect gdm has a way to automate such things that might possibly work, but I can't find it, I only read about some xorg scripts.

Also, there's this issue that's being worked on. One of the commenters uses an udev rule as a work arount but it doesn't work for me.

 

When the jack is inserted the internal speakers stop making sound and the only analog out is the jack, as it's common on laptops. But I want to address the two analog output individually so that I can:

  • Still select the speakers when headphones are plugged
  • Have different sounds come from headphones and speaker
  • Mix them with carla or other audio software

My alsa/pipewire settings are all default, I'm on a thinkpad t480s with fedora 38. My sound card is an intel hd audio card, with a realtek ALC257 analog chip.

I tried disabling auto_mute and rising the volume from alsamixer but nothing happens. Then I switching pipewire to "pro audio" but it doesn't separate the analog outputs. I also tried setting the indep_hp hint from hdarackretask but it doesn't change anything.

The hint enables a new "independent hp" option in alsamixer, but it can only be enabled by the cli and it doesn't work either.

I can provide configuration files or other info if needed but since they are all pretty long I didn't include them in the post. Also because I didn't edit them so they are just fedora's default.

Thanks

 
 
 

Is there a way to apply a apply an opengl shader to the entire screen in either gnome or kde using Wayland? I know hyprland has something like that, but I don't use tiling WMs.

I have an ald projector that I mainly use for game streaming or jellyfin, that has misaligned RGB panels. This model in particular cannot be adjusted, you can only replace the prism assembly all together (which I have no intention of buying). But I have tested that shader that simply samples about one pixel to the left/right is enough to fix the problem almost entirely.

Also, it would be perfect if I could also pass to the shader a uniform sampler of an image file, that I need to perform some extra color corrections. The green color is weaker on some areas, and I have a picture to use as a mask of those areas.

view more: next ›