From nio.wiklund at gmail.com Mon Aug 1 13:19:20 2022 From: nio.wiklund at gmail.com (Nio Wiklund) Date: Mon, 1 Aug 2022 15:19:20 +0200 Subject: [lubuntu-devel] Fwd: [lubuntu-users] "Update pending for Firefox snap"??? In-Reply-To: References: Message-ID: Den 2022-07-31 kl. 18:28, skrev Aaron Rainbolt: > Somehow I accidentally emailed Fritz directly rather than replying to > the whole mailing list (thanks GMail). > > ---------- Forwarded message --------- > From: Aaron Rainbolt > Date: Sun, Jul 31, 2022 at 11:27 AM > Subject: Re: [lubuntu-users] "Update pending for Firefox snap"??? > To: Fritz Hudnut > > > On Sun, Jul 31, 2022 at 10:53 AM Fritz Hudnut wrote: >> >> Folks: >> >> Booted up in Lubuntu kinetic today and I once again get an error message about "update for Firefox snap, close app in the next 13 days"???? >> >> I have "closed the app" numerous times over the last month or so and still getting this error message . . . what's up with that message?? >> >> I run weekly apt updates on the system, with autoremove, etc . . . system isn't clearing this error. > > Welcome to the default Firefox Snap in action. > > Firefox is delivered as a snap by default in Ubuntu 22.04 and all > flavors (including Lubuntu). Snaps are designed to auto-update, > however if your browser is open when Snap is ready to update it, it > will not update in order to avoid causing havoc. If you're still > getting this message even after a month, you're probably getting the > updates like you should, but the message is rather annoying. > > To force the snap to update when you want it to, press Ctrl+Alt+T to > open a terminal, and run "sudo snap refresh". This will update all > your Snaps, including Firefox. (If for some reason you only want to > update just Firefox, "sudo snap refresh firefox" will do that, though > it may also update snap dependencies if necessary.) Hi Aaron, Thanks for these clarifying instructions about snaps :-) Best regards Nio From kc2bez at lubuntu.me Thu Aug 11 21:28:40 2022 From: kc2bez at lubuntu.me (Dan Simmons) Date: Thu, 11 Aug 2022 17:28:40 -0400 Subject: [lubuntu-devel] Lubuntu 22.04.1 LTS is released! Message-ID: <39822952-8e93-6b96-ec1e-0c2d95065283@lubuntu.me> The Lubuntu team is excited to announce that Lubuntu 22.04.1 LTS (Jammy Jellyfish) has been released! Many thanks to all the contributors. You can find out more at our official blog post[1] [1] https://lubuntu.me/jammy-1-released On behalf of the Lubuntu release team, — @kc2bez:matrix.org @kc2bez on Telegram @kc2bez on libera.chat IRC 9150 77E7 6EFC 53F7 5CBC 6EB9 98D2 9485 5C5A 7872 From simon at tsimonq2.net Tue Aug 23 16:30:06 2022 From: simon at tsimonq2.net (Simon Quigley) Date: Tue, 23 Aug 2022 11:30:06 -0500 Subject: [lubuntu-devel] Lubuntu 22.10 Feature Freeze Fast Approaching: What It Means and How To Help Message-ID: <897134d3-cbfe-2cca-ba6d-c0cb68ac2439@tsimonq2.net> Dearest Lubuntu contributors and users, During every release cycle, we hit a milestone titled Feature Freeze, where developers in the Ubuntu and Lubuntu projects are no longer permitted to upload new versions of software without an exception, in order to dedicate the remainder of the cycle to improving stability. The Feature Freeze date for Lubuntu is Thursday, August 25th, 2022. I will be around to process any final uploads from 3 PM to 6 PM US Central Time on that date, after which I will declare Lubuntu to be in Feature Freeze. If you're aware of any new features that would be beneficial to include for users, please ping me in our development channel on Matrix(/IRC/Telegram)[1] and I will address those requests first come, first serve. On my personal wishlist is the LXQt menu overhaul, yet another update to Calamares, and further evaluation of the upstream LXQt code to ensure there isn't a bugfix or feature we can cherry-pick. Unfortunately, after speaking with LXQt upstream, they do not plan on releasing 1.2 until shortly after the release of Lubuntu 22.10, and backports for non-LTS releases are still up in the air. This weekend I will prepare a QA-related document outlining every single commit we have cherry-picked, why, and what users should expect to be different when reporting bugs to upstream. My goal is to have this done in a thorough enough manner that upstream LXQt will have little complaints. I have blocked off 1 PM to 6 PM on Saturday, tentatively, to do that. You may be asking, how can I help? By testing[1], of course :) with features no longer free-flowing into 22.10, this is the time to test every "nook and cranny" of the operating system. What doesn't work for you? Is there anything we can do better without vastly expanding the scope of our mission? If you have any questions, please do let me know. I will note publicly at this point that the Lubuntu Council has granted me some of my former permissions before my hiatus, including Release Manager capacity. I'm glad to be back, and I hope to serve the Lubuntu project well once again. Thanks! [1] https://lubuntu.me/links -- Simon Quigley simon at tsimonq2.net tsimonq2 on LiberaChat and OFTC @tsimonq2:linuxdelta.com on Matrix 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4 -------------- next part -------------- A non-text attachment was scrubbed... Name: OpenPGP_signature Type: application/pgp-signature Size: 840 bytes Desc: OpenPGP digital signature URL: