File: file.png (135 KB, 1476x244)

135 KB PNG

I want to pick a distro that will work the most seamlessly with KiCAD. KiCAD flat-out isn't fully supported by Wayland or it's X-Wayland compatibility layer, and Xorg is only getting more deprecated. KiCAD officially supported Debian, Ubuntu, and Fedora, but none of those are shipping with an option for Xlibre. As far as I can tell, I should be aiming for a derivative of one of these three distros, with the same package manager and all that, such that it's most likely to be bug-free. Is Devuan my best choice? There's been some rumours of Debian's apt and other core utilities getting rewritten in rust and still missing features that were in the original. Do I just use Fedora with third-party Xlibre, or are the team behind Fedora likely to end up making that incompatible?

I've been on Arch for a year, but there's like three somewhat different builds of it in across the aur and flatpak and support won't talk to you unless you're in the 3 supported distros.

Planning on setting up Gentoo soon and will likely change from Nvidia to AMD GPU some time after. Will there be any significant issues in regards to having to rebuild a whole load of shit related to the graphics drivers or am I just overthinking it? Don't have any experience in gentoo hence why I'm asking.

>>107726786
isn't it safe to always assume a change in graphics card, especially from N to AMD brings about complications ?
cant say i have any experience with gentoo but i always just backed up important files and do a clean OS install alongside swapping out the GPU for ease of setup.

>>107726804
On Arch when I had to switch before it was a matter of just updating the packages from what I remember. Just wondering if the process for gentoo is more involved due to the nature of the distro, compared to just deleting and installing a handful of packages.

>old thread is on page 11
What's the video editor situation look like in the year of our flying spaghetti monster 2026?
I need one program to add literal text^1 to like 30 frames of an existing MP4 video. I tried shotcut and it and doesn't work. I can't the video or something I don't understand what it's doing because it doesn't make a frame by frame preview. I tried avidemux and it's just ffmpeg with a GUI. Openshot has no installation candidate so it doesn't exist to me. And I tried to install kdenlive because that was the best in 2006, but it wants to install fucking wayland so I can't use it on my X and ALSA-only, no systemd builds.
^1 I tried doing frame by frame in the GIMP already, and then gluing it all back together with ffmpeg, and it came out like shit because I was fighting compression removing data from non keyframes.
If there's a way to do it with ffmpeg I could almost make do, but I need it shifted by like 20 pixels a frame in a random direction (following motions) which is why I was going to a GUI tool.

>>107726648
computer related magazines still exist? i only bought them back in the day because they came with hundreds of megs of stuff on cd's which would have otherwise taken days to download

File: nvidia trixie.jpg (122 KB, 1280x720)

122 KB JPG

Why is the NVIDIA driver in Debian so outdated? Almost everything in Debian 13 is from 2025, including Mesa, so you'd think the NVIDIA drivers would be a little bit more recent; yet Debian 13 is using the 550 driver EVEN IN THE SID BRANCH, despite 550 being from god damn 2024...

>>107727335
Bro I think your solution is to install Windows XP and download Sony Vegas Pro 8.0 lol

>>107727474
Anon, that's a 1080. Pretty sure you have to use the older NIGVIDIA driver set.

>>107726786
it shouldn't be difficult, add in the support for your new card ahead of time, switch the cards, then remove the nvidia-specific stuff and it should be seamless.
i haven't switched from nvidia to amd in gentoo specifically, but it shouldn't be much different to switching amd cards which i've done, like moving from radeonsi to amdgpu, check your VIDEO_CARDS and LLVM_TARGETS/AMDGPU_TARGETS variables, adjust any relevant use flags (couldn't say which since i haven't use an nvidia card in nearly 15 years)
few packages are built for a specific gpu, so it's less of a deal vs. making a major cpu change (depending on how generic/specific you build your binaries, i think most people build their binaries specifically for their cpu given it's gentoo and you may as well)

>>107727335
>but it wants to install fucking wayland so I can't use it on my X and ALSA-only, no systemd builds.
couldn't you just use a nested compositor, i think valve's gamescope can do single window wayland applications on X
and then isolate systemd in a container or something
most of the container managers i've seen require systemd but i'm pretty sure all you actually need is kernel support for user namespaces so i think if necessary you could do it in bash if there isn't a non-systemd based one

>>107727487
Not my screenshot; I just went on Google Images and chose the most attention-grabbing result for "nvidia debian".

>>107727335
Blender.

File: CONFIG_LOCALVERSION.jpg (23 KB, 751x298)

23 KB JPG

