>The following OpenPGP key (0x74C35BC8) is about to be removed:
Reason : Expired on 2026-02-11 11:44:18
It will be successfully removed.
Tomorrow it will be back.
Why I think so? Because it has returned, and I have re-deleted it, practically every day since February 11.
Joplin update woes:
I don't use Joplin on the desktop as much as on the phone, which means that I had neglected updating the desktop version (AppImage; yes, Linux) for some time.
Today I finally did open it, and saw several notes being un-encryptable. Okay, time to update, I guess.
Only problem turned out to be that version 3.5.11 and 3.5.13 (the two I tried) don't load properly: the app only shows a grey rectangle with a half menubar that doesn't respond to button presses.
So I tried to get back to version 3.4.x. Nope, can't do, the profile is too new. So version 3.5.x did do something: update the profile and prevent me from opening an older version.
What finally solved it was to restore $HOME/.config/Joplin and $HOME/.config/joplin-desktop from backup, and run version 3.4.10. The app opens, and all notes decrypt properly.
I still don't dare trying to run 3.5.x again - it would probably require another restore from backup in order to get back to 3.4.x again.
As an aside, I did learn that backintime backups of softlinks can get you to the live version of a file rather than the backed up version. Which is why my 2 week old backup looked like it contained files that had been updated 43 minutes ago - those files weren't the backed up files, but the live ones.
"wINdoWs jUst wOrkS"
Windows suddenly can't find the external monitor, and the settings dialog freezes.
#TimjanGrumpsOnComputers
One hour later.
"Upgrading system. Do not turn ff your computer. 0% complete"
Wee, I got my main system to hibernate and wake up again...
Except that the network interface didn't come up.
And it doesn't want to poweroff or reboot: it just sits there doing nothing.
Yet again, #fedora freezes hard instead of going to sleep.
Any recommendations on how to figure out what is causing this?
Comparing two journalctl printouts, for a successful and unsuccessful sleep respectively, and it appears to fail to reach this stage:
`
Sep 03 09:22:44 <hostname> kernel: sd 1:0:0:0: [sdb] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: sd 0:0:0:0: [sda] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: ata1.00: Entering standby power mode
Sep 03 09:22:44 <hostname> kernel: sd 2:0:0:0: [sdc] Synchronizing SCSI cache
Sep 03 09:22:44 <hostname> kernel: ata3.00: Entering standby power mode
Sep 03 09:22:44 <hostname> kernel: ata2.00: Entering standby power mode
`
(Forgot to post this after composing...)
I shouldn't only write about computers when they don't work.
This morning, for example, the upgrade from #fedora39 to #fedora40 went smoothly and the system could boot afterwards.
#TimjanGrumpsOnComputers (<-- not today)
XWayland crashes twice during a one hour Skype call.
Someone reported a very similar bug 6 months ago; another half dozen people made "me too" reports.
If someone is working on it, that's not visible from the bug report.
Giving up on Wayland, so trying to log out to switch to Xorg. After clicking on "leave", everything froze. Mouse, keyboard, status bar clock... hard reset, sigh.
Timjan