• 6 Posts
  • 775 Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle


  • Post specs on the KVM. I think to do what you’re asking it to do it needs an EDID stand-in/passthrough to be able to explain the capabilities of the monitor and “hold” it’s place when inactive instead of just sending info that’s in standby or something.

    I believe what’s happening is the signal to the cable is cut off from the monitor, making your GPU think it’s been unplugged, and there is no event to say “hey, I’m plugged back in”.

    Confirm a few things:

    1. Switch to Windows, wait maybe 15s, then switch back and see if the display is still working.
    2. Unplug and replug the display cable to the KVM after the display stops outputting and see if it comes back.



  • So desktops don’t work like laptops in this sense.

    On a laptop, the bus for the video output ports can be connected to one or both GPUs, and the software does the graphics switching or offloading.

    On a desktop, there is no consolidated bus between the PCIe card and the onboard graphics, so you can’t switch between which GPU is rendering what on hardware alone. It’s the whole display that is rendered on the device you’re plugged into.

    Windows does have some sort of offloading utility that allows for this i believe, but I’ve never used it so don’t know how well it works.

    On Linux, your display server (X or Wayland) needs to address one GPU at a time to render things.

    You can totally use both GPUs with multiple monitors, but I think that’s defeating the purpose you have in mind.





  • It really depends on what you intend to develop in, but I can say containers aren’t the way to go whatsoever.

    Every gaming SDK or IDE I’m aware of has their own version of sandboxed environments. You just start a project, clone it, then let their package management tooling do the rest.

    Maybe if you explain a bit more about your approach you could get more constructive answers.


  • As someone who works with multiple projects who have had to beg and plead to get broken packages taken down, I can confidently assert that it is.

    They’ve gotten too popular too fast, and dozens of projects have had similar experiences to OBS.

    Some issues we’ve dealth with in the past year:

    • unmaintained community package which included libraries that made our package vulnerable and was tripping up static scanners
    • one package unpublished due to a complaint from a completely unrelated person
    • spammed and suspect versions of our packages being published with shady blobs that aren’t part of our project

    There’s plenty more. There just isn’t any kind of moderation, and there needs to be. Regardless of their original intent, it’s now become too big to just let go. Similar things have happened over the years with almost every maintained public package repository: gems, npm, pypi…etc.

    Now it’s time for the Flathub folks to step up and do some moderation to prevent worse things from happening. The minimum they could do is add a flag for official packages that are confirmed to be from the proper sources, but that requires a bit of effort on their part.


  • There’s a ton, but I still don’t find them very useful. The real thing I find dumb is the hardware acceleration for 95% of use-cases. Unless you’re just sitting and watching scrolling output, I don’t see the need to sacrifice efficiency for faster rendering, and even then, I can’t say I’ve had many issues with standard terms either.

    Ghostty is the one getting the most hype recently, and it’s alright. It feels more put together than Kitty or Alacritty. Rio is mostly a toy with a bunch of goofy visual effects. Honestly can’t say any of them have features that improve my workflow over just having a bunch of named windows all over the place though.



  • Cachy - you might have some extra hoops to jump through. The performance difference is negligible for just desktop usage.

    PopOS - no real benefit unless you’re running Nvidia, and then it’s only for the moderately useful graphics switching stuff.

    You sound like you want Fedora for simplicity’s sake, honestly. There’s really no other major performance differences between desktop distros. Any tunings that one has you can just apply to another if you know their benefits.