>>107727474
Point releases are supposed to be outdated, that's "stability".
>>107726786
>having to rebuild a whole load of shit
idk about the rest of the graphics stack but what goes for the kernel build, it greatly depends on YOU. It's you who has to go thru the hundreds if not thousands of options and turn off anything that's useless. Compiling support for everything imaginable results in a kernel build that can take a whole day instead of doing a tailored build that compiles in 5-15 minutes.
But don't think of it as a Gentoo thing, think of it as a custom software part tailored for your specific hardware. I do these custom kernel configurations whenever I get a new PC, regardless the Linux distro.

>>107727541
Point releases are meant to BECOME outdated, and Debian 13 was otherwise full of relatively new software when it came out. If the AMD drivers (aka Mesa) were fairly new, and ARE very new if you use the backports, why are the NVIDIA drivers still so god damn old?

>>107727561
Maybe check the unstable repo?

File: Linux_Format_Annual_Volum(...).jpg (3.39 MB, 2000x2588)

3.39 MB JPG

>>107727460
>computer related magazines still exist? i only bought them back in the day because they came with hundreds of megs of stuff on cd's which would have otherwise taken days to download
They still exist. Recent publications too.

Reposting >>107726813
> Linux_Format_Annual_Volume_9_page_40__2026.jpg
> >>107726655
> Magazine from:
> https://web.archive.org/web/20251217225259/https://megalodon.jp/2025-1201-1116-51/https://archive.is:443/2025.11.30-050127/https://www.magazinesdirect.com/us/single-issues/linux-format
>
> Here's another image from it. What I learned from this print media: ChromeOS (proprietary Google software/OS) is based on FOSS ChromiumOS, which is based on Gentoo.
>
> (Photography info. Best to take photos of a magazine with either a scanner, which is cumbersome, or a camera which does great in low-light environments. Taking a photo with flash on results in pic related glare from the glossy paper; you can't see the text "Chevrolet" on the red car because the glossy glare is in the way. Editing: ratio is 8.5 by 11.)

That statement about Gentoo is on page 63. I wonder if some of the images in this magazine are AI-generated. (I was recently reading some other physical magazine; it had a story about a guy dying of ALS, and it had AI-generated images of his in it.)

>>107727594
Like I said, even in Debian Sid you're still only getting the 550 driver, just like Debian Stable. Debian Experimental does have the 555 driver but that's still old as hell.

>>107727474
>Almost everything in Debian 13 is from 2025
...Because debian 13 is from 2025?

File: 550 series.png (92 KB, 731x361)

92 KB PNG

>>107727662
Yeah, so why is it using the 550 series of drivers (which don't even work on the 50xx GPU's) when the 580 drivers already existed by the time Debian 13 launched? Maybe 550 is fine for the stable branch, but 580 REALLY needs to be in the backports and sid.

>>107727674
because to debian family distros stability means pick a package version irrespective of what the actual developers working on the project consider to be stable, bugfree, and atomically versioned or what users would need, and literally never update it aside from having volunteers who are at most vaguely familiar with the package codebase hackport security fixes back onto it
they're meant for the linux version of the retards who run decades EOL windows machines because they built their entire business on some shitty proprietary middleware or drivers by a company that went defunct in the 90s that only runs on 1 version of windows ME, they never had the source code, and refuse to even consider replacing it until it's too late and the computer finally dies or is somehow exposed to the network

I'm using proaudio I guess on pipewire, my problem is that I thought it was the same as alsa hw output (one audio source only, no resampling raw output etc) but I can play audio from multiple sources simultaneously so I know that's not what's being replicated. Am I doing something wrong? What even is proaudio then?

>>107727819
>irrespective of what the actual developers working on the project consider to be stable, bugfree, and atomically versioned or what users would need
The problem is that the software world jumped into the fucking void around debian. Not the other way around.
When you release a major point version you should consider it stable and backport to it for like 5 years. But node and shit broke that. That's why java software still targets 1.8, the actual stable baseline version.
But meanwhile shitters decided that every point version can break API and ABI compatibility breaking semver and and also meaning that each new version needs new debian release with a new build stack done for it.

>>107727918
>But meanwhile shitters decided that every point version can break API and ABI compatibility breaking semver and and also meaning that each new version needs new debian release with a new build stack done for it.
while arbitrary API breakages are annoying as fuck (fuck python in particular, even when they don't change anything it still breaks) i genuinely think ABI breakages at least should be encouraged
windows wouldn't be half the mess it is today if they hard broke and fucked over all the enterprise shitware using undefined/undocumented ABI dependent behavior
aside from one minor breakage in preview code from 2022 their C++ ABI literally doesn't change and hasn't since XP despite the library not even supporting it anymore
there's fuckloads of bugs that wouldn't break proper to specification API usage if the applications were just recompiled that cannot be fixed because muh proprietary enterprise shitware just has to keep running on the latest version
if they had intentionally broke their ABIs from the start it would have encouraged a lot better development and dependency management practice

if you can't recompile or have access to someone who can that indicates a potential long term problem