Have you checked these all on winehq? It would be nice for them to be reported with logs if they haven’t already.
Garmin Express for example is on there with some discussion here: https://appdb.winehq.org/objectManager.php?sClass=version&iId=40213
It might not help in the short term, but even just having logs for more broken programs could be useful for the wine project.
Did you grep that log file for ‘amdgpu’?
I wonder if the error is related to this: https://github.com/NixOS/nixpkgs/issues/229108
I’m still using x11 on my system. Maybe try that and see if it works?
No, I haven’t seen anything like that. That’s odd.
I’ve had those errors on my system for years. I never thought that they were NixOS specific. I just assumed something to do with a buggy firmware:
Enabled 4 GPEs in block 00 to 1F
ACPI Error: Aborting method \_SB.PCI0.GPP2.PTXH.RHUB.POT3._PLD due to previous error (AE_AML_UNINITIALIZED_ELEMENT) (20240322/psparse-529)
[x~20]
ACPI: PCI Root Bridge [PCI0] (domain 0000 [bus 00-ff])
I don’t notice any ill-effects from them, so it may be a red herring. I have a:
$ < /sys/devices/virtual/dmi/id/board_name
ROG STRIX B450-F GAMING
with a 5900X.
I don’t usually see as many prints as you have there, but it’s quite a few, and the number seems to vary (grow?) over time. I keep meaning to investigate it, but haven’t got around to it.
I think you should keep looking in your logs for other problems. If you can share the full log I’d be happy to take a look.
The original error actually makes it sound like there’s a partition on hda that’s bigger than hda itself.
It probably becomes CPU limited with those other compression algorithms.
You could use something like atop to find the bottleneck.
Have you checked all the ethernet links are actually connected at 1G and not 100M?
I was expecting something in the article to back it up, like sales figures, but I couldn’t find anything.
popular
[citation needed]
Does it actually tell you the results? I’m curious how they score your driving, and how effective it is. The scariest things I see on the road are things like:
I don’t see how they’d measure how safe a driver you are.
Perhaps it’s just that people are more careful when they know they’re being monitored, and safe drivers are more likely to opt in?
I’d probably:
systemctl suspendWhen the screen fails to wake, are you able to get it back by powering it off, or by unplugging it? Is it X or wayland?
Oh yeah, that was pretty much the point I was trying to make too.
Of course not, but you have to either trust your users to some extent or give them a system that’s locked down to the point of hindering them.
There’s actually not that much autotools jank, really. There’s configure.ac and a few Makefile.am. The CMakeLists.txt in the root is bigger than any of those files.
There’s also some stuff from autotools archive in m4/. IMO that’s a bad practice and we should instead be referencing them as a build dependencies.
I’m not convinced this backdoor would have been significantly more difficult to hide in the cmake code.
What is ‘unallowed software’? A shell script the user wrote? Something they downloaded and compiled?
Limiting that seems fundamentally at odds with FOSS.
Emacs I assume.
cmake compiles to makefiles as well (it just also supports some other backends). I’m not sure why that matters though. In both cases the makefile is generated.
If you stop shipping autotools generated artefacts in your tarballs, things will be a lot simpler.
Weirdly enough the malicious code does look eerily similar to the benign code, because both are unnecessarily obfuscated.
This is not a human written or readable file you’re talking about. It’s a generated script.
As the other user suggested, you probably just need to mount the root subvolume somewhere and run it on that.
It’s not as stupid as this blog post makes it sound. This was a hashing function that was intentionally taking the end of the path as the most significant part. This just impacts the order of objects in a pack file, and the size of the compression window needed to compress it.
It’s not actually mistaking one file for another, and their proposed solution is not better in all situations.