it even holds up well. the remoteness denotes a lack of tech that isnt too far out of place today.
It holds up so well that I barely even thought about the era until Joel shows up on the street in NYC.
it even holds up well. the remoteness denotes a lack of tech that isnt too far out of place today.
It holds up so well that I barely even thought about the era until Joel shows up on the street in NYC.
Yeah, I would love to stop getting potato quality videos on MMS, but not enough to install a proprietary app. I’ll just have to create matrix accounts for more people.
I can’t vouch for it as a music player, but it’s what I use for videos when I can’t get on a bigger screen. It’s nothing like the desktop app, so you might want to give it a try.
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.
His brain is now empty except for stand-up routines from 90s late night TV.
I love that you have a very specific and arguably moral crime in mind, and it inspired this post.
Chris LaCivita, a top Trump campaign adviser, added in a separate statement that the cemetery official was “a disgrace and does not deserve to represent the hollowed grounds of Arlington National Cemetery.”
How could they resist putting a [sic] in there?
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.
At least you still have ribs. When I do interesting stuff with the oven it usually involves my food becoming charcoal.
I’m not afraid of scissors, but I’m very afraid of my victorinox knife.
Am I just failing to use that site properly, or is it missing a ton of stuff in ‘replays’ that was available live?
I feel like the CBC had a better version of this thing 12 years ago.
I guess at the 2028 Olympics they’ll be jumping on the AI bandwagon.
You’re suggesting people not be able to run software in kernel mode on their own systems.
I would never run kernel mode anti-cheat, but going down this road will lead to hardware attestation and the end of open computing for anything with online services.
Why would there be one answer to this? I’d probably use all the available levels depending on the situation, in the same way I’d use --word-diff
or -b
in git
when I need help understanding a complex change.
The original error actually makes it sound like there’s a partition on hda that’s bigger than hda itself.
That explains why we never hear about either of them anymore.
It probably becomes CPU limited with those other compression algorithms.
You could use something like atop
to find the bottleneck.
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.