“Why doesn’t this just work I never had this problem on Windows!!” leaves no necessary information to troubleshoot
Vs.
“I have this specific and obscure workflow I use with this one package nobody has heard of, I perform XYZ action and after I ran pacman -Syu I’m seeing that the application is segfaulting and leading to this call trace…”
Five page dump of dmesg
“I mapped this to line 748 of the Linux-Zen kernel source file can somebody help explain how I can work around this?”
No responses for eternity, thread archived
The answer is on a 5+ year old YouTube video in a different language than you need half the time that is presented by a 10 yr. old.
Most probably in Hindi too
10 yr olds are really talented these days.
Works for me. You must just suck
experience helps. after some time, you will suckless :)
Pretty much Wayland and X11 situation
Or Nvidia vs AMD, but they go quite hand in hand
ProtonDB comments… at the very least say if you’re using an nvidia or AMD card ffs
Seriously though. Seen people install Mint, and run non-Linux games through steam with no issues. I had to troubleshoot for about 8 hours so kind of make them run.
Hardware is a big factor in this. Mint in particular is a stable distro based on the ubuntu LTS so it’s slow to get new kernels and you need a ppa to get a fresher mesa install and this is essential for newer amd hardware. Conversely if you’re on a rolling bleeding edge distro and you rely on nvidia and their closed drivers then you’re often one update away from breaking them.
Me, installimg a few Flatpak apps, having them work for a while then suddenly break for no apparent reason, spend an enture day trying to fix them, only for an update acouple days later to fix it.
There’s a third kind that uses some weird magic to be both at the same time.
Please add back spacebar heating bug.
Feature*
this you?
Schrödinger’s nerd
There are 10 kinds of people who understand binary.
Those that do And those that don’t
The two hardest problems in programming are cache invalidation, naming things, and off by one errors.
This was fixed ages ago, but you are using Debian because it is “stable” and thus software from ages ago and don’t have the fix.
The best part is when I check to see what exact version of the package I really have and despite it being old, it’s the version a month after the one where the bug was fixed but I’m still getting the bug so I guess I’ll go fuck myself then.
