I’m in Canada, and I sent a cbc.ca news link to someone in instagram chat. It showed a preview of the post with a picture and summary, but when the link was clicked it went to a page that said:

People in Canada can’t view this content.

Content from news publications can’t be viewed in Canada in response to Canadian government legislation.

This seems like a stupid poll, and a stupid spin to put on it. Surely the 26% are just people who would never vote Liberal?

And for the rest of the results, it’s going to be almost entirely down to name recognition, save for Trudeau.

Diplomats the world over are thinking about how cheap it is to bribe trump.

I think graphene does this by default now? Like if you don’t unlock it for 24 hours it’ll reboot.

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.

Do you like the idea of all our payments for everything going through a private duopoly who takes a cut of every transaction?

We don’t have a digital option that’s open or private.

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.

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.

I guess at the 2028 Olympics they’ll be jumping on the AI bandwagon.

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:

• distracted driving
• tailgating
• lack of awareness

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?

There’s a Competition Bureau? In Canada?

I’d probably:

1. make sure it can be reliably reproduced using something like systemctl suspend
2. try swapping the cables and see if it still happens on the same screen, or the same port
3. look at journald/dmesg output for the period from suspend to resume

When 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?