“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
Schrödinger’s nerd
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
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.
There’s a third kind that uses some weird magic to be both at the same time.
Please add back spacebar heating bug.
