=== Probie95 is now known as Probie9
=== Probie92 is now known as Probie9
=== Probie98 is now known as Probie9
=== Probie96 is now known as Probie9
=== ledeni_ is now known as ledeni
[11:04] <Jonopoly> Anyone got a nice terminal based google calander that can recommend ?
[11:06] <lotuspsychje> !info gcalcli
[11:06] <ubottu> gcalcli (4.3.0-1, jammy): Google Calendar Command Line Interface. In component universe, is extra. Built by gcalcli. Size 1,421 kB / 1,777 kB
[11:07] <lotuspsychje> !info khal
[11:08] <ubottu> khal (1:0.10.4~ds-3, jammy): Standards based CLI and terminal calendar program. In component universe, is optional. Built by khal. Size 96 kB / 454 kB
[11:08] <Jonopoly> Thanks, really helpful will try them bothg
[11:08] <Jonopoly> Thanks, really helpful will try them both
[11:08] <lotuspsychje> !info calcurse
[11:08] <ubottu> calcurse (4.6.0-2, jammy): text-based calendar and todo manager. In component universe, is optional. Built by calcurse. Size 232 kB / 914 kB
[12:25] <Jonopoly> I don't think Khal can sync with google calendar
=== JanC_ is now known as JanC
[21:39] <arraybolt3[m]> Over the weeks since Jammy was released, I have seen so many people annoyed, alarmed by, or confused by, the "Pending update of firefox" warning that Snap throws out every so often. It's made worse by the fact that the auto-update doesn't seem to happen immediately after closing the app. Fix ideas?
[21:40] <sarnold> arraybolt3[m]: I think that's the topic of discussion on https://github.com/snapcore/snapd/pull/11912
[21:40] <ubottu> Pull 11912 in snapcore/snapd "features: disable refresh-app-awarness by default again" [Merged]
[21:42] <arraybolt3[m]> Nice! Hopefully that will get an SRU soon.
[21:44] <sarnold> tying updates to the running / not running status of executables in the snaps feels like it was a mistake. granted, firefox and libreoffice were already not reliable if you kept them running after updating their debs
[21:44] <sarnold> but when someone can prevent security updates from installing by leaving a program running -- or, likewise, when the security update kills their running processes -- both those are pretty frustrating situations
[21:45] <arraybolt3[m]> It seems like since Snaps are squashfs-based and sandboxed, this should be easy enough to make work. It's not the notification that's the problem, half so much as the fact that closing the app doesn't auto update.
[21:45] <arraybolt3[m]> If the update would apply in the background, let you know when it was finished, and then tell you to restart the app, that would be great. And while I'm not a big fan of forcing the app to restart after a while if the user is stubborn, it's better than the alternative.