Yesterday I posted a comment on X, that a police person had made about the occupation of Het Maagdenhuis in Amsterdam by pro-Palestinian "demonstrators" (who immediately upon entering the building started trashing it and spraying crap on the walls). During yesterday the comment quietly gained likes, the last low value I saw was this morning, 55.

After that it's exploded.
9,567 Views with over 550 likes. I'm dumbstruck. 😱😁

---

Grant
Darwin NT.

Updating to 25.04 breaks VB.

sudo rmmod kvm_amd kvm

fixed it for me.

sudo rmmod kvm_intel kvm

fixed it for the user on the forum where I found a question about the problem. That user was on Fedora It seems problem is since kernel 6.12.something.

Today's the 19th anniversary of me being your dominator. Uhm no.🤔

Moderator! 😅
Although I do use the anonymous account for now. May at one time switch back again as it feels empty.

What do you think? 😘

Let me be the first one to post sympathy Congratulations on 19 years of babysitting moderating our posts.

Today's Inspirational Quote:
"A woman has the last word in any argument. Anything a man says after that is the beginning of a new argument."

~ Author Unknown

Has anyone heard from or contacted Richard Hselgrove in the past 2 weeks?
People ask me if I know what happened to him, but all I can say is what I heard from someone else in April.

Not directly but he has picked up some testing tasks from CPDN on at least one of his machines this week.

Just noticed, some projects use 17:59 for example to denote times in the task display in the manager, others 05:59 PM. My first thought was a difference between BOINC versions but no, it seems to be the projects' choice.

It's not based on the system's time format settings?

---

Grant
Darwin NT.

In reply to Grant (SSSF)'s message of 14 May 2025:

It's not based on the system's time format settings?

You are right. It was only the Windows VM that didn't use 24 hour format. Only running two projects at the moment and didn't have tasks from both on same machine to check.

Linus Tech Tips calculated the digits on pi to 300 trillion digits.
See how they did it in https://www.youtube.com/watch?v=BD-AJwqzWsU

I have heard back about Richard, he's alive and doing all right.

In reply to Jord's message of 19 May 2025:

I have heard back about Richard, he's alive and doing all right.

Gald to hear that.
I was beginning to worry.

---

Grant
Darwin NT.

Interestingly, I downloaded the daily build of Xubuntu 25.10 Followed my usual steps to build latest alpha of BOINC from source. It failed at the make stage. A couple of weeks of updates and without doing anything differently, it installed first time when I tried it today.

This gets round the problem of the snap install of 8.3.0 updating daily and it will update automagically after 13 days, closing down BOINC to do so. Now I can update when I choose.

Has everyone forgotten how to drive? Or all they all texting?

In reply to Gary Charpentier's message of 24 May 2025:

Has everyone forgotten how to drive? Or all they all texting?

Both?
Even when not on their phone people are either driving it like they stole it, or driving like little old ladies on a Sunday afternoon in a blizzard.
Just driving normally seems to be in the minority these days.

---

Grant
Darwin NT.

Just realised that on LHC@home the massively excessive time remaining estimates are because the time remaining is CPU time and not actual time which with 5 cores crunching is less than a quarter of the time shown.

In reply to Dave's message of 25 May 2025:

Just realised that on LHC@home the massively excessive time remaining estimates are because the time remaining is CPU time and not actual time which with 5 cores crunching is less than a quarter of the time shown.

If that were the case, wouldn't the remaining time drop faster? I'm running now Atlas tasks with 4 cores and the remaining time is dropping about 1 second per screen update sequence (every 3 seconds or so). To my knowledge the VB tasks do not report the progress they make to Boinc. We are seeing just the simulated progress as estimated by Boinc.

That makes sense. The simulated progress though seems to assume just one core. I noticed this morning, the task reaches about somewhere around 20% then goes straight to 100%. I haven't actually caught it happening yet though but the task not informing BOINC through the VM makes sense. My usual projects don't use VB so I am not used to BOINC starting VMs up. My impression though is that not only is the true progress not reported but also BOINC doesn't learn about the speed the tasks progress and learn from it.