Congratulations!

[Valid RSS] This is a valid RSS feed.

Recommendations

This feed is valid, but interoperability with the widest range of feed readers could be improved by implementing the following recommendations.

Source: http://planet.ubuntu.com/rss20.xml

  1. <?xml version="1.0"?>
  2. <rss version="2.0">
  3.  
  4. <channel>
  5. <title>Planet Ubuntu</title>
  6. <link>http://planet.ubuntu.com/</link>
  7. <language>en</language>
  8. <description>Planet Ubuntu - http://planet.ubuntu.com/</description>
  9.  
  10. <item>
  11. <title>Colin Watson: Free software activity in May 2025</title>
  12. <guid isPermaLink="false">tag:www.chiark.greenend.org.uk,2025-06-08:/~cjwatson/blog/activity-2025-05.html</guid>
  13. <link>https://www.chiark.greenend.org.uk/~cjwatson/blog/activity-2025-05.html</link>
  14. <description>&lt;p&gt;My Debian contributions this month were all
  15. &lt;a href=&quot;https://www.freexian.com/about/debian-contributions/&quot;&gt;sponsored&lt;/a&gt; by
  16. Freexian.  Things were a bit quieter than usual, as for the most part I was
  17. sticking to things that seemed urgent for the upcoming trixie release.&lt;/p&gt;
  18. &lt;p&gt;You can also support my work directly via
  19. &lt;a href=&quot;https://liberapay.com/cjwatson&quot;&gt;Liberapay&lt;/a&gt; or &lt;a href=&quot;https://github.com/sponsors/cjwatson&quot;&gt;GitHub
  20. Sponsors&lt;/a&gt;.&lt;/p&gt;
  21. &lt;h2&gt;OpenSSH&lt;/h2&gt;
  22. &lt;p&gt;After my appeal for help &lt;a href=&quot;https://www.chiark.greenend.org.uk/~cjwatson/blog/activity-2025-04.html&quot;&gt;last month&lt;/a&gt; to
  23. debug &lt;a href=&quot;https://bugs.debian.org/1103418&quot;&gt;intermittent &lt;code&gt;sshd&lt;/code&gt; crashes&lt;/a&gt;, Michel
  24. Casabona helped me put together an environment where I could reproduce it,
  25. which allowed me to track it down to a &lt;a href=&quot;https://bugzilla.mindrot.org/show_bug.cgi?id=3822&quot;&gt;root
  26. cause&lt;/a&gt; and fix it.  (I
  27. also found a &lt;a href=&quot;https://bugzilla.mindrot.org/show_bug.cgi?id=3819&quot;&gt;misuse of
  28. &lt;code&gt;strlcpy&lt;/code&gt;&lt;/a&gt; affecting at
  29. least glibc-based systems in passing, though I think that was unrelated.)&lt;/p&gt;
  30. &lt;p&gt;I worked with Daniel Kahn Gillmor to fix a &lt;a href=&quot;https://bugs.debian.org/1103522&quot;&gt;regression in &lt;code&gt;ssh-agent&lt;/code&gt; socket
  31. handling&lt;/a&gt;.&lt;/p&gt;
  32. &lt;p&gt;I fixed a &lt;a href=&quot;https://bugs.debian.org/1104992&quot;&gt;reproducibility bug depending on whether &lt;code&gt;passwd&lt;/code&gt; is installed on
  33. the build system&lt;/a&gt;, which would have
  34. affected security updates during the lifetime of trixie.&lt;/p&gt;
  35. &lt;p&gt;I &lt;a href=&quot;https://bugs.debian.org/1105036&quot;&gt;backported&lt;/a&gt; openssh 1:10.0p1-5 to bookworm-backports.&lt;/p&gt;
  36. &lt;p&gt;I issued bookworm and
  37. &lt;a href=&quot;https://lists.debian.org/debian-lts-announce/2025/05/msg00008.html&quot;&gt;bullseye&lt;/a&gt;
  38. updates for &lt;a href=&quot;https://bugs.debian.org/1102603&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2025-32728&lt;/a&gt;.&lt;/p&gt;
  39. &lt;h2&gt;groff&lt;/h2&gt;
  40. &lt;p&gt;I backported a fix for &lt;a href=&quot;https://bugs.debian.org/1104609&quot;&gt;incorrect output when formatting multiple documents
  41. as &lt;span class=&quot;caps&quot;&gt;PDF&lt;/span&gt;/PostScript at once&lt;/a&gt;.&lt;/p&gt;
  42. &lt;h2&gt;debmirror&lt;/h2&gt;
  43. &lt;p&gt;I added a &lt;a href=&quot;https://salsa.debian.org/debian/debmirror/-/commit/c122f7ff32c4ae24a729a6ecf42d15c9ac05eb5c&quot;&gt;simple
  44. autopkgtest&lt;/a&gt;.&lt;/p&gt;
  45. &lt;h2&gt;Python team&lt;/h2&gt;
  46. &lt;p&gt;I upgraded these packages to new upstream versions:&lt;/p&gt;
  47. &lt;ul&gt;
  48. &lt;li&gt;automat&lt;/li&gt;
  49. &lt;li&gt;celery&lt;/li&gt;
  50. &lt;li&gt;flufl.i18n&lt;/li&gt;
  51. &lt;li&gt;flufl.lock&lt;/li&gt;
  52. &lt;li&gt;frozenlist&lt;/li&gt;
  53. &lt;li&gt;python-charset-normalizer&lt;/li&gt;
  54. &lt;li&gt;python-evalidate (including pointing out an &lt;a href=&quot;https://github.com/yaroslaff/evalidate/issues/15&quot;&gt;upstream release handling
  55.  issue&lt;/a&gt;)&lt;/li&gt;
  56. &lt;li&gt;python-pythonjsonlogger&lt;/li&gt;
  57. &lt;li&gt;python-setproctitle&lt;/li&gt;
  58. &lt;li&gt;python-telethon&lt;/li&gt;
  59. &lt;li&gt;python-typing-inspection&lt;/li&gt;
  60. &lt;li&gt;python-webargs&lt;/li&gt;
  61. &lt;li&gt;pyzmq&lt;/li&gt;
  62. &lt;li&gt;trove-classifiers (including a &lt;a href=&quot;https://github.com/pypa/trove-classifiers/pull/212&quot;&gt;small upstream
  63.  cleanup&lt;/a&gt;)&lt;/li&gt;
  64. &lt;li&gt;uncertainties&lt;/li&gt;
  65. &lt;li&gt;zope.testrunner&lt;/li&gt;
  66. &lt;/ul&gt;
  67. &lt;p&gt;In bookworm-backports, I updated these packages:&lt;/p&gt;
  68. &lt;ul&gt;
  69. &lt;li&gt;python-django to 3:4.2.21-1 (issuing
  70.  &lt;a href=&quot;https://backports.debian.org/news/BSA-124_Security_Update_for_python-django/&quot;&gt;&lt;span class=&quot;caps&quot;&gt;BSA&lt;/span&gt;-124&lt;/a&gt;)&lt;/li&gt;
  71. &lt;li&gt;python-django-pgtrigger to 4.14.0-1&lt;/li&gt;
  72. &lt;/ul&gt;
  73. &lt;p&gt;I fixed problems building these packages reproducibly:&lt;/p&gt;
  74. &lt;ul&gt;
  75. &lt;li&gt;celery (&lt;a href=&quot;https://github.com/celery/celery/pull/9687&quot;&gt;contributed
  76.  upstream&lt;/a&gt;)&lt;/li&gt;
  77. &lt;li&gt;python-setproctitle&lt;/li&gt;
  78. &lt;li&gt;uncertainties (&lt;a href=&quot;https://github.com/lmfit/uncertainties/pull/312&quot;&gt;contributed
  79.  upstream&lt;/a&gt;, after some discussion)&lt;/li&gt;
  80. &lt;/ul&gt;
  81. &lt;p&gt;I backported fixes for some security vulnerabilities to unstable (since
  82. we’re in freeze now so it’s not always appropriate to upgrade to new
  83. upstream versions):&lt;/p&gt;
  84. &lt;ul&gt;
  85. &lt;li&gt;django-select2: &lt;a href=&quot;https://bugs.debian.org/1106747&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2025-48383&lt;/a&gt;&lt;/li&gt;
  86. &lt;li&gt;python-tornado: &lt;a href=&quot;https://bugs.debian.org/1105886&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2025-47287&lt;/a&gt;&lt;/li&gt;
  87. &lt;/ul&gt;
  88. &lt;p&gt;I fixed various other build/test failures:&lt;/p&gt;
  89. &lt;ul&gt;
  90. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/17&quot;&gt;fail2ban&lt;/a&gt;
  91.  (also reviewing and merging &lt;a href=&quot;https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/15&quot;&gt;fix sshd 10.0 log
  92.  identifier&lt;/a&gt;
  93.  and &lt;a href=&quot;https://salsa.debian.org/python-team/packages/fail2ban/-/merge_requests/16&quot;&gt;remove runtime calls to
  94.  distutils&lt;/a&gt;)&lt;/li&gt;
  95. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103147&quot;&gt;karabo-bridge&lt;/a&gt; (&lt;a href=&quot;https://github.com/European-XFEL/karabo-bridge-py/pull/71&quot;&gt;contributed
  96.  upstream&lt;/a&gt;)&lt;/li&gt;
  97. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1104837&quot;&gt;kegtron-ble&lt;/a&gt;&lt;/li&gt;
  98. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1091947&quot;&gt;python-click-option-group&lt;/a&gt; (&lt;span class=&quot;caps&quot;&gt;NMU&lt;/span&gt;)&lt;/li&gt;
  99. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1104508&quot;&gt;python-holidays&lt;/a&gt;&lt;/li&gt;
  100. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103591&quot;&gt;python-mastodon&lt;/a&gt;&lt;/li&gt;
  101. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1106440&quot;&gt;python-mechanize&lt;/a&gt; (&lt;a href=&quot;https://github.com/python-mechanize/mechanize/pull/102&quot;&gt;contributed
  102.  upstream&lt;/a&gt;)&lt;/li&gt;
  103. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/python-team/packages/thermobeacon-ble/-/commit/c1bc246f0a04018483074cbdca1501088165dc07&quot;&gt;thermobeacon-ble&lt;/a&gt;&lt;/li&gt;
  104. &lt;/ul&gt;
  105. &lt;p&gt;I added non-superficial autopkgtests to these packages:&lt;/p&gt;
  106. &lt;ul&gt;
  107. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1035163&quot;&gt;karabo-bridge&lt;/a&gt;&lt;/li&gt;
  108. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/python-team/packages/python-lazy-model/-/compare/debian%2F0.3.0-1...debian%2F0.3.0-2?from_project_id=93488&quot;&gt;python-lazy-model&lt;/a&gt;&lt;/li&gt;
  109. &lt;/ul&gt;
  110. &lt;p&gt;I packaged &lt;a href=&quot;https://bugs.debian.org/1103977&quot;&gt;python-django-hashids&lt;/a&gt; and
  111. &lt;a href=&quot;https://bugs.debian.org/1103880&quot;&gt;python-django-pgbulk&lt;/a&gt;, needed for new
  112. upstream versions of python-django-pgtrigger.&lt;/p&gt;
  113. &lt;p&gt;I
  114. &lt;a href=&quot;https://code.launchpad.net/~cjwatson/storm/py314-beta/+merge/485763&quot;&gt;ported&lt;/a&gt;
  115. storm to Python 3.14.&lt;/p&gt;
  116. &lt;h2&gt;Science team&lt;/h2&gt;
  117. &lt;p&gt;I fixed a &lt;a href=&quot;https://bugs.debian.org/1103232&quot;&gt;build failure&lt;/a&gt; in apertium-oci-fra.&lt;/p&gt;</description>
  118. <pubDate>Sun, 08 Jun 2025 00:20:02 +0000</pubDate>
  119. </item>
  120. <item>
  121. <title>Salih Emin: uCareSystem 25.05.06: Because Even Your WSL Deserves a Spa Day!</title>
  122. <guid isPermaLink="false">https://utappia.org/?p=49897</guid>
  123. <link>https://utappia.org/2025/06/06/ucaresystem-25-05-06-because-even-your-wsl-deserves-a-spa-day/</link>
  124. <description>&lt;p&gt;Hey everyone,&lt;/p&gt;
  125.  
  126.  
  127.  
  128. &lt;p&gt;Get ready to dust off those virtual cobwebs and crack open a cold one (or a digital one, if you’re in a VM) because uCareSystem 25.05.06 has officially landed! And let me tell you, this release is so good, it’s practically a love letter to your Linux system – especially if that system happens to be chilling out in &lt;strong&gt;Windows Subsystem for Linux (WSL)&lt;/strong&gt;.&lt;/p&gt;
  129.  
  130.  
  131.  
  132. &lt;span id=&quot;more-49897&quot;&gt;&lt;/span&gt;
  133.  
  134.  
  135.  
  136. &lt;p&gt;That’s right, folks, the big news is out: &lt;strong&gt;WSL support for uCareSystem has finally landed!&lt;/strong&gt; We know you’ve been asking, we’ve heard your pleas, and we’ve stopped pretending we didn’t see you waving those “Free WSL” signs. &lt;/p&gt;
  137.  
  138.  
  139.  
  140. &lt;p&gt;Now, your WSL instances can enjoy the same tender loving care that uCareSystem provides for your “bare metal” Ubuntu/Debian Linux setups. No more feeling left out, little WSLs! You can now join the cool kids at the digital spa.&lt;/p&gt;
  141.  
  142.  
  143.  
  144. &lt;p&gt;Here is a video of it:&lt;/p&gt;
  145.  
  146.  
  147.  
  148. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  149.  
  150. &lt;/div&gt;&lt;/figure&gt;
  151.  
  152.  
  153.  
  154. &lt;p&gt;But wait, there’s more! (Isn’t there always?) We didn’t just stop at making friends with Windows. We also tackled some pesky gremlins that have been lurking in the shadows:&lt;/p&gt;
  155.  
  156.  
  157.  
  158. &lt;ul class=&quot;wp-block-list&quot;&gt;
  159. &lt;li&gt;&lt;strong&gt;Apt-key dependency? Gone!&lt;/strong&gt; We told it to pack its bags and hit the road. Less dependency drama, more system harmony.&lt;/li&gt;
  160.  
  161.  
  162.  
  163. &lt;li&gt;Remember that time your internet check was slower than a sloth on a caffeine crash? We squashed that &lt;strong&gt;“Bug latency curl in internet check phase”&lt;/strong&gt; bug. Your internet checks will now be snappier than a startled squirrel.&lt;/li&gt;
  164.  
  165.  
  166.  
  167. &lt;li&gt;We fixed that &lt;strong&gt;“Wrong kernel cleanup”&lt;/strong&gt; issue. Your kernels are now safe from accidental digital haircuts.&lt;/li&gt;
  168.  
  169.  
  170.  
  171. &lt;li&gt;And for those of you who hit snags with Snap in WSL, kernel cleanup (again, because we’re thorough!), and other bits, we’ve applied some much-needed digital duct tape and elbow grease to fix and more.&lt;/li&gt;
  172.  
  173.  
  174.  
  175. &lt;li&gt;We even gave our code a good scrub, fixing those annoying &lt;strong&gt;shellcheck warnings&lt;/strong&gt;. Because nobody likes a messy codebase, especially not us!&lt;/li&gt;
  176.  
  177.  
  178.  
  179. &lt;li&gt;Oh, and the &lt;code&gt;-k&lt;/code&gt; option? Yeah, that’s gone too. We decided it was useless so we had to retire it to a nice, quiet digital farm upstate.&lt;/li&gt;
  180.  
  181.  
  182.  
  183. &lt;li&gt;Finally, for all you newcomers and memory-challenged veterans, we’ve added &lt;strong&gt;install and uninstall instructions to &lt;a href=&quot;https://github.com/Utappia/uCareSystem/blob/master/README.md&quot;&gt;the README&lt;/a&gt;&lt;/strong&gt;. Because sometimes, even we forget how to put things together after we’ve taken them apart.&lt;/li&gt;
  184. &lt;/ul&gt;
  185.  
  186.  
  187.  
  188. &lt;p&gt;So, what are you waiting for? Head over to &lt;a href=&quot;https://utappia.org&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;utappia.org&lt;/a&gt; (or wherever you get your uCareSystem goodness) and give your system the pampering it deserves with uCareSystem 25.05.06. Your WSL instance will thank you, probably with a digital high-five.&lt;/p&gt;
  189.  
  190.  
  191.  
  192. &lt;p&gt;Download the latest release and give it a spin. As always, feedback is welcome.&lt;/p&gt;
  193.  
  194.  
  195.  
  196. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Acknowledgements&lt;/h3&gt;
  197.  
  198.  
  199.  
  200. &lt;p&gt;Thanks to the following users for their support:&lt;/p&gt;
  201.  
  202.  
  203.  
  204. &lt;ul class=&quot;wp-block-list&quot;&gt;
  205. &lt;li&gt;&lt;strong&gt;P. Loughman&lt;/strong&gt; – Thanks for your continued support&lt;/li&gt;
  206.  
  207.  
  208.  
  209. &lt;li&gt;&lt;strong&gt;D. Emge&lt;/strong&gt; – Thanks for your continued support&lt;/li&gt;
  210.  
  211.  
  212.  
  213. &lt;li&gt;&lt;strong&gt;W. Schreinemachers&lt;/strong&gt; – Thanks for your continued support&lt;/li&gt;
  214.  
  215.  
  216.  
  217. &lt;li&gt;&lt;strong&gt;W. Schwartz&lt;/strong&gt;&lt;/li&gt;
  218.  
  219.  
  220.  
  221. &lt;li&gt;&lt;strong&gt;D. e Swarthout&lt;/strong&gt;&lt;/li&gt;
  222.  
  223.  
  224.  
  225. &lt;li&gt;&lt;strong&gt;D. Luchini&lt;/strong&gt;&lt;/li&gt;
  226.  
  227.  
  228.  
  229. &lt;li&gt;&lt;strong&gt;M. Stanley&lt;/strong&gt;&lt;/li&gt;
  230.  
  231.  
  232.  
  233. &lt;li&gt;&lt;strong&gt;N. Evangelista&lt;/strong&gt;&lt;/li&gt;
  234. &lt;/ul&gt;
  235.  
  236.  
  237.  
  238. &lt;p&gt;Your involvement helps keep this project alive, evolving, and aligned with real-world needs. Thank you.&lt;/p&gt;
  239.  
  240.  
  241.  
  242. &lt;p&gt;Happy maintaining!&lt;/p&gt;
  243.  
  244.  
  245.  
  246. &lt;h2 class=&quot;wp-block-heading&quot;&gt;Where can I download uCareSystem ?&lt;/h2&gt;
  247.  
  248.  
  249.  
  250. &lt;p&gt;As always, I want to express my gratitude for your support over the past 15 years. I have received countless messages from inside and outside Greece about how useful they found the application. I hope you find the new version useful as well.&lt;/p&gt;
  251.  
  252.  
  253.  
  254. &lt;p&gt;If you’ve found uCareSystem to be valuable and it has saved you time, consider showing your appreciation with a donation. You can contribute via PayPal or Debit/Credit Card by clicking on the banner.&lt;/p&gt;
  255.  
  256.  
  257.  
  258. &lt;table&gt;
  259. &lt;thead&gt;
  260. &lt;tr&gt;
  261. &lt;th&gt;Pay what you want&lt;/th&gt;
  262. &lt;th&gt;Maybe next time&lt;/th&gt;
  263. &lt;/tr&gt;
  264. &lt;/thead&gt;
  265. &lt;tbody&gt;
  266. &lt;tr&gt;
  267. &lt;td&gt;Click the donate button and enter the amount you want to donate. Then you will be navigated to the page with the latest version to download the installer&lt;/td&gt;
  268. &lt;td&gt;If you don’t want to Donate this time, just click the download icon to be navigated to the page with the latest version to download the installer&lt;/td&gt;
  269. &lt;/tr&gt;
  270. &lt;tr&gt;
  271. &lt;td&gt;&lt;a href=&quot;https://www.paypal.com/donate/?hosted_button_id=SATQ6Y9S3UCSG&quot; rel=&quot;attachment wp-att-2601&quot;&gt;&lt;img alt=&quot;btn_donateCC_LG&quot; class=&quot;wp-image-2601 size-full aligncenter&quot; height=&quot;47&quot; src=&quot;http://utappiablog.wordpress.com/wp-content/uploads/2016/03/btn_donatecc_lg1.gif&quot; width=&quot;147&quot; /&gt;&lt;/a&gt;&lt;/td&gt;
  272. &lt;td&gt;&lt;a href=&quot;https://github.com/Utappia/uCareSystem/releases/latest&quot; rel=&quot;attachment wp-att-2593&quot;&gt;&lt;img alt=&quot;ucare-system-download&quot; class=&quot;size-full wp-image-2593 aligncenter&quot; height=&quot;151&quot; src=&quot;http://utappiablog.wordpress.com/wp-content/uploads/2016/03/ucare-system-download.png&quot; width=&quot;151&quot; /&gt;&lt;/a&gt;&lt;/td&gt;
  273. &lt;/tr&gt;
  274. &lt;tr&gt;
  275. &lt;td&gt; &lt;/td&gt;
  276. &lt;td&gt; &lt;/td&gt;
  277. &lt;/tr&gt;
  278. &lt;/tbody&gt;
  279. &lt;/table&gt;
  280. &lt;p&gt;Once installed, the updates for new versions will be installed along with your regular system updates.&lt;/p&gt;
  281. &lt;p&gt;The post &lt;a href=&quot;https://utappia.org/2025/06/06/ucaresystem-25-05-06-because-even-your-wsl-deserves-a-spa-day/&quot;&gt;uCareSystem 25.05.06: Because Even Your WSL Deserves a Spa Day!&lt;/a&gt; appeared first on &lt;a href=&quot;https://utappia.org&quot;&gt;Utappia&lt;/a&gt;.&lt;/p&gt;</description>
  282. <pubDate>Fri, 06 Jun 2025 22:59:05 +0000</pubDate>
  283. </item>
  284. <item>
  285. <title>Ubuntu Blog: What is CMMC compliance?</title>
  286. <guid isPermaLink="true">https://ubuntu.com//blog/what-is-cmmc-compliance</guid>
  287. <link>https://ubuntu.com//blog/what-is-cmmc-compliance</link>
  288. <description>&lt;p&gt;The Cybersecurity Maturity Model Certification, or CMMC for short, is a security framework for protecting Controlled Unclassified Information (CUI) in non-federal systems and organizations. The CMMC compliance requirements map to the set of controls laid out in the NIST SP 800-171 Rev 2 and NIST SP 800-172 families.&lt;/p&gt;
  289. &lt;p&gt;CMMC version 2.0 came into effect on December 26, 2023, and is designed to ensure adherence to rigorous cybersecurity policies and practices within the public sector and amongst wider industry partners.&lt;/p&gt;
  290. &lt;p&gt;Whilst many of the controls relate to how organizations conduct their IT operations, there are several specific technology requirements, and Ubuntu Pro includes features which meet these requirements head on.&lt;/p&gt;
  291. &lt;figure class=&quot;wp-block-image size-full is-resized&quot;&gt;&lt;img alt=&quot;&quot; height=&quot;627&quot; src=&quot;https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,c_fill,w_1200,h_627/https://ubuntu.com/wp-content/uploads/ffbe/Untitled-design-30.png&quot; width=&quot;1200&quot; /&gt;&lt;/figure&gt;
  292. &lt;h2 class=&quot;wp-block-heading&quot;&gt;What are the CMMC maturity levels?&lt;/h2&gt;
  293. &lt;p&gt;CMMC has 3 levels, designed to meet increasing levels of security scrutiny:&lt;/p&gt;
  294. &lt;ol&gt;
  295. &lt;li&gt;Safeguarding Federal Contract Information (FCI), with an annual self-assessment.&lt;/li&gt;
  296. &lt;li&gt;Protection of Controlled Unclassified Information (CUI), with a triennial third-party assessment for critical national security information, and annual self-assessment for other cases.&lt;/li&gt;
  297. &lt;li&gt;Enhanced Protection of Controlled Unclassified Information, with triennial government-led assessments.&lt;/li&gt;
  298. &lt;/ol&gt;
  299. &lt;p&gt;Most independent contractors and industry partners will use level 2, and perform an annual self-assessment of their security posture against the program requirements.&lt;/p&gt;
  300. &lt;h2 class=&quot;wp-block-heading&quot;&gt;When will CMMC compliance become a hard requirement?&lt;/h2&gt;
  301. &lt;p&gt;While the 2.0 standard has been live since December 2023, CMMC will become a contractual requirement after 3 years, which falls in 2026. However, it takes time to work through the controls and achieve the security requirements, and organizations may take anywhere from months to years to gain this level of maturity, depending on their size and agility. Undoubtedly, the best course of action is to start planning now in order to remain eligible for contracts and to keep winning business.&lt;/p&gt;
  302. &lt;h2 class=&quot;wp-block-heading&quot;&gt;How does CMMC compare to NIST SP 800-171? &lt;/h2&gt;
  303. &lt;p&gt;CMMC is based on the NIST SP 800-171 security controls framework for handling Controlled Unclassified Information – similar to FedRAMP – and so anyone familiar with these publications will feel comfortable with the CMMC requirements. Whilst NIST SP 800-171 provides a wide range of security controls, the exact implementation can be left to the user’s discretion; CMMC gives exact requirements and provides a framework for self-assessment and auditing.&lt;/p&gt;
  304. &lt;h2 class=&quot;wp-block-heading&quot;&gt;5 steps to CMMC compliance&lt;/h2&gt;
  305. &lt;p&gt;In order to become CMMC compliant, you should be systematic in your approach. Here’s how to proceed:&lt;/p&gt;
  306. &lt;ol&gt;
  307. &lt;li&gt;Determine your CMMC maturity level requirements: this depends on the type of information that you’ll be handling. Level 1 is just for federal contracts, whilst Level 2 – the most widely used level – is for CUI. Level 3 is for critical infrastructure.&lt;/li&gt;
  308. &lt;li&gt;Determine your scope and assets: – it’s very important to work out the boundary of the systems that will handle the sensitive data, and keep track of which IT assets are included in this.&lt;/li&gt;
  309. &lt;li&gt;Perform a gap analysis: go through the CMMC control framework and check which controls you currently meet, and which ones need attention; either for existing systems or for future designs.&lt;/li&gt;
  310. &lt;li&gt;Choose the right technology platforms: such as Ubuntu Pro, a subscription for open source security that patches critical vulnerabilities within 24 hours.&lt;/li&gt;
  311. &lt;li&gt;Complete a self-assessment.&lt;/li&gt;
  312. &lt;/ol&gt;
  313. &lt;figure class=&quot;wp-block-image size-full is-resized&quot;&gt;&lt;a href=&quot;https://ubuntu.com/engage/achieve-cmmc-with-ubuntu&quot;&gt;&lt;img alt=&quot;&quot; height=&quot;400&quot; src=&quot;https://res.cloudinary.com/canonical/image/fetch/f_auto,q_auto,fl_sanitize,c_fill,w_1200,h_400/https://ubuntu.com/wp-content/uploads/1b93/cmmc-compliance.png&quot; width=&quot;1200&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  314. &lt;h2 class=&quot;wp-block-heading&quot;&gt;How Canonical can support your journey towards CMMC&lt;/h2&gt;
  315. &lt;p&gt;&lt;strong&gt;Patching security vulnerabilities&lt;/strong&gt;&lt;/p&gt;
  316. &lt;p&gt;Ubuntu Pro supports the CMMC requirement to remediate software vulnerabilities in a timely manner. Since starting out 20 years ago, Canonical has typically released patches for critical vulnerabilities within 24 hours. We provide 12 years of &lt;a href=&quot;https://ubuntu.com/security/cves&quot;&gt;security patching&lt;/a&gt; for all the software applications and infrastructure components within the Ubuntu ecosystem. &lt;/p&gt;
  317. &lt;p&gt;&lt;strong&gt;FIPS-certified crypto modules&lt;/strong&gt;&lt;/p&gt;
  318. &lt;p&gt;Ubuntu Pro provides FIPS 140-2 and &lt;a href=&quot;https://ubuntu.com/blog/fips-140-3-for-ubuntu-22-04lts&quot;&gt;FIPS 140-3&lt;/a&gt; certified cryptographic modules that you can deploy with a single command. These certified modules replace the standard cryptographic libraries which ship with Ubuntu by default, making the system FIPS 140 compliant, and allowing existing applications to make use of FIPS-approved cryptographic algorithms and ciphers without further certification or modification.&lt;/p&gt;
  319. &lt;p&gt;&lt;strong&gt;System hardening&lt;/strong&gt;&lt;/p&gt;
  320. &lt;p&gt;&lt;a href=&quot;https://ubuntu.com/security/disa-stig&quot;&gt;DISA-STIG&lt;/a&gt; is a system hardening guide that describes how to configure an Ubuntu system to be maximally secure, by locking it down and restricting unnecessary privileges. The STIG for Ubuntu lists several hundred individual configuration steps to turn a generic Ubuntu installation into a fully secure environment. System hardening is an important CMMC requirement. &lt;/p&gt;
  321. &lt;p&gt;You can simplify STIG hardening with the Ubuntu Security Guide (USG): the USG tool enables automated auditing and remediation of the individual configuration steps in order to comply with the STIG benchmark, and allows you to customize the hardening profile to meet individual deployment needs.&lt;/p&gt;
  322. &lt;h2 class=&quot;wp-block-heading&quot;&gt;Overview &lt;/h2&gt;
  323. &lt;p&gt;Canonical is a software distributor rather than a service provider, and as such we are not CMMC certified ourselves, but through Ubuntu Pro we provide the tools that enable our customers to meet these specific technology requirements within the baseline controls. &lt;/p&gt;
  324. &lt;p&gt;As such, Ubuntu Pro provides an easy pathway to CMMC compliance. It delivers CVE patching for Ubuntu OS and Applications covering 36,000 packages, along with automated, unattended, and restartless updates, and the best tools to secure and manage your Ubuntu infrastructure, developed by the publisher of Ubuntu. Learn more about Ubuntu Pro on our &lt;a href=&quot;https://ubuntu.com/pro&quot;&gt;explanatory web page.&lt;/a&gt;&lt;/p&gt;</description>
  325. <pubDate>Fri, 06 Jun 2025 13:27:14 +0000</pubDate>
  326. </item>
  327. <item>
  328. <title>Launchpad News: Phasing out Bazaar code hosting</title>
  329. <guid isPermaLink="false">https://blog.launchpad.net/?p=4464</guid>
  330. <link>https://blog.launchpad.net/general/phasing-out-bazaar-code-hosting</link>
  331. <description>&lt;h2&gt;What is Bazaar code hosting?&lt;/h2&gt;
  332.  
  333.  
  334.  
  335. &lt;p&gt;Bazaar is a distributed revision control system, originally developed by Canonical. It provides similar functionality compared to the now dominant Git.&lt;/p&gt;
  336.  
  337.  
  338.  
  339. &lt;p&gt;Bazaar code hosting is an offering from Launchpad to both provide a Bazaar backend for hosting code, but also a web frontend for browsing the code. The frontend is provided by the Loggerhead application on Launchpad.&lt;/p&gt;
  340.  
  341.  
  342.  
  343. &lt;h2&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-sunsetting-bazaar&quot;&gt;&lt;/a&gt;Sunsetting Bazaar&lt;/h2&gt;
  344.  
  345.  
  346.  
  347. &lt;p&gt;Bazaar passed its peak a decade ago. &lt;a href=&quot;https://launchpad.net/brz&quot;&gt;Breezy&lt;/a&gt; is a fork of Bazaar that has kept a form of Bazaar alive, but the last release of Bazaar was in 2016. Since then the impact has declined, and there are modern replacements like Git.&lt;/p&gt;
  348.  
  349.  
  350.  
  351. &lt;p&gt;Just keeping Bazaar running requires a non-trivial amount of development, operations time, and infrastructure resources – all of which could be better used elsewhere.&lt;/p&gt;
  352.  
  353.  
  354.  
  355. &lt;p&gt;Launchpad will now begin the process of discontinuing support for Bazaar.&lt;/p&gt;
  356.  
  357.  
  358.  
  359. &lt;h2&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-timelines&quot;&gt;&lt;/a&gt;Timelines&lt;/h2&gt;
  360.  
  361.  
  362.  
  363. &lt;p&gt;We are aware that the migration of the repositories and updating workflows will take some time, that is why we planned sunsetting in two phases.&lt;/p&gt;
  364.  
  365.  
  366.  
  367. &lt;h3&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-phase-1&quot;&gt;&lt;/a&gt;Phase 1&lt;/h3&gt;
  368.  
  369.  
  370.  
  371. &lt;p&gt;Loggerhead, the web frontend, which is used to browse the code in a web browser, will be shut down imminently. Analyzing access logs showed that there are hardly any more requests from legit users, but almost the entire traffic comes from scrapers and other abusers. Sunsetting Loggerhead will not affect the ability to pull, push and merge changes.&lt;/p&gt;
  372.  
  373.  
  374.  
  375. &lt;h3&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-phase-2&quot;&gt;&lt;/a&gt;Phase 2&lt;/h3&gt;
  376.  
  377.  
  378.  
  379. &lt;p&gt;From September 1st, 2025, we do not intend to have Bazaar, the code hosting backend, any more. Users need to migrate all repositories from Bazaar to Git between now and this deadline.&lt;/p&gt;
  380.  
  381.  
  382.  
  383. &lt;h2&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-migration-paths&quot;&gt;&lt;/a&gt;Migration paths&lt;/h2&gt;
  384.  
  385.  
  386.  
  387. &lt;p&gt;The following blog post describes all the necessary steps on how to convert a Bazaar repository hosted on Launchpad to Git.&lt;/p&gt;
  388.  
  389.  
  390.  
  391. &lt;h3&gt;&lt;a href=&quot;https://jugmac00.github.io/blog/migrate-a-repository-from-bazaar-to-git/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Migrate a Repository From Bazaar to Git&lt;/a&gt;&lt;/h3&gt;
  392.  
  393.  
  394.  
  395. &lt;h2&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189#p-160870-call-for-action&quot;&gt;&lt;/a&gt;Call for action&lt;/h2&gt;
  396.  
  397.  
  398.  
  399. &lt;p&gt;Our users are extremely important to us. Ubuntu, for instance, has a long history of Bazaar usage, and we will need to work with the Ubuntu Engineering team to find ways to move forward to remove the reliance on the integration with Bazaar for the development of Ubuntu. If you are also using Bazaar and you have a special use case, or you do not see a clear way forward, please reach out to us to discuss your use case and how we can help you.&lt;/p&gt;
  400.  
  401.  
  402.  
  403. &lt;p&gt;&lt;strong&gt;You can reach us in #launchpad:&lt;a href=&quot;http://ubuntu.com/&quot;&gt;ubuntu.com&lt;/a&gt; on Matrix, or submit a &lt;a href=&quot;https://answers.launchpad.net/launchpad&quot;&gt;question&lt;/a&gt; or send us an e-mail via &lt;a href=&quot;mailto:feedback@launchpad.net&quot;&gt;feedback@launchpad.net&lt;/a&gt;.&lt;/strong&gt;&lt;/p&gt;
  404.  
  405.  
  406.  
  407. &lt;p&gt;It is also recommended to join the ongoing discussion at &lt;a href=&quot;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189&quot;&gt;https://discourse.ubuntu.com/t/phasing-out-bazaar-code-hosting/62189&lt;/a&gt;.&lt;/p&gt;</description>
  408. <pubDate>Fri, 06 Jun 2025 09:26:22 +0000</pubDate>
  409. </item>
  410. <item>
  411. <title>Ubuntu Blog: What if your container images were security-maintained at the source?</title>
  412. <guid isPermaLink="true">https://ubuntu.com//blog/what-if-your-container-images-were-security-maintained-at-the-source</guid>
  413. <link>https://ubuntu.com//blog/what-if-your-container-images-were-security-maintained-at-the-source</link>
  414. <description>&lt;p&gt;Software supply chain security has become a top concern for developers, DevOps engineers, and IT leaders. High-profile breaches and dependency compromises have shown that open source components can introduce risk if not properly vetted and maintained. Although containerization has become commonplace in contemporary development and deployment, it can have drawbacks in terms of reproducibility and security. &lt;/p&gt;
  415. &lt;p&gt;There is a dire need for container builds that are not only simple to deploy, but also safe, repeatable, and maintained long-term against new threats – and that’s why Canonical is introducing the Container Build Service.&lt;/p&gt;
  416. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;The open source security challenge&lt;/strong&gt;&lt;/h2&gt;
  417. &lt;p&gt;The use of open source software (OSS) is becoming more and more prevalent in enterprise environments. With &lt;a href=&quot;https://openssf.org/blog/2025/01/23/predictions-for-open-source-security-in-2025-ai-state-actors-and-supply-chains/&quot;&gt;analyses&lt;/a&gt; showing that it makes up around 70% of all software in use, OSS is no longer considered a supplementary element but rather the foundation of modern applications. What’s even more interesting is that&lt;a href=&quot;https://openssf.org/blog/2025/01/23/predictions-for-open-source-security-in-2025-ai-state-actors-and-supply-chains/&quot;&gt; 97% of commercial codebases&lt;/a&gt; are reported to have integrated some OSS components, highlighting how fundamental it has truly become. However, we’re also seeing that with this growing use of OSS, open source vulnerabilities are frequently discovered. &lt;a href=&quot;https://www.csoonline.com/article/574607/at-least-one-open-source-vulnerability-found-in-84-of-code-bases-report.html&quot;&gt;Research &lt;/a&gt;indicates that 84% of codebases contain at least one known open source vulnerability, with almost half of those vulnerabilities being categorized as high-severity. &lt;a href=&quot;https://www.blackduck.com/resources/analyst-reports/open-source-security-risk-analysis.html&quot;&gt;Black Duck’s 2025 Open Source Security and Risk Analysis (OSSRA)&lt;/a&gt; report showed that this risk has been increased due to by the sheer number of open source files used by applications -, which have tripled in just four years, this number has nearly tripled, from an average of 5,300 in 2020 to over 16,000 in 2024. This increased attack surface is directly correlated with this rise. &lt;/p&gt;
  418. &lt;p&gt;According to a &lt;a href=&quot;https://ubuntu.com/engage/2025-state-of-software-supply-chain?utm_source=linkedin&amp;amp;utm_medium=newsletter&amp;amp;utm_campaign=701N100000UbRw2IAF&quot;&gt;report from Canonical and IDC&lt;/a&gt;, organizations are adopting OSS primarily to reduce costs (44%), accelerate development (36%), and increase reliability (31%). Despite nine out of ten organizations expressing a preference to source packages from trusted OS repositories like those in their OS, most still pull directly from upstream registries. This means that the responsibility for patching falls heavily on IT teams. The report found that seven in ten teams dedicate over six hours per week (almost a full working day) to sourcing and applying security updates., and tThe same proportion mandates that high and critical-severity vulnerabilities arebe patched within 24 hours, yet only 41% feel confident they can meet that SLA. What’s also interesting is that more than half of organizations do not automatically upgrade their in-production systems or applications to the newest versions, leaving them exposed to known vulnerabilities.&lt;/p&gt;
  419. &lt;p&gt;Supply chain attacks are also becoming more frequent. A study conducted by &lt;a href=&quot;https://www.sonatype.com/state-of-the-software-supply-chain/2024/10-year-look#:~:text=Sadly%2C%20seven%20years%20later%2C%20in,defenseless%20against%20these%20growing%20risks&quot;&gt;Sonatype &lt;/a&gt;displayed how the number of software supply chain attacks doubled in 2024 alone, and according to a study done by &lt;a href=&quot;https://blogs.blackberry.com/en/2024/06/supply-chain-cybersecurity-survey-research#:~:text=What%20is%20the%20state%20of,in%20securing%20software%20supply%20chains&quot;&gt;Blackberry&lt;/a&gt; over 75% of organizations experienced a supply chain-related attack in the previous year. The Sonatype study also highlighted how malicious packages became highly prevalent in the last 12 months, with more than 500,000 malicious packages being found in public repositories – a 156% increase from the previous year. This highlights how attackers target upstream open source in order to compromise downstream users. &lt;/p&gt;
  420. &lt;p&gt;In light of these trends, development teams are seeking ways to ensure the integrity of their container images. Practices like reproducible builds and signed images are gaining popularity as defenses against tampering, while minimal images promise fewer vulnerabilities. However, implementing these measures requires significant effort and expertise. This is where Canonical’s latest offering comes in.&lt;/p&gt;
  421. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Canonical’s Container Build Service:  reproducible, hardened and security-maintained images&lt;/strong&gt;&lt;/h2&gt;
  422. &lt;p&gt;Canonical has launched a new &lt;a href=&quot;https://ubuntu.com/containers/container-build-service&quot;&gt;Container Build Service&lt;/a&gt; designed to meet the above challenges head-on. In essence, through this service, Canonical’s engineers will custom-build container images for any open source project or stack, with security and longevity as primary features. Whether it’s an open source application or a custom base image containing all the dependencies for your app, Canonical will containerize it according to your specifications and harden the image for production. The resulting container image is delivered in the Open Container Initiative (OCI) format and comes with up to 12 years of security maintenance.&lt;/p&gt;
  423. &lt;h3 class=&quot;wp-block-heading&quot;&gt;The entire container supported for up to 12 years&lt;/h3&gt;
  424. &lt;p&gt;Every package and library in the container – even those not originally in Ubuntu’s repositories – is covered under Canonical’s security maintenance commitment. We have a track record of patching critical vulnerabilities within an average of 24 hours on average, ensuring quick remediation of emerging threats. Unlike standard base images that cover only OS components, Canonical’s service will include all required upstream open source components in the container build. In other words, your entire open source dependency tree is kept safe – even if some parts of it were not packaged in Ubuntu before. This means teams can confidently use the latest frameworks, AI/ML libraries, or niche utilities, knowing Canonical will extend Ubuntu’s famous long-term support to those pieces as well.&lt;/p&gt;
  425. &lt;p&gt;Each container image build comes with a guaranteed security updates period of up to 12 years. This far outlasts the typical support window for community container images. It ensures that organizations in regulated or long-lived environments can run containers in production for a decade or more with ongoing patching. &lt;/p&gt;
  426. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Truly portable&lt;/h3&gt;
  427. &lt;p&gt;The hardened images are designed to run on any popular Linux host or Kubernetes platform. Whether your infrastructure is Ubuntu, RHEL, VMware, or a public cloud Kubernetes service, Canonical will support these images on that platform. This broad compatibility means you don’t have to be running Ubuntu on the host to benefit: the container images are truly portable and backed by Canonical across environments.&lt;/p&gt;
  428. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Long-term reproducibility and automation&lt;/h3&gt;
  429. &lt;p&gt;Canonical’s build pipeline emphasizes reproducibility and automation. Once your container image is designed and built, an automated pipeline takes over to continuously rebuild and update the image with the latest security patches. This ensures the image remains up to date over time without manual intervention, and it provides a reproducible build process (verifiable by Canonical) to guarantee that the image you run in production exactly matches the source and binaries that were vetted.&lt;/p&gt;
  430. &lt;p&gt;In short, the new Container Build Service delivers secure, reproducible, and highly dependable container images, tailor-made for your applications by the experts behind Ubuntu. It effectively offloads the heavy lifting of container security maintenance to Canonical, so your teams can focus on writing code and deploying features and not constantly chasing the next vulnerability in your container image.&lt;/p&gt;
  431. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Minimal footprint, optimal performance&lt;/strong&gt;&lt;/h2&gt;
  432. &lt;p&gt;A standout aspect of Canonical’s approach is the use of &lt;a href=&quot;https://ubuntu.com/containers/chiseled&quot;&gt;chiseled Ubuntu container images&lt;/a&gt;. Chiseled images are Canonical’s take on the “distroless” container concept – ultra-minimal images that include only the essential runtime components needed by your application and nothing more. By stripping away unnecessary packages, utilities, and metadata, chiseled images dramatically reduce image size and attack surface.&lt;/p&gt;
  433. &lt;p&gt;What exactly are chiseled images? They are built using an open source tool called Chisel which effectively sculpts down an application to its bare essentials. A chiseled Ubuntu container image  still originates from the Ubuntu base you know, but with all surplus components carved away.&lt;/p&gt;
  434. &lt;p&gt;Chiseled images include only the files and libraries strictly required to run your application, excluding surplus distro metadata, shells, package managers, and other tools not needed in production. Because of this minimalist approach, chiseled images are significantly smaller than typical Ubuntu images. This not only means less storage and faster transfer, but also inherently fewer places for vulnerabilities to hide. In a &lt;a href=&quot;https://azure.github.io/aca-dotnet-workshop/aca/12-optimize-containers/&quot;&gt;.NET container optimization exercise done by the ACA team at Microsoft&lt;/a&gt;, chiseling reduced the Backend API image size from 226 MB to 119 MB, a 56.6% reduction, and slashed CVEs from 25 to just 2 meaning a 92% decrease. Packages also dropped from 451 to 328, offering far fewer potential vulnerabilities to manage. &lt;/p&gt;
  435. &lt;p&gt;With less bloat, chiseled containers start up faster and use less memory. They have only the essentials, so pulling images and launching containers is quicker. For example, chiseling the .NET runtime images trimmed about 100 MB from the official image and produced a runtime base as small as 6 MB (compressed) for self-contained apps. Such a tiny footprint translates to faster network transfers and lower memory overhead at scale.&lt;/p&gt;
  436. &lt;p&gt;By using chiseled Ubuntu images in its container builds, Canonical ensures that each container is as small and locked down as possible, while still being based on the world’s most popular Linux distribution for developers. It’s a combination that delivers strong security out of the box. And because these images are built on Ubuntu, they inherit Ubuntu’s long-term support policies. Our container images align with Ubuntu LTS release cycles and receive the same five years of free security updates, extended to ten years with Ubuntu Pro, for the core components. In the new build service, that support can stretch to 12 years for enterprise customers, keeping even the minimal runtime components patched against CVEs over the long term.&lt;/p&gt;
  437. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Built on Ubuntu Pro &lt;/strong&gt;&lt;/h2&gt;
  438. &lt;p&gt;Canonical coined the term “Long Term Support (LTS)” back in 2006 with Ubuntu 6.06 LTS, pioneering the idea of stable OS releases with 5 years of guaranteed updates. Since then, Ubuntu LTS has become a byword for reliability in enterprises. In 2019, Canonical introduced Ubuntu Pro, which expanded on this foundation by providing comprehensive security maintenance not just for Ubuntu’s core system, but for thousands of community (universe) packages as well, along with enterprise features like FIPS 140 certified cryptography. Today, Ubuntu Pro is a very comprehensive open source security offering, covering over 36,000 packages with 10-year maintenance. &lt;/p&gt;
  439. &lt;p&gt;This background matters because the new Container Build Service is essentially Ubuntu Pro for your container images. Canonical is extending its expertise in automated patching, vulnerability remediation, and long-term maintenance to the full stack inside your containers. By having Canonical design and maintain your container image, you’re effectively gaining a dedicated team to watch over your software supply chain. Every upstream project included in your container is continually monitored for security issues. If a new vulnerability emerges in any layer of your stack – whether it’s in the OS, a shared library, or an obscure Python package –  Canonical will proactively apply the patch and issue an updated image through the automated pipeline. All of this happens largely behind the scenes, and you receive notifications or can track updates as needed for compliance. It’s a level of diligence that would be costly and difficult to replicate in-house.&lt;/p&gt;
  440. &lt;p&gt;Furthermore, Canonical’s involvement provides a chain of custody and trust that is hard to achieve with self-built images. The containers are built and signed by Canonical using the same infrastructure that builds official Ubuntu releases, ensuring integrity. Canonical and its partners have even established a zero-distance supply chain for critical assets – meaning there’s tight integration and verification from source code to the final container artefact. This approach greatly reduces the risk of tampering or hidden malware in the supply chain.&lt;/p&gt;
  441. &lt;p&gt;Because Ubuntu is so widely trusted, Canonical’s container images come pre-approved for use in highly regulated environments. Notably, hardened Ubuntu container images are already certified and available in the U.S. Department of Defense’s “Iron Bank” repository, which is a collection of hardened containers for government use. By leveraging Canonical’s service, organizations inherit this level of credibility and compliance. It’s easier to meet standards like FedRAMP, DISA-STIG, or the upcoming&lt;a href=&quot;https://canonical.com/solutions/open-source-security/cyber-resilience-act&quot;&gt; EU Cyber Resilience Act&lt;/a&gt; when your base images and components are backed by Ubuntu Pro’s security regime and provide auditable evidence of maintenance.&lt;/p&gt;
  442. &lt;p&gt;In summary, the Container Build Service stands on the shoulders of Ubuntu Pro and Canonical’s long experience in  open source security. Your custom container isn’t just another bespoke image, it becomes an enterprise-grade artifact, with clear maintenance commitments and security SLAs that auditors and IT governance teams will appreciate.&lt;/p&gt;
  443. &lt;p&gt;Canonical’s container build service aims to have every layer of the container stack – from OS to app dependencies – maintained. With optimized chiseled sizes, a decade of updates, and Canonical’s support, these images are crafted for production. &lt;/p&gt;
  444. &lt;p&gt;&lt;a href=&quot;https://ubuntu.com/containers/container-build-service&quot;&gt;Learn more about Canonical’s Container build Service &amp;gt;&lt;/a&gt;&lt;/p&gt;
  445. &lt;p&gt;&lt;a href=&quot;https://ubuntu.com/containers#get-in-touch&quot;&gt;Get in touch to discuss securing your container stack today &amp;gt; &lt;/a&gt;&lt;/p&gt;</description>
  446. <pubDate>Thu, 05 Jun 2025 13:00:00 +0000</pubDate>
  447. </item>
  448. <item>
  449. <title>St&amp;eacute;phane Graber: Announcing Incus 6.13</title>
  450. <guid isPermaLink="false">https://stgraber.org/?p=1739</guid>
  451. <link>https://stgraber.org/2025/06/05/announcing-incus-6-13/</link>
  452. <description>&lt;p&gt;The Incus team is pleased to announce the release of Incus 6.13!&lt;br /&gt;&lt;br /&gt;This is a VERY busy release with a lot of new features of all sizes&lt;br /&gt;and for all kinds of different users, so there should be something for&lt;br /&gt;everyone!&lt;/p&gt;
  453.  
  454.  
  455.  
  456. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://linuxcontainers.org/incus/try-it/&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-1740&quot; height=&quot;313&quot; src=&quot;https://stgraber.org/wp-content/uploads/2025/06/image.png&quot; width=&quot;874&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  457.  
  458.  
  459.  
  460. &lt;p&gt;The highlights for this release are:&lt;/p&gt;
  461.  
  462.  
  463.  
  464. &lt;ul class=&quot;wp-block-list&quot;&gt;
  465. &lt;li&gt;Windows agent support&lt;/li&gt;
  466.  
  467.  
  468.  
  469. &lt;li&gt;Improvements to incus-migrate&lt;/li&gt;
  470.  
  471.  
  472.  
  473. &lt;li&gt;SFTP on custom volumes&lt;/li&gt;
  474.  
  475.  
  476.  
  477. &lt;li&gt;Configurable instance external IP address on OVN networks&lt;/li&gt;
  478.  
  479.  
  480.  
  481. &lt;li&gt;Ability to pin gateway MAC address on OVN networks&lt;/li&gt;
  482.  
  483.  
  484.  
  485. &lt;li&gt;Clock handling in virtual machines&lt;/li&gt;
  486.  
  487.  
  488.  
  489. &lt;li&gt;New get-client-certificate and get-client-token commands&lt;/li&gt;
  490.  
  491.  
  492.  
  493. &lt;li&gt;DHCPv6 support for OCI&lt;/li&gt;
  494.  
  495.  
  496.  
  497. &lt;li&gt;Network host tables configuration for routed NICs&lt;/li&gt;
  498.  
  499.  
  500.  
  501. &lt;li&gt;Support for split image publishing&lt;/li&gt;
  502.  
  503.  
  504.  
  505. &lt;li&gt;Preseed of certificates&lt;/li&gt;
  506.  
  507.  
  508.  
  509. &lt;li&gt;Configuration of list format in the CLI&lt;/li&gt;
  510.  
  511.  
  512.  
  513. &lt;li&gt;Add CLI aliases for create/add and delete/remove/rm&lt;/li&gt;
  514.  
  515.  
  516.  
  517. &lt;li&gt;OS metrics are now included in Incus metrics when running on Incus OS&lt;/li&gt;
  518.  
  519.  
  520.  
  521. &lt;li&gt;Converted more database logic to generated code&lt;/li&gt;
  522.  
  523.  
  524.  
  525. &lt;li&gt;Converted more CLI list functions to using server side filtering&lt;/li&gt;
  526.  
  527.  
  528.  
  529. &lt;li&gt;Converted more documentation to be generated from the code&lt;/li&gt;
  530. &lt;/ul&gt;
  531.  
  532.  
  533.  
  534. &lt;p&gt;The full announcement and changelog can be &lt;a href=&quot;https://discuss.linuxcontainers.org/t/incus-6-13-has-been-released/23899&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;found here&lt;/a&gt;.&lt;br /&gt;And for those who prefer videos, here’s the release overview video:&lt;/p&gt;
  535.  
  536.  
  537.  
  538. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  539.  
  540. &lt;/div&gt;&lt;/figure&gt;
  541.  
  542.  
  543.  
  544. &lt;p&gt;You can take the latest release of Incus up for a spin through our online demo service at: &lt;a href=&quot;https://linuxcontainers.org/incus/try-it/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;https://linuxcontainers.org/incus/try-it/&lt;/a&gt;&lt;/p&gt;
  545.  
  546.  
  547.  
  548. &lt;p&gt;And as always, my company is offering commercial support on Incus, ranging from by-the-hour support contracts to one-off services on things like initial migration from LXD, review of your deployment to squeeze the most out of Incus or even feature sponsorship. You’ll find all details of that here: &lt;a href=&quot;https://zabbly.com/incus&quot;&gt;https://zabbly.com/incus&lt;/a&gt;&lt;/p&gt;
  549.  
  550.  
  551.  
  552. &lt;p&gt;Donations towards my work on this and other open source projects is also always appreciated, you can  find me on &lt;a href=&quot;https://github.com/sponsors/stgraber&quot;&gt;Github Sponsors&lt;/a&gt;, &lt;a href=&quot;https://patreon.com/stgraber&quot;&gt;Patreon&lt;/a&gt; and &lt;a href=&quot;https://ko-fi.com/stgraber&quot;&gt;Ko-fi&lt;/a&gt;.&lt;/p&gt;
  553.  
  554.  
  555.  
  556. &lt;p&gt;Enjoy!&lt;/p&gt;
  557.  
  558.  
  559. &lt;p&gt;&lt;/p&gt;</description>
  560. <pubDate>Thu, 05 Jun 2025 05:07:55 +0000</pubDate>
  561. </item>
  562. <item>
  563. <title>Podcast Ubuntu Portugal: E350 a Senhora Dos Anéis</title>
  564. <guid isPermaLink="false">https://hub.podcastubuntuportugal.org/s/MYkEab99dWM6zpH/download/e350.mp3</guid>
  565. <link>https://podcastubuntuportugal.org/e350/</link>
  566. <description>&lt;p&gt;De regresso triunfal do Oppidum Sena, onde apanharam uma onda de calor e uma barrigada de cabrito, queijo e vinho, os nossos heróis trazem novidades da Wikicon Portugal 2025 e contam-nos as suas aventuras tecnológicas, que incluem despir um Cervantes e apanhar felinos chamados Felicity em sítios estranhos da Internet. Para recebê-los esteve presente a Princesa Leia, a.k.a., Joana Simões, a.k.a. A Senhora dos Anéis, regressada de uma gloriosa missão em Tóquio e de partida para o México - a conversa fará tremer a terra debaixo dos vossos pés e os satélites acima das vossas cabeças!&lt;/p&gt;
  567. &lt;p&gt;Já sabem: oiçam, subscrevam e partilhem!&lt;/p&gt;
  568. &lt;ul&gt;
  569. &lt;li&gt;BQ Cervantes Touch Light: &lt;a href=&quot;https://youtu.be/OO33OnIZjmg&quot;&gt;https://youtu.be/OO33OnIZjmg&lt;/a&gt;&lt;/li&gt;
  570. &lt;li&gt;Arqueologia BQ: &lt;a href=&quot;https://web.archive.org/web/20130807115903/http://www.bqreaders.com/productos/cervantes-touch-light.html&quot;&gt;https://web.archive.org/web/20130807115903/http://www.bqreaders.com/productos/cervantes-touch-light.html&lt;/a&gt;&lt;/li&gt;
  571. &lt;li&gt;Um Cervantes todo nu: &lt;a href=&quot;https://youtu.be/TuR9sY94Nq8&quot;&gt;https://youtu.be/TuR9sY94Nq8&lt;/a&gt;&lt;/li&gt;
  572. &lt;li&gt;Colmi R02 ring: &lt;a href=&quot;https://www.colmi.info/products/colmi-r02-smart-ring&quot;&gt;https://www.colmi.info/products/colmi-r02-smart-ring&lt;/a&gt;
  573. &lt;ul&gt;
  574. &lt;li&gt;&lt;a href=&quot;https://github.com/doublebyte1/calmi/tree/master?tab=readme-ov-file&quot;&gt;https://github.com/doublebyte1/calmi/tree/master?tab=readme-ov-file&lt;/a&gt;&lt;/li&gt;
  575. &lt;li&gt;&lt;a href=&quot;https://github.com/tahnok/colmi_r02_client&quot;&gt;https://github.com/tahnok/colmi_r02_client&lt;/a&gt;&lt;/li&gt;
  576. &lt;/ul&gt;
  577. &lt;/li&gt;
  578. &lt;li&gt;PC Componentes / Felicity in the wild: &lt;a href=&quot;https://youtu.be/psbRzO5Wb4U?t=580&quot;&gt;https://youtu.be/psbRzO5Wb4U?t=580&lt;/a&gt;&lt;/li&gt;
  579. &lt;li&gt;Impulse Poetry Night, 4 Junho: &lt;a href=&quot;https://noc.social/@doublebyte/114620767468634362&quot;&gt;https://noc.social/@doublebyte/114620767468634362&lt;/a&gt;&lt;/li&gt;
  580. &lt;li&gt;FOSS4G Europe 2025: &lt;a href=&quot;https://2025.europe.foss4g.org/&quot;&gt;https://2025.europe.foss4g.org/&lt;/a&gt;&lt;/li&gt;
  581. &lt;li&gt;Tokyo Code Sprint: &lt;a href=&quot;https://noc.social/@doublebyte/114559916913502591&quot;&gt;https://noc.social/@doublebyte/114559916913502591&lt;/a&gt;&lt;/li&gt;
  582. &lt;li&gt;Jovem! Desenha uma mascote e ganha prémios! Inscreve-te! Participa! &lt;a href=&quot;https://digitalfreedoms.org/en/sfd/blog/sfd-mascot-huion-challenge-2025&quot;&gt;https://digitalfreedoms.org/en/sfd/blog/sfd-mascot-huion-challenge-2025&lt;/a&gt;&lt;/li&gt;
  583. &lt;li&gt;LCD Porto – Laboratório de Criação Digital: &lt;a href=&quot;https://lcdporto.org&quot;&gt;https://lcdporto.org&lt;/a&gt;&lt;/li&gt;
  584. &lt;li&gt;WikiCon Portugal 2025, Seia, 30/05-01/06: &lt;a href=&quot;https://pt.wikimedia.org/wiki/WikiCon_Portugal_2025/Programa&quot;&gt;https://pt.wikimedia.org/wiki/WikiCon_Portugal_2025/Programa&lt;/a&gt;&lt;/li&gt;
  585. &lt;li&gt;Ubucon Europe 2025, Málaga, 20-21 de Junho (Open South Code): &lt;a href=&quot;https://discourse.ubuntu.com/t/ubucon-europe-opensouthcode-2025/57060&quot;&gt;https://discourse.ubuntu.com/t/ubucon-europe-opensouthcode-2025/57060&lt;/a&gt;&lt;/li&gt;
  586. &lt;li&gt;Festa do Software Livre 2025, Porto, 3 a 5 de Outubro: &lt;a href=&quot;https://festa2025.softwarelivre.eu/pt/&quot;&gt;https://festa2025.softwarelivre.eu/pt/&lt;/a&gt;&lt;/li&gt;
  587. &lt;li&gt;Ubuntu Summit 2025, Londres, 23-24 de Outubro: &lt;a href=&quot;https://ubuntu.com/blog/ubuntu-summit-25-10-is-coming-to-your-circle-of-friends-from-london&quot;&gt;https://ubuntu.com/blog/ubuntu-summit-25-10-is-coming-to-your-circle-of-friends-from-london&lt;/a&gt;&lt;/li&gt;
  588. &lt;li&gt;LoCo PT: &lt;a href=&quot;https://loco.ubuntu.com/teams/ubuntu-pt/&quot;&gt;https://loco.ubuntu.com/teams/ubuntu-pt/&lt;/a&gt;&lt;/li&gt;
  589. &lt;li&gt;Mastodon: &lt;a href=&quot;https://masto.pt/@pup&quot;&gt;https://masto.pt/@pup&lt;/a&gt;&lt;/li&gt;
  590. &lt;li&gt;Youtube: &lt;a href=&quot;https://youtube.com/PodcastUbuntuPortugal&quot;&gt;https://youtube.com/PodcastUbuntuPortugal&lt;/a&gt;&lt;/li&gt;
  591. &lt;/ul&gt;
  592. &lt;h3 id=&quot;atribuição-e-licenças&quot;&gt;Atribuição e licenças&lt;/h3&gt;
  593. &lt;p&gt;Este episódio foi produzido por Diogo Constantino, Miguel e Tiago Carrondo e editado pelo &lt;a href=&quot;https://senhorpodcast.pt/&quot;&gt;Senhor Podcast&lt;/a&gt;.
  594. O website é produzido por Tiago Carrondo e o &lt;a href=&quot;https://gitlab.com/podcastubuntuportugal/website&quot;&gt;código aberto&lt;/a&gt; está licenciado nos termos da &lt;a href=&quot;https://gitlab.com/podcastubuntuportugal/website/main/LICENSE&quot;&gt;Licença MIT&lt;/a&gt;. (&lt;a href=&quot;https://creativecommons.org/licenses/by/4.0/)&quot;&gt;https://creativecommons.org/licenses/by/4.0/)&lt;/a&gt;. A música do genérico é: “Won’t see it comin’ (Feat Aequality &amp;amp; N’sorte d’autruche)”, por Alpha Hydrae e está licenciada nos termos da &lt;a href=&quot;https://creativecommons.org/publicdomain/zero/1.0/&quot;&gt;CC0 1.0 Universal License&lt;/a&gt;.
  595. Este episódio e a imagem utilizada estão licenciados nos termos da licença: &lt;a href=&quot;https://creativecommons.org/licenses/by-nc-nd/4.0/&quot;&gt;Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)&lt;/a&gt;, &lt;a href=&quot;https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode&quot;&gt;cujo texto integral pode ser lido aqui&lt;/a&gt;. Estamos abertos a licenciar para permitir outros tipos de utilização, &lt;a href=&quot;https://podcastubuntuportugal.org/contactos&quot;&gt;contactem-nos&lt;/a&gt; para validação e autorização.
  596. A arte de episódio foi criada por encomenda pela Shizamura - artista, ilustradora e autora de BD. Podem ficar a conhecer melhor a &lt;a href=&quot;https://ciberlandia.pt/@shizamura&quot;&gt;Shizamura na Ciberlândia&lt;/a&gt; e no &lt;a href=&quot;https://sarilho.net/&quot;&gt;seu sítio web&lt;/a&gt;.&lt;/p&gt;</description>
  597. <pubDate>Thu, 05 Jun 2025 00:00:00 +0000</pubDate>
  598.        <enclosure url="https://hub.podcastubuntuportugal.org/s/MYkEab99dWM6zpH/download/e350.mp3" length="30742777" type="audio/mpeg"/>
  599. </item>
  600. <item>
  601. <title>Faizul &quot;Piju&quot; 9M2PJU: Building a Plex Media Server with Raspberry Pi</title>
  602. <guid isPermaLink="false">https://hamradio.my/?p=7464</guid>
  603. <link>https://hamradio.my/2025/06/building-a-plex-media-server-with-raspberry-pi/</link>
  604. <description>&lt;p&gt;&lt;/p&gt;
  605.  
  606.  
  607.  
  608. &lt;p&gt;If you’re looking for a low-power, always-on solution for streaming your personal media library, the &lt;strong&gt;Raspberry Pi&lt;/strong&gt; makes a great Plex server. It’s compact, quiet, affordable, and perfect for handling basic media streaming—especially for home use.&lt;/p&gt;
  609.  
  610.  
  611.  
  612. &lt;p&gt;In this post, I’ll guide you through setting up &lt;strong&gt;Plex Media Server&lt;/strong&gt; on a &lt;strong&gt;Raspberry Pi&lt;/strong&gt;, using Raspberry Pi OS (Lite or Full) or Debian-based distros like Ubuntu Server.&lt;/p&gt;
  613.  
  614.  
  615.  
  616. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  617.  
  618.  
  619.  
  620. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-what-you-ll-need&quot;&gt;&lt;img alt=&quot;🧰&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f9f0.png&quot; style=&quot;height: 1em;&quot; /&gt; What You’ll Need&lt;/h3&gt;
  621.  
  622.  
  623.  
  624. &lt;ul class=&quot;wp-block-list&quot;&gt;
  625. &lt;li&gt;Raspberry Pi 4 or 5 (at least 2GB RAM, 4GB+ recommended)&lt;/li&gt;
  626.  
  627.  
  628.  
  629. &lt;li&gt;microSD card (32GB+), or SSD via USB 3.0&lt;/li&gt;
  630.  
  631.  
  632.  
  633. &lt;li&gt;External storage for media (USB HDD/SSD or NAS)&lt;/li&gt;
  634.  
  635.  
  636.  
  637. &lt;li&gt;Ethernet or Wi-Fi connection&lt;/li&gt;
  638.  
  639.  
  640.  
  641. &lt;li&gt;Raspberry Pi OS (Lite or Desktop)&lt;/li&gt;
  642.  
  643.  
  644.  
  645. &lt;li&gt;A Plex account (free is enough)&lt;/li&gt;
  646. &lt;/ul&gt;
  647.  
  648.  
  649.  
  650. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  651.  
  652.  
  653.  
  654. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-step-1-prepare-the-raspberry-pi&quot;&gt;&lt;img alt=&quot;⚙&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2699.png&quot; style=&quot;height: 1em;&quot; /&gt; Step 1: Prepare the Raspberry Pi&lt;/h3&gt;
  655.  
  656.  
  657.  
  658. &lt;ol class=&quot;wp-block-list&quot;&gt;
  659. &lt;li&gt;Flash Raspberry Pi OS using &lt;a href=&quot;https://www.raspberrypi.com/software/&quot;&gt;Raspberry Pi Imager&lt;/a&gt;&lt;/li&gt;
  660.  
  661.  
  662.  
  663. &lt;li&gt;Enable SSH and set hostname (optional)&lt;/li&gt;
  664.  
  665.  
  666.  
  667. &lt;li&gt;Boot the Pi, log in, and update:&lt;/li&gt;
  668. &lt;/ol&gt;
  669.  
  670.  
  671.  
  672. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo apt update &amp;amp;&amp;amp; sudo apt upgrade -y
  673. &lt;/code&gt;&lt;/pre&gt;
  674.  
  675.  
  676.  
  677. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  678.  
  679.  
  680.  
  681. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-step-2-install-plex-media-server&quot;&gt;&lt;img alt=&quot;📦&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4e6.png&quot; style=&quot;height: 1em;&quot; /&gt; Step 2: Install Plex Media Server&lt;/h3&gt;
  682.  
  683.  
  684.  
  685. &lt;p&gt;Plex is available for ARM-based devices via their official repository.&lt;/p&gt;
  686.  
  687.  
  688.  
  689. &lt;ol class=&quot;wp-block-list&quot;&gt;
  690. &lt;li&gt;Add Plex repo and key:&lt;/li&gt;
  691. &lt;/ol&gt;
  692.  
  693.  
  694.  
  695. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;curl https://downloads.plex.tv/plex-keys/PlexSign.key | sudo apt-key add -
  696. echo deb https://downloads.plex.tv/repo/deb public main | sudo tee /etc/apt/sources.list.d/plexmediaserver.list
  697. sudo apt update
  698. &lt;/code&gt;&lt;/pre&gt;
  699.  
  700.  
  701.  
  702. &lt;ol class=&quot;wp-block-list&quot; start=&quot;2&quot;&gt;
  703. &lt;li&gt;Install Plex:&lt;/li&gt;
  704. &lt;/ol&gt;
  705.  
  706.  
  707.  
  708. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo apt install plexmediaserver -y
  709. &lt;/code&gt;&lt;/pre&gt;
  710.  
  711.  
  712.  
  713. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  714.  
  715.  
  716.  
  717. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-step-3-enable-and-start-the-service&quot;&gt;&lt;img alt=&quot;🔁&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f501.png&quot; style=&quot;height: 1em;&quot; /&gt; Step 3: Enable and Start the Service&lt;/h3&gt;
  718.  
  719.  
  720.  
  721. &lt;p&gt;Enable Plex on boot and start the service:&lt;/p&gt;
  722.  
  723.  
  724.  
  725. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo systemctl enable plexmediaserver
  726. sudo systemctl start plexmediaserver
  727. &lt;/code&gt;&lt;/pre&gt;
  728.  
  729.  
  730.  
  731. &lt;p&gt;Make sure it’s running:&lt;/p&gt;
  732.  
  733.  
  734.  
  735. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo systemctl status plexmediaserver
  736. &lt;/code&gt;&lt;/pre&gt;
  737.  
  738.  
  739.  
  740. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  741.  
  742.  
  743.  
  744. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-step-4-access-plex-web-interface&quot;&gt;&lt;img alt=&quot;🌐&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f310.png&quot; style=&quot;height: 1em;&quot; /&gt; Step 4: Access Plex Web Interface&lt;/h3&gt;
  745.  
  746.  
  747.  
  748. &lt;p&gt;Open your browser and go to:&lt;/p&gt;
  749.  
  750.  
  751.  
  752. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;http://&amp;lt;your-pi-ip&amp;gt;:32400/web
  753. &lt;/code&gt;&lt;/pre&gt;
  754.  
  755.  
  756.  
  757. &lt;p&gt;Log in with your Plex account and begin the setup wizard.&lt;/p&gt;
  758.  
  759.  
  760.  
  761. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  762.  
  763.  
  764.  
  765. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-step-5-add-your-media-library&quot;&gt;&lt;img alt=&quot;📂&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4c2.png&quot; style=&quot;height: 1em;&quot; /&gt; Step 5: Add Your Media Library&lt;/h3&gt;
  766.  
  767.  
  768.  
  769. &lt;p&gt;Plug in your external HDD or mount a network share, then:&lt;/p&gt;
  770.  
  771.  
  772.  
  773. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo mkdir -p /mnt/media
  774. sudo mount /dev/sda1 /mnt/media
  775. &lt;/code&gt;&lt;/pre&gt;
  776.  
  777.  
  778.  
  779. &lt;p&gt;Make sure Plex can access it:&lt;/p&gt;
  780.  
  781.  
  782.  
  783. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;sudo chown -R plex:plex /mnt/media
  784. &lt;/code&gt;&lt;/pre&gt;
  785.  
  786.  
  787.  
  788. &lt;p&gt;Add the media folder during the Plex setup under Library &amp;gt; Add Library.&lt;/p&gt;
  789.  
  790.  
  791.  
  792. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  793.  
  794.  
  795.  
  796. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-optional-tips&quot;&gt;&lt;img alt=&quot;💡&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4a1.png&quot; style=&quot;height: 1em;&quot; /&gt; Optional Tips&lt;/h3&gt;
  797.  
  798.  
  799.  
  800. &lt;ul class=&quot;wp-block-list&quot;&gt;
  801. &lt;li&gt;&lt;strong&gt;Transcoding:&lt;/strong&gt; The Pi can handle direct play (no transcoding) well, but struggles with transcoding large files. Use compatible formats like H.264 (MP4).&lt;/li&gt;
  802.  
  803.  
  804.  
  805. &lt;li&gt;&lt;strong&gt;USB Boot:&lt;/strong&gt; For better performance, boot the Pi from an SSD instead of a microSD card.&lt;/li&gt;
  806.  
  807.  
  808.  
  809. &lt;li&gt;&lt;strong&gt;Power Supply:&lt;/strong&gt; Use a proper 5V/3A PSU to avoid crashes under heavy disk load.&lt;/li&gt;
  810.  
  811.  
  812.  
  813. &lt;li&gt;&lt;strong&gt;Thermal:&lt;/strong&gt; Add a heatsink or fan for the Pi if using Plex for long sessions.&lt;/li&gt;
  814. &lt;/ul&gt;
  815.  
  816.  
  817.  
  818. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  819.  
  820.  
  821.  
  822. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-secure-your-server&quot;&gt;&lt;img alt=&quot;🔐&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f510.png&quot; style=&quot;height: 1em;&quot; /&gt; Secure Your Server&lt;/h3&gt;
  823.  
  824.  
  825.  
  826. &lt;ul class=&quot;wp-block-list&quot;&gt;
  827. &lt;li&gt;Use your router to forward port &lt;code&gt;32400&lt;/code&gt; only if you want remote access.&lt;/li&gt;
  828.  
  829.  
  830.  
  831. &lt;li&gt;Set a strong Plex password.&lt;/li&gt;
  832.  
  833.  
  834.  
  835. &lt;li&gt;Enable Tailscale or WireGuard for secure remote access without exposing ports.&lt;/li&gt;
  836. &lt;/ul&gt;
  837.  
  838.  
  839.  
  840. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  841.  
  842.  
  843.  
  844. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;h-conclusion&quot;&gt;&lt;img alt=&quot;✅&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2705.png&quot; style=&quot;height: 1em;&quot; /&gt; Conclusion&lt;/h3&gt;
  845.  
  846.  
  847.  
  848. &lt;p&gt;A Raspberry Pi might not replace a full-blown NAS or dedicated server, but for personal use or as a secondary Plex node, it’s surprisingly capable. With low energy usage and silent operation, it’s the perfect DIY home media solution.&lt;/p&gt;
  849.  
  850.  
  851.  
  852. &lt;p&gt;If you’re running other services like Pi-hole or Home Assistant, the Pi can multitask well — just avoid overloading it with too much transcoding.&lt;/p&gt;
  853.  
  854.  
  855.  
  856. &lt;p&gt;&lt;/p&gt;
  857. &lt;p&gt;The post &lt;a href=&quot;https://hamradio.my/2025/06/building-a-plex-media-server-with-raspberry-pi/&quot;&gt;Building a Plex Media Server with Raspberry Pi&lt;/a&gt; appeared first on &lt;a href=&quot;https://hamradio.my&quot;&gt;Hamradio.my - Amateur Radio, Tech Insights and Product Reviews&lt;/a&gt; by &lt;a href=&quot;https://hamradio.my/author/9m2pju/&quot;&gt;9M2PJU&lt;/a&gt;.&lt;/p&gt;</description>
  858. <pubDate>Wed, 04 Jun 2025 21:30:17 +0000</pubDate>
  859. </item>
  860. <item>
  861. <title>The Fridge: Ubuntu Weekly Newsletter Issue 894</title>
  862. <guid isPermaLink="false">https://fridge.ubuntu.com/?p=10529</guid>
  863. <link>https://fridge.ubuntu.com/2025/06/02/ubuntu-weekly-newsletter-issue-894/</link>
  864. <description>&lt;figure class=&quot;wp-block-image&quot;&gt;&lt;img alt=&quot;&quot; src=&quot;https://fridge.ubuntu.com/wp-content/uploads/2020/02/c9d7/header.png&quot; /&gt;&lt;/figure&gt;
  865.  
  866.  
  867.  
  868. &lt;p&gt;Welcome to the Ubuntu Weekly Newsletter, &lt;strong&gt;Issue 894 for the week of May 25 – 31, 2025&lt;/strong&gt;. The full version of this issue is available &lt;a href=&quot;https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-issue-894/61717&quot;&gt;here&lt;/a&gt;.&lt;/p&gt;
  869.  
  870.  
  871.  
  872. &lt;p&gt;In this issue we cover:&lt;/p&gt;
  873.  
  874.  
  875.  
  876. &lt;ul&gt;&lt;li&gt;Extended Security Maintenance for Ubuntu 20.04 (Focal Fossa) began on May 29, 2025&lt;/li&gt;&lt;li&gt;Ubuntu Studio 22.04 LTS has reached End-Of-Life (EOL)&lt;/li&gt;&lt;li&gt;Bringing together 20 years of documentation&lt;/li&gt;&lt;li&gt;Ubuntu Stats&lt;/li&gt;&lt;li&gt;Hot in Support&lt;/li&gt;&lt;li&gt;LXD: Weekly news #396&lt;/li&gt;&lt;li&gt;Rocks Public Journal; 2025-05-30&lt;/li&gt;&lt;li&gt;Other Meeting Reports&lt;/li&gt;&lt;li&gt;Upcoming Meetings and Events&lt;/li&gt;&lt;li&gt;Successful Training Session by Ubuntu Nepal in Collaboration with GNOME Nepal&lt;/li&gt;&lt;li&gt;Web Frontend deployment with Ubuntu Workshop @ Pohang&lt;/li&gt;&lt;li&gt;LoCo Events&lt;/li&gt;&lt;li&gt;LXD 6.4 has been released&lt;/li&gt;&lt;li&gt;Dependency merging in APT 3.1.0ubuntu2&lt;/li&gt;&lt;li&gt;Supercharging Ubuntu Releases: Monthly Snapshots &amp;amp; Automation&lt;/li&gt;&lt;li&gt;Ubuntu Summit 25.10 is coming to your circle of friends, from London&lt;/li&gt;&lt;li&gt;The 2025 Frankfurt Engineering Sprint: What did you miss?&lt;/li&gt;&lt;li&gt;Apport local information disclosure vulnerability fixes available&lt;/li&gt;&lt;li&gt;Other Community News&lt;/li&gt;&lt;li&gt;Ubuntu Cloud News&lt;/li&gt;&lt;li&gt;In the Blogosphere&lt;/li&gt;&lt;li&gt;Other Articles of Interest&lt;/li&gt;&lt;li&gt;Featured Audio and Video&lt;/li&gt;&lt;li&gt;Updates and Security for Ubuntu 20.04, 22.04, 24.04, 24.10, and 25.04&lt;/li&gt;&lt;li&gt;And much more!&lt;/li&gt;&lt;/ul&gt;
  877.  
  878.  
  879.  
  880. &lt;p&gt;&lt;strong&gt;The Ubuntu Weekly Newsletter is brought to you by:&lt;/strong&gt;&lt;/p&gt;
  881.  
  882.  
  883.  
  884. &lt;ul&gt;&lt;li&gt;Krytarik Raido&lt;/li&gt;&lt;li&gt;Bashing-om&lt;/li&gt;&lt;li&gt;Chris Guiver&lt;/li&gt;&lt;li&gt;Wild Man&lt;/li&gt;&lt;li&gt;Din Mušić – LXD&lt;/li&gt;&lt;li&gt;Cristovao Cordeiro (cjdc) – Rocks&lt;/li&gt;&lt;li&gt;And many others&lt;/li&gt;&lt;/ul&gt;
  885.  
  886.  
  887.  
  888. &lt;p&gt;If you have a story idea for the Weekly Newsletter, join the &lt;a href=&quot;https://lists.ubuntu.com/mailman/listinfo/Ubuntu-news-team&quot;&gt;Ubuntu News Team mailing list&lt;/a&gt; and submit it. Ideas can also be added to the &lt;a href=&quot;https://discourse.ubuntu.com/t/ubuntu-weekly-newsletter-ideas/40053&quot;&gt;wiki&lt;/a&gt;!&lt;/p&gt;
  889.  
  890.  
  891.  
  892. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignleft&quot;&gt;&lt;img alt=&quot;&quot; src=&quot;https://fridge.ubuntu.com/wp-content/uploads/2015/05/ab28/CCL.png&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  893.  
  894.  
  895.  
  896. &lt;p&gt;&lt;a href=&quot;https://fridge.ubuntu.com/2025/06/02/ubuntu-weekly-newsletter-issue-894/&quot;&gt;&lt;/a&gt;.&lt;/p&gt;</description>
  897. <pubDate>Mon, 02 Jun 2025 22:07:22 +0000</pubDate>
  898. </item>
  899. <item>
  900. <title>Simon Quigley: Willpower is a muscle</title>
  901. <guid isPermaLink="false">https://medium.com/p/803530d6eb74</guid>
  902. <link>https://medium.com/@tsimonq2/willpower-is-a-muscle-803530d6eb74?source=rss-abe8950a00ea------2</link>
  903. <description>&lt;p&gt;“The most frustrating thing in the world for me, is when normal people judge a man like myself on what it really takes to extract &lt;em&gt;greatness&lt;/em&gt; from &lt;em&gt;nothing&lt;/em&gt;. It takes &lt;strong&gt;&lt;em&gt;every bit&lt;/em&gt;&lt;/strong&gt; of who you are.”&lt;br /&gt; — David Goggins&lt;/p&gt;&lt;p&gt;Willpower is a muscle, just like lifting weights. Just like a muscle, in order to build it up, you must actively do things you &lt;em&gt;do &lt;/em&gt;&lt;strong&gt;&lt;em&gt;not&lt;/em&gt;&lt;/strong&gt; want to do.&lt;/p&gt;&lt;p&gt;If you’re an athlete, you already understand this to an extent. When you’re training to run a marathon, you’re not training your physical muscles, as much as you are training your mind to overcome that barrier. When you progressively run more distance, and perhaps some days take it a bit easy, that’s a muscle.&lt;/p&gt;&lt;p&gt;Still don’t believe me? Don’t worry, the neuroscience is still new. It’s entirely possible I’m wrong. :)&lt;/p&gt;&lt;p&gt;I’ll start by sharing the podcast which made me realize this is an actual muscle:&lt;/p&gt;&lt;a href=&quot;https://medium.com/media/8ee564a66edae48d09412033fdadecf2/href&quot;&gt;https://medium.com/media/8ee564a66edae48d09412033fdadecf2/href&lt;/a&gt;&lt;p&gt;I’d encourage you to take the time and watch that podcast in its entirety. It will answer any remaining questions you have about David Goggins.&lt;/p&gt;&lt;p&gt;In case Goggins is a bit too crude for you, I’ll share the following quote from Dr. Huberman in that exact episode:&lt;/p&gt;&lt;p&gt;“In &lt;em&gt;humans&lt;/em&gt;, not some mouse, when people do something they &lt;em&gt;don’t want to do&lt;/em&gt;, it’s not about adding more work. It’s about adding more work &lt;em&gt;that you don’t want to do&lt;/em&gt;.”&lt;/p&gt;&lt;p&gt;He also introduces us to the Anterior Mid-Cingulate Cortex.&lt;/p&gt;&lt;p&gt;“But Simon, you don’t have a doctorate. How do you know about this?”&lt;br /&gt;I just showed you. The video is linked above. :)&lt;/p&gt;&lt;p&gt;The Anterior Mid-Cingulate Cortex is the part of your brain dealing with willpower. We now know &lt;a href=&quot;https://arxiv.org/abs/2503.04453&quot;&gt;we can measure it&lt;/a&gt;, how &lt;a href=&quot;https://www.nature.com/articles/s41467-024-49600-7&quot;&gt;it’s related to the pleasure center of the brain&lt;/a&gt;, and even that &lt;a href=&quot;https://www.nature.com/articles/s41598-025-97529-8&quot;&gt;it’s related to neuroticism&lt;/a&gt;. Decision-making skills? &lt;a href=&quot;https://academic.oup.com/cercor/article/34/4/bhae135/7644533&quot;&gt;Yep.&lt;/a&gt;&lt;/p&gt;&lt;p&gt;As you can probably see, the science on this is &lt;em&gt;incredibly&lt;/em&gt; new. If you’re in a position to fund academic research, please, &lt;strong&gt;graciously&lt;/strong&gt; go fund research on this part of the brain. I genuinely want to see if someone can give me an agreeable dissent.&lt;/p&gt;&lt;p&gt;In the meantime, I’ll lean on psychology here:&lt;/p&gt;&lt;a href=&quot;https://medium.com/media/fcadeff588931b9ed5982bce2e058a3b/href&quot;&gt;https://medium.com/media/fcadeff588931b9ed5982bce2e058a3b/href&lt;/a&gt;&lt;p&gt;I’m human, just like you. I can’t tell you to do things you don’t want to do. I’m also not right 100% of the time. In fact, if you’re okay reading the Bible, I’d recommend you read Matthew 18:3–5. It will explain a lot.&lt;/p&gt;&lt;p&gt;In short, your motivation and willpower has to come &lt;em&gt;from you&lt;/em&gt;.&lt;br /&gt;Not me, not Goggins, not Jocko, not Peterson. It has to come from within. I’m not talking spiritually here (again, does not replace the underlying spiritual motivators), but rather, &lt;em&gt;mentally.&lt;/em&gt;&lt;/p&gt;&lt;p&gt;I walked 15 miles last week.&lt;/p&gt;&lt;p&gt;Did I want to walk 15 miles? Nope. It hurt.&lt;br /&gt;Did I do it anyway, because it was sunny outside and I’ve been sincerely focused on improving my habit structure? Yes.&lt;br /&gt;Did I inspire tons of people to start walking in a healthy way, just by leading by example? Yes.&lt;/p&gt;&lt;p&gt;My advice to you all is, remember to take your day off. That doesn’t mean a lazy day:&lt;/p&gt;&lt;a href=&quot;https://medium.com/media/e4eff5dc25bd5d9dfdb27acfd29b8be4/href&quot;&gt;https://medium.com/media/e4eff5dc25bd5d9dfdb27acfd29b8be4/href&lt;/a&gt;&lt;p&gt;Meaning, be responsible. Just know your own limits. Know your own personal local minimums and maximums. Know your absolutes, too. Show love to others; don’t hit them with a hammer from my toolbox, please.&lt;/p&gt;&lt;p&gt;That’s all for now. Be well. This week doesn’t have a theme; now I can &lt;em&gt;finally&lt;/em&gt; write about more of the technical topics! :D&lt;/p&gt;&lt;p&gt;&lt;a href=&quot;https://music.youtube.com/playlist?list=PLTFKpItPoJaz5zwtCiP8_YplfO-65oqbB&quot;&gt;&lt;em&gt;New month, new mixtape, by the way.&lt;/em&gt;&lt;/a&gt;&lt;/p&gt;&lt;img alt=&quot;&quot; height=&quot;1&quot; src=&quot;https://medium.com/_/stat?event=post.clientViewed&amp;amp;referrerSource=full_rss&amp;amp;postId=803530d6eb74&quot; width=&quot;1&quot; /&gt;</description>
  904. <pubDate>Mon, 02 Jun 2025 22:04:18 +0000</pubDate>
  905. </item>
  906. <item>
  907. <title>Faizul &quot;Piju&quot; 9M2PJU: 0 A.D. on Linux: A Stunning, Free RTS Experience That Rivals the Best</title>
  908. <guid isPermaLink="false">https://hamradio.my/?p=7744</guid>
  909. <link>https://hamradio.my/2025/06/0-a-d-on-linux-a-stunning-free-rts-experience-that-rivals-the-best/</link>
  910. <description>&lt;h1 class=&quot;wp-block-heading&quot;&gt;&lt;/h1&gt;
  911.  
  912.  
  913.  
  914. &lt;p&gt;If you’re a Linux user craving a real-time strategy (RTS) game with the polish of &lt;em&gt;Age of Empires&lt;/em&gt; and the historical depth of a university textbook—yet entirely &lt;em&gt;free&lt;/em&gt; and &lt;em&gt;open source&lt;/em&gt;—then you need to try &lt;strong&gt;0 A.D.&lt;/strong&gt;. This epic project by &lt;strong&gt;Wildfire Games&lt;/strong&gt; is not just an open-source alternative to mainstream RTS games—it’s a serious contender in its own right, crafted with passion, precision, and community spirit.&lt;/p&gt;
  915.  
  916.  
  917.  
  918. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🎮&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3ae.png&quot; style=&quot;height: 1em;&quot; /&gt; What is 0 A.D.?&lt;/h2&gt;
  919.  
  920.  
  921.  
  922. &lt;p&gt;&lt;strong&gt;0 A.D. (Zero Anno Domini)&lt;/strong&gt; is a &lt;strong&gt;free&lt;/strong&gt;, &lt;strong&gt;open-source&lt;/strong&gt;, &lt;strong&gt;cross-platform RTS game&lt;/strong&gt; that takes players deep into ancient history, allowing them to build and battle with civilizations from 500 B.C. to 500 A.D. The game is built using the custom &lt;strong&gt;Pyrogenesis&lt;/strong&gt; engine, a modern 3D engine developed from scratch for this purpose, and available under the GPL license—yes, you can even tinker with the code yourself.&lt;/p&gt;
  923.  
  924.  
  925.  
  926. &lt;p&gt;It’s not just a clone. 0 A.D. sets itself apart with:&lt;/p&gt;
  927.  
  928.  
  929.  
  930. &lt;ul class=&quot;wp-block-list&quot;&gt;
  931. &lt;li&gt;&lt;img alt=&quot;🛡&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f6e1.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Historically accurate civilizations&lt;/strong&gt;&lt;/li&gt;
  932.  
  933.  
  934.  
  935. &lt;li&gt;&lt;img alt=&quot;🗺&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f5fa.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Dynamic and random map generation&lt;/strong&gt;&lt;/li&gt;
  936.  
  937.  
  938.  
  939. &lt;li&gt;&lt;img alt=&quot;⚔&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2694.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Tactical land and naval combat&lt;/strong&gt;&lt;/li&gt;
  940.  
  941.  
  942.  
  943. &lt;li&gt;&lt;img alt=&quot;🏗&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3d7.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;City-building with tech progression&lt;/strong&gt;&lt;/li&gt;
  944.  
  945.  
  946.  
  947. &lt;li&gt;&lt;img alt=&quot;🧠&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f9e0.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;AI opponents and multiplayer support&lt;/strong&gt;&lt;/li&gt;
  948.  
  949.  
  950.  
  951. &lt;li&gt;&lt;img alt=&quot;💬&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4ac.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Modding tools and community-created content&lt;/strong&gt;&lt;/li&gt;
  952. &lt;/ul&gt;
  953.  
  954.  
  955.  
  956. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🐧&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f427.png&quot; style=&quot;height: 1em;&quot; /&gt; Why It’s Perfect for Linux Users&lt;/h2&gt;
  957.  
  958.  
  959.  
  960. &lt;p&gt;Linux gamers often get the short end of the stick when it comes to big-name games—but 0 A.D. feels like it was made &lt;em&gt;for us&lt;/em&gt;. Here’s why Linux users should care:&lt;/p&gt;
  961.  
  962.  
  963.  
  964. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;✔&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2714.png&quot; style=&quot;height: 1em;&quot; /&gt; Native Linux Support&lt;/h3&gt;
  965.  
  966.  
  967.  
  968. &lt;p&gt;0 A.D. runs natively on &lt;strong&gt;Linux&lt;/strong&gt; without the need for Wine, Proton, or compatibility layers. You can install it directly from your distro’s package manager or build it from source if you like full control.&lt;/p&gt;
  969.  
  970.  
  971.  
  972. &lt;p&gt;For example:&lt;/p&gt;
  973.  
  974.  
  975.  
  976. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;# On Debian/Ubuntu
  977. sudo apt install 0ad
  978.  
  979. # On Arch Linux
  980. sudo pacman -S 0ad
  981.  
  982. # On Fedora
  983. sudo dnf install 0ad
  984. &lt;/code&gt;&lt;/pre&gt;
  985.  
  986.  
  987.  
  988. &lt;p&gt;No weird dependencies. No workarounds. Just pure, native performance.&lt;/p&gt;
  989.  
  990.  
  991.  
  992. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🎨&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3a8.png&quot; style=&quot;height: 1em;&quot; /&gt; Vulkan Renderer and FSR Support&lt;/h3&gt;
  993.  
  994.  
  995.  
  996. &lt;p&gt;With &lt;strong&gt;Alpha 27 “Agni”&lt;/strong&gt;, 0 A.D. now supports &lt;strong&gt;Vulkan&lt;/strong&gt;, giving Linux users much better graphics performance, lower CPU overhead, and compatibility with modern GPU features. Plus, it includes &lt;strong&gt;AMD FidelityFX Super Resolution (FSR)&lt;/strong&gt;—which boosts frame rates and visual quality even on low-end hardware.&lt;/p&gt;
  997.  
  998.  
  999.  
  1000. &lt;p&gt;This makes 0 A.D. one of the few FOSS games optimized for modern Linux graphics stacks like &lt;strong&gt;Mesa&lt;/strong&gt;, &lt;strong&gt;Wayland&lt;/strong&gt;, and &lt;strong&gt;PipeWire&lt;/strong&gt;.&lt;/p&gt;
  1001.  
  1002.  
  1003.  
  1004. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🔄&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f504.png&quot; style=&quot;height: 1em;&quot; /&gt; Rolling Updates and Dev Engagement&lt;/h3&gt;
  1005.  
  1006.  
  1007.  
  1008. &lt;p&gt;The development team and community are highly active, with new features, bug fixes, and optimizations arriving steadily. You don’t need to wait years for meaningful updates—0 A.D. grows with each alpha release, and Linux users are treated as first-class citizens.&lt;/p&gt;
  1009.  
  1010.  
  1011.  
  1012. &lt;p&gt;Want to contribute a patch or translate the UI into Malay? You can. Everything is transparent and accessible.&lt;/p&gt;
  1013.  
  1014.  
  1015.  
  1016. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1017.  
  1018.  
  1019.  
  1020. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🏛&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3db.png&quot; style=&quot;height: 1em;&quot; /&gt; What Makes the Gameplay So Good?&lt;/h2&gt;
  1021.  
  1022.  
  1023.  
  1024. &lt;p&gt;Let’s dive deeper into why the gameplay itself shines.&lt;/p&gt;
  1025.  
  1026.  
  1027.  
  1028. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🏗&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3d7.png&quot; style=&quot;height: 1em;&quot; /&gt; Realistic Economy and Base Building&lt;/h3&gt;
  1029.  
  1030.  
  1031.  
  1032. &lt;p&gt;Unlike many fast-paced arcade RTS games, 0 A.D. rewards planning and resource management. You’ll manage four resources—&lt;strong&gt;food, wood, stone, and metal&lt;/strong&gt;—to construct buildings, raise armies, and advance through &lt;strong&gt;phases&lt;/strong&gt; that represent a civilization’s growth. Advancing from &lt;strong&gt;village phase to town phase to city phase&lt;/strong&gt; unlocks more units and structures.&lt;/p&gt;
  1033.  
  1034.  
  1035.  
  1036. &lt;p&gt;Each civilization has unique architectural styles, tech trees, and military units. For example:&lt;/p&gt;
  1037.  
  1038.  
  1039.  
  1040. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1041. &lt;li&gt;&lt;strong&gt;Romans&lt;/strong&gt; have disciplined legionaries and siege weapons.&lt;/li&gt;
  1042.  
  1043.  
  1044.  
  1045. &lt;li&gt;&lt;strong&gt;Persians&lt;/strong&gt; boast fast cavalry and majestic palaces.&lt;/li&gt;
  1046.  
  1047.  
  1048.  
  1049. &lt;li&gt;&lt;strong&gt;Athenians&lt;/strong&gt; excel in naval warfare.&lt;/li&gt;
  1050. &lt;/ul&gt;
  1051.  
  1052.  
  1053.  
  1054. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;⚔&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2694.png&quot; style=&quot;height: 1em;&quot; /&gt; Intense Tactical Combat&lt;/h3&gt;
  1055.  
  1056.  
  1057.  
  1058. &lt;p&gt;Units in 0 A.D. aren’t just damage sponges. There’s formation control, terrain advantage, flanking tactics, and unit counters. The AI behaves strategically, and in multiplayer, experienced players can pull off devastating maneuvers.&lt;/p&gt;
  1059.  
  1060.  
  1061.  
  1062. &lt;p&gt;Naval combat has received significant improvements recently, with better ship handling and water pathfinding—something many commercial RTS games still struggle with.&lt;/p&gt;
  1063.  
  1064.  
  1065.  
  1066. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🗺&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f5fa.png&quot; style=&quot;height: 1em;&quot; /&gt; Endless Map Variety and Mod Support&lt;/h3&gt;
  1067.  
  1068.  
  1069.  
  1070. &lt;p&gt;0 A.D. includes:&lt;/p&gt;
  1071.  
  1072.  
  1073.  
  1074. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1075. &lt;li&gt;Skirmish maps&lt;/li&gt;
  1076.  
  1077.  
  1078.  
  1079. &lt;li&gt;Random maps (with different biomes and elevation)&lt;/li&gt;
  1080.  
  1081.  
  1082.  
  1083. &lt;li&gt;Scenario maps (with scripted events)&lt;/li&gt;
  1084. &lt;/ul&gt;
  1085.  
  1086.  
  1087.  
  1088. &lt;p&gt;And thanks to the integrated &lt;strong&gt;mod downloader&lt;/strong&gt;, you can browse, install, and play with community mods in just a few clicks. Want to add new units, tweak balance, or add fantasy elements? You can.&lt;/p&gt;
  1089.  
  1090.  
  1091.  
  1092. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1093.  
  1094.  
  1095.  
  1096. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🕹&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f579.png&quot; style=&quot;height: 1em;&quot; /&gt; Multiplayer and Replays&lt;/h2&gt;
  1097.  
  1098.  
  1099.  
  1100. &lt;p&gt;Play with friends over LAN, the Internet, or against the built-in AI. The game includes:&lt;/p&gt;
  1101.  
  1102.  
  1103.  
  1104. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1105. &lt;li&gt;&lt;img alt=&quot;🧭&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f9ed.png&quot; style=&quot;height: 1em;&quot; /&gt; Multiplayer save and resume support&lt;/li&gt;
  1106.  
  1107.  
  1108.  
  1109. &lt;li&gt;&lt;img alt=&quot;👁&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f441.png&quot; style=&quot;height: 1em;&quot; /&gt; Observer tools (with flares, commands, and overlays)&lt;/li&gt;
  1110.  
  1111.  
  1112.  
  1113. &lt;li&gt;&lt;img alt=&quot;⏪&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/23ea.png&quot; style=&quot;height: 1em;&quot; /&gt; Replay functionality to study your tactics or cast tournaments&lt;/li&gt;
  1114. &lt;/ul&gt;
  1115.  
  1116.  
  1117.  
  1118. &lt;p&gt;There’s even an in-game lobby where players coordinate matches across all platforms.&lt;/p&gt;
  1119.  
  1120.  
  1121.  
  1122. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1123.  
  1124.  
  1125.  
  1126. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;👥&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f465.png&quot; style=&quot;height: 1em;&quot; /&gt; Community and Contribution&lt;/h2&gt;
  1127.  
  1128.  
  1129.  
  1130. &lt;p&gt;The 0 A.D. project thrives because of its community:&lt;/p&gt;
  1131.  
  1132.  
  1133.  
  1134. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1135. &lt;li&gt;Developers contribute code via GitHub.&lt;/li&gt;
  1136.  
  1137.  
  1138.  
  1139. &lt;li&gt;Artists create stunning 3D models and animations.&lt;/li&gt;
  1140.  
  1141.  
  1142.  
  1143. &lt;li&gt;Historians help ensure cultural accuracy.&lt;/li&gt;
  1144.  
  1145.  
  1146.  
  1147. &lt;li&gt;Translators localize the game into dozens of languages.&lt;/li&gt;
  1148.  
  1149.  
  1150.  
  1151. &lt;li&gt;Players write guides, tutorials, and strategy posts.&lt;/li&gt;
  1152. &lt;/ul&gt;
  1153.  
  1154.  
  1155.  
  1156. &lt;p&gt;If you’re a Linux user and want to contribute to an ambitious FOSS project, this is the perfect gateway into game development, design, or open collaboration.&lt;/p&gt;
  1157.  
  1158.  
  1159.  
  1160. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1161.  
  1162.  
  1163.  
  1164. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🧑‍💻&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f9d1-200d-1f4bb.png&quot; style=&quot;height: 1em;&quot; /&gt; How to Install on Linux&lt;/h2&gt;
  1165.  
  1166.  
  1167.  
  1168. &lt;p&gt;Here’s a quick reference:&lt;/p&gt;
  1169.  
  1170.  
  1171.  
  1172. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Option 1: Package Manager (Recommended)&lt;/h3&gt;
  1173.  
  1174.  
  1175.  
  1176. &lt;ul class=&quot;wp-block-list&quot;&gt;
  1177. &lt;li&gt;&lt;strong&gt;Debian/Ubuntu&lt;/strong&gt;: &lt;code&gt;sudo apt install 0ad&lt;/code&gt;&lt;/li&gt;
  1178.  
  1179.  
  1180.  
  1181. &lt;li&gt;&lt;strong&gt;Arch Linux&lt;/strong&gt;: &lt;code&gt;sudo pacman -S 0ad&lt;/code&gt;&lt;/li&gt;
  1182.  
  1183.  
  1184.  
  1185. &lt;li&gt;&lt;strong&gt;Fedora&lt;/strong&gt;: &lt;code&gt;sudo dnf install 0ad&lt;/code&gt;&lt;/li&gt;
  1186.  
  1187.  
  1188.  
  1189. &lt;li&gt;&lt;strong&gt;openSUSE&lt;/strong&gt;: &lt;code&gt;sudo zypper install 0ad&lt;/code&gt;&lt;/li&gt;
  1190. &lt;/ul&gt;
  1191.  
  1192.  
  1193.  
  1194. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Option 2: Compile from Source&lt;/h3&gt;
  1195.  
  1196.  
  1197.  
  1198. &lt;p&gt;Follow the official instructions at &lt;a href=&quot;https://trac.wildfiregames.com/wiki/BuildInstructions&quot;&gt;https://trac.wildfiregames.com/wiki/BuildInstructions&lt;/a&gt;&lt;/p&gt;
  1199.  
  1200.  
  1201.  
  1202. &lt;hr class=&quot;wp-block-separator has-alpha-channel-opacity&quot; /&gt;
  1203.  
  1204.  
  1205.  
  1206. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;img alt=&quot;🎯&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f3af.png&quot; style=&quot;height: 1em;&quot; /&gt; Final Thoughts&lt;/h2&gt;
  1207.  
  1208.  
  1209.  
  1210. &lt;p&gt;0 A.D. is more than just a game—it’s a testament to what free and open-source software can achieve. For Linux gamers, it’s a rare gem: a game that respects your platform, performs well, and lets you own your experience entirely.&lt;/p&gt;
  1211.  
  1212.  
  1213.  
  1214. &lt;p&gt;So whether you’re a seasoned general or a curious strategist, &lt;strong&gt;download 0 A.D. today and relive history—on your terms&lt;/strong&gt;.&lt;/p&gt;
  1215.  
  1216.  
  1217.  
  1218. &lt;p&gt;&lt;img alt=&quot;👉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f449.png&quot; style=&quot;height: 1em;&quot; /&gt; Visit &lt;a href=&quot;https://play0ad.com/&quot;&gt;https://play0ad.com&lt;/a&gt; to download and start playing.&lt;/p&gt;
  1219. &lt;p&gt;The post &lt;a href=&quot;https://hamradio.my/2025/06/0-a-d-on-linux-a-stunning-free-rts-experience-that-rivals-the-best/&quot;&gt;0 A.D. on Linux: A Stunning, Free RTS Experience That Rivals the Best&lt;/a&gt; appeared first on &lt;a href=&quot;https://hamradio.my&quot;&gt;Hamradio.my - Amateur Radio, Tech Insights and Product Reviews&lt;/a&gt; by &lt;a href=&quot;https://hamradio.my/author/9m2pju/&quot;&gt;9M2PJU&lt;/a&gt;.&lt;/p&gt;</description>
  1220. <pubDate>Sun, 01 Jun 2025 16:14:40 +0000</pubDate>
  1221. </item>
  1222. <item>
  1223. <title>Simon Quigley: Trains and Cats: The Trolley Problem</title>
  1224. <guid isPermaLink="false">https://medium.com/p/102a4430023c</guid>
  1225. <link>https://medium.com/@tsimonq2/trains-and-cats-the-trolley-problem-102a4430023c?source=rss-abe8950a00ea------2</link>
  1226. <description>&lt;p&gt;“Do not forget about the Trolley Problem,” a middle school teacher once told us. “You’ll look back on this moment and be glad you studied this specific dilemma early.”&lt;/p&gt;&lt;p&gt;In hindsight, &lt;strong&gt;she was right&lt;/strong&gt;. In fact, I had no idea I would need to use that knowledge until I was &lt;em&gt;directly&lt;/em&gt; in the middle of the situation.&lt;/p&gt;&lt;p&gt;Imagine this: you’re standing by a railroad track. There’s a lever in front of that railroad track, next to a button. The button sends an affirmative signal to a waiting train, so it can proceed. The lever allows the operators to switch between the primary track, and a secondary track, just in case.&lt;/p&gt;&lt;p&gt;Before pressing the button, standard operating procedure is to manually inspect the tracks, to ensure no debris exists. The operators even run a small cart through, to ensure the tracks themselves are not in bad shape.&lt;/p&gt;&lt;p&gt;All of the operators are out for the weekend. That’s okay, they just helped prepare the train for departure. They deserve the time off.&lt;/p&gt;&lt;p&gt;Except, someone bumped the big red button on the way out, without realizing it.&lt;/p&gt;&lt;p&gt;The train starts to build momentum. There’s no stopping it now. Everyone was so busy preparing the train, that checking the tracks to see if they were ready… not on their mind.&lt;/p&gt;&lt;p&gt;How could they forget? Well, the cart was out for repair. It passed the last three dozen times, why would it fail this time? Why would there suddenly be debris on the tracks?&lt;/p&gt;&lt;p&gt;Imagine you’re an engineer who just happened to walk by the button and lever. You see the train is starting to move. There’s debris even before the junction, and you can hear it. It’s loud.&lt;/p&gt;&lt;p&gt;But again, the operators are off-site. It’s not technically “your job” to even touch the lever. You’re just an engineer, you’re not an operator. Why would you flip that switch?&lt;/p&gt;&lt;p&gt;Well, because there’s a large rock straight ahead. If nobody flips the lever, it will hurdle right towards it and crash.&lt;/p&gt;&lt;p&gt;So, last second, you walk up to the lever, and flip it. That being said, in order to clear the last bit of debris off that secondary track to avoid the rock, you have to sacrifice your favorite wooden stick.&lt;/p&gt;&lt;p&gt;You spent decades whittling that stick until it was perfect. Except now, it’s the only thing you have to stop the train.&lt;/p&gt;&lt;p&gt;Would you sacrifice your favorite stick to save the train from the rock?&lt;/p&gt;&lt;p&gt;Let’s entertain both scenarios.&lt;/p&gt;&lt;p&gt;What if you just “let it be,” and pretended you didn’t see it? That would probably make some feel guilty, as if they were the person that pressed the button.&lt;/p&gt;&lt;p&gt;The other option would be to sacrifice your stick. It’s a material object, but you put years of effort into it. That would make you feel a different set of emotions.&lt;/p&gt;&lt;p&gt;That’s why the Trolley Problem is so difficult. You’re either sacrificing one person, or multiple. You have to choose one, you can’t choose both.&lt;/p&gt;&lt;p&gt;For the sake of argument, let’s say there’s a perfect 50% chance that you walk by the train. There are security cameras, but they can’t be viewed off-site due to a technical outage.&lt;/p&gt;&lt;p&gt;A few people in management heard the sound of the train from a great distance away, which made them nervous. They might be asking several questions, such as:&lt;br /&gt; * Is the train intact?&lt;br /&gt; * Which track did the train go down?&lt;br /&gt; * Was there actually any debris in the way?&lt;br /&gt; * Who caused the train to start moving prematurely?&lt;/p&gt;&lt;p&gt;It was an honest mistake, someone just pushed the button. All of these questions though, they almost remind me of a different dilemma of sorts:&lt;/p&gt;&lt;a href=&quot;https://medium.com/media/4ec6b678f4c67437bd9f844bd50b9acb/href&quot;&gt;https://medium.com/media/4ec6b678f4c67437bd9f844bd50b9acb/href&lt;/a&gt;&lt;p&gt;What would &lt;em&gt;you&lt;/em&gt; do?&lt;/p&gt;&lt;p&gt;&lt;em&gt;Talk to you all on Monday.&lt;/em&gt;&lt;/p&gt;&lt;img alt=&quot;&quot; height=&quot;1&quot; src=&quot;https://medium.com/_/stat?event=post.clientViewed&amp;amp;referrerSource=full_rss&amp;amp;postId=102a4430023c&quot; width=&quot;1&quot; /&gt;</description>
  1227. <pubDate>Sun, 01 Jun 2025 03:30:02 +0000</pubDate>
  1228. </item>
  1229. <item>
  1230. <title>The Fridge: Extended Security Maintenance for Ubuntu 20.04 (Focal) began on May 29, 2025</title>
  1231. <guid isPermaLink="false">https://fridge.ubuntu.com/?p=10520</guid>
  1232. <link>https://fridge.ubuntu.com/2025/05/30/extended-security-maintenance-for-ubuntu-20-04-focal-began-on-may-29-2025/</link>
  1233. <description>&lt;p&gt;This is a follow-up to the Extended Support warning sent one month ago to confirm that as of May 29, 2025, Ubuntu 20.04 LTS standard support has ended.  No more package updates are planned to be accepted to the primary archive of Ubuntu 20.04 LTS.&lt;/p&gt;
  1234. &lt;p&gt;Remember that if you can’t upgrade to 22.04 LTS or later immediately, Canonical provides Extended Security Maintenance for Ubuntu 20.04 LTS to users with Ubuntu Pro. You can find more info about Ubuntu Pro here:&lt;/p&gt;
  1235. &lt;p style=&quot;margin-left: 15px;&quot;&gt;
  1236. &lt;a href=&quot;https://ubuntu.com/blog/ubuntu-20-04-lts-end-of-life-standard-support-is-coming-to-an-end-heres-how-to-prepare&quot;&gt;https://ubuntu.com/blog/ubuntu-20-04-lts-end-of-life-standard-support-is-coming-to-an-end-heres-how-to-prepare&lt;/a&gt;&lt;br /&gt;
  1237. &lt;a href=&quot;https://ubuntu.com/esm&quot;&gt;https://ubuntu.com/esm&lt;/a&gt;&lt;/p&gt;
  1238. &lt;p&gt;The original Extended Support warning follows, with upgrade instructions:&lt;/p&gt;
  1239. &lt;p&gt;Ubuntu released its 20.04 (Focal Fossa) release 5 years ago, on March 23, 2020. As with the earlier LTS releases, Ubuntu committed to ongoing security and critical fixes for a period of 5 years. The standard support period is now nearing its end and Ubuntu 20.04 LTS will transition to Extended Security Maintenance (ESM) on May 29, 2025.&lt;/p&gt;
  1240. &lt;p&gt;Users are encouraged to evaluate and upgrade to our latest 24.04 LTS release via 22.04 LTS. The supported upgrade path from Ubuntu 20.04 LTS is via Ubuntu 22.04 LTS. Instructions and caveats for the upgrades may be found at:&lt;/p&gt;
  1241. &lt;p style=&quot;margin-left: 15px;&quot;&gt;
  1242. &lt;a href=&quot;https://help.ubuntu.com/community/JammyUpgrades&quot;&gt;https://help.ubuntu.com/community/JammyUpgrades&lt;/a&gt; for Ubuntu 22.04 LTS&lt;br /&gt;
  1243. &lt;a href=&quot;https://help.ubuntu.com/community/NobleUpgrades&quot;&gt;https://help.ubuntu.com/community/NobleUpgrades&lt;/a&gt; for Ubuntu 24.04 LTS&lt;/p&gt;
  1244. &lt;p&gt;Ubuntu 22.04 LTS and 24.04 LTS continue to be actively supported with security updates and bug fixes. All announcements of official security updates for Ubuntu releases are sent to the ubuntu-security-announce mailing list, information about which may be found here:&lt;/p&gt;
  1245. &lt;p style=&quot;margin-left: 15px;&quot;&gt;
  1246. &lt;a href=&quot;https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce&quot;&gt;https://lists.ubuntu.com/mailman/listinfo/ubuntu-security-announce&lt;/a&gt;&lt;/p&gt;
  1247. &lt;p&gt;Canonical provides Extended Security Maintenance for Ubuntu 20.04 LTS to customers through Ubuntu Pro. Further information can be found here:&lt;/p&gt;
  1248. &lt;p style=&quot;margin-left: 15px;&quot;&gt;
  1249. &lt;a href=&quot;https://ubuntu.com/blog/focal-fossa-end-of-standard-support&quot;&gt;https://ubuntu.com/blog/focal-fossa-end-of-standard-support&lt;/a&gt;&lt;br /&gt;
  1250. &lt;a href=&quot;https://www.ubuntu.com/esm&quot;&gt;https://www.ubuntu.com/esm&lt;/a&gt;&lt;/p&gt;
  1251. &lt;p&gt;Since its launch in October 2004, Ubuntu has become one of the most highly regarded Linux distributions with millions of users in homes, schools, businesses and governments around the world. Ubuntu is Open Source software, costs nothing to download, and users are free to customize or alter their software in order to meet their needs.&lt;/p&gt;
  1252.  
  1253.  
  1254. &lt;p&gt;&lt;em&gt;Originally posted to the &lt;a href=&quot;https://lists.ubuntu.com/archives/ubuntu-announce/2025-May/000312.html&quot;&gt;ubuntu-announce mailing list&lt;/a&gt; on Thu May 29 16:37:01 UTC 2025 by Ural Tunaboyu, on behalf of the Ubuntu Release Team.&lt;/em&gt;&lt;/p&gt;</description>
  1255. <pubDate>Fri, 30 May 2025 06:54:56 +0000</pubDate>
  1256. </item>
  1257. <item>
  1258. <title>Ubuntu Studio: Ubuntu Studio 22.04 LTS has reached End-Of-Life (EOL)</title>
  1259. <guid isPermaLink="false">https://ubuntustudio.org/?p=2999</guid>
  1260. <link>https://ubuntustudio.org/2025/05/ubuntu-studio-22-04-lts-has-reached-end-of-life-eol/</link>
  1261. <description>&lt;p&gt;&lt;strong&gt;Ubuntu Studio 22.04 LTS has reached the end of its three years of supported life&lt;/strong&gt; provided by the Ubuntu Studio team. All users are urged to upgrade to 24.04 LTS at this time.&lt;/p&gt;
  1262.  
  1263.  
  1264.  
  1265. &lt;p&gt;This means that the KDE Plasma, audio, video, graphics, photography, and publishing components of your system will no longer receive updates, plus &lt;strong&gt;we at Ubuntu Studio won’t support it after 29-May-2025,&lt;/strong&gt; though your base packages from Ubuntu will continue to receive security updates from Ubuntu until 2027 since Ubuntu Desktop, Ubuntu Server, Ubuntu Cloud and Ubuntu Core continue to receive updates.&lt;/p&gt;
  1266.  
  1267.  
  1268.  
  1269. &lt;p&gt;See the &lt;a data-id=&quot;2745&quot; data-type=&quot;page&quot; href=&quot;https://ubuntustudio.org/ubuntu-studio-24-04-lts-release-notes/&quot;&gt;Ubuntu Studio 24.04 LTS Release Notes&lt;/a&gt; for upgrade instructions.&lt;/p&gt;
  1270.  
  1271.  
  1272.  
  1273. &lt;p&gt;No single release of any operating system can be supported indefinitely, and Ubuntu Studio has no exception to this rule.&lt;/p&gt;
  1274.  
  1275.  
  1276.  
  1277. &lt;p&gt;Long-Term Support releases are identified by an even numbered year-of-release and a month-of-release of April (04). Hence, the most recent Long-Term Support release is 24.04 (YY.MM = 2024.April), and the next Long-Term Support release will be 26.04 (2026.April). LTS releases for official Ubuntu flavors (not Desktop or Server which are supported for five years) are three years, meaning LTS users are expected to upgrade after every LTS release with a one-year buffer.&lt;/p&gt;</description>
  1278. <pubDate>Thu, 29 May 2025 16:50:01 +0000</pubDate>
  1279. </item>
  1280. <item>
  1281. <title>Podcast Ubuntu Portugal: E349 Choques Com Tinta</title>
  1282. <guid isPermaLink="false">https://hub.podcastubuntuportugal.org/s/HzDyna824fnMdWe/download/e349.mp3</guid>
  1283. <link>https://podcastubuntuportugal.org/e349/</link>
  1284. <description>&lt;p&gt;O episódio de hoje fará correr muita tinta…electrónica. Como escapar aos monopólios de «e-readers» de marcas abelhudas? Podemos fazer um em casa com fita-cola, cartão, cuspo e Alpine Linux? Estas e outras questões mais profundas sobre um mundo que morre e outro que está em dores de parto colam-se a todas as outras coisas a acontecerem na agenda: Firefox 139, terminais retro engraçados, Teletexto num Terminal(!), Home Assistant Community Day, Wikicon Portugal, Ubucon Europe, Ubuntu Summit, Festa do Software Livre, ECTL Porto…é um nunca acabar. E decidimos fazer uma autópsia ao Pocket, mais uma vítima da Mozilla. Querem pacotes? Perguntem ao Dan!&lt;/p&gt;
  1285. &lt;p&gt;Já sabem: oiçam, subscrevam e partilhem!&lt;/p&gt;
  1286. &lt;ul&gt;
  1287. &lt;li&gt;Cool Retro Term: &lt;a href=&quot;https://github.com/Swordfish90/cool-retro-term&quot;&gt;https://github.com/Swordfish90/cool-retro-term&lt;/a&gt;&lt;/li&gt;
  1288. &lt;li&gt;Navegador para terminal «Links»: &lt;a href=&quot;http://links.twibright.com/user_en.html#ch-introduction_into_links_web_browser&quot;&gt;http://links.twibright.com/user_en.html#ch-introduction_into_links_web_browser&lt;/a&gt;&lt;/li&gt;
  1289. &lt;li&gt;Alpine Linux: &lt;a href=&quot;https://www.alpinelinux.org/&quot;&gt;https://www.alpinelinux.org/&lt;/a&gt;&lt;/li&gt;
  1290. &lt;li&gt;Para onde foram os «e-readers» baratos? &lt;a href=&quot;https://shkspr.mobi/blog/2025/05/whatever-happened-to-cheap-ereaders/&quot;&gt;https://shkspr.mobi/blog/2025/05/whatever-happened-to-cheap-ereaders/&lt;/a&gt;&lt;/li&gt;
  1291. &lt;li&gt;Tabela de privacidade de «e-readers» da EFF (2012): &lt;a href=&quot;https://www.eff.org/pages/reader-privacy-chart-2012)&quot;&gt;https://www.eff.org/pages/reader-privacy-chart-2012)&lt;/a&gt;.&lt;/li&gt;
  1292. &lt;li&gt;Um Leitor de Livros Electrónicos Faça-Você-Mesmo: &lt;a href=&quot;https://hackaday.com/2019/10/31/building-an-open-hardware-ebook-reader/&quot;&gt;https://hackaday.com/2019/10/31/building-an-open-hardware-ebook-reader/&lt;/a&gt;&lt;/li&gt;
  1293. &lt;li&gt;Um casamento feliz entre um Raspberry Pi Zero e Tinta Electrónica: &lt;a href=&quot;https://www.hackster.io/lukehaas/e-ink-display-for-daily-news-weather-and-more-3dd7b1&quot;&gt;https://www.hackster.io/lukehaas/e-ink-display-for-daily-news-weather-and-more-3dd7b1&lt;/a&gt;&lt;/li&gt;
  1294. &lt;li&gt;Como requisitar e-livros na Biblioled sem tralha da Adobe: &lt;a href=&quot;https://ajuda.biblioled.gov.pt/pt/doc/ST2445/1/abrir-um-emprestimo-com-o-seu-pc&quot;&gt;https://ajuda.biblioled.gov.pt/pt/doc/ST2445/1/abrir-um-emprestimo-com-o-seu-pc&lt;/a&gt;&lt;/li&gt;
  1295. &lt;li&gt;Biblioled: &lt;a href=&quot;https://www.biblioled.gov.pt/&quot;&gt;https://www.biblioled.gov.pt/&lt;/a&gt;&lt;/li&gt;
  1296. &lt;li&gt;Thorium Reader: &lt;a href=&quot;https://thorium.edrlab.org/en/&quot;&gt;https://thorium.edrlab.org/en/&lt;/a&gt;&lt;/li&gt;
  1297. &lt;li&gt;KoReader: &lt;a href=&quot;https://koreader.rocks/&quot;&gt;https://koreader.rocks/&lt;/a&gt;&lt;/li&gt;
  1298. &lt;li&gt;Calibre: &lt;a href=&quot;https://calibre-ebook.com/&quot;&gt;https://calibre-ebook.com/&lt;/a&gt;&lt;/li&gt;
  1299. &lt;li&gt;Reflexões sobre um mundo novo que quer emergir e pulsões regressivas: &lt;a href=&quot;https://ageoftransformation.org/the-us-is-collapsing-like-the-ussr-so-what-comes-next/&quot;&gt;https://ageoftransformation.org/the-us-is-collapsing-like-the-ussr-so-what-comes-next/&lt;/a&gt;&lt;/li&gt;
  1300. &lt;li&gt;Um Minitel num comboio?… &lt;a href=&quot;https://corneill.es/@Ortie/114557692921180947&quot;&gt;https://corneill.es/@Ortie/114557692921180947&lt;/a&gt;&lt;/li&gt;
  1301. &lt;li&gt;Wallabag: &lt;a href=&quot;https://wallabag.org/&quot;&gt;https://wallabag.org/&lt;/a&gt;
  1302. &lt;ul&gt;
  1303. &lt;li&gt;&lt;a href=&quot;https://github.com/wallabag/wallabag&quot;&gt;https://github.com/wallabag/wallabag&lt;/a&gt;&lt;/li&gt;
  1304. &lt;li&gt;&lt;a href=&quot;https://www.wallabag.it/en&quot;&gt;https://www.wallabag.it/en&lt;/a&gt;&lt;/li&gt;
  1305. &lt;/ul&gt;
  1306. &lt;/li&gt;
  1307. &lt;li&gt;Adeus, Pocket: &lt;a href=&quot;https://support.mozilla.org/en-US/kb/future-of-pocket&quot;&gt;https://support.mozilla.org/en-US/kb/future-of-pocket&lt;/a&gt;
  1308. &lt;ul&gt;
  1309. &lt;li&gt;&lt;a href=&quot;https://www.phoronix.com/news/Mozilla-Pocket-Ending&quot;&gt;https://www.phoronix.com/news/Mozilla-Pocket-Ending&lt;/a&gt;&lt;/li&gt;
  1310. &lt;li&gt;&lt;a href=&quot;https://www.omgubuntu.co.uk/2025/05/mozilla-kills-pocket-so-it-can-focus-on-firefox&quot;&gt;https://www.omgubuntu.co.uk/2025/05/mozilla-kills-pocket-so-it-can-focus-on-firefox&lt;/a&gt;&lt;/li&gt;
  1311. &lt;/ul&gt;
  1312. &lt;/li&gt;
  1313. &lt;li&gt;Firefox 139: &lt;a href=&quot;https://blog.mozilla.org/en/mozilla/building-whats-next/&quot;&gt;https://blog.mozilla.org/en/mozilla/building-whats-next/&lt;/a&gt;&lt;/li&gt;
  1314. &lt;li&gt;Jovem! Desenha uma mascote e ganha prémios! Inscreve-te! Participa! &lt;a href=&quot;https://digitalfreedoms.org/en/sfd/blog/sfd-mascot-huion-challenge-2025&quot;&gt;https://digitalfreedoms.org/en/sfd/blog/sfd-mascot-huion-challenge-2025&lt;/a&gt;&lt;/li&gt;
  1315. &lt;li&gt;Teletexto num Terminal para Pessoas Saudosistas: &lt;a href=&quot;https://github.com/marado/teletexto/blob/main/teletexto.sh&quot;&gt;https://github.com/marado/teletexto/blob/main/teletexto.sh&lt;/a&gt;&lt;/li&gt;
  1316. &lt;li&gt;Qual pacote? Pergunta ao Dan: &lt;a href=&quot;https://snapcraft.io/askdan&quot;&gt;https://snapcraft.io/askdan&lt;/a&gt;&lt;/li&gt;
  1317. &lt;li&gt;LCD Porto – Laboratório de Criação Digital: &lt;a href=&quot;https://lcdporto.org&quot;&gt;https://lcdporto.org&lt;/a&gt;&lt;/li&gt;
  1318. &lt;li&gt;ECTL Porto, 29 e 31 de Maio: &lt;a href=&quot;https://ectl.pt/pt/schedule/2025/&quot;&gt;https://ectl.pt/pt/schedule/2025/&lt;/a&gt;&lt;/li&gt;
  1319. &lt;li&gt;WikiCon Portugal 2025, Seia, 30/05-01/06: &lt;a href=&quot;https://pt.wikimedia.org/wiki/WikiCon_Portugal_2025/Programa&quot;&gt;https://pt.wikimedia.org/wiki/WikiCon_Portugal_2025/Programa&lt;/a&gt;&lt;/li&gt;
  1320. &lt;li&gt;Ubucon Europe 2025, Málaga, 20-21 de Junho (Open South Code): &lt;a href=&quot;https://discourse.ubuntu.com/t/ubucon-europe-opensouthcode-2025/57060&quot;&gt;https://discourse.ubuntu.com/t/ubucon-europe-opensouthcode-2025/57060&lt;/a&gt;&lt;/li&gt;
  1321. &lt;li&gt;Festa do Software Livre 2025, Porto, 3 a 5 de Outubro: &lt;a href=&quot;https://festa2025.softwarelivre.eu/pt/&quot;&gt;https://festa2025.softwarelivre.eu/pt/&lt;/a&gt;&lt;/li&gt;
  1322. &lt;li&gt;Ubuntu Summit 2025, Londres, 23-24 de Outubro: &lt;a href=&quot;https://ubuntu.com/blog/ubuntu-summit-25-10-is-coming-to-your-circle-of-friends-from-london&quot;&gt;https://ubuntu.com/blog/ubuntu-summit-25-10-is-coming-to-your-circle-of-friends-from-london&lt;/a&gt;&lt;/li&gt;
  1323. &lt;li&gt;LoCo PT: &lt;a href=&quot;https://loco.ubuntu.com/teams/ubuntu-pt/&quot;&gt;https://loco.ubuntu.com/teams/ubuntu-pt/&lt;/a&gt;&lt;/li&gt;
  1324. &lt;li&gt;Mastodon: &lt;a href=&quot;https://masto.pt/@pup&quot;&gt;https://masto.pt/@pup&lt;/a&gt;&lt;/li&gt;
  1325. &lt;li&gt;Youtube: &lt;a href=&quot;https://youtube.com/PodcastUbuntuPortugal&quot;&gt;https://youtube.com/PodcastUbuntuPortugal&lt;/a&gt;&lt;/li&gt;
  1326. &lt;/ul&gt;
  1327. &lt;h3 id=&quot;atribuição-e-licenças&quot;&gt;Atribuição e licenças&lt;/h3&gt;
  1328. &lt;p&gt;Este episódio foi produzido por Diogo Constantino, Miguel e Tiago Carrondo e editado pelo &lt;a href=&quot;https://senhorpodcast.pt/&quot;&gt;Senhor Podcast&lt;/a&gt;.
  1329. O website é produzido por Tiago Carrondo e o &lt;a href=&quot;https://gitlab.com/podcastubuntuportugal/website&quot;&gt;código aberto&lt;/a&gt; está licenciado nos termos da &lt;a href=&quot;https://gitlab.com/podcastubuntuportugal/website/main/LICENSE&quot;&gt;Licença MIT&lt;/a&gt;. (&lt;a href=&quot;https://creativecommons.org/licenses/by/4.0/)&quot;&gt;https://creativecommons.org/licenses/by/4.0/)&lt;/a&gt;. A música do genérico é: “Won’t see it comin’ (Feat Aequality &amp;amp; N’sorte d’autruche)”, por Alpha Hydrae e está licenciada nos termos da &lt;a href=&quot;https://creativecommons.org/publicdomain/zero/1.0/&quot;&gt;CC0 1.0 Universal License&lt;/a&gt;. Os efeitos sonoros deste episódio possuem as seguintes licenças: Helicóptero; TV2 loop.wav by Figowitz – &lt;a href=&quot;https://freesound.org/s/69609/&quot;&gt;https://freesound.org/s/69609/&lt;/a&gt; – License: Attribution NonCommercial 4.0; Toque de telefone: 01592 dialing phone number.wav by Robinhood76 – &lt;a href=&quot;https://freesound.org/s/94933/&quot;&gt;https://freesound.org/s/94933/&lt;/a&gt; – License: Attribution NonCommercial 4.0. A flauta mal tocada dos separadores é inteiramente culpa do Miguel e aquele efeito manhoso de um helicóptero Bell Huey UH-1 com rotor de duas pás também.
  1330. Este episódio e a imagem utilizada estão licenciados nos termos da licença: &lt;a href=&quot;https://creativecommons.org/licenses/by-nc-nd/4.0/&quot;&gt;Attribution-NonCommercial-NoDerivatives 4.0 International (CC BY-NC-ND 4.0)&lt;/a&gt;, &lt;a href=&quot;https://creativecommons.org/licenses/by-nc-nd/4.0/legalcode&quot;&gt;cujo texto integral pode ser lido aqui&lt;/a&gt;. Estamos abertos a licenciar para permitir outros tipos de utilização, &lt;a href=&quot;https://podcastubuntuportugal.org/contactos&quot;&gt;contactem-nos&lt;/a&gt; para validação e autorização.
  1331. A arte de episódio foi criada por encomenda pela Shizamura - artista, ilustradora e autora de BD. Podem ficar a conhecer melhor a &lt;a href=&quot;https://ciberlandia.pt/@shizamura&quot;&gt;Shizamura na Ciberlândia&lt;/a&gt; e no &lt;a href=&quot;https://sarilho.net/&quot;&gt;seu sítio web&lt;/a&gt;.&lt;/p&gt;</description>
  1332. <pubDate>Thu, 29 May 2025 00:00:00 +0000</pubDate>
  1333.        <enclosure url="https://hub.podcastubuntuportugal.org/s/HzDyna824fnMdWe/download/e349.mp3" length="32101563" type="audio/mpeg"/>
  1334. </item>
  1335. <item>
  1336. <title>Julian Andres Klode: A SomewhatMaxSAT Solver</title>
  1337. <guid isPermaLink="true">https://blog.jak-linux.org/2025/05/24/somewhatmax-sat-solver/</guid>
  1338. <link>https://blog.jak-linux.org/2025/05/24/somewhatmax-sat-solver/</link>
  1339. <description>&lt;p&gt;&lt;strong&gt;As you may recall&lt;/strong&gt; from previous posts and elsewhere I have been busy writing a new solver for APT.
  1340. Today I want to share some of the latest changes in how to approach solving.&lt;/p&gt;
  1341. &lt;p&gt;The idea for the solver was that manually installed packages are always protected from removals –
  1342. in terms of SAT solving, they are facts. Automatically installed packages become optional unit
  1343. clauses. Optional clauses are solved after manual ones, they don’t partake in normal unit propagation.&lt;/p&gt;
  1344. &lt;p&gt;This worked fine, say you had&lt;/p&gt;
  1345. &lt;pre tabindex=&quot;0&quot;&gt;&lt;code&gt;A                                   # install request for A
  1346. B                                   # manually installed, keep it
  1347. A depends on: conflicts-B | C
  1348. &lt;/code&gt;&lt;/pre&gt;&lt;p&gt;Installing &lt;code&gt;A&lt;/code&gt; on a system with &lt;code&gt;B&lt;/code&gt; installed installed &lt;code&gt;C&lt;/code&gt;, as it was not allowed to
  1349. install the &lt;code&gt;conflicts-B&lt;/code&gt; package since &lt;code&gt;B&lt;/code&gt; is installed.&lt;/p&gt;
  1350. &lt;p&gt;&lt;strong&gt;However,&lt;/strong&gt; I also introduced a mode to allow removing manually installed packages, and that’s
  1351. where it broke down, now instead of &lt;code&gt;B&lt;/code&gt; being a fact, our clauses looked like:&lt;/p&gt;
  1352. &lt;pre tabindex=&quot;0&quot;&gt;&lt;code&gt;A                               # install request for A
  1353. A depends on: conflicts-B | C
  1354. Optional: B                     # try to keep B installed
  1355. &lt;/code&gt;&lt;/pre&gt;&lt;p&gt;As a result, we installed &lt;code&gt;conflicts-B&lt;/code&gt; and removed &lt;code&gt;B&lt;/code&gt;; the steps the solver takes are:&lt;/p&gt;
  1356. &lt;ol&gt;
  1357. &lt;li&gt;&lt;code&gt;A&lt;/code&gt; is a fact, mark it&lt;/li&gt;
  1358. &lt;li&gt;&lt;code&gt;A depends on: conflicts-B | C&lt;/code&gt; is the strongest clause, try to install &lt;code&gt;conflicts-B&lt;/code&gt;&lt;/li&gt;
  1359. &lt;li&gt;We unit propagate that &lt;code&gt;conflicts-B&lt;/code&gt; conflicts with &lt;code&gt;B&lt;/code&gt;, so we mark &lt;code&gt;not B&lt;/code&gt;&lt;/li&gt;
  1360. &lt;li&gt;&lt;code&gt;Optional: B&lt;/code&gt; is reached, but not satisfiable, ignore it because it’s optional.&lt;/li&gt;
  1361. &lt;/ol&gt;
  1362. &lt;p&gt;This isn’t correct: Just because we allow removing manually installed packages doesn’t mean that we should remove manually installed packages if we don’t need to.&lt;/p&gt;
  1363. &lt;p&gt;&lt;strong&gt;Fixing&lt;/strong&gt; this turns out to be surprisingly easy. In addition to adding our optional (soft) clauses, let’s first assume all of them!&lt;/p&gt;
  1364. &lt;p&gt;But to explain how this works, we first need to explain some terminology:&lt;/p&gt;
  1365. &lt;ol&gt;
  1366. &lt;li&gt;The solver operates on a stack of decisions&lt;/li&gt;
  1367. &lt;li&gt;“enqueue” means a fact is being added at the current decision level, and enqueued for propagation&lt;/li&gt;
  1368. &lt;li&gt;“assume” bumps the decision level, and then enqueues the assumed variable&lt;/li&gt;
  1369. &lt;li&gt;“propagate” looks at all the facts and sees if any clause becomes unit, and then enqueues it&lt;/li&gt;
  1370. &lt;li&gt;“unit” is when a clause has a single literal left to assign&lt;/li&gt;
  1371. &lt;/ol&gt;
  1372. &lt;p&gt;To illustrate this in pseudo Python code:&lt;/p&gt;
  1373. &lt;ol&gt;
  1374. &lt;li&gt;
  1375. &lt;p&gt;We introduce all our facts, and if they conflict, we are unsat:&lt;/p&gt;
  1376. &lt;div class=&quot;highlight&quot;&gt;&lt;pre tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-python3&quot; data-lang=&quot;python3&quot;&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; fact &lt;span style=&quot;color: #f92672;&quot;&gt;in&lt;/span&gt; facts:
  1377. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    enqueue(fact)
  1378. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;if&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;not&lt;/span&gt; propagate():
  1379. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;return&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;False&lt;/span&gt;
  1380. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;
  1381. &lt;li&gt;
  1382. &lt;p&gt;For each optional literal, we register a soft clause and assume it. If the assumption fails,
  1383. we ignore it. If it succeeds, but propagation fails, we undo the assumption.&lt;/p&gt;
  1384. &lt;div class=&quot;highlight&quot;&gt;&lt;pre tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-python3&quot; data-lang=&quot;python3&quot;&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; optionalLiteral &lt;span style=&quot;color: #f92672;&quot;&gt;in&lt;/span&gt; optionalLiterals:
  1385. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    registerClause(SoftClause([optionalLiteral]))
  1386. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;if&lt;/span&gt; assume(optionalLiteral) &lt;span style=&quot;color: #f92672;&quot;&gt;and&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;not&lt;/span&gt; propagate():
  1387. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        undo()
  1388. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;
  1389. &lt;li&gt;
  1390. &lt;p&gt;Finally we enter the main solver loop:&lt;/p&gt;
  1391. &lt;div class=&quot;highlight&quot;&gt;&lt;pre tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-python3&quot; data-lang=&quot;python3&quot;&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;while&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;True&lt;/span&gt;:
  1392. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;if&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;not&lt;/span&gt; propagate():
  1393. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        &lt;span style=&quot;color: #66d9ef;&quot;&gt;if&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;not&lt;/span&gt; backtrack():
  1394. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;            &lt;span style=&quot;color: #66d9ef;&quot;&gt;return&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;False&lt;/span&gt;
  1395. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;elif&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;all clauses are satisfied&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt;:
  1396. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        &lt;span style=&quot;color: #66d9ef;&quot;&gt;return&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;True&lt;/span&gt;
  1397. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;elif&lt;/span&gt; it &lt;span style=&quot;color: #f92672;&quot;&gt;:=&lt;/span&gt; find(&lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;best unassigned literal satisfying a hard clause&quot;&lt;/span&gt;):
  1398. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        assume(it)
  1399. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;    &lt;span style=&quot;color: #66d9ef;&quot;&gt;elif&lt;/span&gt; it &lt;span style=&quot;color: #f92672;&quot;&gt;:=&lt;/span&gt; find(&lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;best literal satisfying a soft clause&quot;&lt;/span&gt;):
  1400. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        assume(it)
  1401. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;/li&gt;
  1402. &lt;/ol&gt;
  1403. &lt;p&gt;The key point to note is that the main loop will undo the assumptions in order; so
  1404. if you assume &lt;code&gt;A,B,C&lt;/code&gt; and &lt;code&gt;B&lt;/code&gt; is not possible, we will have also undone &lt;code&gt;C&lt;/code&gt;. But since
  1405. &lt;code&gt;C&lt;/code&gt; is also enqueued as a soft clause, we will then later find it again:&lt;/p&gt;
  1406. &lt;ol&gt;
  1407. &lt;li&gt;Assume &lt;code&gt;A&lt;/code&gt;: &lt;code&gt;State=[Assume(A)]&lt;/code&gt;, &lt;code&gt;Clauses=[SoftClause([A])]&lt;/code&gt;&lt;/li&gt;
  1408. &lt;li&gt;Assume &lt;code&gt;B&lt;/code&gt;: &lt;code&gt;State=[Assume(A),Assume(B)]&lt;/code&gt;, &lt;code&gt;Clauses=[SoftClause([A]),SoftClause([B])]&lt;/code&gt;&lt;/li&gt;
  1409. &lt;li&gt;Assume &lt;code&gt;C&lt;/code&gt;: &lt;code&gt;State=[Assume(A),Assume(B),Assume(C)]&lt;/code&gt;, &lt;code&gt;Clauses=[SoftClause([A]),SoftClause([B]),SoftClause([C])]&lt;/code&gt;&lt;/li&gt;
  1410. &lt;li&gt;Solve finds a conflict, backtracks, and sets &lt;code&gt;not C&lt;/code&gt;: &lt;code&gt;State=[Assume(A),Assume(B),not(C)]&lt;/code&gt;&lt;/li&gt;
  1411. &lt;li&gt;Solve finds a conflict, backtracks, and sets &lt;code&gt;not B&lt;/code&gt;: &lt;code&gt;State=[Assume(A),not(B)]&lt;/code&gt; – C is no longer assumed either&lt;/li&gt;
  1412. &lt;li&gt;Solve, assume &lt;code&gt;C&lt;/code&gt; as it satisfies &lt;code&gt;SoftClause([C])&lt;/code&gt; as next best literal: &lt;code&gt;State=[Assume(A),not(B),Assume(C)]&lt;/code&gt;&lt;/li&gt;
  1413. &lt;li&gt;All clauses are satisfied, solution is &lt;code&gt;A&lt;/code&gt;, &lt;code&gt;not B&lt;/code&gt;, and &lt;code&gt;C&lt;/code&gt;.&lt;/li&gt;
  1414. &lt;/ol&gt;
  1415. &lt;p&gt;&lt;strong&gt;This is not (correct) MaxSAT&lt;/strong&gt;, because we actually do not guarantee that we satisfy as many soft clauses as possible. Consider you have the following clauses:&lt;/p&gt;
  1416. &lt;pre&gt;&lt;code&gt;Optional: A
  1417. Optional: B
  1418. Optional: C
  1419. B Conflicts with A
  1420. C Conflicts with A
  1421. &lt;/code&gt;&lt;/pre&gt;
  1422. &lt;p&gt;There are two possible results here:&lt;/p&gt;
  1423. &lt;ol&gt;
  1424. &lt;li&gt;&lt;code&gt;{A}&lt;/code&gt;   – If we assume &lt;code&gt;A&lt;/code&gt; first, we are unable to satisfy &lt;code&gt;B&lt;/code&gt; or &lt;code&gt;C&lt;/code&gt;.&lt;/li&gt;
  1425. &lt;li&gt;&lt;code&gt;{B,C}&lt;/code&gt; – If we assume either &lt;code&gt;B&lt;/code&gt; or &lt;code&gt;C&lt;/code&gt; first, &lt;code&gt;A&lt;/code&gt; is unsat.&lt;/li&gt;
  1426. &lt;/ol&gt;
  1427. &lt;p&gt;The question to ponder though is whether we actually need a global maximum or whether a local maximum is satisfactory in practice for a dependency solver
  1428. If you look at it, a naive MaxSAT solver needs to run the SAT solver &lt;code&gt;2**n&lt;/code&gt; times for &lt;code&gt;n&lt;/code&gt; soft clauses, whereas our heuristic only needs &lt;code&gt;n&lt;/code&gt; runs.&lt;/p&gt;
  1429. &lt;p&gt;For dependency solving, it seems we do not seem have a strong need for a global maximum:
  1430. There are various other preferences between our literals, say priorities;
  1431. and empirically, from evaluating hundreds of regressions &lt;em&gt;without&lt;/em&gt; the initial assumptions,
  1432. I can say that the assumptions do fix those cases and the result is correct.&lt;/p&gt;
  1433. &lt;p&gt;&lt;strong&gt;Further improvements&lt;/strong&gt; exist, though, and we can look into them if they are needed, such as:&lt;/p&gt;
  1434. &lt;ul&gt;
  1435. &lt;li&gt;
  1436. &lt;p&gt;Use a &lt;em&gt;better heuristic&lt;/em&gt;:&lt;/p&gt;
  1437. &lt;p&gt;If we assume 1 clause and solve, and we cause 2 or more clauses to become unsatisfiable,
  1438. then that clause is a local minimum and can be skipped.
  1439. This is a more common heuristical MaxSAT solver.
  1440. This gives us a &lt;em&gt;better&lt;/em&gt; local maximum, but not a global one.&lt;/p&gt;
  1441. &lt;p&gt;This is more or less what the &lt;a href=&quot;https://labix.org/smart&quot;&gt;Smart package manager&lt;/a&gt; did,
  1442. except that in Smart, all packages were optional, and the entire solution was scored.
  1443. It calculated a basic solution without optimization and then toggled each variable and saw if the score improved.&lt;/p&gt;
  1444. &lt;/li&gt;
  1445. &lt;li&gt;
  1446. &lt;p&gt;Implement &lt;em&gt;an actual search for a global maximum&lt;/em&gt;:&lt;/p&gt;
  1447. &lt;p&gt;This involves reading the literature.
  1448. There are various versions of this, for example:&lt;/p&gt;
  1449. &lt;ol&gt;
  1450. &lt;li&gt;
  1451. &lt;p&gt;Find unsatisfiable cores and use those to guide relaxation of clauses.&lt;/p&gt;
  1452. &lt;/li&gt;
  1453. &lt;li&gt;
  1454. &lt;p&gt;A bounds-based search, where we translate sum(satisifed clauses) &amp;gt; k into SAT, and then search in one of the following ways:&lt;/p&gt;
  1455. &lt;ol&gt;
  1456. &lt;li&gt;from 0 upward&lt;/li&gt;
  1457. &lt;li&gt;from n downward&lt;/li&gt;
  1458. &lt;li&gt;perform a binary search on [0, k] satisfied clauses.&lt;/li&gt;
  1459. &lt;/ol&gt;
  1460. &lt;p&gt;&lt;em&gt;Actually&lt;/em&gt; we do not even need to calculate sum constraints into CNF, because we can just add a specialized new type of constraint to our code.&lt;/p&gt;
  1461. &lt;/li&gt;
  1462. &lt;/ol&gt;
  1463. &lt;/li&gt;
  1464. &lt;/ul&gt;</description>
  1465. <pubDate>Sat, 24 May 2025 10:14:58 +0000</pubDate>
  1466. </item>
  1467. <item>
  1468. <title>Launchpad News: Sunsetting Launchpad’s mailing lists</title>
  1469. <guid isPermaLink="false">https://blog.launchpad.net/?p=4460</guid>
  1470. <link>https://blog.launchpad.net/general/sunsetting-launchpads-mailing-lists</link>
  1471. <description>&lt;h2&gt;What are Launchpad’s mailing lists?&lt;/h2&gt;
  1472.  
  1473.  
  1474.  
  1475. &lt;p&gt;Launchpad’s mailing lists are team-based mailing lists, which means that each team can have one of them. E-mails from Launchpad’s mailing lists contain `lists.launchpad.net ` in their address.&lt;/p&gt;
  1476.  
  1477.  
  1478.  
  1479. &lt;p&gt;For more information on the topic please see &lt;a href=&quot;https://help.launchpad.net/ListHelp&quot;&gt;https://help.launchpad.net/ListHelp&lt;/a&gt;.&lt;/p&gt;
  1480.  
  1481.  
  1482.  
  1483. &lt;h2&gt;What are they not?&lt;/h2&gt;
  1484.  
  1485.  
  1486.  
  1487. &lt;p&gt;Please note that both &lt;a href=&quot;http://lists.canonical.com&quot;&gt;lists.canonical.com&lt;/a&gt; and &lt;a href=&quot;http://lists.ubuntu.com&quot;&gt;lists.ubuntu.com&lt;/a&gt; are not managed by Launchpad, but by Canonical Information Systems.&lt;/p&gt;
  1488.  
  1489.  
  1490.  
  1491. &lt;h2&gt;Timeline&lt;/h2&gt;
  1492.  
  1493.  
  1494.  
  1495. &lt;p&gt;Launchpad will no longer offer mailing lists as of the end of October 2025, which aligns with the end of the 25.10 cycle.&lt;/p&gt;
  1496.  
  1497.  
  1498.  
  1499. &lt;h2&gt;Migration paths&lt;/h2&gt;
  1500.  
  1501.  
  1502.  
  1503. &lt;p&gt;Depending on your use case, there are different alternatives available.&lt;/p&gt;
  1504.  
  1505.  
  1506.  
  1507. &lt;p&gt;For a couple of years now, discourse has become a viable alternative for most scenarios. Launchpad also offers the &lt;a href=&quot;https://help.launchpad.net/Answers&quot;&gt;Answers feature&lt;/a&gt; for discussions. If it is not so much about communication, but more about receiving information, e.g. for updates on a bug report, you should be aware that you can also subscribe teams to bugs.&lt;/p&gt;
  1508.  
  1509.  
  1510.  
  1511. &lt;h2&gt;Call for action&lt;/h2&gt;
  1512.  
  1513.  
  1514.  
  1515. &lt;p&gt;We are aware that your use case may be very different from the above listed ones. If you are using Launchpad’s mailing lists today and you do not see a clear way forward, please reach out to us to discuss your use case and how we can help you.&lt;/p&gt;
  1516.  
  1517.  
  1518.  
  1519. &lt;p&gt;Please contact us on Matrix (#launchpad:&lt;a href=&quot;http://ubuntu.com&quot;&gt;ubuntu.com&lt;/a&gt;) or drop as a message via feedback@launchpad.net.&lt;/p&gt;
  1520.  
  1521.  
  1522.  
  1523. &lt;p&gt;Please note that this is still work in progress, and we will provide more information over the upcoming weeks and months.&lt;/p&gt;</description>
  1524. <pubDate>Thu, 22 May 2025 17:42:38 +0000</pubDate>
  1525. </item>
  1526. <item>
  1527. <title>Scarlett Gately Moore: KDE Application Snaps 25.04.1 with Major Bug Fix!,Life ( Good news finally!)</title>
  1528. <guid isPermaLink="false">https://www.scarlettgatelymoore.dev/?p=2079</guid>
  1529. <link>https://www.scarlettgatelymoore.dev/kde-application-snaps-25-04-1-with-major-bug-fixlife-good-news-finally/</link>
  1530. <description>&lt;div class=&quot;elementor elementor-2079&quot; data-elementor-id=&quot;2079&quot; data-elementor-type=&quot;wp-post&quot;&gt;
  1531. &lt;div class=&quot;elementor-element elementor-element-d7a6ffc e-flex e-con-boxed wpr-particle-no wpr-jarallax-no wpr-parallax-no wpr-sticky-section-no e-con e-parent&quot; data-element_type=&quot;container&quot; data-id=&quot;d7a6ffc&quot;&gt;
  1532. &lt;div class=&quot;e-con-inner&quot;&gt;
  1533. &lt;div class=&quot;elementor-element elementor-element-389a8ca elementor-widget elementor-widget-image&quot; data-element_type=&quot;widget&quot; data-id=&quot;389a8ca&quot; data-widget_type=&quot;image.default&quot;&gt;
  1534. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1535. &lt;img alt=&quot;&quot; class=&quot;attachment-large size-large wp-image-1816&quot; height=&quot;600&quot; src=&quot;https://www.scarlettgatelymoore.dev/wp-content/uploads/424px-Mascot_konqi-dev-kde.png&quot; width=&quot;424&quot; /&gt; &lt;/div&gt;
  1536. &lt;/div&gt;
  1537. &lt;div class=&quot;elementor-element elementor-element-27d9057 elementor-widget elementor-widget-heading&quot; data-element_type=&quot;widget&quot; data-id=&quot;27d9057&quot; data-widget_type=&quot;heading.default&quot;&gt;
  1538. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1539. &lt;h2 class=&quot;elementor-heading-title elementor-size-default&quot;&gt;Snaps!&lt;/h2&gt; &lt;/div&gt;
  1540. &lt;/div&gt;
  1541. &lt;div class=&quot;elementor-element elementor-element-2e9fb3f elementor-widget elementor-widget-text-editor&quot; data-element_type=&quot;widget&quot; data-id=&quot;2e9fb3f&quot; data-widget_type=&quot;text-editor.default&quot;&gt;
  1542. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1543. &lt;p&gt;I actually released last week &lt;img alt=&quot;🙂&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f642.png&quot; style=&quot;height: 1em;&quot; /&gt; I haven’t had time to blog, but today is my birthday and taking some time to myself!&lt;/p&gt;&lt;p&gt;This release came with a major bugfix. As it turns out our applications were very crashy on non-KDE platforms including Ubuntu proper. Unfortunately, for years, and I didn’t know. Developers were closing the bug reports as invalid because users couldn’t provide a stacktrace. I have now convinced most developers to assign snap bugs to the Snap platform so I at least get a chance to try and fix them. So with that said, if you tried our snaps in the past and gave up in frustration, please do try them again! I also spent some time cleaning up our snaps to only have current releases in the store, as rumor has it snapcrafters will be responsible for any security issues. With 200+ snaps I maintain, that is a lot of responsibility. We’ll see if I can pull it off.&lt;/p&gt; &lt;/div&gt;
  1544. &lt;/div&gt;
  1545. &lt;div class=&quot;elementor-element elementor-element-d42ab1c elementor-widget elementor-widget-heading&quot; data-element_type=&quot;widget&quot; data-id=&quot;d42ab1c&quot; data-widget_type=&quot;heading.default&quot;&gt;
  1546. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1547. &lt;h2 class=&quot;elementor-heading-title elementor-size-default&quot;&gt;Life!&lt;/h2&gt; &lt;/div&gt;
  1548. &lt;/div&gt;
  1549. &lt;div class=&quot;elementor-element elementor-element-c48fce7 elementor-widget elementor-widget-text-editor&quot; data-element_type=&quot;widget&quot; data-id=&quot;c48fce7&quot; data-widget_type=&quot;text-editor.default&quot;&gt;
  1550. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1551. &lt;p&gt;My last surgery was a success! I am finally healing and out of a sling for the first time in almost a year. I have also lined up a good amount of web work for next month and hopefully beyond. I have decided to drop the piece work for donations and will only accept per project proposals for open source work. I will continue to maintain KDE snaps for as long as time allows. A big thank you to everyone that has donated over the last year to fund my survival during this broken arm fiasco. I truly appreciate it!&lt;/p&gt; &lt;/div&gt;
  1552. &lt;/div&gt;
  1553. &lt;div class=&quot;elementor-element elementor-element-c0f7b20 elementor-widget elementor-widget-text-editor&quot; data-element_type=&quot;widget&quot; data-id=&quot;c0f7b20&quot; data-widget_type=&quot;text-editor.default&quot;&gt;
  1554. &lt;div class=&quot;elementor-widget-container&quot;&gt;
  1555. &lt;p&gt;With that said,  if you want to drop me a donation for my work, birthday or well-being until I get paid for the aforementioned web work please do so here:&lt;/p&gt;&lt;ul class=&quot;wp-block-list&quot;&gt;&lt;li&gt;&lt;a href=&quot;https://gofund.me/561ae227&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;GoFundMe&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://www.patreon.com/c/sgmoore&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Patreon&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://github.com/sponsors/ScarlettGatelyMoore?o=sd&amp;amp;sc=t&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Github&lt;/a&gt;&lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://donorbox.org/open-source-survival-fund&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Donorbox&lt;/a&gt;&lt;/li&gt;&lt;/ul&gt; &lt;/div&gt;
  1556. &lt;/div&gt;
  1557. &lt;/div&gt;
  1558. &lt;/div&gt;
  1559. &lt;/div&gt;</description>
  1560. <pubDate>Thu, 22 May 2025 12:49:25 +0000</pubDate>
  1561. </item>
  1562. <item>
  1563. <title>Kubuntu General News: Plasma 6.4 Beta1 available for testing</title>
  1564. <guid isPermaLink="false">https://kubuntu.org/?p=5329</guid>
  1565. <link>https://kubuntu.org/news/plasma-6-4-beta1-available-for-testing/</link>
  1566. <description>&lt;p id=&quot;block-d172a06c-2462-4906-86fc-3e208056ff7b&quot;&gt;&lt;br /&gt;Are you using Kubuntu 25.04 Plucky Puffin, our current stable release? Or are you already running our development builds of the upcoming 25.10 (Questing Quokka)?&lt;/p&gt;
  1567.  
  1568.  
  1569.  
  1570. &lt;p id=&quot;block-9c699339-e52d-4677-b409-c9b4fc924032&quot;&gt;We currently have &lt;a href=&quot;https://kde.org/announcements/plasma/6/6.3.90/&quot;&gt;Plasma 6.3.90 (Plasma 6.4 Beta1)&lt;/a&gt; available in our &lt;a href=&quot;https://launchpad.net/~kubuntu-ppa/+archive/ubuntu/beta&quot;&gt;Beta PPA&lt;/a&gt; for Kubuntu 25.04 and for the &lt;a href=&quot;http://cdimage.ubuntu.com/kubuntu/daily-live/current/&quot;&gt;25.10 development series&lt;/a&gt;.&lt;/p&gt;
  1571.  
  1572.  
  1573.  
  1574. &lt;p id=&quot;block-7b4e6602-72d0-43c0-b3f0-2d1b0eb96594&quot;&gt;However this is a Beta release, and we should re-iterate the disclaimer:&lt;/p&gt;
  1575.  
  1576.  
  1577.  
  1578. &lt;p id=&quot;block-a55e81b0-9713-490a-8522-a3e883c91e9e&quot;&gt;&lt;/p&gt;
  1579.  
  1580.  
  1581.  
  1582. &lt;p&gt;&lt;strong&gt;DISCLAIMER&lt;/strong&gt;: This release contains untested and unstable software. It is highly recommended you &lt;strong&gt;do not use this version in a production environment&lt;/strong&gt; and do not use it as your daily work environment. You risk crashes and loss of data.&lt;/p&gt;
  1583.  
  1584.  
  1585.  
  1586. &lt;p id=&quot;block-5d444010-ea6d-4273-9f29-15ec644b9564&quot;&gt;&lt;/p&gt;
  1587.  
  1588.  
  1589.  
  1590. &lt;p id=&quot;block-d8658d77-9e53-4d05-90f1-a48116e660bc&quot;&gt;6.4 Beta1 packages and required dependencies are available in our Beta PPA. The PPA should work whether you are currently using our backports PPA or not. If you are prepared to test via the PPA, then add the beta PPA and then upgrade:&lt;/p&gt;
  1591.  
  1592.  
  1593.  
  1594. &lt;pre class=&quot;wp-block-preformatted&quot; id=&quot;block-cfba50ba-2e9d-4487-9d61-21bc3167f4ee&quot;&gt;sudo add-apt-repository ppa:kubuntu-ppa/beta &amp;amp;&amp;amp; sudo apt full-upgrade -y&lt;/pre&gt;
  1595.  
  1596.  
  1597.  
  1598. &lt;p id=&quot;block-dc67bdb2-40cb-478f-8be2-048722434756&quot;&gt;Then reboot.&lt;/p&gt;
  1599.  
  1600.  
  1601.  
  1602. &lt;p id=&quot;block-60926ba5-9c4a-414f-a41a-5ffdacd7745b&quot;&gt;&lt;em&gt;&lt;strong&gt;In case of issues, testers should be prepared to use ppa-purge to remove the PPA and revert/downgrade packages.&lt;/strong&gt;&lt;/em&gt;&lt;/p&gt;
  1603.  
  1604.  
  1605.  
  1606. &lt;p id=&quot;block-eb072a47-2abc-4f23-947a-04467dfbe81b&quot;&gt;Kubuntu is part of the &lt;a href=&quot;https://www.kde.org/community/whatiskde/&quot;&gt;KDE community&lt;/a&gt;, so this testing will benefit both Kubuntu as well as upstream KDE Plasma software, which is used by many other distributions too.&lt;/p&gt;
  1607.  
  1608.  
  1609.  
  1610. &lt;ul id=&quot;block-5dfd69bc-7925-48b9-956f-378d0207d24f&quot;&gt;&lt;li&gt;If you believe you might have found a packaging bug, you can use &lt;a href=&quot;https://launchpad.net/&quot;&gt;launchpad.net&lt;/a&gt; to post testing feedback to the Kubuntu team as a bug, or give feedback on Matrix [1], or mailing lists [2].&lt;/li&gt;&lt;li&gt;If you believe you have found a bug in the underlying software, then &lt;a href=&quot;https://bugs.kde.org/&quot;&gt;bugs.kde.org&lt;/a&gt; is the best place to file your bug report.&lt;/li&gt;&lt;/ul&gt;
  1611.  
  1612.  
  1613.  
  1614. &lt;p id=&quot;block-1bd358e6-4a09-4d8b-a34d-90a1eaa241b4&quot;&gt;Please review the &lt;a href=&quot;https://community.kde.org/Plasma/Plasma_6#Plasma_6.4&quot;&gt;planned feature list&lt;/a&gt;,  &lt;a href=&quot;https://kde.org/announcements/plasma/5/5.24.90/&quot;&gt;&lt;/a&gt;&lt;a href=&quot;https://kde.org/announcements/plasma/6/6.3.90/&quot;&gt;release announcement&lt;/a&gt; and &lt;a href=&quot;https://kde.org/announcements/changelogs/plasma/6/6.3.5-6.3.90/&quot;&gt;changelog&lt;/a&gt;.&lt;/p&gt;
  1615.  
  1616.  
  1617.  
  1618. &lt;p id=&quot;block-15544460-9659-44c0-9c72-d8b6198392bf&quot;&gt;[Test Case]&lt;br /&gt;* General tests:&lt;br /&gt;– Does plasma desktop start as normal with no apparent regressions over 6.3?&lt;br /&gt;– General workflow – testers should carry out their normal tasks, using the plasma features they normally do, and test common subsystems such as audio, settings changes, compositing, desktop affects, suspend etc.&lt;br /&gt;* Specific tests:&lt;br /&gt;– Identify items with front/user facing changes capable of specific testing.&lt;br /&gt;– Test the ‘fixed’ functionality or ‘new’ feature.&lt;/p&gt;
  1619.  
  1620.  
  1621.  
  1622. &lt;p id=&quot;block-13f71df5-c42e-4782-b7e4-6613e3f0306e&quot;&gt;Testing may involve some technical set up to do, so while you do not need to be a highly advanced K/Ubuntu user, some proficiently in apt-based package management is advisable.&lt;/p&gt;
  1623.  
  1624.  
  1625.  
  1626. &lt;p id=&quot;block-8200b920-6a21-490c-8562-64576f2386c5&quot;&gt;Testing is very important to the quality of the software Ubuntu and Kubuntu developers package and release.&lt;/p&gt;
  1627.  
  1628.  
  1629.  
  1630. &lt;p id=&quot;block-cdc80c41-5654-4736-a57f-9738b9465e02&quot;&gt;We need your help to get this important beta release in shape for Kubuntu and the KDE community as a whole.&lt;/p&gt;
  1631.  
  1632.  
  1633.  
  1634. &lt;p id=&quot;block-cefe282e-0ef3-4aa1-a996-278b35dc0587&quot;&gt;Thanks!&lt;/p&gt;
  1635.  
  1636.  
  1637.  
  1638. &lt;p id=&quot;block-98c05cf6-5993-413e-b021-8c0bdbaffa4d&quot;&gt;Please stop by the Kubuntu-devel Matrix channel on if you need clarification of any of the steps to follow.&lt;/p&gt;
  1639.  
  1640.  
  1641.  
  1642. &lt;p id=&quot;block-e997dfca-5ffb-4535-b33b-1842bcbcfcdc&quot;&gt;[1] – &lt;a href=&quot;https://matrix.to/#/#kubuntu-devel:ubuntu.com&quot;&gt;https://matrix.to/#/#kubuntu-devel:ubuntu.com&lt;/a&gt;&lt;br /&gt;[2] –&lt;a href=&quot;https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel&quot;&gt; https://lists.ubuntu.com/mailman/listinfo/kubuntu-devel&lt;/a&gt;&lt;br /&gt;&lt;/p&gt;</description>
  1643. <pubDate>Sun, 18 May 2025 09:26:10 +0000</pubDate>
  1644. </item>
  1645. <item>
  1646. <title>Oliver Grawert: Rooming with Mark</title>
  1647. <guid isPermaLink="false">http://ograblog.wordpress.com/?p=389</guid>
  1648. <link>https://ograblog.wordpress.com/2025/05/16/rooming-with-mark/</link>
  1649. <description>&lt;p class=&quot;has-black-color has-text-color has-link-color wp-elements-6d4834a493ab5517648658b889ae02a2&quot;&gt;Yesterday, exactly twenty years ago my mobile rang while I was walking the dog. &lt;br /&gt;&lt;br /&gt;I had just returned from Sydney about a week ago (still battling with the last remains of my Jet-lag (I had never left Europe before!)) where I had attended the UbuntuDownUnder summit and had a 30min interview on the last day (that was literally rather like having a coffee with friends after lunch) with Mark Shuttleworth and Matt Zimmerman (back then Canonicals CTO) on a nice hotel terrace directly under a tree with a colony of flying foxes sleeping above our heads.&lt;br /&gt;&lt;br /&gt;There was Jane Silber (CEO) on the phone, telling me: “I’m so happy to tell you you are hired! In your new role we want you to create an educational flavor of Ubuntu, there will be a debian-edu/skolelinux gathering in Bergen in Norway from the 10th to 12th of June, are you okay flying there with Mark?”&lt;br /&gt;&lt;br /&gt;I rushed back home and told my girlfriend: “I’m hired, and I’ll fly Canonical One on my first business trip next month!” (Canonical One was the name of Marks plane). I learned the next weeks that Canonical had indeed booked a generic scheduled flight for me and we’d only meet at the venue &lt;img alt=&quot;🙂&quot; class=&quot;wp-smiley&quot; src=&quot;https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f642.png&quot; style=&quot;height: 1em;&quot; /&gt;&lt;br /&gt;&lt;br /&gt;The flight was a disaster, after we were boarding that small 20-seater 2 prop plane that was supposed to get us from Cologne to Amsterdam and the pilot started the engine my window all of a sudden was soaked in oil. We had to stay in the plane out on the filed while the mechanics were fixing the engine for like 2-3h so indeed I missed the connection in Amsterdam and had to stay for the night instead of arriving in Bergen the evening before the event started.&lt;br /&gt;&lt;br /&gt;When I arrived at the venue everyone was already busy hacking on stuff and I jumped right in alongside, finally meeting some users of LTSP (Linux Terminal Server Project) which I was upstream for at that time and working with them on the problems they faced in debian with it, tinkering with moodle as a teaching support system and looking at other edu software, meanwhile Mark was sitting on a bar-stool in a corner with his laptop hacking on launchpad code.&lt;br /&gt;&lt;br /&gt;When we went to our hotel in the evening it turned out they did not have our booking at all and were completely overbooked due to a jewelry exhibition they had in the house for that week. I talked like 15min to the lady behind the counter, showed her my booking confirmation PDF on the laptop, begged and flirted a lot and eventually she told us “We do have an exhibition room that we keep as spare, it only has one bed but you can have it and we will add a folding bed”. The room was actually a normal hotel room but completely set up with wallpaper tables all around the walls. &lt;br /&gt;&lt;br /&gt;Mark insisted to take the folding bed and I can tell you, he does not snore … (well, he didn’t back then)&lt;br /&gt;&lt;br /&gt;This was only the first of a plethora of adventures that followed in the upcoming 20 years, that phone call clearly changed my life and the company gave me the opportunity to work with the brightest, sharpest and most intelligent people on the planet in and outside of Canonical.&lt;br /&gt;&lt;br /&gt;It surely changed a lot over these years (when I started we were building the distro with 18 people in the distro team and did that for quite a few years before it actually got split into server, foundations, kernel and desktop teams) but it never lost its special spirit of having these exceptional people with such a high focus on bringing opensource to everyone and making it accessible to everyone. &lt;br /&gt;Indeed, with growth comes the requirement to make more money to pay the people, the responsibility to give your employees a certain amount of security and persistence grows, but Canonical and especially Mark have always managed to keep the balance to not lose that focus and do the right thing in the end.&lt;br /&gt;&lt;br /&gt;Ten years ago I said “onward to the next ten!!”, I won’t really say “onward to the nest 20!” today, not because I ever plan to resign but simply because I doubt I still want to work full time when I’m 75 &lt;img alt=&quot;😉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s0.wp.com/wp-content/mu-plugins/wpcom-smileys/twemoji/2/72x72/1f609.png&quot; style=&quot;height: 1em;&quot; /&gt;&lt;br /&gt;&lt;br /&gt;Thank you Mark for dragging me into this adventure and thank you for still having me! I still love the ride!!&lt;/p&gt;
  1650.  
  1651.  
  1652.  
  1653. &lt;p&gt;&lt;/p&gt;
  1654.  
  1655.  
  1656.  
  1657. &lt;p&gt;&lt;/p&gt;
  1658.  
  1659.  
  1660.  
  1661. &lt;p&gt;&lt;/p&gt;</description>
  1662. <pubDate>Fri, 16 May 2025 14:34:17 +0000</pubDate>
  1663. </item>
  1664. <item>
  1665. <title>Kubuntu General News: Plasma 6.3.5 update for Kubuntu 25.04 available via PPA</title>
  1666. <guid isPermaLink="false">https://kubuntu.org/?p=5326</guid>
  1667. <link>https://kubuntu.org/news/plasma-6-3-5-update-for-kubuntu-25-04-available-via-ppa/</link>
  1668. <description>&lt;p&gt;We are pleased to announce that the &lt;a href=&quot;https://kde.org/announcements/changelogs/plasma/6/6.3.4-6.3.5/&quot;&gt;Plasma 6.3.5 bugfix update&lt;/a&gt; is now available for Kubuntu 25.04 Plucky Puffin in our backports PPA.&lt;/p&gt;
  1669.  
  1670.  
  1671.  
  1672. &lt;p&gt;As usual with our PPAs, there is the caveat that the PPA may receive additional updates and new releases of KDE Plasma, Gear (Apps), and Frameworks, plus other apps and required libraries. Users should always review proposed updates to decide whether they wish to receive them.&lt;/p&gt;
  1673.  
  1674.  
  1675.  
  1676. &lt;p id=&quot;block-41439926-19ff-4ba1-b2d8-e1510a46c91c&quot;&gt;&lt;strong&gt;To upgrade:&lt;/strong&gt;&lt;/p&gt;
  1677.  
  1678.  
  1679.  
  1680. &lt;p id=&quot;block-064bf9c0-d3e6-4ba1-b03c-8e521932d684&quot;&gt;Add the following repository to your software sources list:&lt;/p&gt;
  1681.  
  1682.  
  1683.  
  1684. &lt;p id=&quot;block-a7e92586-3a90-42d3-9399-13a4a1b851b3&quot;&gt;&lt;strong&gt;&lt;em&gt;ppa:kubuntu-ppa/backports&lt;/em&gt;&lt;/strong&gt;&lt;/p&gt;
  1685.  
  1686.  
  1687.  
  1688. &lt;p id=&quot;block-6c6e34fc-0229-434c-895b-f9d88c130046&quot;&gt;or if it is already added, the updates should become available via your preferred update method.&lt;/p&gt;
  1689.  
  1690.  
  1691.  
  1692. &lt;p id=&quot;block-b4604309-93d2-417e-80a1-8cc452715567&quot;&gt;The PPA can be added manually in the Konsole terminal with the command:&lt;/p&gt;
  1693.  
  1694.  
  1695.  
  1696. &lt;p id=&quot;block-d080f84a-57e9-4b78-8d77-d9a43b4d4431&quot;&gt;&lt;em&gt;&lt;code&gt;sudo add-apt-repository ppa:kubuntu-ppa/backports&lt;/code&gt;&lt;/em&gt;&lt;/p&gt;
  1697.  
  1698.  
  1699.  
  1700. &lt;p id=&quot;block-719edd42-50bc-4443-93e2-96b65761e8f8&quot;&gt;and packages then updated with&lt;/p&gt;
  1701.  
  1702.  
  1703.  
  1704. &lt;p id=&quot;block-30a646d4-b528-46f4-8cd0-149b056c5689&quot;&gt;&lt;em&gt;sudo apt full-upgrade&lt;/em&gt;&lt;/p&gt;
  1705.  
  1706.  
  1707.  
  1708. &lt;p&gt;We hope you enjoy using Plasma 6.3.5!&lt;/p&gt;
  1709.  
  1710.  
  1711.  
  1712. &lt;p&gt;Issues with Plasma itself can be reported on the KDE bugtracker [1]. In the case of packaging or other issues, please provide feedback on our mailing list [2], and/or file a bug against our PPA packages [3].&lt;/p&gt;
  1713.  
  1714.  
  1715.  
  1716. &lt;p&gt;&lt;em&gt;&lt;em&gt;1. KDE bugtracker:&lt;/em&gt;:https://bugs.kde.org&lt;/em&gt;&lt;br /&gt;&lt;em&gt;2. Kubuntu-devel mailing list: https://lists.u&lt;br /&gt;3. Kubuntu ppa bugs: https://bugs.launchpad.net/kubuntu-ppa&lt;/em&gt;&lt;/p&gt;</description>
  1717. <pubDate>Thu, 08 May 2025 18:28:15 +0000</pubDate>
  1718. </item>
  1719. <item>
  1720. <title>Colin Watson: Free software activity in April 2025</title>
  1721. <guid isPermaLink="false">tag:www.chiark.greenend.org.uk,2025-05-04:/~cjwatson/blog/activity-2025-04.html</guid>
  1722. <link>https://www.chiark.greenend.org.uk/~cjwatson/blog/activity-2025-04.html</link>
  1723. <description>&lt;p&gt;About 90% of my Debian contributions this month were
  1724. &lt;a href=&quot;https://www.freexian.com/about/debian-contributions/&quot;&gt;sponsored&lt;/a&gt; by Freexian.&lt;/p&gt;
  1725. &lt;p&gt;You can also support my work directly via
  1726. &lt;a href=&quot;https://liberapay.com/cjwatson&quot;&gt;Liberapay&lt;/a&gt;.&lt;/p&gt;
  1727. &lt;h2&gt;Request for OpenSSH debugging help&lt;/h2&gt;
  1728. &lt;p&gt;Following the OpenSSH work described below, I have an &lt;a href=&quot;https://bugs.debian.org/1103418&quot;&gt;open
  1729. report&lt;/a&gt; about the &lt;code&gt;sshd&lt;/code&gt; server sometimes
  1730. crashing when clients try to connect to it.  I can’t reproduce this myself,
  1731. and arm’s-length debugging is very difficult, but three different users have
  1732. reported it.  For the time being I can’t pass it upstream, as it’s entirely
  1733. possible it’s due to a Debian patch.&lt;/p&gt;
  1734. &lt;p&gt;Is there anyone reading this who can reproduce this bug and is capable of
  1735. doing some independent debugging work, most likely involving bisecting
  1736. changes to OpenSSH?  I’d suggest first seeing whether a build of the
  1737. unmodified upstream 10.0p2 release exhibits the same bug.  If it does, then
  1738. bisect between 9.9p2 and 10.0p2; if not, then bisect the list of Debian
  1739. patches.  This would be extremely helpful, since at the moment it’s a bit
  1740. like trying to look for a needle in a haystack from the next field over by
  1741. sending instructions to somebody with a magnifying glass.&lt;/p&gt;
  1742. &lt;h2&gt;OpenSSH&lt;/h2&gt;
  1743. &lt;p&gt;I upgraded the Debian packaging to &lt;a href=&quot;https://www.openssh.com/releasenotes.html#10.0p2&quot;&gt;OpenSSH
  1744. 10.0p1&lt;/a&gt; (now &lt;a href=&quot;https://lists.mindrot.org/pipermail/openssh-unix-announce/2025-April/000163.html&quot;&gt;designated
  1745. 10.0p2&lt;/a&gt;
  1746. by upstream due to a mistake in the release process, but they’re the same
  1747. thing), fixing &lt;a href=&quot;https://bugs.debian.org/1102603&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2025-32728&lt;/a&gt;.  This also
  1748. involved a &lt;a href=&quot;https://bugs.debian.org/1102658&quot;&gt;diffoscope bug report&lt;/a&gt; due to
  1749. the version number change.&lt;/p&gt;
  1750. &lt;p&gt;I enabled the new &lt;code&gt;--with-linux-memlock-onfault&lt;/code&gt; configure option to protect
  1751. &lt;code&gt;sshd&lt;/code&gt; against being swapped out, but this turned out to cause test failures
  1752. on riscv64, so I disabled it again there.  Debugging this took some time
  1753. since I needed to do it under emulation, and in the process of setting up a
  1754. testbed I &lt;a href=&quot;https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/154&quot;&gt;added riscv64 support to
  1755. vmdb2&lt;/a&gt;.&lt;/p&gt;
  1756. &lt;p&gt;In &lt;a href=&quot;https://bugs.debian.org/1102643&quot;&gt;coordination&lt;/a&gt; with the wtmpdb
  1757. maintainer, I enabled the new Y2038-safe native wtmpdb support in OpenSSH,
  1758. so &lt;code&gt;wtmpdb last&lt;/code&gt; now reports the correct tty.&lt;/p&gt;
  1759. &lt;p&gt;I fixed a couple of packaging bugs:&lt;/p&gt;
  1760. &lt;ul&gt;
  1761. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1072184&quot;&gt;Please stop writing /var/log/btmp&lt;/a&gt;&lt;/li&gt;
  1762. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1095686&quot;&gt;Restore sshd_config(5) documentation about rdomain&lt;/a&gt;&lt;/li&gt;
  1763. &lt;/ul&gt;
  1764. &lt;p&gt;I reviewed and merged several packaging contributions from others:&lt;/p&gt;
  1765. &lt;ul&gt;
  1766. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103037&quot;&gt;ssh-agent: Improve systemd user service socket
  1767.  activation&lt;/a&gt; (Daniel Kahn Gillmor)&lt;/li&gt;
  1768. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/ssh-team/openssh/-/merge_requests/30&quot;&gt;Switch from adduser to
  1769.  sysusers.d&lt;/a&gt;
  1770.  (Luca Boccassi)&lt;/li&gt;
  1771. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/ssh-team/openssh/-/merge_requests/31&quot;&gt;Add sshd-keygen
  1772.  service&lt;/a&gt;
  1773.  (Luca Boccassi)&lt;/li&gt;
  1774. &lt;/ul&gt;
  1775. &lt;h2&gt;dput-ng&lt;/h2&gt;
  1776. &lt;p&gt;Since we &lt;a href=&quot;https://salsa.debian.org/freexian-team/debusine/-/issues/713&quot;&gt;added &lt;code&gt;dput-ng&lt;/code&gt; integration to
  1777. Debusine&lt;/a&gt;
  1778. recently, I wanted to make sure that it was in good condition in trixie, so
  1779. I fixed &lt;a href=&quot;https://bugs.debian.org/1078613&quot;&gt;dput-ng: will &lt;span class=&quot;caps&quot;&gt;FTBFS&lt;/span&gt; during trixie support
  1780. period&lt;/a&gt;.  Previously a similar bug had been
  1781. fixed by just using different Ubuntu release names in tests; this time I
  1782. made the tests independent of the current supported release data returned by
  1783. &lt;code&gt;distro_info&lt;/code&gt;, so this shouldn’t come up again.&lt;/p&gt;
  1784. &lt;p&gt;We also ran into &lt;a href=&quot;https://bugs.debian.org/983160&quot;&gt;dput-ng: —override doesn’t override profile
  1785. parameters&lt;/a&gt;, which needed somewhat more
  1786. extensive changes since it turned out that that option had never worked.  I
  1787. fixed this after some discussion with Paul Tagliamonte to make sure I
  1788. understood the background properly.&lt;/p&gt;
  1789. &lt;h2&gt;man-db&lt;/h2&gt;
  1790. &lt;p&gt;I released &lt;a href=&quot;https://gitlab.com/man-db/man-db/-/releases/2.13.1&quot;&gt;man-db
  1791. 2.13.1&lt;/a&gt;.  This just
  1792. included various small fixes and a number of translation updates, but I
  1793. wanted to get it into trixie in order to include a contribution to &lt;a href=&quot;https://gitlab.com/man-db/man-db/-/issues/48&quot;&gt;increase
  1794. the &lt;code&gt;MAX_NAME&lt;/code&gt; constant&lt;/a&gt;,
  1795. since that was now causing problems for some pathological cases of manual
  1796. pages in the wild that documented a very large number of terms.&lt;/p&gt;
  1797. &lt;h2&gt;debmirror&lt;/h2&gt;
  1798. &lt;p&gt;I fixed one security bug: &lt;a href=&quot;https://bugs.debian.org/1104091&quot;&gt;debmirror prints credentials with
  1799. —progress&lt;/a&gt;.&lt;/p&gt;
  1800. &lt;h2&gt;Python team&lt;/h2&gt;
  1801. &lt;p&gt;I upgraded these packages to new upstream versions:&lt;/p&gt;
  1802. &lt;ul&gt;
  1803. &lt;li&gt;celery&lt;/li&gt;
  1804. &lt;li&gt;django-modeltranslation (maintained by Freexian)&lt;/li&gt;
  1805. &lt;li&gt;django-phonenumber-field&lt;/li&gt;
  1806. &lt;li&gt;djangorestframework&lt;/li&gt;
  1807. &lt;li&gt;kombu&lt;/li&gt;
  1808. &lt;li&gt;orderly-set&lt;/li&gt;
  1809. &lt;li&gt;pox&lt;/li&gt;
  1810. &lt;li&gt;pydantic-extra-types&lt;/li&gt;
  1811. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1072833&quot;&gt;python-cmarkgfm&lt;/a&gt; (fixing
  1812.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2022-39209&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2022-39209&lt;/a&gt;,
  1813.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-22483&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-22483&lt;/a&gt;,
  1814.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-22484&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-22484&lt;/a&gt;,
  1815.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-22485&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-22485&lt;/a&gt;,
  1816.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-22486&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-22486&lt;/a&gt;,
  1817.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-24824&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-24824&lt;/a&gt;,
  1818.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-26485&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-26485&lt;/a&gt;,
  1819.  and
  1820.  &lt;a href=&quot;https://security-tracker.debian.org/tracker/CVE-2023-37463&quot;&gt;&lt;span class=&quot;caps&quot;&gt;CVE&lt;/span&gt;-2023-37463&lt;/a&gt;)&lt;/li&gt;
  1821. &lt;li&gt;python-django-crispy-forms&lt;/li&gt;
  1822. &lt;li&gt;python-django-extensions (fixing incompatibilities with Python 3.12:
  1823.  &lt;a href=&quot;https://bugs.debian.org/1040091&quot;&gt;#1040091&lt;/a&gt;,
  1824.  &lt;a href=&quot;https://bugs.debian.org/1040119&quot;&gt;#1040119&lt;/a&gt;)&lt;/li&gt;
  1825. &lt;li&gt;python-django-pgtrigger&lt;/li&gt;
  1826. &lt;li&gt;python-django-test-migrations&lt;/li&gt;
  1827. &lt;li&gt;python-holidays&lt;/li&gt;
  1828. &lt;li&gt;python-legacy-cgi&lt;/li&gt;
  1829. &lt;li&gt;python-pydash&lt;/li&gt;
  1830. &lt;li&gt;python-redis (4.3.4 to 5.2.1; needed some autopkgtest adjustments)&lt;/li&gt;
  1831. &lt;li&gt;python-tblib&lt;/li&gt;
  1832. &lt;li&gt;python-typing-extensions&lt;/li&gt;
  1833. &lt;li&gt;trove-classifiers&lt;/li&gt;
  1834. &lt;li&gt;xonsh&lt;/li&gt;
  1835. &lt;/ul&gt;
  1836. &lt;p&gt;In bookworm-backports, I updated these packages:&lt;/p&gt;
  1837. &lt;ul&gt;
  1838. &lt;li&gt;python-django to 3:4.2.20-1 (issuing
  1839.  &lt;a href=&quot;https://backports.debian.org/news/BSA-123_Security_Update_for_python-django/&quot;&gt;&lt;span class=&quot;caps&quot;&gt;BSA&lt;/span&gt;-123&lt;/a&gt;)&lt;/li&gt;
  1840. &lt;li&gt;python-django-pgtrigger to 4.13.3&lt;/li&gt;
  1841. &lt;/ul&gt;
  1842. &lt;p&gt;I dropped a stale build-dependency from
  1843. &lt;a href=&quot;https://bugs.debian.org/1102526&quot;&gt;python-aiohttp-security&lt;/a&gt; that kept it out
  1844. of testing (though unfortunately too late for the trixie freeze).&lt;/p&gt;
  1845. &lt;p&gt;I fixed or helped to fix various other build/test failures:&lt;/p&gt;
  1846. &lt;ul&gt;
  1847. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101621&quot;&gt;billiard&lt;/a&gt; (&lt;a href=&quot;https://github.com/celery/billiard/pull/423&quot;&gt;contributed
  1848.  upstream&lt;/a&gt;)&lt;/li&gt;
  1849. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1102380&quot;&gt;bleak-retry-connector&lt;/a&gt;&lt;/li&gt;
  1850. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103184&quot;&gt;cairosvg&lt;/a&gt;&lt;/li&gt;
  1851. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103066&quot;&gt;errbot&lt;/a&gt; (&lt;a href=&quot;https://github.com/errbotio/errbot/pull/1724&quot;&gt;contributed
  1852.  upstream&lt;/a&gt;)&lt;/li&gt;
  1853. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103116&quot;&gt;haversine&lt;/a&gt;&lt;/li&gt;
  1854. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1104240&quot;&gt;json-tricks&lt;/a&gt;&lt;/li&gt;
  1855. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103146&quot;&gt;jsonpickle&lt;/a&gt; (&lt;a href=&quot;https://github.com/jsonpickle/jsonpickle/pull/560&quot;&gt;contributed
  1856.  upstream&lt;/a&gt;)&lt;/li&gt;
  1857. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/python-team/packages/lazygal/-/commit/ea71ae96f4a48dd390f0e2b514234ce864ba430f&quot;&gt;lazygal&lt;/a&gt;&lt;/li&gt;
  1858. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101856&quot;&gt;mypy&lt;/a&gt;&lt;/li&gt;
  1859. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1102283&quot;&gt;pydantic&lt;/a&gt;&lt;/li&gt;
  1860. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101417&quot;&gt;pydantic-core&lt;/a&gt;&lt;/li&gt;
  1861. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101859&quot;&gt;pydantic-settings&lt;/a&gt;&lt;/li&gt;
  1862. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103197&quot;&gt;pympress&lt;/a&gt; (&lt;a href=&quot;https://github.com/Cimbali/pympress/pull/333&quot;&gt;contributed
  1863.  upstream&lt;/a&gt;)&lt;/li&gt;
  1864. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101861&quot;&gt;pysequoia&lt;/a&gt;&lt;/li&gt;
  1865. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103103&quot;&gt;pysodium&lt;/a&gt; (&lt;a href=&quot;https://github.com/stef/pysodium/pull/117&quot;&gt;contributed
  1866.  upstream&lt;/a&gt;)&lt;/li&gt;
  1867. &lt;li&gt;&lt;a href=&quot;https://salsa.debian.org/python-team/packages/python-decorator/-/commit/e9d3b610e7cc7e3766ea0be2b21b3489dc11d9d9&quot;&gt;python-decorator&lt;/a&gt;&lt;/li&gt;
  1868. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103593&quot;&gt;python-djvulibre&lt;/a&gt; (&lt;a href=&quot;https://github.com/FriedrichFroebel/python-djvulibre/pull/25&quot;&gt;contributed
  1869.  upstream&lt;/a&gt;)&lt;/li&gt;
  1870. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103140&quot;&gt;python-momepy&lt;/a&gt; (&lt;a href=&quot;https://github.com/pysal/momepy/pull/698&quot;&gt;contributed
  1871.  upstream&lt;/a&gt;)&lt;/li&gt;
  1872. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103362&quot;&gt;python-msgspec&lt;/a&gt;&lt;/li&gt;
  1873. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103581&quot;&gt;python-tz&lt;/a&gt;&lt;/li&gt;
  1874. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103501&quot;&gt;storm&lt;/a&gt;&lt;/li&gt;
  1875. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103208&quot;&gt;supysonic&lt;/a&gt;&lt;/li&gt;
  1876. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1101258&quot;&gt;uvloop&lt;/a&gt; (&lt;a href=&quot;https://github.com/MagicStack/uvloop/pull/662&quot;&gt;contributed
  1877.  upstream&lt;/a&gt;)&lt;/li&gt;
  1878. &lt;/ul&gt;
  1879. &lt;p&gt;I packaged &lt;a href=&quot;https://bugs.debian.org/1102391&quot;&gt;python-typing-inspection&lt;/a&gt;,
  1880. needed for a new upstream version of pydantic.&lt;/p&gt;
  1881. &lt;p&gt;I
  1882. &lt;a href=&quot;https://salsa.debian.org/python-team/tools/dh-python/-/merge_requests/57&quot;&gt;documented&lt;/a&gt;
  1883. the &lt;code&gt;architecture&lt;/code&gt; field in &lt;code&gt;debian/tests/autopkgtest-pkg-pybuild.conf&lt;/code&gt;
  1884. files.&lt;/p&gt;
  1885. &lt;p&gt;I fixed other odds and ends of bugs:&lt;/p&gt;
  1886. &lt;ul&gt;
  1887. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1087330&quot;&gt;python-pydash: please make the build reproducible&lt;/a&gt;&lt;/li&gt;
  1888. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1092859&quot;&gt;thunarx-python: fails to allow plugins to
  1889.  run&lt;/a&gt; / &lt;a href=&quot;https://bugs.debian.org/1103704&quot;&gt;thunarx-python: fails to discover
  1890.  &lt;span class=&quot;caps&quot;&gt;SONAME&lt;/span&gt; of libpython, tries to load
  1891.  /usr/lib/&lt;span class=&quot;caps&quot;&gt;MULTIARCH&lt;/span&gt;/lib.so.1.0&lt;/a&gt;&lt;/li&gt;
  1892. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1086561&quot;&gt;ttconv: package installs superfluous files under /usr/lib/python3/dist-packages&lt;/a&gt;&lt;/li&gt;
  1893. &lt;/ul&gt;
  1894. &lt;h2&gt;Science team&lt;/h2&gt;
  1895. &lt;p&gt;I fixed various build/test failures:&lt;/p&gt;
  1896. &lt;ul&gt;
  1897. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1102477&quot;&gt;python-vispy&lt;/a&gt; (also fixing &lt;a href=&quot;https://bugs.debian.org/1064607&quot;&gt;unhandled
  1898.  failures to build documentation can
  1899.  occur&lt;/a&gt; while I was there)&lt;/li&gt;
  1900. &lt;li&gt;&lt;a href=&quot;https://bugs.debian.org/1103004&quot;&gt;skimage&lt;/a&gt;&lt;/li&gt;
  1901. &lt;/ul&gt;</description>
  1902. <pubDate>Sun, 04 May 2025 15:38:13 +0000</pubDate>
  1903. </item>
  1904. <item>
  1905. <title>Simos Xenitellis: How to run a Linux Desktop virtual machine on Incus</title>
  1906. <guid isPermaLink="false">https://blog.simos.info/?p=51377</guid>
  1907. <link>https://blog.simos.info/how-to-run-a-linux-desktop-virtual-machine-on-incus/</link>
  1908. <description>&lt;p&gt;&lt;a href=&quot;https://linuxcontainers.org/incus/&quot;&gt;Incus&lt;/a&gt; is a manager for virtual machines and system containers.&lt;/p&gt;
  1909.  
  1910.  
  1911.  
  1912. &lt;p&gt;A &lt;strong&gt;virtual machine&lt;/strong&gt; (VM) is an instance of an operating system that runs on a computer, along with the main operating system. A virtual machine uses hardware virtualization features for the separation from the main operating system. With virtual machines, the full operating system boots up in them. While in most cases you would run Linux on a VM without a desktop environment, you can also run Linux with a desktop environment (like in VirtualBox and VMWare).&lt;/p&gt;
  1913.  
  1914.  
  1915.  
  1916. &lt;p&gt;In &lt;a href=&quot;https://blog.simos.info/how-to-run-a-windows-virtual-machine-on-incus-on-linux/&quot;&gt;How to run a Windows virtual machine on Incus on Linux&lt;/a&gt; we saw how to run a run a Windows VM on Incus. In this post we see how to run a Linux Desktop virtual machine on Incus. &lt;/p&gt;
  1917.  
  1918.  
  1919. &lt;h2 class=&quot;simpletoc-title&quot;&gt;Table of Contents&lt;/h2&gt;
  1920. &lt;ul class=&quot;simpletoc-list&quot;&gt;
  1921. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#updates&quot;&gt;Updates&lt;/a&gt;
  1922.  
  1923. &lt;/li&gt;
  1924. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#prerequisites&quot;&gt;Prerequisites&lt;/a&gt;
  1925.  
  1926. &lt;/li&gt;
  1927. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#cheat-sheet&quot;&gt;Cheat sheet&lt;/a&gt;
  1928.  
  1929. &lt;/li&gt;
  1930. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#availability-of-images&quot;&gt;Availability of images&lt;/a&gt;
  1931.  
  1932. &lt;/li&gt;
  1933. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#booting-a-desktop-linux-vm-on-incus&quot;&gt;Booting a desktop Linux VM on Incus&lt;/a&gt;
  1934.  
  1935.  
  1936. &lt;ul&gt;&lt;li&gt;
  1937. &lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#booting-the-ubuntu-desktop-image-on-incus&quot;&gt;Booting the Ubuntu desktop image on Incus&lt;/a&gt;
  1938.  
  1939. &lt;/li&gt;
  1940. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#booting-the-archlinux-desktop-image-on-incus&quot;&gt;Booting the ArchLinux desktop image on Incus&lt;/a&gt;
  1941.  
  1942. &lt;/li&gt;
  1943. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#booting-the-opensuse-desktop-image-on-incus&quot;&gt;Booting the OpenSUSE desktop image on Incus&lt;/a&gt;
  1944.  
  1945. &lt;/li&gt;
  1946. &lt;/ul&gt;
  1947. &lt;/li&gt;&lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#troubleshooting&quot;&gt;Troubleshooting&lt;/a&gt;
  1948.  
  1949.  
  1950. &lt;ul&gt;&lt;li&gt;
  1951.  
  1952. &lt;ul&gt;&lt;li&gt;
  1953. &lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#i-closed-the-desktop-window-but-the-vm-is-running-how-do-i-get-it-back-up&quot;&gt;I closed the desktop window but the VM is running. How do I get it back up?&lt;/a&gt;
  1954.  
  1955. &lt;/li&gt;
  1956. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#error-this-console-is-already-connected-force-is-required-to-take-it-over&quot;&gt;Error: This console is already connected. Force is required to take it over.&lt;/a&gt;
  1957.  
  1958. &lt;/li&gt;
  1959. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#error-instance-is-not-running&quot;&gt;Error: Instance is not running&lt;/a&gt;
  1960.  
  1961. &lt;/li&gt;
  1962. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#i-get-no-audio-from-the-desktop-vm-how-do-i-get-sound-in-the-desktop-vm&quot;&gt;I get no audio from the desktop VM! How do I get sound in the desktop VM?&lt;/a&gt;
  1963.  
  1964. &lt;/li&gt;
  1965. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#how-do-i-shutdown-the-desktop-vm&quot;&gt;How do I shutdown the desktop VM?&lt;/a&gt;
  1966.  
  1967. &lt;/li&gt;
  1968. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#error-failed-instance-creation-the-image-used-by-this-instance-is-incompatible-with-secureboot-please-set-securitysecurebootfalse-on-the-instance&quot;&gt;Error: Failed instance creation: The image used by this instance is incompatible with secureboot. Please set security.secureboot=false on the instance&lt;/a&gt;
  1969.  
  1970. &lt;/li&gt;
  1971. &lt;li&gt;&lt;a href=&quot;https://blog.simos.info/category/planet-ubuntu/feed/?mrss=off#error-failed-instance-creation-failed-creating-instance-record-add-instance-info-to-the-database-failed-to-create-instances-entry-unique-constraint-failed-instancesprojectid-instancesname&quot;&gt;Error: Failed instance creation: Failed creating instance record: Add instance info to the database: Failed to create “instances” entry: UNIQUE constraint failed: instances.project_id, instances.name&lt;/a&gt;
  1972. &lt;/li&gt;
  1973. &lt;/ul&gt;
  1974. &lt;/li&gt;
  1975. &lt;/ul&gt;
  1976. &lt;/li&gt;&lt;/ul&gt;
  1977.  
  1978. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;updates&quot;&gt;Updates&lt;/h2&gt;
  1979.  
  1980.  
  1981. &lt;p&gt;No updates yet.&lt;/p&gt;
  1982.  
  1983.  
  1984. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;prerequisites&quot;&gt;Prerequisites&lt;/h2&gt;
  1985.  
  1986.  
  1987. &lt;ol class=&quot;wp-block-list&quot;&gt;
  1988. &lt;li&gt;You should have &lt;a href=&quot;https://linuxcontainers.org/incus/docs/main/tutorial/first_steps/&quot;&gt;a system that runs Incus&lt;/a&gt;. &lt;/li&gt;
  1989.  
  1990.  
  1991.  
  1992. &lt;li&gt;A system with support for hardware virtualization so that it can run virtual machines.&lt;/li&gt;
  1993.  
  1994.  
  1995.  
  1996. &lt;li&gt;A virtual machine image of your preferred Linux desktop distribution.&lt;/li&gt;
  1997. &lt;/ol&gt;
  1998.  
  1999.  
  2000. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;cheat-sheet&quot;&gt;Cheat sheet&lt;/h2&gt;
  2001.  
  2002.  
  2003. &lt;p&gt;You should specify how much RAM memory you are giving to the VM. The default is only 1GiB of RAM, which is not enough for desktop VMs. The &lt;code&gt;--console=vga&lt;/code&gt; launches for you the Remote Viewer GUI application to allow you to use the desktop in a window.&lt;/p&gt;
  2004.  
  2005.  
  2006.  
  2007. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus image list images:desktop       # List all available desktop images
  2008. $ incus launch --vm images:ubuntu/jammy/desktop mydesktop -c limits.memory=3GiB --console=vga
  2009. $ incus console mydesktop --type=vga    # Reconnect to already running instance
  2010. $ incus start mydesktop --console=vga   # Start an existing desktop VM&lt;/code&gt;&lt;/pre&gt;
  2011.  
  2012.  
  2013. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;availability-of-images&quot;&gt;Availability of images&lt;/h2&gt;
  2014.  
  2015.  
  2016. &lt;p&gt;Currently, Incus provides you with the following VM images of Linux desktop distributions. The architecture is &lt;code&gt;x86_64&lt;/code&gt;.&lt;/p&gt;
  2017.  
  2018.  
  2019.  
  2020. &lt;p&gt;Run the following command to list all available Linux desktop images. &lt;code&gt;incus image&lt;/code&gt; is the section of Incus that deals with the management of images. The &lt;code&gt;list&lt;/code&gt; command lists the available images of a &lt;em&gt;remote&lt;/em&gt;/repository, the default being &lt;code&gt;images:&lt;/code&gt; (run &lt;code&gt;incus remote list&lt;/code&gt; for the full list of &lt;em&gt;remotes&lt;/em&gt;). After the colon (&lt;code&gt;:&lt;/code&gt;), you type &lt;em&gt;filter&lt;/em&gt; keywords, and in this case we typed &lt;code&gt;desktop&lt;/code&gt; to show images that have the word &lt;code&gt;desktop&lt;/code&gt; in them (to show only Desktop images). We are interested in a few columns only, therefore &lt;code&gt;-c ldt&lt;/code&gt; only shows the columns for the &lt;em&gt;Alias&lt;/em&gt;, the &lt;em&gt;Description&lt;/em&gt; and the &lt;em&gt;Type&lt;/em&gt;.&lt;/p&gt;
  2021.  
  2022.  
  2023.  
  2024. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus image list images:desktop -c ldt
  2025. +------------------------------------------+---------------------------+-----------------+
  2026. |                  ALIAS                   |      DESCRIPTION          |      TYPE       |
  2027. +------------------------------------------+---------------------------+-----------------+
  2028. | archlinux/desktop-gnome (3 more)         | Archlinux current amd64   | VIRTUAL-MACHINE |
  2029. +------------------------------------------+---------------------------+-----------------+
  2030. | opensuse/15.5/desktop-kde (1 more)       | Opensuse 15.5 amd64       | VIRTUAL-MACHINE |
  2031. +------------------------------------------+---------------------------+-----------------+
  2032. | opensuse/15.6/desktop-kde (1 more)       | Opensuse 15.6 amd64       | VIRTUAL-MACHINE |
  2033. +------------------------------------------+---------------------------+-----------------+
  2034. | opensuse/tumbleweed/desktop-kde (1 more) | Opensuse tumbleweed amd64 | VIRTUAL-MACHINE |
  2035. +------------------------------------------+---------------------------+-----------------+
  2036. | ubuntu/24.10/desktop (3 more)            | Ubuntu oracular amd64     | VIRTUAL-MACHINE |
  2037. +------------------------------------------+---------------------------+-----------------+
  2038. | ubuntu/focal/desktop (3 more)            | Ubuntu focal amd64        | VIRTUAL-MACHINE |
  2039. +------------------------------------------+---------------------------+-----------------+
  2040. | ubuntu/jammy/desktop (3 more)            | Ubuntu jammy amd64        | VIRTUAL-MACHINE |
  2041. +------------------------------------------+---------------------------+-----------------+
  2042. | ubuntu/noble/desktop (3 more)            | Ubuntu noble amd64        | VIRTUAL-MACHINE |
  2043. +------------------------------------------+---------------------------+-----------------+
  2044. | ubuntu/plucky/desktop (1 more)           | Ubuntu plucky amd64       | VIRTUAL-MACHINE |
  2045. +------------------------------------------+---------------------------+-----------------+
  2046. $ &lt;/code&gt;&lt;/pre&gt;
  2047.  
  2048.  
  2049.  
  2050. &lt;p&gt;These images have been generated with the utility &lt;code&gt;distrobuilder&lt;/code&gt;, &lt;a href=&quot;https://github.com/lxc/distrobuilder&quot;&gt;https://github.com/lxc/distrobuilder&lt;/a&gt; The purpose of the utility is to prepare the images so that when we launch them, we get immediately the desktop environment and do not perform any manual configuration. The configuration files for distrobuilder to create these images can be found at &lt;a href=&quot;https://github.com/lxc/lxc-ci/tree/main/images&quot;&gt;https://github.com/lxc/lxc-ci/tree/main/images&lt;/a&gt; For example, the &lt;code&gt;archlinux.yaml&lt;/code&gt; configuration file has a section to create the desktop image, along with the container and other virtual machine images. &lt;/p&gt;
  2051.  
  2052.  
  2053.  
  2054. &lt;p&gt;The full list of Incus images are also available on the Web, through the website &lt;a href=&quot;https://images.linuxcontainers.org/&quot;&gt;https://images.linuxcontainers.org/&lt;/a&gt; It is possible to generate more such desktop images by following the steps of the existing configuration files. Perhaps a Kali Linux desktop image would be very useful. In the &lt;a href=&quot;https://images.linuxcontainers.org/&quot;&gt;https://images.linuxcontainers.org/&lt;/a&gt; website you can also view the build logs that were generated while building the images, and figure out what parameters are needed for &lt;code&gt;distrobuilder&lt;/code&gt; to build them (along with the actual configuration file). For example, here are the logs for the ArchLinux desktop image, &lt;a href=&quot;https://images.linuxcontainers.org/images/archlinux/current/amd64/desktop-gnome/&quot;&gt;https://images.linuxcontainers.org/images/archlinux/current/amd64/desktop-gnome/&lt;/a&gt;&lt;/p&gt;
  2055.  
  2056.  
  2057.  
  2058. &lt;p&gt;Up to this point we got a list of the available virtual machine images that are provided by Incus. We are ready to boot them.&lt;/p&gt;
  2059.  
  2060.  
  2061. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;booting-a-desktop-linux-vm-on-incus&quot;&gt;Booting a desktop Linux VM on Incus&lt;/h2&gt;
  2062.  
  2063.  
  2064. &lt;p&gt;When launching a VM, Incus provides by default 1GiB RAM and 10GiB of disk space. The disk space is generally OK, but the RAM is too little for a desktop image (it’s OK for non-desktop images). For example, for an Ubuntu desktop image, the instance requires about 1.2GB of memory to start up and obviously more to run other programs. Therefore, if we do not specify more RAM, then the VM would struggle to make do of the mere 1GiB of RAM.&lt;/p&gt;
  2065.  
  2066.  
  2067. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;booting-the-ubuntu-desktop-image-on-incus&quot;&gt;Booting the Ubuntu desktop image on Incus&lt;/h3&gt;
  2068.  
  2069.  
  2070. &lt;p&gt;Here is the command to launch a desktop image. We use &lt;code&gt;incus launch&lt;/code&gt; to launch the image. It’s a VM, hence &lt;code&gt;--vm&lt;/code&gt;. We are using the image from the &lt;code&gt;images:&lt;/code&gt; remote, the one called &lt;code&gt;ubuntu/plucky/desktop&lt;/code&gt; (it’s the last from the list of the previous section). We configure a new limit for the memory usage, &lt;code&gt;-c limits.memory=3GiB&lt;/code&gt;, so that the instance will be able to run successfully. Finally, the console is not textual but graphical. We specify that with &lt;code&gt;--console=vga&lt;/code&gt; which means that Incus will launch the remote desktop utility for us. &lt;/p&gt;
  2071.  
  2072.  
  2073.  
  2074. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus launch --vm images:ubuntu/plucky/desktop mydesktop -c limits.memory=3GiB --console=vga
  2075. Launching mydesktop
  2076. &lt;/code&gt;&lt;/pre&gt;
  2077.  
  2078.  
  2079.  
  2080. &lt;p&gt;Here is a screenshot of the new window with the running desktop virtual machine. &lt;/p&gt;
  2081.  
  2082.  
  2083.  
  2084. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;a href=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-01-23-03-37.png?ssl=1&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-51379&quot; data-attachment-id=&quot;51379&quot; data-comments-opened=&quot;1&quot; data-image-caption=&quot;&quot; data-image-description=&quot;&quot; data-image-meta=&quot;{&amp;quot;aperture&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;credit&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;camera&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;caption&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;created_timestamp&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;copyright&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;focal_length&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;iso&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;shutter_speed&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;title&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;orientation&amp;quot;:&amp;quot;0&amp;quot;}&quot; data-image-title=&quot;Screenshot from 2025-05-01 23-03-37&quot; data-large-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-01-23-03-37.png?fit=750%2C508&amp;amp;ssl=1&quot; data-medium-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-01-23-03-37.png?fit=300%2C203&amp;amp;ssl=1&quot; data-orig-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-01-23-03-37.png?fit=1300%2C880&amp;amp;ssl=1&quot; data-orig-size=&quot;1300,880&quot; data-permalink=&quot;https://blog.simos.info/how-to-run-a-linux-desktop-virtual-machine-on-incus/screenshot-from-2025-05-01-23-03-37/&quot; data-recalc-dims=&quot;1&quot; height=&quot;508&quot; src=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-01-23-03-37.png?resize=750%2C508&amp;amp;ssl=1&quot; width=&quot;750&quot; /&gt;&lt;/a&gt;Screenshot of images:ubuntu/plucky/desktop&lt;/figure&gt;
  2085.  
  2086.  
  2087.  
  2088. &lt;p&gt;Now we closed the wizard.&lt;/p&gt;
  2089.  
  2090.  
  2091.  
  2092. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;a href=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/image.png?ssl=1&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-51380&quot; data-attachment-id=&quot;51380&quot; data-comments-opened=&quot;1&quot; data-image-caption=&quot;&quot; data-image-description=&quot;&quot; data-image-meta=&quot;{&amp;quot;aperture&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;credit&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;camera&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;caption&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;created_timestamp&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;copyright&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;focal_length&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;iso&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;shutter_speed&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;title&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;orientation&amp;quot;:&amp;quot;0&amp;quot;}&quot; data-image-title=&quot;image&quot; data-large-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/image.png?fit=750%2C508&amp;amp;ssl=1&quot; data-medium-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/image.png?fit=300%2C203&amp;amp;ssl=1&quot; data-orig-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/image.png?fit=1300%2C880&amp;amp;ssl=1&quot; data-orig-size=&quot;1300,880&quot; data-permalink=&quot;https://blog.simos.info/how-to-run-a-linux-desktop-virtual-machine-on-incus/image-13/&quot; data-recalc-dims=&quot;1&quot; height=&quot;508&quot; src=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/image.png?resize=750%2C508&amp;amp;ssl=1&quot; width=&quot;750&quot; /&gt;&lt;/a&gt;Screenshot of images:ubuntu/plucky/desktop after we close the wizard.&lt;/figure&gt;
  2093.  
  2094.  
  2095. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;booting-the-archlinux-desktop-image-on-incus&quot;&gt;Booting the ArchLinux desktop image on Incus&lt;/h3&gt;
  2096.  
  2097.  
  2098. &lt;p&gt;I cannot get this image to show the desktop. If someone can make this work, please post in a comment.&lt;/p&gt;
  2099.  
  2100.  
  2101.  
  2102. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus launch --vm images:archlinux/desktop-gnome mydesktop -c limits.memory=3GiB --console=vga -c security.secureboot=false
  2103. Launching mydesktop
  2104. &lt;/code&gt;&lt;/pre&gt;
  2105.  
  2106.  
  2107. &lt;h3 class=&quot;wp-block-heading&quot; id=&quot;booting-the-opensuse-desktop-image-on-incus&quot;&gt;Booting the OpenSUSE desktop image on Incus&lt;/h3&gt;
  2108.  
  2109.  
  2110. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus launch --vm images:opensuse/15.5/desktop-kde mydesktop -c limits.memory=3GiB --console=vga
  2111. Launching mydesktop
  2112. &lt;/code&gt;&lt;/pre&gt;
  2113.  
  2114.  
  2115.  
  2116. &lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;a href=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-02-01-41-39.png?ssl=1&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-51382&quot; data-attachment-id=&quot;51382&quot; data-comments-opened=&quot;1&quot; data-image-caption=&quot;&quot; data-image-description=&quot;&quot; data-image-meta=&quot;{&amp;quot;aperture&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;credit&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;camera&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;caption&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;created_timestamp&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;copyright&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;focal_length&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;iso&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;shutter_speed&amp;quot;:&amp;quot;0&amp;quot;,&amp;quot;title&amp;quot;:&amp;quot;&amp;quot;,&amp;quot;orientation&amp;quot;:&amp;quot;0&amp;quot;}&quot; data-image-title=&quot;Screenshot from 2025-05-02 01-41-39&quot; data-large-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-02-01-41-39.png?fit=750%2C508&amp;amp;ssl=1&quot; data-medium-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-02-01-41-39.png?fit=300%2C203&amp;amp;ssl=1&quot; data-orig-file=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-02-01-41-39.png?fit=1300%2C880&amp;amp;ssl=1&quot; data-orig-size=&quot;1300,880&quot; data-permalink=&quot;https://blog.simos.info/how-to-run-a-linux-desktop-virtual-machine-on-incus/screenshot-from-2025-05-02-01-41-39/&quot; data-recalc-dims=&quot;1&quot; height=&quot;508&quot; src=&quot;https://i0.wp.com/blog.simos.info/wp-content/uploads/2025/05/Screenshot-from-2025-05-02-01-41-39.png?resize=750%2C508&amp;amp;ssl=1&quot; width=&quot;750&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  2117.  
  2118.  
  2119. &lt;h2 class=&quot;wp-block-heading&quot; id=&quot;troubleshooting&quot;&gt;Troubleshooting&lt;/h2&gt;
  2120.  
  2121. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;i-closed-the-desktop-window-but-the-vm-is-running-how-do-i-get-it-back-up&quot;&gt;I closed the desktop window but the VM is running. How do I get it back up?&lt;/h4&gt;
  2122.  
  2123.  
  2124. &lt;p&gt;If you closed the Remote Viewer window, you can get Incus to start it again with the following command. By doing so, you are actually reconnecting back to the VM and continue working from where you left off.&lt;/p&gt;
  2125.  
  2126.  
  2127.  
  2128. &lt;p&gt;We are using the &lt;code&gt;incus console&lt;/code&gt; action to connect to the running &lt;em&gt;mydesktop&lt;/em&gt; instance and request access through the Remote Viewer (rather than a text console).&lt;/p&gt;
  2129.  
  2130.  
  2131.  
  2132. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus console mydesktop --type=vga
  2133. &lt;/code&gt;&lt;/pre&gt;
  2134.  
  2135.  
  2136. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;error-this-console-is-already-connected-force-is-required-to-take-it-over&quot;&gt;Error: This console is already connected. Force is required to take it over.&lt;/h4&gt;
  2137.  
  2138.  
  2139. &lt;p&gt;You are already connected to the desktop VM with the Remote Viewer and you are trying to connect again. Either go to the existing Remote Viewer window, or add the parameter &lt;code&gt;--force&lt;/code&gt; to close the existing Remote Viewer window and open a new one. &lt;/p&gt;
  2140.  
  2141.  
  2142. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;error-instance-is-not-running&quot;&gt;Error: Instance is not running&lt;/h4&gt;
  2143.  
  2144.  
  2145. &lt;p&gt;You are trying to connect to a desktop VM with the Remote Viewer but the instance (which already exists) is not running. Use the action &lt;code&gt;incus start&lt;/code&gt; to start the virtual machine, along with the &lt;code&gt;--type=vga&lt;/code&gt; parameter to get Incus to launch the Remote Viewer for you.&lt;/p&gt;
  2146.  
  2147.  
  2148.  
  2149. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus start mydesktop --console=vga&lt;/code&gt;&lt;/pre&gt;
  2150.  
  2151.  
  2152. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;i-get-no-audio-from-the-desktop-vm-how-do-i-get-sound-in-the-desktop-vm&quot;&gt;I get no audio from the desktop VM! How do I get sound in the desktop VM?&lt;/h4&gt;
  2153.  
  2154.  
  2155. &lt;p&gt;This requires extra steps which I do not show yet. There are three options. The first is to use the QEMU device emulation to emulate a sound device in the VM. The second is to somehow push an audio device into the VM so that this audio device is used exclusively in the VM (have not tried this but I think it’s possible). The third and perhaps best option is to use network audio with PulseAudio/Pipewire. You enable network audio on your desktop and then configure the VM instance to connect to that network audio server. I have tried that and it worked well for me. The downside is that the Firefox snap package in the VM could not figure out that there is network audio there and I could not get audio in that application. &lt;/p&gt;
  2156.  
  2157.  
  2158. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;how-do-i-shutdown-the-desktop-vm&quot;&gt;How do I shutdown the desktop VM?&lt;/h4&gt;
  2159.  
  2160.  
  2161. &lt;p&gt;Use the desktop UI to perform the shutdown. The VM will shut down cleanly.&lt;/p&gt;
  2162.  
  2163.  
  2164. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;error-failed-instance-creation-the-image-used-by-this-instance-is-incompatible-with-secureboot-please-set-securitysecurebootfalse-on-the-instance&quot;&gt;Error: Failed instance creation: The image used by this instance is incompatible with secureboot. Please set security.secureboot=false on the instance&lt;/h4&gt;
  2165.  
  2166.  
  2167. &lt;p&gt;You tried to launch a virtual machine with SecureBoot enabled but the image does not support SecureBoot. You need to disable SecureBoot when you launch this image. The instance has been created but is unable to run unless you disable SecureBoot. You can either disable SecureBoot through an Incus configuration for this image, or just delete the instance, and try again with the parameter &lt;code&gt;-c security.secureboot=false&lt;/code&gt;. &lt;/p&gt;
  2168.  
  2169.  
  2170.  
  2171. &lt;p&gt;Here is how to disable SecureBoot, then try to &lt;code&gt;incus start&lt;/code&gt; that instance. &lt;/p&gt;
  2172.  
  2173.  
  2174.  
  2175. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;$ incus config set mydesktop security.secureboot=true&lt;/code&gt;&lt;/pre&gt;
  2176.  
  2177.  
  2178.  
  2179. &lt;p&gt;Here is how you would enable that flag when you launch such a VM.&lt;/p&gt;
  2180.  
  2181.  
  2182.  
  2183. &lt;pre class=&quot;wp-block-code&quot;&gt;&lt;code&gt;incus launch --vm images:archlinux/desktop-gnome mydesktop -c limits.memory=3GiB --console=vga -c security.secureboot=false&lt;/code&gt;&lt;/pre&gt;
  2184.  
  2185.  
  2186.  
  2187. &lt;p&gt;Note that official Ubuntu images can work with SecureBoot enabled, most others don’t. It has to do with the Linux kernel being digitally signed by some certification authority.&lt;/p&gt;
  2188.  
  2189.  
  2190. &lt;h4 class=&quot;wp-block-heading&quot; id=&quot;error-failed-instance-creation-failed-creating-instance-record-add-instance-info-to-the-database-failed-to-create-instances-entry-unique-constraint-failed-instancesprojectid-instancesname&quot;&gt;Error: Failed instance creation: Failed creating instance record: Add instance info to the database: Failed to create “instances” entry: UNIQUE constraint failed: instances.project_id, instances.name&lt;/h4&gt;
  2191.  
  2192.  
  2193. &lt;p&gt;This error message is a bit cryptic. It just means that you are trying to create or launch an instance while the instance already exists. Read as &lt;em&gt;&lt;strong&gt;Error: The instance name already exists&lt;/strong&gt;&lt;/em&gt;.&lt;/p&gt;
  2194.  
  2195.  
  2196.  
  2197. &lt;p&gt;&lt;/p&gt;
  2198. &lt;div class=&quot;saboxplugin-wrap&quot;&gt;&lt;div class=&quot;saboxplugin-tab&quot;&gt;&lt;div class=&quot;saboxplugin-gravatar&quot;&gt;&lt;img alt=&quot;Simos Xenitellis&quot; class=&quot;avatar avatar-100 photo&quot; height=&quot;100&quot; src=&quot;https://secure.gravatar.com/avatar/fadb0e15964fa5c57144f8b9bccf3985281d04e3817a69d0885c0b911d66c59d?s=100&amp;amp;d=wavatar&amp;amp;r=g&quot; width=&quot;100&quot; /&gt;&lt;/div&gt;&lt;div class=&quot;saboxplugin-authorname&quot;&gt;&lt;a class=&quot;vcard author&quot; href=&quot;https://blog.simos.info/author/simos/&quot; rel=&quot;author&quot;&gt;&lt;span class=&quot;fn&quot;&gt;Simos Xenitellis&lt;/span&gt;&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;saboxplugin-desc&quot;&gt;&lt;div&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;saboxplugin-web &quot;&gt;&lt;a href=&quot;https://blog.simos.info/&quot; target=&quot;_self&quot;&gt;blog.simos.info/&lt;/a&gt;&lt;/div&gt;&lt;div class=&quot;clearfix&quot;&gt;&lt;/div&gt;&lt;/div&gt;&lt;/div&gt;</description>
  2199. <pubDate>Thu, 01 May 2025 22:51:53 +0000</pubDate>
  2200. </item>
  2201. <item>
  2202. <title>Scarlett Gately Moore: KDE Snaps and life. Spirits are up, but I need a little help please</title>
  2203. <guid isPermaLink="false">https://www.scarlettgatelymoore.dev/?p=1891</guid>
  2204. <link>https://www.scarlettgatelymoore.dev/kde-snaps-and-life-spirits-are-up-but-i-need-a-little-help-please/</link>
  2205. <description>&lt;figure class=&quot;wp-block-image size-large&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-1892&quot; height=&quot;1024&quot; src=&quot;https://www.scarlettgatelymoore.dev/wp-content/uploads/20250425_091105-768x1024.jpg&quot; width=&quot;768&quot; /&gt;&lt;/figure&gt;
  2206.  
  2207.  
  2208.  
  2209. &lt;p&gt;I was just released from the hospital after a 3 day stay for my ( hopefully ) last surgery. There was concern with massive blood loss and low heart rate. I have stabilized and have come home. Unfortunately, they had to prescribe many medications this round and they are extremely expensive and used up all my funds. I need gas money to get to my post-op doctors appointments, and food would be cool. I would appreciate any help, even just a dollar!&lt;/p&gt;
  2210.  
  2211.  
  2212.  
  2213. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2214. &lt;li&gt;&lt;a href=&quot;https://gofund.me/561ae227&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;GoFundMe&lt;/a&gt;&lt;/li&gt;
  2215.  
  2216.  
  2217.  
  2218. &lt;li&gt;&lt;a href=&quot;https://www.patreon.com/c/sgmoore&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Patreon&lt;/a&gt;&lt;/li&gt;
  2219.  
  2220.  
  2221.  
  2222. &lt;li&gt;&lt;a href=&quot;https://github.com/sponsors/ScarlettGatelyMoore?o=sd&amp;amp;sc=t&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Github&lt;/a&gt;&lt;/li&gt;
  2223.  
  2224.  
  2225.  
  2226. &lt;li&gt;&lt;a href=&quot;https://donorbox.org/open-source-survival-fund&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;Donorbox&lt;/a&gt;&lt;/li&gt;
  2227. &lt;/ul&gt;
  2228.  
  2229.  
  2230.  
  2231. &lt;p&gt;I am already back to work, and continued work on the crashy KDE snaps in a non KDE env. ( Also affects anyone using kde-neon extensions such as FreeCAD) I hope to have a fix in the next day or so.&lt;/p&gt;
  2232.  
  2233.  
  2234.  
  2235. &lt;p&gt;Fixed kate bug &lt;a href=&quot;https://bugs.kde.org/show_bug.cgi?id=503285&quot;&gt;https://bugs.kde.org/show_bug.cgi?id=503285&lt;/a&gt;&lt;/p&gt;
  2236.  
  2237.  
  2238.  
  2239. &lt;p&gt;Thanks for stopping by.&lt;/p&gt;</description>
  2240. <pubDate>Mon, 28 Apr 2025 13:04:09 +0000</pubDate>
  2241. </item>
  2242. <item>
  2243. <title>St&amp;eacute;phane Graber: Announcing Incus 6.12</title>
  2244. <guid isPermaLink="false">https://stgraber.org/?p=1733</guid>
  2245. <link>https://stgraber.org/2025/04/25/announcing-incus-6-12/</link>
  2246. <description>&lt;p&gt;The Incus team is pleased to announce the release of Incus 6.12!&lt;/p&gt;
  2247.  
  2248.  
  2249.  
  2250. &lt;p&gt;This release comes with some very long awaited improvements such as online growth of virtual machine memory, network address sets for easier network ACLs, revamped logging support and more!&lt;/p&gt;
  2251.  
  2252.  
  2253.  
  2254. &lt;p&gt;On top of the new features, this release also features quite a few welcome performance improvements, especially for systems with a lot of snapshots and with extra performance enhancements for those using ZFS.&lt;/p&gt;
  2255.  
  2256.  
  2257.  
  2258. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;a href=&quot;https://stgraber.org/wp-content/uploads/2025/04/image.png&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-1734&quot; height=&quot;330&quot; src=&quot;https://stgraber.org/wp-content/uploads/2025/04/image.png&quot; width=&quot;751&quot; /&gt;&lt;/a&gt;&lt;/figure&gt;
  2259.  
  2260.  
  2261.  
  2262. &lt;p&gt;The highlights for this release are:&lt;/p&gt;
  2263.  
  2264.  
  2265.  
  2266. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2267. &lt;li&gt;Network address sets&lt;/li&gt;
  2268.  
  2269.  
  2270.  
  2271. &lt;li&gt;Memory hotplug support in VMs&lt;/li&gt;
  2272.  
  2273.  
  2274.  
  2275. &lt;li&gt;Reworked logging handling &amp;amp; remote syslog&lt;/li&gt;
  2276.  
  2277.  
  2278.  
  2279. &lt;li&gt;SNAT support on complex network forwards&lt;/li&gt;
  2280.  
  2281.  
  2282.  
  2283. &lt;li&gt;Authentication through access_token parameter&lt;/li&gt;
  2284.  
  2285.  
  2286.  
  2287. &lt;li&gt;Improved server-side filtering in the CLI&lt;/li&gt;
  2288.  
  2289.  
  2290.  
  2291. &lt;li&gt;More generated documentation&lt;/li&gt;
  2292. &lt;/ul&gt;
  2293.  
  2294.  
  2295.  
  2296. &lt;p&gt;The full announcement and changelog can be &lt;a href=&quot;https://discuss.linuxcontainers.org/t/incus-6-12-has-been-released/23556&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;found here&lt;/a&gt;.&lt;br /&gt;And for those who prefer videos, here’s the release overview video:&lt;/p&gt;
  2297.  
  2298.  
  2299.  
  2300. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  2301.  
  2302. &lt;/div&gt;&lt;/figure&gt;
  2303.  
  2304.  
  2305.  
  2306. &lt;p&gt;You can take the latest release of Incus up for a spin through our online demo service at: &lt;a href=&quot;https://linuxcontainers.org/incus/try-it/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;https://linuxcontainers.org/incus/try-it/&lt;/a&gt;&lt;/p&gt;
  2307.  
  2308.  
  2309.  
  2310. &lt;p&gt;And as always, my company is offering commercial support on Incus, ranging from by-the-hour support contracts to one-off services on things like initial migration from LXD, review of your deployment to squeeze the most out of Incus or even feature sponsorship. You’ll find all details of that here: &lt;a href=&quot;https://zabbly.com/incus&quot;&gt;https://zabbly.com/incus&lt;/a&gt;&lt;/p&gt;
  2311.  
  2312.  
  2313.  
  2314. &lt;p&gt;Donations towards my work on this and other open source projects is also always appreciated, you can  find me on &lt;a href=&quot;https://github.com/sponsors/stgraber&quot;&gt;Github Sponsors&lt;/a&gt;, &lt;a href=&quot;https://patreon.com/stgraber&quot;&gt;Patreon&lt;/a&gt; and &lt;a href=&quot;https://ko-fi.com/stgraber&quot;&gt;Ko-fi&lt;/a&gt;.&lt;/p&gt;
  2315.  
  2316.  
  2317.  
  2318. &lt;p&gt;Enjoy!&lt;/p&gt;
  2319.  
  2320.  
  2321. &lt;p&gt;&lt;/p&gt;</description>
  2322. <pubDate>Fri, 25 Apr 2025 04:05:05 +0000</pubDate>
  2323. </item>
  2324. <item>
  2325. <title>Ubuntu MATE: Ubuntu MATE 25.04 Release Notes</title>
  2326. <guid isPermaLink="false">https://ubuntu-mate.org/blog/ubuntu-mate-plucky-puffin</guid>
  2327. <link>https://ubuntu-mate.org/blog/ubuntu-mate-plucky-puffin-release-notes/</link>
  2328. <description>&lt;p&gt;Ubuntu MATE 25.04 is ready to soar! 🪽 Celebrating our 10th anniversary as an official Ubuntu flavour with the reliable MATE Desktop experience you love, built on the latest Ubuntu foundations. Read on to learn more 👓️&lt;/p&gt;
  2329.  
  2330. &lt;h2 id=&quot;a-decade-of-mate&quot;&gt;A Decade of MATE&lt;/h2&gt;
  2331.  
  2332. &lt;p&gt;This release marks the 10th anniversary of Ubuntu MATE becoming an official Ubuntu flavour. From our humble beginnings, we’ve developed a loyal following of users who value a traditional desktop experience with modern capabilities. Thanks to our amazing community, contributors, and users who have been with us throughout this journey. Here’s to many more years of Ubuntu MATE! 🥂&lt;/p&gt;
  2333.  
  2334. &lt;h2 id=&quot;what-changed-in-ubuntu-mate-2504&quot;&gt;What changed in Ubuntu MATE 25.04?&lt;/h2&gt;
  2335.  
  2336. &lt;p&gt;Here are the highlights of what’s new in the Plucky Puffin release:&lt;/p&gt;
  2337.  
  2338. &lt;ul&gt;
  2339.  &lt;li&gt;Celebrating 10 years as an official Ubuntu flavour! 🎂&lt;/li&gt;
  2340.  &lt;li&gt;Optional full disk encryption in the installer 🔐
  2341.    &lt;ul&gt;
  2342.      &lt;li&gt;Enhanced advanced partitioning options&lt;/li&gt;
  2343.      &lt;li&gt;Better interaction with existing BitLocker-enabled Windows installations&lt;/li&gt;
  2344.      &lt;li&gt;Improved experience when installing alongside other operating systems&lt;/li&gt;
  2345.    &lt;/ul&gt;
  2346.  &lt;/li&gt;
  2347. &lt;/ul&gt;
  2348.  
  2349. &lt;h2 id=&quot;major-applications&quot;&gt;Major Applications&lt;/h2&gt;
  2350.  
  2351. &lt;p&gt;Accompanying &lt;strong&gt;MATE Desktop&lt;/strong&gt; 🧉 and &lt;strong&gt;Linux 6.14&lt;/strong&gt; 🐧 are &lt;strong&gt;Firefox 137&lt;/strong&gt; 🔥🦊,
  2352. &lt;strong&gt;Evolution 3.56&lt;/strong&gt; 📧, &lt;strong&gt;LibreOffice 25.2.2&lt;/strong&gt; 📚&lt;/p&gt;
  2353.  
  2354. &lt;p&gt;See the &lt;a href=&quot;https://discourse.ubuntu.com/t/plucky-puffin-release-notes/48687&quot;&gt;Ubuntu 25.04 Release Notes&lt;/a&gt;
  2355. for details of all the changes and improvements that Ubuntu MATE benefits from.&lt;/p&gt;
  2356.  
  2357. &lt;div class=&quot;jumbotron&quot;&gt;
  2358.  
  2359.    &lt;h2&gt;Download Ubuntu MATE 25.04&lt;/h2&gt;
  2360.  
  2361.    &lt;p&gt;Available for 64-bit desktop computers!&lt;/p&gt;
  2362.  
  2363.  
  2364.    
  2365.        &lt;a class=&quot;btn&quot; href=&quot;https://ubuntu-mate.org/download/&quot;&gt;Download&lt;/a&gt;
  2366.    
  2367.  
  2368. &lt;/div&gt;
  2369.  
  2370. &lt;h2 id=&quot;upgrading-to-ubuntu-mate-2504&quot;&gt;Upgrading to Ubuntu MATE 25.04&lt;/h2&gt;
  2371.  
  2372. &lt;p&gt;The upgrade process to Ubuntu MATE 25.04 is the same as Ubuntu.&lt;/p&gt;
  2373.  
  2374. &lt;ul&gt;
  2375.  &lt;li&gt;&lt;a href=&quot;https://help.ubuntu.com/community/PluckyUpgrades&quot;&gt;Ubuntu 25.04 Upgrade Process&lt;/a&gt;&lt;/li&gt;
  2376. &lt;/ul&gt;
  2377.  
  2378. &lt;p&gt;There are no offline upgrade options for Ubuntu MATE. Please ensure you have
  2379. network connectivity to one of the official mirrors or to a locally accessible
  2380. mirror and follow the instructions above.&lt;/p&gt;</description>
  2381. <pubDate>Sat, 19 Apr 2025 04:48:24 +0000</pubDate>
  2382. </item>
  2383. <item>
  2384. <title>Xubuntu: Xubuntu 25.04 released!</title>
  2385. <guid isPermaLink="false">https://xubuntu.org/?p=5647</guid>
  2386. <link>https://xubuntu.org/news/xubuntu-25-04-released/</link>
  2387. <description>&lt;p&gt;The Xubuntu team is happy to announce the immediate release of Xubuntu 25.04.&lt;/p&gt;
  2388.  
  2389.  
  2390.  
  2391. &lt;p&gt;Xubuntu 25.04, codenamed &lt;strong&gt;Plucky Puffin&lt;/strong&gt;, is a regular release and will be supported for 9 months, until January 2026.&lt;/p&gt;
  2392.  
  2393.  
  2394.  
  2395. &lt;figure class=&quot;wp-block-image size-full&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-5648&quot; height=&quot;800&quot; src=&quot;https://xubuntu.org/wp-content/uploads/2025/04/2e04/xubuntu-25.04.png&quot; width=&quot;1280&quot; /&gt;Xubuntu 25.04, featuring the latest updates from Xfce 4.20 and GNOME 48.&lt;/figure&gt;
  2396.  
  2397.  
  2398.  
  2399. &lt;p&gt;Xubuntu 25.04 features the latest Xfce 4.20, GNOME 48, and MATE 1.26 updates. &lt;strong&gt;Xfce 4.20&lt;/strong&gt; features many bug fixes and minor improvements, modernizing the Xubuntu desktop while maintaining a familiar look and feel. &lt;strong&gt;GNOME 48&lt;/strong&gt; apps are tightly integrated and have full support for dark mode. Users of &lt;strong&gt;QEMU and KVM&lt;/strong&gt; will be delighted to find new stability with the desktop session—the long-running &lt;a href=&quot;https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1861609&quot;&gt;X server crash&lt;/a&gt; has been resolved in Xubuntu 25.04 and backported to all supported Xubuntu releases.&lt;/p&gt;
  2400.  
  2401.  
  2402.  
  2403. &lt;p&gt;The &lt;strong&gt;final release images&lt;/strong&gt; for &lt;strong&gt;Xubuntu Desktop&lt;/strong&gt; and &lt;strong&gt;Xubuntu Minimal&lt;/strong&gt; are available as torrents and direct downloads from &lt;a href=&quot;https://xubuntu.org/download/&quot;&gt;xubuntu.org/download/&lt;/a&gt;.&lt;/p&gt;
  2404.  
  2405.  
  2406.  
  2407. &lt;p&gt;As the main server might be busy the first few days after the release, we recommend using the torrents if possible.&lt;/p&gt;
  2408.  
  2409.  
  2410.  
  2411. &lt;p&gt;We want to thank everybody who contributed to this release of Xubuntu!&lt;/p&gt;
  2412.  
  2413.  
  2414.  
  2415. &lt;h2&gt;Highlights and Known Issues&lt;/h2&gt;
  2416.  
  2417.  
  2418.  
  2419. &lt;h3&gt;Highlights&lt;/h3&gt;
  2420.  
  2421.  
  2422.  
  2423. &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Xfce 4.20&lt;/strong&gt;, released in December 2024, is included and contains many new features. Early Wayland support has been added, but is not available in Xubuntu.&lt;/li&gt;&lt;li&gt;&lt;strong&gt;GNOME 48&lt;/strong&gt; apps, including &lt;em&gt;Font Viewer&lt;/em&gt; (gnome-font-viewer) and &lt;em&gt;Mines&lt;/em&gt; (gnome-mines), include a refreshed appearance and usability improvements.&lt;/li&gt;&lt;/ul&gt;
  2424.  
  2425.  
  2426.  
  2427. &lt;h3&gt;Known Issues&lt;/h3&gt;
  2428.  
  2429.  
  2430.  
  2431. &lt;ul&gt;&lt;li&gt;The shutdown prompt may not be displayed at the end of the installation. Instead, you might just see a Xubuntu logo, a black screen with an underscore in the upper left-hand corner, or a black screen. Press Enter, and the system will reboot into the installed environment. (LP: &lt;a href=&quot;https://bugs.launchpad.net/ubuntu-release-notes/+bug/1944519&quot;&gt;#1944519&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;You may experience choppy audio or poor system performance while playing audio, but only in some virtual machines (observed in VMware and VirtualBox).&lt;/li&gt;&lt;li&gt;OEM installation options are not currently supported or available.&lt;/li&gt;&lt;/ul&gt;
  2432.  
  2433.  
  2434.  
  2435. &lt;p&gt;Please refer to the &lt;a href=&quot;https://wiki.xubuntu.org/releases/25.04/release-notes&quot;&gt;Xubuntu Release Notes&lt;/a&gt; for more obscure known issues, information on affecting bugs, bug fixes, and a list of new package versions.&lt;/p&gt;
  2436.  
  2437.  
  2438.  
  2439. &lt;p&gt;The main &lt;a href=&quot;https://discourse.ubuntu.com/t/plucky-puffin-release-notes/48687&quot;&gt;Ubuntu Release Notes&lt;/a&gt; cover many other packages we carry and more generic issues.&lt;/p&gt;
  2440.  
  2441.  
  2442.  
  2443. &lt;h2&gt;Support&lt;/h2&gt;
  2444.  
  2445.  
  2446.  
  2447. &lt;p&gt;&lt;strong&gt;For support&lt;/strong&gt; with the release, navigate to &lt;a href=&quot;https://xubuntu.org/help/&quot;&gt;Help &amp;amp; Support&lt;/a&gt; for a complete list of methods to get help.&lt;/p&gt;</description>
  2448. <pubDate>Thu, 17 Apr 2025 20:59:18 +0000</pubDate>
  2449. </item>
  2450. <item>
  2451. <title>Lubuntu Blog: Lubuntu 25.04 (Plucky Puffin) Released!</title>
  2452. <guid isPermaLink="false">https://lubuntu.me/?p=4126</guid>
  2453. <link>https://lubuntu.me/plucky-released/</link>
  2454. <description>The Lubuntu Team is proud to announce Lubuntu 25.04, codenamed Plucky Puffin. Lubuntu 25.04 is the 28th release of Lubuntu, the 14th release of Lubuntu with LXQt as the default desktop environment. With 25.04 being an interim release, it will be supported until January of 2026. If you're a 24.10 user, please upgrade to 25.04 […]</description>
  2455. <pubDate>Thu, 17 Apr 2025 18:27:20 +0000</pubDate>
  2456. </item>
  2457. <item>
  2458. <title>Ubuntu Studio: Ubuntu Studio 25.04 Released</title>
  2459. <guid isPermaLink="false">https://ubuntustudio.org/?p=2980</guid>
  2460. <link>https://ubuntustudio.org/2025/04/ubuntu-studio-25-04-released/</link>
  2461. <description>&lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;aligncenter size-full is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-2981&quot; height=&quot;223&quot; src=&quot;https://ubuntustudio.org/wp-content/uploads/2025/04/6c42/finalbanner.png&quot; width=&quot;600&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2462.  
  2463.  
  2464.  
  2465. &lt;p id=&quot;block-08eb94aa-8521-4ed2-adb1-72f6f4094411&quot;&gt;The Ubuntu Studio team is pleased to announce the release of Ubuntu Studio 25.04 code-named “Plucky Puffin”. This marks Ubuntu Studio’s 36th release. This release is a Regular release and as such, it is supported for 9 months, until January 2026.&lt;/p&gt;
  2466.  
  2467.  
  2468.  
  2469. &lt;p id=&quot;block-895e2f57-e719-450c-a4c8-9405017a7e75&quot;&gt;Since it’s just out, you may experience some issues, so you might want to wait a bit before upgrading. Please see the &lt;a href=&quot;https://discourse.ubuntu.com/t/ubuntu-studio-25-04-release-notes/53099&quot;&gt;release notes&lt;/a&gt; for a more complete list of changes and known issues. Listed here are some of the major highlights.&lt;/p&gt;
  2470.  
  2471.  
  2472.  
  2473. &lt;p&gt;&lt;em&gt;This release is dedicated to the memory of &lt;a href=&quot;https://discourse.ubuntu.com/t/remembering-and-thanking-steve-langasek/52665&quot;&gt;Steve Langasek&lt;/a&gt;. Without Steve, Ubuntu Studio would not be where it is today. He provided invaluable guidance, insight, and instruction to our leader, Erich Eickmeyer, who not only learned how to package applications but learned how to do it properly. We owe him an eternal debt of gratitude.&lt;/em&gt;&lt;/p&gt;
  2474.  
  2475.  
  2476.  
  2477. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;aligncenter size-full is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-2990&quot; height=&quot;405&quot; src=&quot;https://ubuntustudio.org/wp-content/uploads/2025/04/f9e4/UbuntuStudio25.04small.png&quot; width=&quot;720&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2478.  
  2479.  
  2480.  
  2481. &lt;p id=&quot;block-aef9a406-e305-4f97-a130-f522c2f1ce7e&quot;&gt;You can download Ubuntu Studio 25.04 from our &lt;a href=&quot;https://ubuntustudio.org/download&quot;&gt;download page&lt;/a&gt;.&lt;/p&gt;
  2482.  
  2483.  
  2484.  
  2485. &lt;h2 id=&quot;block-6ca66e3a-8d42-42a8-a0cf-a8ed86e6025f&quot;&gt;Special Notes&lt;/h2&gt;
  2486.  
  2487.  
  2488.  
  2489. &lt;p id=&quot;block-708043b1-523e-4fb9-92ca-720e3316371a&quot;&gt;The Ubuntu Studio 25.04 disk image (ISO) exceeds 4 GB and cannot be downloaded to some file systems such as FAT32 and may not be readable when burned to a standard DVD. For this reason, we recommend downloading to a compatible file system. When creating a boot medium, we recommend &lt;a href=&quot;https://ubuntu.com/tutorials/create-a-usb-stick-on-ubuntu#1-overview&quot;&gt;creating a bootable USB stick&lt;/a&gt; with the ISO image or burning to a Dual-Layer DVD.&lt;/p&gt;
  2490.  
  2491.  
  2492.  
  2493. &lt;p&gt;Minimum installation media requirements: Dual-Layer DVD or 8GB USB drive.&lt;/p&gt;
  2494.  
  2495.  
  2496.  
  2497. &lt;p id=&quot;block-fa4be379-b904-4919-9502-c73469ca31ef&quot;&gt;Images can be obtained from this link: &lt;a href=&quot;https://cdimage.ubuntu.com/ubuntustudio/releases/25.04/release/&quot; rel=&quot;noreferrer noopener&quot; target=&quot;_blank&quot;&gt;https://cdimage.ubuntu.com/ubuntustudio/releases/25.04/release/&lt;/a&gt;&lt;/p&gt;
  2498.  
  2499.  
  2500.  
  2501. &lt;p id=&quot;block-bf39c734-e080-4549-9621-044e9241d48c&quot;&gt;Full updated information, including &lt;strong&gt;Upgrade Instructions,&lt;/strong&gt; are available in the &lt;strong&gt;&lt;a href=&quot;https://discourse.ubuntu.com/t/ubuntu-studio-25-04-release-notes/53099&quot;&gt;Release Notes&lt;/a&gt;&lt;/strong&gt;&lt;a href=&quot;https://wiki.ubuntu.com/GroovyGorilla/Beta/UbuntuStudio&quot;&gt;.&lt;/a&gt;&lt;/p&gt;
  2502.  
  2503.  
  2504.  
  2505. &lt;p&gt;Upgrades from 24.10 should be enabled within a month after release, so we appreciate your patience. Upgrades from 25.04 LTS will be enabled after 24.10 reaches End-Of-Life in July 2025.&lt;/p&gt;
  2506.  
  2507.  
  2508.  
  2509. &lt;h2&gt;New This Release&lt;/h2&gt;
  2510.  
  2511.  
  2512.  
  2513. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignright is-resized&quot;&gt;&lt;img alt=&quot;GIMP 3.0: Wilber logo by Aryeom&quot; height=&quot;100&quot; src=&quot;https://www.gimp.org/images/frontpage/wilber-big.png&quot; width=&quot;100&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2514.  
  2515.  
  2516.  
  2517. &lt;h3&gt;GIMP 3.0!&lt;/h3&gt;
  2518.  
  2519.  
  2520.  
  2521. &lt;p&gt;The long-awaited GIMP 3.0 is included by default. GIMP is now capable of non-destructive editing with filters, better Photoshop PSD export, and so very much more! Check out the &lt;a href=&quot;https://www.gimp.org/news/2025/03/16/gimp-3-0-released/&quot;&gt;GIMP 3.0 release announcement&lt;/a&gt; for more information.&lt;/p&gt;
  2522.  
  2523.  
  2524.  
  2525. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignright is-resized&quot;&gt;&lt;img alt=&quot;Pencil2D Icon&quot; height=&quot;128&quot; src=&quot;https://www.pencil2d.org/images/pencil_icon.png&quot; width=&quot;128&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2526.  
  2527.  
  2528.  
  2529. &lt;h3&gt;Pencil2D&lt;/h3&gt;
  2530.  
  2531.  
  2532.  
  2533. &lt;p&gt;Ubuntu Studio now includes &lt;strong&gt;&lt;a data-id=&quot;pencil2d.org&quot; data-type=&quot;URL&quot; href=&quot;http://pencil2d.org&quot;&gt;Pencil2D&lt;/a&gt;&lt;/strong&gt;! This is a 2D animation and drawing application that is sure to be helpful to animators. You can use basic clipart to make animations!&lt;/p&gt;
  2534.  
  2535.  
  2536.  
  2537. &lt;p&gt;The basic features of Pencil2D are:&lt;/p&gt;
  2538.  
  2539.  
  2540.  
  2541. &lt;ul&gt;&lt;li&gt;layers support (separated layer for bitmap, vector and soud part)&lt;/li&gt;&lt;li&gt;bitmap drawing&lt;/li&gt;&lt;li&gt;vector drawing&lt;/li&gt;&lt;li&gt;sound support&lt;/li&gt;&lt;/ul&gt;
  2542.  
  2543.  
  2544.  
  2545. &lt;h3&gt;LibreOffice No Longer in Minimal Install&lt;/h3&gt;
  2546.  
  2547.  
  2548.  
  2549. &lt;p&gt;The LibreOffice suite is now part of the full desktop install. This will save space for those wishing for a minimalistic setup for their needs.&lt;/p&gt;
  2550.  
  2551.  
  2552.  
  2553. &lt;h3&gt;Invada Studio Plugins&lt;/h3&gt;
  2554.  
  2555.  
  2556.  
  2557. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignright size-full&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-2983&quot; height=&quot;61&quot; src=&quot;https://ubuntustudio.org/wp-content/uploads/2025/04/47bb/invada-logo1.png&quot; width=&quot;183&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2558.  
  2559.  
  2560.  
  2561. &lt;p&gt;Beginning this release we are including the Invada Studio Plugins first created by Invada Records Australia. This includes distortion, delay, dynamics, filter, phaser, reverb, and utility audio plugins.&lt;/p&gt;
  2562.  
  2563.  
  2564.  
  2565. &lt;h3&gt;PipeWire 1.2.7&lt;/h3&gt;
  2566.  
  2567.  
  2568.  
  2569. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignright size-full is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-2766&quot; height=&quot;70&quot; src=&quot;https://ubuntustudio.org/wp-content/uploads/2024/04/be34/Pipewire_logo.svg_.png&quot; width=&quot;324&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2570.  
  2571.  
  2572.  
  2573. &lt;p&gt;This release contains &lt;strong&gt;PipeWire 1.2.7&lt;/strong&gt;. One major feature this has over 1.2.4 is that &lt;code&gt;v4l2loopback&lt;/code&gt; support is available via the &lt;code&gt;pipewire-v4l2&lt;/code&gt; package which is not installed by default.&lt;/p&gt;
  2574.  
  2575.  
  2576.  
  2577. &lt;p&gt;PipeWire’s JACK compatibility is configured to use out-of-the-box and is zero-latency internally. System latency is configurable via &lt;a data-id=&quot;2797&quot; data-type=&quot;page&quot; href=&quot;https://ubuntustudio.org/audio-configuration/&quot;&gt;Ubuntu Studio Audio Configuration&lt;/a&gt;.&lt;/p&gt;
  2578.  
  2579.  
  2580.  
  2581. &lt;p&gt;However, if you would rather use straight JACK 2 instead, that’s also possible. Ubuntu Studio Audio Configuration can disable and enable PipeWire’s JACK compatibility on-the-fly. From there, you can simply use JACK via QJackCtl.&lt;/p&gt;
  2582.  
  2583.  
  2584.  
  2585. &lt;h3&gt;Ardour 8.12&lt;/h3&gt;
  2586.  
  2587.  
  2588.  
  2589. &lt;div class=&quot;wp-block-image&quot;&gt;&lt;figure class=&quot;alignright size-full is-resized&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-1977&quot; height=&quot;73&quot; src=&quot;https://ubuntustudio.org/wp-content/uploads/2020/06/2a76/ardour.png&quot; width=&quot;84&quot; /&gt;&lt;/figure&gt;&lt;/div&gt;
  2590.  
  2591.  
  2592.  
  2593. &lt;p&gt;This is, as of this writing, the latest release of Ardour, packed with the latest bugfixes.&lt;/p&gt;
  2594.  
  2595.  
  2596.  
  2597. &lt;p&gt;To help support Ardour’s funding, you may obtain later versions directly from ardour.org. To do so, please &lt;a data-id=&quot;https://ardour.org&quot; data-type=&quot;URL&quot; href=&quot;https://ardour.org&quot;&gt;one-time purchase or subscribe to Ardour from their website.&lt;/a&gt; If you wish to get later versions of Ardour from us, you will have to wait until the next regular release of Ubuntu Studio, due in October 2025.&lt;/p&gt;
  2598.  
  2599.  
  2600.  
  2601. &lt;h2&gt;Deprecation of Mailing Lists&lt;/h2&gt;
  2602.  
  2603.  
  2604.  
  2605. &lt;p&gt;Our mailing lists are getting inundated with spam and there is no proper way to fix the filtering. It uses an outdated version of MailMan, so this release announcement will be the last release announcement we send out via email. To get support, we encourage using &lt;a data-id=&quot;https://discourse.ubuntu.com&quot; data-type=&quot;URL&quot; href=&quot;https://discourse.ubuntu.com&quot;&gt;Ubuntu Discourse&lt;/a&gt; for support, and for community clicking the notification bell in the &lt;a href=&quot;https://discourse.ubuntu.com/c/flavors/ubuntustudio/188&quot;&gt;Ubuntu Studio category&lt;/a&gt; there.&lt;/p&gt;
  2606.  
  2607.  
  2608.  
  2609. &lt;h2 id=&quot;block-c7a21be7-9349-421e-a098-c0d2919f320a&quot;&gt;Frequently Asked Questions&lt;/h2&gt;
  2610.  
  2611.  
  2612.  
  2613. &lt;p id=&quot;block-163f794a-f451-40b0-bbbd-6f26c6cbe8e8&quot;&gt;&lt;strong&gt;Q:&lt;/strong&gt; Does Ubuntu Studio contain snaps?&lt;br /&gt;&lt;strong&gt;A:&lt;/strong&gt; Yes. Mozilla’s distribution agreement with Canonical changed, and Ubuntu was forced to no longer distribute Firefox in a native .deb package. We have found that, after numerous improvements, Firefox now performs just as well as the native .deb package did.&lt;/p&gt;
  2614.  
  2615.  
  2616.  
  2617. &lt;p&gt;Thunderbird also became a snap so that the maintainers can get security patches delivered faster.&lt;/p&gt;
  2618.  
  2619.  
  2620.  
  2621. &lt;p id=&quot;block-342134d3-a024-4b7b-b768-76c758b20acd&quot;&gt;Additionally, Freeshow is an Electron-based application. Electron-based applications cannot be packaged in the Ubuntu repositories in that they cannot be packaged in a traditional Debian source package. While such apps do have a build system to create a .deb binary package, it circumvents the source package build system in Launchpad, which is required when packaging for Ubuntu. However, Electron apps also have a facility for creating snaps, which can be uploaded and included. Therefore, for Freeshow to be included in Ubuntu Studio, it had to be packaged as a snap.&lt;/p&gt;
  2622.  
  2623.  
  2624.  
  2625. &lt;p&gt;We have additional snaps that are Ubuntu-specific, such as the Firmware Updater and the Security Center. Contrary to popular myth, Ubuntu does not have any plans to switch all packages to snaps, nor do we.&lt;/p&gt;
  2626.  
  2627.  
  2628.  
  2629. &lt;p id=&quot;block-2266cee7-0ea1-49cf-8340-594da42a09d7&quot;&gt;&lt;strong&gt;Q&lt;/strong&gt;: Will you make an ISO with {my favorite desktop environment}?&lt;br /&gt;&lt;strong&gt;A:&lt;/strong&gt; To do so would require creating an entirely new flavor of Ubuntu, which would require going through the Official Ubuntu Flavor application process. Since we’re completely volunteer-run, we don’t have the time or resources to do this. Instead, we recommend you download the &lt;a href=&quot;https://ubuntu.com/download/flavours&quot;&gt;official flavor for the desktop environment of your choice&lt;/a&gt; and use &lt;a href=&quot;https://ubuntustudio.org/ubuntu-studio-installer&quot;&gt;Ubuntu Studio Installer&lt;/a&gt; to get Ubuntu Studio – which does *not* convert that flavor to Ubuntu Studio but adds its benefits.&lt;/p&gt;
  2630.  
  2631.  
  2632.  
  2633. &lt;p id=&quot;block-48669a69-39bc-4971-b46b-c7da87133d24&quot;&gt;&lt;strong&gt;Q: &lt;/strong&gt;What if I don’t want all these packages installed on my machine?&lt;br /&gt;&lt;strong&gt;A: &lt;/strong&gt;Simply use the &lt;strong&gt;Ubuntu Studio Installer&lt;/strong&gt; to remove the features of Ubuntu Studio you don’t want or need!&lt;/p&gt;
  2634.  
  2635.  
  2636.  
  2637. &lt;h2&gt;Get Involved!&lt;/h2&gt;
  2638.  
  2639.  
  2640.  
  2641. &lt;p&gt;A wonderful way to contribute is to get involved with the project directly! We’re always looking for new volunteers to help with packaging, documentation, tutorials, user support, and MORE! &lt;a href=&quot;https://ubuntustudio.org/contribute/&quot;&gt;Check out all the ways you can contribute!&lt;/a&gt;&lt;/p&gt;
  2642.  
  2643.  
  2644.  
  2645. &lt;p&gt;&lt;strong&gt;Our project leader, Erich Eickmeyer, is now working on Ubuntu Studio at least part-time, and is hoping that the users of Ubuntu Studio can give enough to generate a monthly part-time income. We’re not there, but if every Ubuntu Studio user donated monthly, we’d be there! Your donations are appreciated! If other distributions can do it, surely we can! See the sidebar for ways to give&lt;/strong&gt;!&lt;/p&gt;
  2646.  
  2647.  
  2648.  
  2649. &lt;h2&gt;Special Thanks&lt;/h2&gt;
  2650.  
  2651.  
  2652.  
  2653. &lt;p&gt;Huge special thanks for this release go to:&lt;/p&gt;
  2654.  
  2655.  
  2656.  
  2657. &lt;ul&gt;&lt;li&gt;&lt;strong&gt;Eylul Dogruel&lt;/strong&gt;: Artwork, Graphics Design&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Ross Gammon&lt;/strong&gt;: Upstream Debian Developer, Testing, Email Support&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Sebastien Ramacher&lt;/strong&gt;:&lt;strong&gt; &lt;/strong&gt;Upstream Debian Developer&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Dennis Braun&lt;/strong&gt;: Upstream Debian Developer&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Rik Mills&lt;/strong&gt;: Kubuntu Council Member, help with Plasma desktop&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Scarlett Moore: &lt;/strong&gt;Kubuntu Project Lead, help with Plasma desktop&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Len Ovens:&lt;/strong&gt; Testing, insight&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Mauro Gaspari&lt;/strong&gt;: Tutorials, Promotion, and Documentation, Testing, keeping Erich sane&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Simon Quigley: &lt;/strong&gt;Qt6 Megastuff&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Erich Eickmeyer&lt;/strong&gt;: Project Leader, Packaging, Development, Direction, Treasurer&lt;/li&gt;&lt;li&gt;&lt;strong&gt;Steve Langasek: &lt;/strong&gt;You are missed.&lt;/li&gt;&lt;/ul&gt;</description>
  2658. <pubDate>Thu, 17 Apr 2025 17:08:25 +0000</pubDate>
  2659. </item>
  2660. <item>
  2661. <title>Stuart Langridge: Serving streaming video that adapts to bandwidth from your own website</title>
  2662. <guid isPermaLink="false">tag:www.kryogenix.org,2025-04-16:/days/2025/04/16/serving-streaming-video-that-adapts-to-bandwidth-from-your-own-website/</guid>
  2663. <link>https://www.kryogenix.org/days/2025/04/16/serving-streaming-video-that-adapts-to-bandwidth-from-your-own-website/</link>
  2664. <description>&lt;p&gt;Recently, I was involved in an event where a video was shown, and the event was filmed. It would be nice to put the video of the event up somewhere so other people who weren't there could watch it. Obvious answer: upload it to YouTube. However, the video that was shown &lt;em&gt;at&lt;/em&gt; the event is Copyrighted Media Content and therefore is disallowed by YouTube and the copyright holder; it's not demonetised (which wouldn't be a problem), it's flat-out blocked. So YouTube is out.&lt;/p&gt;
  2665. &lt;p&gt;I'd like the video I'm posting to stick around for a long time; this is a sort of archival, reference thing where not many people will ever want to watch it but those that do might want to do so in ten years. So I'm loath to find some other random video hosting site, which will probably go bust, or pivot to selling online AI shoes or something. And the best way to ensure that something keeps going long-term is to put it on your own website, and use decent HTML, because that means that even in ten or twenty years it'll still work where the latest flavour-of-the-month thing will go the way of other old technologies and fade away and stop working over time. HTML won't do that.&lt;/p&gt;
  2666. &lt;p&gt;But... it's an hour long and in full HD. 2.6GB of video. And one of the benefits of YouTube is that they'll make the video adaptive: it'll fit the screen, and the bandwidth, of whatever device someone's watching it on. If someone wants to look at this from their phone and its slightly-shaky two bars of 4G connection, they probably don't want to watch the loading spinner for an hour while it buffers a full HD video; they can ideally get a cut down, lower-quality but quicker to serve, version. But... how is this possible?&lt;/p&gt;
  2667. &lt;p&gt;There are two aspects to doing this. One is that you serve up different &lt;em&gt;resolutions&lt;/em&gt; of video, based on the viewer's screen size. This is exactly the same problem as is solved for images by the &lt;code&gt;&amp;lt;picture&amp;gt;&lt;/code&gt; element to provide responsive images (where if you're on a 400px-wide screen you get a 400px version of the background image, not the 2000px full-res version), and indeed the magic words to search for here are &lt;em&gt;responsive video&lt;/em&gt;. And the person you will find who is explaning all this is &lt;a href=&quot;https://bsky.app/profile/scottjehl.com&quot;&gt;Scott Jehl&lt;/a&gt;, who has written &lt;a href=&quot;https://scottjehl.com/posts/using-responsive-video/&quot;&gt;a good description of how to do responsive video&lt;/a&gt; which explains it all in detail. You make versions of the video at different resolutions, and serve whichever one best matches the screen you're on, just like responsive images. Nice work; just what the doctor ordered.&lt;/p&gt;
  2668. &lt;p&gt;But there's also a second aspect to this: responsive video adapts to screen size, but it doesn't adapt to bandwidth. What we want, in addition to the responsive stuff, is that on poor connections the viewer gets a lower-bandwidth version as well as a lower-resolution version, and that the viewer's browser can dynamically switch from moment to moment between different versions of the video to match their current network speed. This task is the job of &lt;a href=&quot;https://en.wikipedia.org/wiki/HTTP_Live_Streaming&quot;&gt;HTTP Live Streaming&lt;/a&gt;, or HLS. To do this, you essentially encode the video in a bunch of different qualities and screen sizes, so you've got a bunch of separate videos (which you've probably already done above for the responsive part) and then (and this is the key) you chop up each video into a load of small segments. That way, instead of the browser downloading the whole one hour of video at a particular resolution, it only downloads the next &lt;em&gt;segment&lt;/em&gt; at its current choice of resolution, and then if you suddenly get more (or less) bandwidth, it can switch to getting segment 2 from a &lt;em&gt;different&lt;/em&gt; version of the video which better matches where you currently are.&lt;/p&gt;
  2669. &lt;p&gt;Doing this sounds hard. Fortunately, all hard things to do with video are handled by ffmpeg. There's a nice writeup by Mux on &lt;a href=&quot;https://www.mux.com/articles/how-to-convert-mp4-to-hls-format-with-ffmpeg-a-step-by-step-guide&quot;&gt;how to convert an mp4 video to HLS with ffmpeg&lt;/a&gt;, and it works great. I put myself together a &lt;a href=&quot;https://gist.github.com/stuartlangridge/c0ae266306604c7db23e9855eea83976&quot;&gt;little Python script&lt;/a&gt; to construct the ffmpeg command line to do it, but you can do it yourself; the script just does some of the boilerplate for you. Very useful.&lt;/p&gt;
  2670. &lt;p&gt;So now I can serve up a video which adapts to the viewer's viewing conditions, and that's just what I wanted. I have to pay for the bandwidth now (which is the &lt;em&gt;other&lt;/em&gt; benefit of having YouTube do it, and one I now don't get) but that's worth it for this, I think. Cheers to Scott and Mux for explaining all this stuff.&lt;/p&gt;</description>
  2671. <pubDate>Wed, 16 Apr 2025 08:26:00 +0000</pubDate>
  2672. </item>
  2673. <item>
  2674. <title>David Mohammed: Ubuntu Budgie 25.04 release notes</title>
  2675. <guid isPermaLink="false">https://ubuntubudgie.org/?p=3898</guid>
  2676. <link>https://ubuntubudgie.org/2025/04/ubuntu-budgie-25-04-release-notes/</link>
  2677. <description>&lt;p&gt;Ubuntu Budgie 25.04 (Plucky Puffin) is a Standard Release with 9 months of support by your distro maintainers and Canonical, from April 2025 to Jan 2026. These release notes showcase the key takeaways for 24.10 upgraders to 25.04. Please note – there is no direct upgrade path from 24.04.2 to 25.04; you must uplift to 24.10 first or perform a fresh install. In these release notes the areas…&lt;/p&gt;
  2678. &lt;p&gt;&lt;a href=&quot;https://ubuntubudgie.org/2025/04/ubuntu-budgie-25-04-release-notes/&quot; rel=&quot;nofollow&quot;&gt;Source&lt;/a&gt;&lt;/p&gt;</description>
  2679. <pubDate>Tue, 15 Apr 2025 17:31:49 +0000</pubDate>
  2680. </item>
  2681. <item>
  2682. <title>Salih Emin: Git turns 20! : A conversation with creator Linus Torvalds</title>
  2683. <guid isPermaLink="false">https://utappiablog.wordpress.com/?p=49839</guid>
  2684. <link>https://utappia.org/2025/04/11/git-turns-20-a-conversation-with-creator-linus-torvalds/</link>
  2685. <description>&lt;p&gt;Watch a conversation reflecting on the 20th anniversary of Git, the version control system created by Linus Torvalds. He discusses his initial motivations for developing Git as a response to the limitations of existing systems like CVS and BitKeeper, and his desire to establish a better tool for the open-source community. &lt;/p&gt;
  2686.  
  2687.  
  2688.  
  2689. &lt;span id=&quot;more-49839&quot;&gt;&lt;/span&gt;
  2690.  
  2691.  
  2692.  
  2693. &lt;p&gt;Torvalds explains the processes involved in Git’s early development, including the challenges he faced and key decisions he made, like the choice to implement SHA-1 hashing for data integrity. He acknowledges the initial difficulty users experienced when transitioning from centralized systems to Git’s distributed model.&lt;/p&gt;
  2694.  
  2695.  
  2696.  
  2697. &lt;p&gt; The discussion continues into the evolution and widespread adoption of Git, including its implications for software development, with Torvalds explaining that while he did not originally set out to revolutionize the industry, Git’s design principles ended up facilitating collaboration among developers of all experience levels. The conversation touches on Torvalds’ transition from maintainer to a more distant role, the continuing evolution of Git, and the challenges it might face moving forward. He concludes by reflecting on the rich legacy of Git and its impact on software engineering practices.&lt;/p&gt;
  2698.  
  2699.  
  2700.  
  2701. &lt;figure class=&quot;wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio&quot;&gt;&lt;div class=&quot;wp-block-embed__wrapper&quot;&gt;
  2702. &lt;div class=&quot;embed-youtube&quot;&gt;&lt;/div&gt;
  2703. &lt;/div&gt;&lt;/figure&gt;
  2704.  
  2705.  
  2706.  
  2707. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Highlights&lt;/h3&gt;
  2708.  
  2709.  
  2710.  
  2711. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2712. &lt;li&gt;&lt;img alt=&quot;🎉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f389.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;20-Year Milestone&lt;/strong&gt;: Git celebrates two decades since its inception, highlighting its enduring relevance in software development.&lt;/li&gt;
  2713.  
  2714.  
  2715.  
  2716. &lt;li&gt;&lt;img alt=&quot;🛠&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f6e0.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Open Source Roots&lt;/strong&gt;: Torvalds created Git as an open-source alternative to proprietary systems like BitKeeper, aiming to empower developers.&lt;/li&gt;
  2717.  
  2718.  
  2719.  
  2720. &lt;li&gt;&lt;img alt=&quot;🔑&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f511.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Key Design Choices&lt;/strong&gt;: The use of SHA-1 hashing was pivotal for securing data integrity, a choice Torvalds admits had its complications but ultimately strengthened Git.&lt;/li&gt;
  2721.  
  2722.  
  2723.  
  2724. &lt;li&gt;&lt;img alt=&quot;🧩&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f9e9.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;User Experience Challenges&lt;/strong&gt;: Initial users found Git “hard to use,” reflecting the difficulty of shifting from centralized to distributed version control paradigms.&lt;/li&gt;
  2725.  
  2726.  
  2727.  
  2728. &lt;li&gt;&lt;img alt=&quot;🌍&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f30d.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Widespread Adoption&lt;/strong&gt;: Git’s unique functionality has led to its dominance in the version control market, with significant impact on projects of all sizes.&lt;/li&gt;
  2729.  
  2730.  
  2731.  
  2732. &lt;li&gt;&lt;img alt=&quot;⚙&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/2699.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Evolution and Maintenance&lt;/strong&gt;: Torvalds transitioned out of the maintainer role but retains a vested interest in Git’s continuous improvement and community growth.&lt;/li&gt;
  2733.  
  2734.  
  2735.  
  2736. &lt;li&gt;&lt;img alt=&quot;🔮&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f52e.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Future of Git&lt;/strong&gt;: Although Git is highly effective, questions about how it will adapt to emerging workflows and challenges remain significant.&lt;/li&gt;
  2737. &lt;/ul&gt;
  2738.  
  2739.  
  2740.  
  2741. &lt;h3 class=&quot;wp-block-heading&quot;&gt;Key Insights&lt;/h3&gt;
  2742.  
  2743.  
  2744.  
  2745. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2746. &lt;li&gt;&lt;img alt=&quot;📉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4c9.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Market Impact&lt;/strong&gt;: Git’s explosive growth indicates a network effect in software development; as more projects adopt Git, it becomes increasingly less practical for new developers to consider alternatives.
  2747. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2748. &lt;li&gt;The substantial statistics surrounding Git’s use as “98% of the SCM space” illustrate its dominance and the challenges for other version control systems to compete.&lt;/li&gt;
  2749. &lt;/ul&gt;
  2750. &lt;/li&gt;
  2751.  
  2752.  
  2753.  
  2754. &lt;li&gt;&lt;img alt=&quot;📦&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4e6.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Distributed vs. Centralized&lt;/strong&gt;: A fundamental shift in project management ethos has occurred because Git promotes a distributed model that allows local operations without constant connectivity.
  2755. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2756. &lt;li&gt;This design alleviates the burdens traditionally associated with centralized systems, making Git particularly appealing to indie developers and small teams.&lt;/li&gt;
  2757. &lt;/ul&gt;
  2758. &lt;/li&gt;
  2759.  
  2760.  
  2761.  
  2762. &lt;li&gt;&lt;img alt=&quot;💡&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f4a1.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Intuitive Simplicity&lt;/strong&gt;: The development methodology used in Git, rooted in the principles of Unix, emphasizes simplicity at its core while managing sophisticated functionalities.
  2763. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2764. &lt;li&gt;Torvalds attributes Git’s clarity of design to its foundation, suggesting that successful projects are often built on straightforward principles that can evolve over time.&lt;/li&gt;
  2765. &lt;/ul&gt;
  2766. &lt;/li&gt;
  2767.  
  2768.  
  2769.  
  2770. &lt;li&gt;&lt;img alt=&quot;🔄&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f504.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Adaptation Design&lt;/strong&gt;: The way Git supports adaptability through its inherent structure allows for various workflows, catering to everything from kernel development to simple student projects.
  2771. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2772. &lt;li&gt;Torvalds highlights that the real value comes in making collaboration seamless, which can be attractive for newcomers to software development.&lt;/li&gt;
  2773. &lt;/ul&gt;
  2774. &lt;/li&gt;
  2775.  
  2776.  
  2777.  
  2778. &lt;li&gt;&lt;img alt=&quot;🔍&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f50d.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Feature Appreciation&lt;/strong&gt;: There is a contrast between the initial backlash against Git’s interface and the eventual recognition of its powerful capabilities.
  2779. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2780. &lt;li&gt;As Git became entrenched within new development communities, user experience shifted from resentment to an appreciation of the tool’s potential.&lt;/li&gt;
  2781. &lt;/ul&gt;
  2782. &lt;/li&gt;
  2783.  
  2784.  
  2785.  
  2786. &lt;li&gt;&lt;img alt=&quot;⏳&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/23f3.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Community and Maintenance&lt;/strong&gt;: Torvalds handed over maintainership after a few months, preferring to let the active community shape Git’s evolution.
  2787. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2788. &lt;li&gt;This decision reflects his pragmatic approach, allowing others who are passionate about Git’s future to take the reins, fostering broader community involvement.&lt;/li&gt;
  2789. &lt;/ul&gt;
  2790. &lt;/li&gt;
  2791.  
  2792.  
  2793.  
  2794. &lt;li&gt;&lt;img alt=&quot;🚧&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.1.0/72x72/1f6a7.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Future Challenges&lt;/strong&gt;: While Git is effective, its future may involve addressing issues raised by large-scale implementations or new methodologies that conflict with Git’s design philosophy.
  2795. &lt;ul class=&quot;wp-block-list&quot;&gt;
  2796. &lt;li&gt;As software practices evolve, Git’s maintainers will need to balance tradition with innovation. Managing user expectations and feature requests will be critical moving forward.&lt;/li&gt;
  2797. &lt;/ul&gt;
  2798. &lt;/li&gt;
  2799. &lt;/ul&gt;
  2800.  
  2801.  
  2802.  
  2803. &lt;p&gt;In conclusion, the discussions presents a rich narrative of Git’s journey from its inception to a critical component of modern software development, reflecting the thoughts and contributions of its creator while contemplating its future in a fast-evolving landscape.&lt;/p&gt;
  2804.  
  2805.  
  2806.  
  2807. &lt;p&gt;&lt;/p&gt;
  2808. &lt;p&gt;The post &lt;a href=&quot;https://utappia.org/2025/04/11/git-turns-20-a-conversation-with-creator-linus-torvalds/&quot;&gt;Git turns 20! : A conversation with creator Linus Torvalds&lt;/a&gt; appeared first on &lt;a href=&quot;https://utappia.org&quot;&gt;Utappia&lt;/a&gt;.&lt;/p&gt;</description>
  2809. <pubDate>Fri, 11 Apr 2025 13:41:22 +0000</pubDate>
  2810. </item>
  2811. <item>
  2812. <title>Ubuntu MATE: Ubuntu MATE 24.10 Release Notes</title>
  2813. <guid isPermaLink="false">https://ubuntu-mate.org/blog/ubuntu-mate-oracular-oriole</guid>
  2814. <link>https://ubuntu-mate.org/blog/ubuntu-mate-oracular-oriole-release-notes/</link>
  2815. <description>&lt;p&gt;Ubuntu MATE 24.10 is more of what you like, stable MATE Desktop on top of current Ubuntu. Read on to learn more 👓️&lt;/p&gt;
  2816.  
  2817. &lt;p class=&quot;center&quot;&gt;&lt;img alt=&quot;Ubuntu MATE 24.10&quot; src=&quot;https://ubuntu-mate.org/images/blog/oracular/screenshot.png&quot; /&gt;
  2818. &lt;strong&gt;Ubuntu MATE 24.10&lt;/strong&gt;&lt;/p&gt;
  2819.  
  2820. &lt;h2 id=&quot;thank-you-&quot;&gt;Thank you! 🙇&lt;/h2&gt;
  2821.  
  2822. &lt;p&gt;&lt;strong&gt;My sincere thanks to everyone who has played an active role in improving Ubuntu MATE for this release 👏
  2823. I’d like to acknowledge the close collaboration with the Ubuntu Foundations team and the Ubuntu flavour teams, in particular &lt;a href=&quot;https://launchpad.net/~eeickmeyer&quot;&gt;Erich Eickmeyer&lt;/a&gt; who pushed critical fixes while I was travelling.
  2824. Thank you!&lt;/strong&gt; 💚&lt;/p&gt;
  2825.  
  2826. &lt;h2 id=&quot;what-changed-since-the-ubuntu-mate-2404-lts&quot;&gt;What changed since the Ubuntu MATE 24.04 LTS?&lt;/h2&gt;
  2827.  
  2828. &lt;p&gt;Here are the highlights of what’s changed since the &lt;a href=&quot;https://ubuntu-mate.org/blog/ubuntu-mate-noble-numbat-release-notes/&quot;&gt;release of Ubuntu MATE 24.04&lt;/a&gt;&lt;/p&gt;
  2829.  
  2830. &lt;ul&gt;
  2831.  &lt;li&gt;Ships stable &lt;a href=&quot;https://mate-desktop.org&quot;&gt;MATE Desktop&lt;/a&gt; 1.26.2 with a handful of bug fixes 🐛&lt;/li&gt;
  2832.  &lt;li&gt;Switched back to Slick Greeter (replacing Arctica Greeter) due to race-condition in the boot process which results the display manager failing to initialise.
  2833.    &lt;ul&gt;
  2834.      &lt;li&gt;Returning to Slick Greeter reintroduces the ability to easily configure the login screen via a graphical application, something users have been requesting be re-instated 👍&lt;/li&gt;
  2835.    &lt;/ul&gt;
  2836.  &lt;/li&gt;
  2837.  &lt;li&gt;Ubuntu MATE 24.10 .iso 📀 is now 3.3GB 🤏 Down from 4.1GB in the 24.04 LTS release.
  2838.    &lt;ul&gt;
  2839.      &lt;li&gt;This is thanks to some fixes in the installer that no longer require as many packages in the live-seed.&lt;/li&gt;
  2840.    &lt;/ul&gt;
  2841.  &lt;/li&gt;
  2842. &lt;/ul&gt;
  2843.  
  2844. &lt;p class=&quot;center&quot;&gt;&lt;img alt=&quot;Login Window Configuration&quot; src=&quot;https://ubuntu-mate.org/images/blog/oracular/login-window.png&quot; /&gt;
  2845. &lt;strong&gt;Login Window&lt;/strong&gt;&lt;/p&gt;
  2846.  
  2847. &lt;h2 id=&quot;what-didnt-change-since-the-ubuntu-mate-2404-lts&quot;&gt;What didn’t change since the Ubuntu MATE 24.04 LTS?&lt;/h2&gt;
  2848.  
  2849. &lt;p&gt;If you follow upstream MATE Desktop development, then you’ll have noticed that Ubuntu MATE 24.10 doesn’t ship with the recently released MATE Desktop 1.28 🧉&lt;/p&gt;
  2850.  
  2851. &lt;p&gt;I have prepared packaging for MATE Desktop 1.28, along with the associated components but encountered some bugs and regressions 🐞 I wasn’t able to get things to a standard I’m happy to ship be default, so it is tried and true MATE 1.26.2 one last time 🪨&lt;/p&gt;
  2852.  
  2853. &lt;h2 id=&quot;major-applications&quot;&gt;Major Applications&lt;/h2&gt;
  2854.  
  2855. &lt;p&gt;Accompanying &lt;strong&gt;MATE Desktop 1.26.2&lt;/strong&gt; 🧉 and &lt;strong&gt;Linux 6.11&lt;/strong&gt; 🐧 are &lt;strong&gt;Firefox 131&lt;/strong&gt; 🔥🦊,
  2856. &lt;strong&gt;Celluloid 0.27&lt;/strong&gt; 🎥, &lt;strong&gt;Evolution 3.54&lt;/strong&gt; 📧, &lt;strong&gt;LibreOffice 24.8.2&lt;/strong&gt; 📚&lt;/p&gt;
  2857.  
  2858. &lt;p&gt;See the &lt;a href=&quot;https://discourse.ubuntu.com/t/oracular-oriole-release-notes/44878/1&quot;&gt;Ubuntu 24.10 Release Notes&lt;/a&gt;
  2859. for details of all the changes and improvements that Ubuntu MATE benefits from.&lt;/p&gt;
  2860.  
  2861. &lt;div class=&quot;jumbotron&quot;&gt;
  2862.  
  2863.    &lt;h2&gt;Download Ubuntu MATE 24.10&lt;/h2&gt;
  2864.  
  2865.    &lt;p&gt;Available for 64-bit desktop computers!&lt;/p&gt;
  2866.  
  2867.  
  2868.    
  2869.        &lt;a class=&quot;btn&quot; href=&quot;https://ubuntu-mate.org/download/&quot;&gt;Download&lt;/a&gt;
  2870.    
  2871.  
  2872. &lt;/div&gt;
  2873.  
  2874. &lt;h2 id=&quot;upgrading-to-ubuntu-mate-2410&quot;&gt;Upgrading to Ubuntu MATE 24.10&lt;/h2&gt;
  2875.  
  2876. &lt;p&gt;The upgrade process to Ubuntu MATE 24.10 is the same as Ubuntu.&lt;/p&gt;
  2877.  
  2878. &lt;ul&gt;
  2879.  &lt;li&gt;&lt;a href=&quot;https://help.ubuntu.com/community/OracularUpgrades&quot;&gt;Ubuntu 24.10 Upgrade Process&lt;/a&gt;&lt;/li&gt;
  2880. &lt;/ul&gt;
  2881.  
  2882. &lt;p&gt;There are no offline upgrade options for Ubuntu MATE. Please ensure you have
  2883. network connectivity to one of the official mirrors or to a locally accessible
  2884. mirror and follow the instructions above.&lt;/p&gt;</description>
  2885. <pubDate>Sun, 06 Apr 2025 16:54:02 +0000</pubDate>
  2886. </item>
  2887. <item>
  2888. <title>Elizabeth K. Joseph: A VisionFive 2 and a Raspberry Pi 1 B</title>
  2889. <guid isPermaLink="false">https://princessleia.com/journal/?p=17828</guid>
  2890. <link>https://princessleia.com/journal/2025/04/a-visionfive-2-and-a-raspberry-pi-1-b/</link>
  2891. <description>&lt;p&gt;A couple weeks ago I was playing around with a multiple architecture CI setup with another team, and that led me to pull out my StarFive VisionFive 2 SBC again to see where I could make it this time with an install.&lt;/p&gt;
  2892. &lt;p&gt;I left off about a year ago when I succeeded in getting an older version of Debian on it, but attempts to get the tooling to install a more broadly supported version of U-Boot to the SPI flash were unsuccessful. Then I got pulled away to other things, effectively just bringing my VF2 around to events as a prop for my multiarch talks – which it did beautifully! I even had one conference attendee buy one to play with while sitting in the audience of my talk. Cool.&lt;/p&gt;
  2893. &lt;p&gt;I was delighted to learn how much progress had been made since I last looked. Canonical has published more formalized documentation: &lt;a href=&quot;https://canonical-ubuntu-boards.readthedocs-hosted.com/en/latest/how-to/starfive-visionfive-2/&quot;&gt;Install Ubuntu on the StarFive VisionFive 2&lt;/a&gt; in the place of what had been a rather cluttered wiki page. So I got all hooked up and began my latest attempt.&lt;/p&gt;
  2894. &lt;div align=&quot;center&quot;&gt;&lt;a href=&quot;https://princessleia.com/images/journalpics/032025/visionfive2_install_philly.jpg&quot;&gt;&lt;img src=&quot;https://princessleia.com/images/journalpics/032025/visionfive2_install_philly_sm.jpg&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
  2895. &lt;p&gt;My first step was to grab the pre-installed server image. I got that installed, but struggled a little with persistence once I unplugged the USB UART adapter and rebooted. I then decided just to move forward with the &lt;a href=&quot;https://canonical-ubuntu-boards.readthedocs-hosted.com/en/latest/how-to/starfive-visionfive-2/#install-u-boot-to-the-spi-flash&quot;&gt;Install U-Boot to the SPI flash&lt;/a&gt; instructions. I struggled a bit here for two reasons:&lt;/p&gt;
  2896. &lt;ol&gt;
  2897. &lt;li&gt;The documentation today leads off with having you download the livecd, but you actually want the pre-installed server image to flash U-Boot, the livecd step doesn’t come until later. Admittedly, the instructions do &lt;em&gt;say&lt;/em&gt; this, but I wasn’t reading carefully enough and was more focused on the steps.&lt;/li&gt;
  2898. &lt;li&gt;I couldn’t get the 24.10 pre-installed image to work for flashing U-Boot, but once I went back to the 24.04 pre-installed image it worked.&lt;/li&gt;
  2899. &lt;/ol&gt;
  2900. &lt;p&gt;And then I had to fly across the country. We’re spending a couple weeks around spring break here at our vacation house in Philadelphia, but the good thing about SBCs is that they’re incredibly portable and I just tossed my gear into my backpack and brought it along.&lt;/p&gt;
  2901. &lt;p&gt;Thanks to Emil Renner Berthing (esmil) on the &lt;a href=&quot;https://discourse.ubuntu.com/t/getting-started-with-matrix/41000&quot;&gt;Ubuntu Matrix server&lt;/a&gt; for providing me with enough guidance to figure out where I had gone wrong above, and got me on my way just a few days after we arrived in Philly.&lt;/p&gt;
  2902. &lt;p&gt;With the newer U-Boot installed, I was able to use the Ubuntu 24.04 livecd image on a micro SD Card to install Ubuntu 24.04 on an NVMe drive! That’s another new change since I last looked at installation, using my little NVMe drive as a target was a lot simpler than it would have been a year ago. In fact, it was rather anticlimactic, hah!&lt;/p&gt;
  2903. &lt;div align=&quot;center&quot;&gt;&lt;a href=&quot;https://princessleia.com/images/journalpics/032025/visionfive2_nvme.jpg&quot;&gt;&lt;img src=&quot;https://princessleia.com/images/journalpics/032025/visionfive2_nvme_sm.jpg&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
  2904. &lt;p&gt;And with that, I was fully logged in to my new system.&lt;/p&gt;
  2905. &lt;p&gt;&lt;code&gt;elizabeth@r2kt:~$ cat /proc/cpuinfo&lt;br /&gt;
  2906. processor : 0&lt;br /&gt;
  2907. hart : 2&lt;br /&gt;
  2908. isa : rv64imafdc_zicntr_zicsr_zifencei_zihpm_zba_zbb&lt;br /&gt;
  2909. mmu : sv39&lt;br /&gt;
  2910. uarch : sifive,u74-mc&lt;br /&gt;
  2911. mvendorid : 0x489&lt;br /&gt;
  2912. marchid : 0x8000000000000007&lt;br /&gt;
  2913. mimpid : 0x4210427&lt;br /&gt;
  2914. hart isa : rv64imafdc_zicntr_zicsr_zifencei_zihpm_zba_zbb&lt;/code&gt;&lt;/p&gt;
  2915. &lt;p&gt;It has 4 cores, so here’s the full output: &lt;a href=&quot;https://princessleia.com/txt/vf2-cpus.txt&quot;&gt;vf2-cpus.txt&lt;/a&gt;&lt;/p&gt;
  2916. &lt;p&gt;What will I do with this little single board computer? I don’t know yet. I joked with my husband that I’d “install Debian on it and forget about it like everything else” but I really would like to get past that. I have my little multiarch demo CI project in the wings, and I’ll probably loop it into that.&lt;/p&gt;
  2917. &lt;p&gt;Since we were in Philly, I had a look over at my long-neglected Raspberry Pi 1B that I have here. When we first moved in, I used it as an ssh tunnel to get to this network from California. It was great for that! But now we have a more sophisticated network setup between the houses with a VLAN that connects them, so the ssh tunnel is unnecessary. In fact, my poor Raspberry Pi fell off the WiFi network when we switched to 802.1X just over a year ago and I never got around to getting it back on the network. I connected it to a keyboard and monitor and started some investigation. Honestly, I’m surprised the little guy was still running, but it’s doing fine!&lt;/p&gt;
  2918. &lt;p&gt;And it had been chugging along running Rasbian based on Debian 9. Well, that’s worth an upgrade. But not just an upgrade, I didn’t want to stress the device and SD card, so I figured flashing it with the latest version of Raspberry Pi OS was the right way to go. It turns out, it’s been a long time since I’ve done a Raspberry Pi install.&lt;/p&gt;
  2919. &lt;p&gt;I grabbed the &lt;a href=&quot;https://www.raspberrypi.com/software/&quot;&gt;Raspberry Pi Imager&lt;/a&gt; and went on my way. It’s really nice. I went with the Raspberry Pi OS Lite install since it’s the RP1, I didn’t want a GUI. The imager asked the usual installation questions, loaded up my SSH key, and I was ready to load it up in my Pi.&lt;/p&gt;
  2920. &lt;div align=&quot;center&quot;&gt;&lt;a href=&quot;https://princessleia.com/images/journalpics/032025/raspberripi1b_imager_2025.png&quot;&gt;&lt;img src=&quot;https://princessleia.com/images/journalpics/032025/raspberripi1b_imager_2025_sm.png&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
  2921. &lt;p&gt;The only thing I need to finish sorting out is networking. The old USB WiFi adapter I have it in doesn’t initialize until after it’s booted up, so wpa_supplicant on boot can’t negotiate with the access point. I’ll have to play around with it. And what will I use this for once I do, now that it’s not an SSH tunnel? I’m not sure yet.&lt;/p&gt;
  2922. &lt;div align=&quot;center&quot;&gt;&lt;a href=&quot;https://princessleia.com/images/journalpics/032025/raspberry_pi_1_dusty_case.jpg&quot;&gt;&lt;img src=&quot;https://princessleia.com/images/journalpics/032025/raspberry_pi_1_dusty_case_sm.jpg&quot; /&gt;&lt;/a&gt;&lt;/div&gt;
  2923. &lt;p&gt;I realize this blog post isn’t very deep or technical, but I guess that’s the point. We’ve come a long way in recent years in support for non-x86 architectures, so installation has gotten a lot easier across several of them. If you’re new to playing around with architectures, I’d say it’s a really good time to start. You can hit the ground running with some wins, and then play around as you go with various things you want to help get working. It’s a lot of fun, and the years I spent playing around with Debian on Sparc back in the day definitely laid the groundwork for the job I have at IBM working on mainframes. You never know where a bit of technical curiosity will get you.&lt;/p&gt;</description>
  2924. <pubDate>Thu, 03 Apr 2025 20:43:31 +0000</pubDate>
  2925. </item>
  2926. <item>
  2927. <title>Lubuntu Blog: Lubuntu Plucky Puffin Beta Released!</title>
  2928. <guid isPermaLink="false">https://lubuntu.me/?p=4122</guid>
  2929. <link>https://lubuntu.me/plucky-beta/</link>
  2930. <description>Thanks to the hard work of our contributors, we are happy to announce the release of Lubuntu's Plucky Beta, which will become Lubuntu 25.04. This is a snapshot of the daily images. Approximately two months ago, we posted an Alpha-level update. While some information is duplicated below, that contains an accurate, concise technical summary of […]</description>
  2931. <pubDate>Thu, 27 Mar 2025 21:02:47 +0000</pubDate>
  2932. </item>
  2933. <item>
  2934. <title>Luke Faraone: I'm running for the OSI board... maybe</title>
  2935. <guid isPermaLink="false">tag:blogger.com,1999:blog-1354659632607599854.post-8137871464316542520</guid>
  2936. <link>https://blog.luke.wf/2025/02/im-running-for-osi-board-maybe.html</link>
  2937. <description>&lt;p&gt;The Open Source Initiative has two classes of board seats: Affiliate seats, and Individual Member seats. &lt;/p&gt;&lt;p&gt;In the upcoming election, each affiliate can nominate a candidate, and each affiliate can cast a vote for the Affiliate candidates, but there's only 1 Affiliate seat available. I initially expressed interest in being nominated as an Affiliate candidate via Debian. But since &lt;a href=&quot;https://ebb.org/bkuhn/&quot;&gt;Bradley Kuhn&lt;/a&gt; is also running for an Affiliate seat with a similar platform to me, especially with regards to the OSAID, I decided to run as part of an aligned &quot;ticket&quot; as an Individual Member to avoid contention for the 1 Affiliate seat.&lt;/p&gt;&lt;p&gt;Bradley and I discussed running on a similar ticket around 8/9pm Pacific, and I submitted my candidacy around 9pm PT on 17 February. &lt;/p&gt;&lt;p&gt;I was dismayed when I received the following mail from &lt;span style=&quot;white-space: normal;&quot;&gt;Nick Vidal:&lt;/span&gt;&lt;/p&gt;&lt;p&gt;&lt;/p&gt;&lt;blockquote&gt;&lt;span face=&quot;Arial, Helvetica, sans-serif&quot; style=&quot;background-color: white; color: #222222; font-size: small;&quot;&gt;Dear Luke,&lt;/span&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;span face=&quot;Arial, Helvetica, sans-serif&quot; style=&quot;background-color: white; color: #222222; font-size: small;&quot;&gt;Thank you for your interest in the OSI Board of Directors election. Unfortunately, we are unable to accept your application as it was submitted after the official deadline of Monday Feb 17 at 11:59 pm UTC. To ensure a fair process,&lt;b&gt; we must adhere to the deadline for all candidates.&lt;/b&gt;&lt;/span&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;span face=&quot;Arial, Helvetica, sans-serif&quot; style=&quot;background-color: white; color: #222222; font-size: small;&quot;&gt;We appreciate your enthusiasm and encourage you to stay engaged with OSI’s mission. We hope you’ll consider applying in the future or contributing in other meaningful ways.&lt;/span&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;span face=&quot;Arial, Helvetica, sans-serif&quot; style=&quot;background-color: white; color: #222222; font-size: small;&quot;&gt;Best regards,&lt;/span&gt;&lt;br style=&quot;background-color: white; color: #222222; font-family: Arial, Helvetica, sans-serif; font-size: small;&quot; /&gt;&lt;span face=&quot;Arial, Helvetica, sans-serif&quot; style=&quot;background-color: white; color: #222222; font-size: small;&quot;&gt;OSI Election Teams&lt;/span&gt;&lt;/blockquote&gt;&lt;p&gt;Nowhere on the &lt;a href=&quot;https://opensource.org/blog/osis-board-of-directors-in-2025-details-about-the-elections&quot;&gt;&quot;OSI’s board of directors in 2025: details about the elections&quot;&lt;/a&gt; page do they list a timezone for closure of nominations; they simply list Monday 17 February. &lt;/p&gt;&lt;p&gt;The OSI's contact address is in California, so it seems arbitrary and capricious to retroactively define all of these processes as being governed by UTC.&lt;/p&gt;&lt;p&gt;I was not able to participate in the &quot;potential board director&quot; info sessions accordingly, but people who attended heard that the importance of accommodating differing TZ's was discussed during the info session, and that OSI representatives mentioned they try to accommodate TZ's of everyone. This seems in sharp contrast with the above policy. &lt;/p&gt;&lt;p&gt;I urge the OSI to reconsider this policy and allow me to stand for an Individual seat in the current cycle. &lt;/p&gt;&lt;p&gt;&lt;b&gt;Upd&lt;/b&gt;, N.B.: to people writing about this, I use they/them pronouns&lt;/p&gt;&lt;p&gt;&lt;/p&gt;</description>
  2938. <pubDate>Sat, 22 Mar 2025 16:30:44 +0000</pubDate>
  2939. <author>noreply@blogger.com (Luke Faraone)</author>
  2940. </item>
  2941. <item>
  2942. <title>Sean Davis: Xubuntu Development Update February 2025</title>
  2943. <guid isPermaLink="false">https://seand.xyz/tag/xubuntu/rss/68338e7c38f598252d964017</guid>
  2944. <link>https://seand.xyz/blog/2025/02/22/xubuntu-development-update-february-2025/</link>
  2945. <description>&lt;img alt=&quot;Xubuntu Development Update February 2025&quot; src=&quot;https://seand.xyz/content/images/2024/12/xubuntu-25-04-dev-featured.png&quot; /&gt;&lt;p&gt;Better late than never, here&amp;amp;aposs your Xubuntu February 2025 update! This month, Xubuntu 24.04.2 was released with a new Linux kernel and bug fixes in tow. 25.04 Feature Freeze is now in effect, with many package updates arriving just before the deadline. Xubuntu&amp;amp;aposs first RISC-V package support has landed. And so much more!&lt;/p&gt;
  2946. &lt;h2 id=&quot;februaryschedule&quot;&gt;February Schedule&lt;/h2&gt;
  2947. &lt;p&gt;The &lt;a href=&quot;https://discourse.ubuntu.com/t/plucky-puffin-release-schedule/36461?ref=seand.xyz&quot;&gt;Plucky Puffin Release Schedule&lt;/a&gt; for February includes &lt;em&gt;Feature Freeze&lt;/em&gt; on the 20th and an optional testing week at the end of the month. It also features the next point release for Xubuntu 24.04 &quot;Noble Numbat&quot;.&lt;/p&gt;
  2948. &lt;table&gt;
  2949. &lt;thead&gt;
  2950. &lt;tr&gt;
  2951. &lt;th&gt;Date&lt;/th&gt;
  2952. &lt;th&gt;Milestones&lt;/th&gt;
  2953. &lt;/tr&gt;
  2954. &lt;/thead&gt;
  2955. &lt;tbody&gt;
  2956. &lt;tr&gt;
  2957. &lt;td&gt;February 06&lt;/td&gt;
  2958. &lt;td&gt;&lt;/td&gt;
  2959. &lt;/tr&gt;
  2960. &lt;tr&gt;
  2961. &lt;td&gt;February 13&lt;/td&gt;
  2962. &lt;td&gt;&lt;a href=&quot;https://wiki.ubuntu.com/PointReleaseProcess?ref=seand.xyz&quot;&gt;24.04.2 Point Release&lt;/a&gt; &lt;em&gt;(delayed to 2/20)&lt;/em&gt;&lt;/td&gt;
  2963. &lt;/tr&gt;
  2964. &lt;tr&gt;
  2965. &lt;td&gt;February 20&lt;/td&gt;
  2966. &lt;td&gt;&lt;a href=&quot;https://wiki.ubuntu.com/FeatureFreeze?ref=seand.xyz&quot;&gt;Feature Freeze&lt;/a&gt;, &lt;a href=&quot;https://wiki.ubuntu.com/DebianImportFreeze?ref=seand.xyz&quot;&gt;Debian Import Freeze&lt;/a&gt;&lt;/td&gt;
  2967. &lt;/tr&gt;
  2968. &lt;tr&gt;
  2969. &lt;td&gt;February 27&lt;/td&gt;
  2970. &lt;td&gt;Ubuntu Testing Week (optional)&lt;/td&gt;
  2971. &lt;/tr&gt;
  2972. &lt;/tbody&gt;
  2973. &lt;/table&gt;
  2974. &lt;h2 id=&quot;majorpackageupdatesinxubuntu24042&quot;&gt;Major Package Updates in Xubuntu 24.04.2&lt;/h2&gt;
  2975. &lt;p&gt;Xubuntu 24.04.2 was released on Thursday, February 20, 2025. It features a modest set of changes in addition to the 6.11 Linux kernel and updated graphics stack. &lt;code&gt;xfce4-panel&lt;/code&gt; 4.18.4-1ubuntu0.1 features a fix for the crash-on-exit bug that plagued users with unexplainable error notifications (LP: &lt;a href=&quot;https://launchpad.net/bugs/2064846?ref=seand.xyz&quot;&gt;#2064846&lt;/a&gt;).&lt;/p&gt;
  2976. &lt;p&gt;&lt;a href=&quot;https://github.com/Xubuntu/xubuntu-manifest/compare/24.04.1...24.04.2?ref=seand.xyz&quot;&gt;Changes from Xubuntu 24.04.1 to 24.04.2&lt;/a&gt;&lt;/p&gt;
  2977. &lt;table&gt;
  2978. &lt;thead&gt;
  2979. &lt;tr&gt;
  2980. &lt;th&gt;Package&lt;/th&gt;
  2981. &lt;th&gt;24.04.1&lt;/th&gt;
  2982. &lt;th&gt;24.04.2&lt;/th&gt;
  2983. &lt;/tr&gt;
  2984. &lt;/thead&gt;
  2985. &lt;tbody&gt;
  2986. &lt;tr&gt;
  2987. &lt;td&gt;firefox&lt;/td&gt;
  2988. &lt;td&gt;134&lt;/td&gt;
  2989. &lt;td&gt;135&lt;/td&gt;
  2990. &lt;/tr&gt;
  2991. &lt;tr&gt;
  2992. &lt;td&gt;libdrm&lt;/td&gt;
  2993. &lt;td&gt;2.4.120&lt;/td&gt;
  2994. &lt;td&gt;2.4.122&lt;/td&gt;
  2995. &lt;/tr&gt;
  2996. &lt;tr&gt;
  2997. &lt;td&gt;libreoffice&lt;/td&gt;
  2998. &lt;td&gt;24.2.5&lt;/td&gt;
  2999. &lt;td&gt;24.2.7&lt;/td&gt;
  3000. &lt;/tr&gt;
  3001. &lt;tr&gt;
  3002. &lt;td&gt;Linux kernel&lt;/td&gt;
  3003. &lt;td&gt;6.8.0&lt;/td&gt;
  3004. &lt;td&gt;6.11.0&lt;/td&gt;
  3005. &lt;/tr&gt;
  3006. &lt;tr&gt;
  3007. &lt;td&gt;Mesa&lt;/td&gt;
  3008. &lt;td&gt;24.0.9&lt;/td&gt;
  3009. &lt;td&gt;24.2.8&lt;/td&gt;
  3010. &lt;/tr&gt;
  3011. &lt;tr&gt;
  3012. &lt;td&gt;xfce4-panel&lt;/td&gt;
  3013. &lt;td&gt;4.18.4-1build2&lt;/td&gt;
  3014. &lt;td&gt;4.18.4-1ubuntu0.1&lt;/td&gt;
  3015. &lt;/tr&gt;
  3016. &lt;/tbody&gt;
  3017. &lt;/table&gt;
  3018. &lt;h2 id=&quot;majorpackageupdatesinxubuntu2504&quot;&gt;Major Package Updates in Xubuntu 25.04&lt;/h2&gt;
  3019. &lt;p&gt;There was a flurry of upload activity in the lead up to the 25.04 Feature Freeze. GIMP 3.0.0 was bumped from RC2 to RC3. The Linux kernel was updated from 6.11.0 to 6.12.0. A handful of Xfce components also saw new releases to further stabilize Xubuntu&amp;amp;aposs base. For more information on the progress of Xubuntu 25.04, check out the following links:&lt;/p&gt;
  3020. &lt;ul&gt;
  3021. &lt;li&gt;&lt;a href=&quot;https://github.com/Xubuntu/xubuntu-manifest/compare/23d5548ebeede9ad7431f669b96635d9b828f55c...9b0d1f97c07f446002156435343ea3f2a8246639?ref=seand.xyz&quot;&gt;Changes from January 1 to February 22&lt;/a&gt;&lt;/li&gt;
  3022. &lt;li&gt;&lt;a href=&quot;https://seand.xyz/2024/12/07/xubuntu-development-update-december-2024/&quot;&gt;December Update&lt;/a&gt;&lt;/li&gt;
  3023. &lt;li&gt;&lt;a href=&quot;https://seand.xyz/2025/01/01/xubuntu-development-update-january-2025&quot;&gt;January Update&lt;/a&gt;&lt;/li&gt;
  3024. &lt;/ul&gt;
  3025. &lt;table&gt;
  3026. &lt;thead&gt;
  3027. &lt;tr&gt;
  3028. &lt;th&gt;Package&lt;/th&gt;
  3029. &lt;th&gt;January 1, 2025&lt;/th&gt;
  3030. &lt;th&gt;February 22, 2025&lt;/th&gt;
  3031. &lt;/tr&gt;
  3032. &lt;/thead&gt;
  3033. &lt;tbody&gt;
  3034. &lt;tr&gt;
  3035. &lt;td&gt;blueman&lt;/td&gt;
  3036. &lt;td&gt;2.4.3&lt;/td&gt;
  3037. &lt;td&gt;2.4.4&lt;/td&gt;
  3038. &lt;/tr&gt;
  3039. &lt;tr&gt;
  3040. &lt;td&gt;gigolo&lt;/td&gt;
  3041. &lt;td&gt;0.5.3&lt;/td&gt;
  3042. &lt;td&gt;0.5.4&lt;/td&gt;
  3043. &lt;/tr&gt;
  3044. &lt;tr&gt;
  3045. &lt;td&gt;gimp&lt;/td&gt;
  3046. &lt;td&gt;3.0.0 RC2&lt;/td&gt;
  3047. &lt;td&gt;3.0.0 RC3&lt;/td&gt;
  3048. &lt;/tr&gt;
  3049. &lt;tr&gt;
  3050. &lt;td&gt;gnome-mines&lt;/td&gt;
  3051. &lt;td&gt;40.1&lt;/td&gt;
  3052. &lt;td&gt;48 Alpha&lt;/td&gt;
  3053. &lt;/tr&gt;
  3054. &lt;tr&gt;
  3055. &lt;td&gt;libgtk-3&lt;/td&gt;
  3056. &lt;td&gt;3.24.43&lt;/td&gt;
  3057. &lt;td&gt;3.24.48&lt;/td&gt;
  3058. &lt;/tr&gt;
  3059. &lt;tr&gt;
  3060. &lt;td&gt;libgtk-4&lt;/td&gt;
  3061. &lt;td&gt;4.17.1&lt;/td&gt;
  3062. &lt;td&gt;4.17.4&lt;/td&gt;
  3063. &lt;/tr&gt;
  3064. &lt;tr&gt;
  3065. &lt;td&gt;libreoffice&lt;/td&gt;
  3066. &lt;td&gt;24.8.4&lt;/td&gt;
  3067. &lt;td&gt;25.2.1&lt;/td&gt;
  3068. &lt;/tr&gt;
  3069. &lt;tr&gt;
  3070. &lt;td&gt;libxfce4windowing&lt;/td&gt;
  3071. &lt;td&gt;4.20.0&lt;/td&gt;
  3072. &lt;td&gt;4.20.2&lt;/td&gt;
  3073. &lt;/tr&gt;
  3074. &lt;tr&gt;
  3075. &lt;td&gt;lightdm&lt;/td&gt;
  3076. &lt;td&gt;1.30.0&lt;/td&gt;
  3077. &lt;td&gt;1.32.0&lt;/td&gt;
  3078. &lt;/tr&gt;
  3079. &lt;tr&gt;
  3080. &lt;td&gt;Linux kernel&lt;/td&gt;
  3081. &lt;td&gt;6.11.0&lt;/td&gt;
  3082. &lt;td&gt;6.12.0&lt;/td&gt;
  3083. &lt;/tr&gt;
  3084. &lt;tr&gt;
  3085. &lt;td&gt;Mesa&lt;/td&gt;
  3086. &lt;td&gt;24.2.8&lt;/td&gt;
  3087. &lt;td&gt;24.3.4&lt;/td&gt;
  3088. &lt;/tr&gt;
  3089. &lt;tr&gt;
  3090. &lt;td&gt;parole&lt;/td&gt;
  3091. &lt;td&gt;4.18.1&lt;/td&gt;
  3092. &lt;td&gt;4.18.2&lt;/td&gt;
  3093. &lt;/tr&gt;
  3094. &lt;tr&gt;
  3095. &lt;td&gt;python&lt;/td&gt;
  3096. &lt;td&gt;3.12.8&lt;/td&gt;
  3097. &lt;td&gt;3.13.1&lt;/td&gt;
  3098. &lt;/tr&gt;
  3099. &lt;tr&gt;
  3100. &lt;td&gt;rhythmbox&lt;/td&gt;
  3101. &lt;td&gt;3.4.7&lt;/td&gt;
  3102. &lt;td&gt;3.4.8&lt;/td&gt;
  3103. &lt;/tr&gt;
  3104. &lt;tr&gt;
  3105. &lt;td&gt;snapd&lt;/td&gt;
  3106. &lt;td&gt;2.66.1&lt;/td&gt;
  3107. &lt;td&gt;2.67.1&lt;/td&gt;
  3108. &lt;/tr&gt;
  3109. &lt;tr&gt;
  3110. &lt;td&gt;synaptic&lt;/td&gt;
  3111. &lt;td&gt;0.91.3&lt;/td&gt;
  3112. &lt;td&gt;0.91.5&lt;/td&gt;
  3113. &lt;/tr&gt;
  3114. &lt;tr&gt;
  3115. &lt;td&gt;thunar&lt;/td&gt;
  3116. &lt;td&gt;4.20.0&lt;/td&gt;
  3117. &lt;td&gt;4.20.2&lt;/td&gt;
  3118. &lt;/tr&gt;
  3119. &lt;tr&gt;
  3120. &lt;td&gt;xfce4-notifyd&lt;/td&gt;
  3121. &lt;td&gt;0.9.6&lt;/td&gt;
  3122. &lt;td&gt;0.9.7&lt;/td&gt;
  3123. &lt;/tr&gt;
  3124. &lt;tr&gt;
  3125. &lt;td&gt;xfce4-panel&lt;/td&gt;
  3126. &lt;td&gt;4.20.0&lt;/td&gt;
  3127. &lt;td&gt;4.20.3&lt;/td&gt;
  3128. &lt;/tr&gt;
  3129. &lt;tr&gt;
  3130. &lt;td&gt;xfce4-panel-profiles&lt;/td&gt;
  3131. &lt;td&gt;1.0.14&lt;/td&gt;
  3132. &lt;td&gt;1.0.15&lt;/td&gt;
  3133. &lt;/tr&gt;
  3134. &lt;tr&gt;
  3135. &lt;td&gt;xfce4-screensaver&lt;/td&gt;
  3136. &lt;td&gt;4.18.3&lt;/td&gt;
  3137. &lt;td&gt;4.18.4&lt;/td&gt;
  3138. &lt;/tr&gt;
  3139. &lt;tr&gt;
  3140. &lt;td&gt;xfce4-taskmanager&lt;/td&gt;
  3141. &lt;td&gt;1.5.7&lt;/td&gt;
  3142. &lt;td&gt;1.5.8&lt;/td&gt;
  3143. &lt;/tr&gt;
  3144. &lt;tr&gt;
  3145. &lt;td&gt;xfce4-whiskermenu-plugin&lt;/td&gt;
  3146. &lt;td&gt;2.8.3&lt;/td&gt;
  3147. &lt;td&gt;2.9.1&lt;/td&gt;
  3148. &lt;/tr&gt;
  3149. &lt;tr&gt;
  3150. &lt;td&gt;xfce4-xkb-plugin&lt;/td&gt;
  3151. &lt;td&gt;0.8.3&lt;/td&gt;
  3152. &lt;td&gt;0.8.5&lt;/td&gt;
  3153. &lt;/tr&gt;
  3154. &lt;tr&gt;
  3155. &lt;td&gt;xfwm4&lt;/td&gt;
  3156. &lt;td&gt;4.18.0&lt;/td&gt;
  3157. &lt;td&gt;4.20.0&lt;/td&gt;
  3158. &lt;/tr&gt;
  3159. &lt;tr&gt;
  3160. &lt;td&gt;xubuntu-default-settings&lt;/td&gt;
  3161. &lt;td&gt;25.04.0&lt;/td&gt;
  3162. &lt;td&gt;25.04.1&lt;/td&gt;
  3163. &lt;/tr&gt;
  3164. &lt;tr&gt;
  3165. &lt;td&gt;xubuntu-meta&lt;/td&gt;
  3166. &lt;td&gt;2.265&lt;/td&gt;
  3167. &lt;td&gt;2.266&lt;/td&gt;
  3168. &lt;/tr&gt;
  3169. &lt;/tbody&gt;
  3170. &lt;/table&gt;
  3171. &lt;p&gt;In the interest of keeping this post short, I&amp;amp;aposm only going to dive into Xubuntu&amp;amp;aposs package updates...&lt;/p&gt;
  3172. &lt;h3 id=&quot;xubuntudefaultsettings25041&quot;&gt;xubuntu-default-settings 25.04.1&lt;/h3&gt;
  3173. &lt;p&gt;&lt;code&gt;xubuntu-default-settings&lt;/code&gt; 25.04.1 includes a minor improvement: The &lt;code&gt;gtk-print-preview-command&lt;/code&gt; setting has been correctly associated with Atril (LP: &lt;a href=&quot;https://launchpad.net/bugs/2025332?ref=seand.xyz&quot;&gt;#2025332&lt;/a&gt;). Will Thompson&amp;amp;aposs &lt;a href=&quot;https://blogs.gnome.org/wjjt/2022/05/30/evince-flatpak-and-gtk-print-previews/?ref=seand.xyz&quot;&gt;Evince, Flatpak, and GTK print previews&lt;/a&gt; provides more context on this feature:&lt;/p&gt;
  3174. &lt;blockquote&gt;
  3175. &lt;p&gt;GTK provides API for applications to print documents. This presents the user with a print dialog, with many knobs to control how your document will be printed. That dialog has a Preview button; when you press it, the dialog vanishes and another one appears, showing a preview of your document. You can press Print on that dialog to print the document, or close it to cancel.&lt;/p&gt;
  3176. &lt;/blockquote&gt;
  3177. &lt;h3 id=&quot;xubuntumeta2266&quot;&gt;xubuntu-meta 2.266&lt;/h3&gt;
  3178. &lt;p&gt;&lt;code&gt;xubuntu-meta&lt;/code&gt; 2.266 adds support for the &lt;code&gt;riscv64&lt;/code&gt; architecture (LP: &lt;a href=&quot;https://launchpad.net/bugs/2092942?ref=seand.xyz&quot;&gt;#2092942&lt;/a&gt;)! Similar to the arm achitectures, this isn&amp;amp;apost supported by the Xubuntu team and you won&amp;amp;apost find downloadable ISOs. Instead, this enables package builds so the &lt;code&gt;xubuntu-desktop&lt;/code&gt; metapackage will be found on the riscv64 archives. If you put in the effort, you should now be able to get Xubuntu up and running on your riscv hardware. Let me know if you do!&lt;/p&gt;
  3179. &lt;h2 id=&quot;the2504todolist&quot;&gt;The 25.04 To-Do List&lt;/h2&gt;
  3180. &lt;p&gt;The Xubuntu 25.04 &lt;a href=&quot;https://github.com/orgs/Xubuntu/projects/11?ref=seand.xyz&quot;&gt;project board&lt;/a&gt; lists many outstanding tasks that we&amp;amp;aposd like to review this cycle. If you&amp;amp;aposd like to contribute to Xubuntu, pick a task and get to work. :) There are many other ways to contribute to Xubuntu &lt;a href=&quot;https://xubuntu.org/contribute/?ref=seand.xyz&quot;&gt;listed on our website&lt;/a&gt;.&lt;/p&gt;
  3181. &lt;p&gt;Xubuntu development marches steadily onward!&lt;/p&gt;</description>
  3182. <pubDate>Sat, 22 Feb 2025 04:40:00 +0000</pubDate>
  3183. </item>
  3184. <item>
  3185. <title>Paul Tagliamonte: boot2kier</title>
  3186. <guid isPermaLink="true">https://notes.pault.ag/boot2kier/</guid>
  3187. <link>https://notes.pault.ag/boot2kier/</link>
  3188. <description>&lt;p&gt;I can’t remember exactly the joke I was making at the time in my
  3189. &lt;a href=&quot;https://zoo.dev&quot;&gt;work’s&lt;/a&gt; slack instance (I’m sure it wasn’t particularly
  3190. funny, though; and not even worth re-reading the thread to work out), but it
  3191. wound up with me writing a UEFI binary for the punchline. Not to spoil the
  3192. ending but it worked - no pesky kernel, no messing around with “userland”. I
  3193. guess the only part of this you really need to know for the setup here is that
  3194. it was a &lt;a href=&quot;https://en.wikipedia.org/wiki/Severance_(TV_series)&quot;&gt;Severance&lt;/a&gt; joke,
  3195. which is some fantastic TV. If you haven’t seen it, this post will seem perhaps
  3196. weirder than it actually is. I promise I haven’t joined any new cults. For
  3197. those who have seen it, the payoff to my joke is that I wanted my machine to
  3198. boot directly to an image of
  3199. &lt;a href=&quot;https://severance-tv.fandom.com/wiki/Kier_Eagan&quot;&gt;Kier Eagan&lt;/a&gt;.&lt;/p&gt;
  3200. &lt;p&gt;As for how to do it – I figured I’d give the &lt;a href=&quot;https://docs.rs/uefi/latest/uefi/&quot;&gt;uefi
  3201. crate&lt;/a&gt; a shot, and see how it is to use,
  3202. since this is a low stakes way of trying it out. In general, this isn’t the
  3203. sort of thing I’d usually post about – except this wound up being easier and
  3204. way cleaner than I thought it would be. That alone is worth sharing, in the
  3205. hopes someome comes across this in the future and feels like they, too, can
  3206. write something fun targeting the UEFI.&lt;/p&gt;
  3207. &lt;p&gt;First thing’s first – gotta create a rust project (I’ll leave that part to you
  3208. depending on your life choices), and to add the &lt;code&gt;uefi&lt;/code&gt; crate to your
  3209. &lt;code&gt;Cargo.toml&lt;/code&gt;. You can either use &lt;code&gt;cargo add&lt;/code&gt; or add a line like this by hand:&lt;/p&gt;
  3210. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-toml&quot; data-lang=&quot;toml&quot;&gt;&lt;span style=&quot;color: #a6e22e;&quot;&gt;uefi&lt;/span&gt; = { &lt;span style=&quot;color: #a6e22e;&quot;&gt;version&lt;/span&gt; = &lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;0.33&quot;&lt;/span&gt;, &lt;span style=&quot;color: #a6e22e;&quot;&gt;features&lt;/span&gt; = [&lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;panic_handler&quot;&lt;/span&gt;, &lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;alloc&quot;&lt;/span&gt;, &lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;global_allocator&quot;&lt;/span&gt;] }
  3211. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;We also need to teach cargo about how to go about building for the UEFI target,
  3212. so we need to create a &lt;code&gt;rust-toolchain.toml&lt;/code&gt; with one (or both) of the UEFI
  3213. targets we’re interested in:&lt;/p&gt;
  3214. &lt;aside class=&quot;left&quot;&gt;
  3215. I think there's a UEFI for riscv64 too, but I haven't found notes about it
  3216. in Rust-land.
  3217. &lt;/aside&gt;
  3218. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-toml&quot; data-lang=&quot;toml&quot;&gt;[&lt;span style=&quot;color: #a6e22e;&quot;&gt;toolchain&lt;/span&gt;]
  3219. &lt;span style=&quot;color: #a6e22e;&quot;&gt;targets&lt;/span&gt; = [&lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;aarch64-unknown-uefi&quot;&lt;/span&gt;, &lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;x86_64-unknown-uefi&quot;&lt;/span&gt;]
  3220. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Unfortunately, I wasn’t able to use the
  3221. &lt;a href=&quot;https://docs.rs/image/latest/image/&quot;&gt;image&lt;/a&gt; crate,
  3222. since it won’t build against the &lt;code&gt;uefi&lt;/code&gt; target. This looks like it’s
  3223. because rustc had no way to compile the required floating point operations
  3224. within the &lt;code&gt;image&lt;/code&gt; crate without hardware floating point instructions
  3225. specifically. Rust tends to punt a lot of that to &lt;code&gt;libm&lt;/code&gt; usually, so this isnt
  3226. entirely shocking given we’re &lt;code&gt;nostd&lt;/code&gt; for a non-hardfloat target.&lt;/p&gt;
  3227. &lt;aside class=&quot;right&quot;&gt;
  3228. I didn't file any bugs or even track them down between the image crate
  3229. and rustc, since I figured this isn't actionable for anyone involved aside
  3230. from &quot;implement soft floats in the compiler to backfill this target&quot;.
  3231. &lt;/aside&gt;
  3232. &lt;p&gt;So-called “softening” requires a software floating point implementation that
  3233. the compiler can use to “polyfill” (feels weird to use the term polyfill here,
  3234. but I guess it’s spiritually right?) the lack of hardware floating point
  3235. operations, which rust hasn’t implemented for this target yet. As a result, I
  3236. changed tactics, and figured I’d use &lt;code&gt;ImageMagick&lt;/code&gt; to pre-compute the pixels
  3237. from a &lt;code&gt;jpg&lt;/code&gt;, rather than doing it at runtime. A bit of a bummer, since I need
  3238. to do more out of band pre-processing and hardcoding, and updating the image
  3239. kinda sucks as a result – but it’s entirely manageable.&lt;/p&gt;
  3240. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ convert -resize 1280x900 kier.jpg kier.full.jpg
  3241. $ convert -depth &lt;span style=&quot;color: #ae81ff;&quot;&gt;8&lt;/span&gt; kier.full.jpg rgba:kier.bin
  3242. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;This will take our input file (&lt;code&gt;kier.jpg&lt;/code&gt;), resize it to get as close to the
  3243. desired resolution as possible while maintaining aspect ration, then convert it
  3244. from a &lt;code&gt;jpg&lt;/code&gt; to a flat array of 4 byte &lt;code&gt;RGBA&lt;/code&gt; pixels. Critically, it’s also
  3245. important to remember that the size of the &lt;code&gt;kier.full.jpg&lt;/code&gt; file may not actually
  3246. be the requested size – it will not change the aspect ratio, so be sure to
  3247. make a careful note of the resulting size of the &lt;code&gt;kier.full.jpg&lt;/code&gt; file.&lt;/p&gt;
  3248. &lt;p&gt;Last step with the image is to compile it into our Rust bianary, since we
  3249. don’t want to struggle with trying to read this off disk, which is thankfully
  3250. real easy to do.&lt;/p&gt;
  3251. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-rust&quot; data-lang=&quot;rust&quot;&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;const&lt;/span&gt; KIER: &lt;span style=&quot;color: #66d9ef;&quot;&gt;&amp;amp;&lt;/span&gt;[&lt;span style=&quot;color: #66d9ef;&quot;&gt;u8&lt;/span&gt;] &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; include_bytes&lt;span style=&quot;color: #f92672;&quot;&gt;!&lt;/span&gt;(&lt;span style=&quot;color: #e6db74;&quot;&gt;&quot;../kier.bin&quot;&lt;/span&gt;);
  3252. &lt;span style=&quot;color: #66d9ef;&quot;&gt;const&lt;/span&gt; KIER_WIDTH: &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;1280&lt;/span&gt;;
  3253. &lt;span style=&quot;color: #66d9ef;&quot;&gt;const&lt;/span&gt; KIER_HEIGHT: &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;641&lt;/span&gt;;
  3254. &lt;span style=&quot;color: #66d9ef;&quot;&gt;const&lt;/span&gt; KIER_PIXEL_SIZE: &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;4&lt;/span&gt;;
  3255. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Remember to use the width and height from the final &lt;code&gt;kier.full.jpg&lt;/code&gt; file as the
  3256. values for &lt;code&gt;KIER_WIDTH&lt;/code&gt; and &lt;code&gt;KIER_HEIGHT&lt;/code&gt;. &lt;code&gt;KIER_PIXEL_SIZE&lt;/code&gt; is 4, since we
  3257. have 4 byte wide values for each pixel as a result of our conversion step into
  3258. RGBA. We’ll only use RGB, and if we ever drop the alpha channel, we can drop
  3259. that down to 3. I don’t entirely know why I kept alpha around, but I figured it
  3260. was fine. My &lt;code&gt;kier.full.jpg&lt;/code&gt; image winds up shorter than the requested height
  3261. (which is also qemu’s default resolution for me) – which means we’ll get a
  3262. semi-annoying black band under the image when we go to run it – but it’ll
  3263. work.&lt;/p&gt;
  3264. &lt;p&gt;Anyway, now that we have our image as bytes, we can get down to work, and
  3265. write the rest of the code to handle moving bytes around from in-memory
  3266. as a flat block if pixels, and request that they be displayed using the
  3267. &lt;a href=&quot;https://wiki.osdev.org/GOP&quot;&gt;UEFI GOP&lt;/a&gt;. We’ll just need to hack up a container
  3268. for the image pixels and teach it how to blit to the display.&lt;/p&gt;
  3269. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-rust&quot; data-lang=&quot;rust&quot;&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;/// RGB Image to move around. This isn't the same as an
  3270. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;/// `image::RgbImage`, but we can associate the size of
  3271. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;/// the image along with the flat buffer of pixels.
  3272. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;struct&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;RgbImage&lt;/span&gt; {
  3273. &lt;span style=&quot;color: #e6db74;&quot;&gt;/// Size of the image as a tuple, as the
  3274. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #e6db74;&quot;&gt;/// (width, height)
  3275. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; size: (&lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;),
  3276. &lt;span style=&quot;color: #e6db74;&quot;&gt;/// raw pixels we'll send to the display.
  3277. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; inner: Vec&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;BltPixel&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt;,
  3278. }
  3279. &lt;span style=&quot;color: #66d9ef;&quot;&gt;impl&lt;/span&gt; RgbImage {
  3280. &lt;span style=&quot;color: #e6db74;&quot;&gt;/// Create a new `RgbImage`.
  3281. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;new&lt;/span&gt;(width: &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, height: &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;) -&amp;gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;Self&lt;/span&gt; {
  3282. RgbImage {
  3283. size: (width, height),
  3284. inner: &lt;span style=&quot;color: #a6e22e;&quot;&gt;vec&lt;/span&gt;&lt;span style=&quot;color: #f92672;&quot;&gt;!&lt;/span&gt;[BltPixel::new(&lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;, &lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;, &lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;); width &lt;span style=&quot;color: #f92672;&quot;&gt;*&lt;/span&gt; height],
  3285. }
  3286. }
  3287. &lt;span style=&quot;color: #e6db74;&quot;&gt;/// Take our pixels and request that the UEFI GOP
  3288. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #e6db74;&quot;&gt;/// display them for us.
  3289. &lt;/span&gt;&lt;span style=&quot;color: #e6db74;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;write&lt;/span&gt;(&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;self, gop: &lt;span style=&quot;color: #66d9ef;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #a6e22e;&quot;&gt;mut&lt;/span&gt; GraphicsOutput) -&amp;gt; Result {
  3290. gop.blt(BltOp::BufferToVideo {
  3291. buffer: &lt;span style=&quot;color: #66d9ef;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #a6e22e;&quot;&gt;self&lt;/span&gt;.inner,
  3292. src: &lt;span style=&quot;color: #a6e22e;&quot;&gt;BltRegion&lt;/span&gt;::Full,
  3293. dest: (&lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;, &lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;),
  3294. dims: &lt;span style=&quot;color: #a6e22e;&quot;&gt;self&lt;/span&gt;.size,
  3295. })
  3296. }
  3297. }
  3298. &lt;span style=&quot;color: #66d9ef;&quot;&gt;impl&lt;/span&gt; Index&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;(&lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;)&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; RgbImage {
  3299. &lt;span style=&quot;color: #66d9ef;&quot;&gt;type&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;Output&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; BltPixel;
  3300. &lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;index&lt;/span&gt;(&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;self, idx: (&lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;)) -&amp;gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #a6e22e;&quot;&gt;BltPixel&lt;/span&gt; {
  3301. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; (x, y) &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; idx;
  3302. &lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;self.inner[y &lt;span style=&quot;color: #f92672;&quot;&gt;*&lt;/span&gt; self.size.&lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;+&lt;/span&gt; x]
  3303. }
  3304. }
  3305. &lt;span style=&quot;color: #66d9ef;&quot;&gt;impl&lt;/span&gt; IndexMut&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;(&lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;)&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; RgbImage {
  3306. &lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;index_mut&lt;/span&gt;(&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; self, idx: (&lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;, &lt;span style=&quot;color: #66d9ef;&quot;&gt;usize&lt;/span&gt;)) -&amp;gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #a6e22e;&quot;&gt;mut&lt;/span&gt; BltPixel {
  3307. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; (x, y) &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; idx;
  3308. &lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; self.inner[y &lt;span style=&quot;color: #f92672;&quot;&gt;*&lt;/span&gt; self.size.&lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;+&lt;/span&gt; x]
  3309. }
  3310. }
  3311. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;We also need to do some basic setup to get a handle to the UEFI
  3312. GOP via the UEFI crate (using
  3313. &lt;a href=&quot;https://docs.rs/uefi/latest/uefi/boot/fn.get_handle_for_protocol.html&quot;&gt;uefi::boot::get_handle_for_protocol&lt;/a&gt;
  3314. and
  3315. &lt;a href=&quot;https://docs.rs/uefi/latest/uefi/boot/fn.open_protocol_exclusive.html&quot;&gt;uefi::boot::open_protocol_exclusive&lt;/a&gt;
  3316. for the &lt;a href=&quot;https://docs.rs/uefi/latest/uefi/proto/console/gop/struct.GraphicsOutput.html&quot;&gt;GraphicsOutput&lt;/a&gt;
  3317. protocol), so that we have the object we need to pass to &lt;code&gt;RgbImage&lt;/code&gt; in order
  3318. for it to write the pixels to the display. The only trick here is that the
  3319. display on the booted system can really be any resolution – so we need to do
  3320. some capping to ensure that we don’t write more pixels than the display can
  3321. handle. Writing fewer than the display’s maximum seems fine, though.&lt;/p&gt;
  3322. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-rust&quot; data-lang=&quot;rust&quot;&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;praise&lt;/span&gt;() -&amp;gt; Result {
  3323. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; gop_handle &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; boot::get_handle_for_protocol::&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;GraphicsOutput&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt;()&lt;span style=&quot;color: #f92672;&quot;&gt;?&lt;/span&gt;;
  3324. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; gop &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; boot::open_protocol_exclusive::&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;lt;&lt;/span&gt;GraphicsOutput&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;gt;&lt;/span&gt;(gop_handle)&lt;span style=&quot;color: #f92672;&quot;&gt;?&lt;/span&gt;;
  3325. &lt;span style=&quot;color: #75715e;&quot;&gt;// Get the (width, height) that is the minimum of
  3326. &lt;/span&gt;&lt;span style=&quot;color: #75715e;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #75715e;&quot;&gt;// our image and the display we're using.
  3327. &lt;/span&gt;&lt;span style=&quot;color: #75715e;&quot;&gt;&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; (width, height) &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; gop.current_mode_info().resolution();
  3328. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; (width, height) &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; (width.min(KIER_WIDTH), height.min(KIER_HEIGHT));
  3329. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; &lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; buffer &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; RgbImage::new(width, height);
  3330. &lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; y &lt;span style=&quot;color: #66d9ef;&quot;&gt;in&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;..height {
  3331. &lt;span style=&quot;color: #66d9ef;&quot;&gt;for&lt;/span&gt; x &lt;span style=&quot;color: #66d9ef;&quot;&gt;in&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;0&lt;/span&gt;..width {
  3332. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; idx_r &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; ((y &lt;span style=&quot;color: #f92672;&quot;&gt;*&lt;/span&gt; KIER_WIDTH) &lt;span style=&quot;color: #f92672;&quot;&gt;+&lt;/span&gt; x) &lt;span style=&quot;color: #f92672;&quot;&gt;*&lt;/span&gt; KIER_PIXEL_SIZE;
  3333. &lt;span style=&quot;color: #66d9ef;&quot;&gt;let&lt;/span&gt; pixel &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; &lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; buffer[(x, y)];
  3334. pixel.red &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; KIER[idx_r];
  3335. pixel.green &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; KIER[idx_r &lt;span style=&quot;color: #f92672;&quot;&gt;+&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;1&lt;/span&gt;];
  3336. pixel.blue &lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt; KIER[idx_r &lt;span style=&quot;color: #f92672;&quot;&gt;+&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;2&lt;/span&gt;];
  3337. }
  3338. }
  3339. buffer.write(&lt;span style=&quot;color: #f92672;&quot;&gt;&amp;amp;&lt;/span&gt;&lt;span style=&quot;color: #66d9ef;&quot;&gt;mut&lt;/span&gt; gop)&lt;span style=&quot;color: #f92672;&quot;&gt;?&lt;/span&gt;;
  3340. Ok(())
  3341. }
  3342. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Not so bad! A bit tedious – we could solve some of this by turning
  3343. &lt;code&gt;KIER&lt;/code&gt; into an &lt;code&gt;RgbImage&lt;/code&gt; at compile-time using some clever &lt;code&gt;Cow&lt;/code&gt; and
  3344. &lt;code&gt;const&lt;/code&gt; tricks and implement blitting a sub-image of the image – but this
  3345. will do for now. This is a joke, after all, let’s not go nuts. All that’s
  3346. left with our code is for us to write our &lt;code&gt;main&lt;/code&gt; function and try and boot
  3347. the thing!&lt;/p&gt;
  3348. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-rust&quot; data-lang=&quot;rust&quot;&gt;&lt;span style=&quot;color: #75715e;&quot;&gt;#[entry]&lt;/span&gt;
  3349. &lt;span style=&quot;color: #66d9ef;&quot;&gt;fn&lt;/span&gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;main&lt;/span&gt;() -&amp;gt; &lt;span style=&quot;color: #a6e22e;&quot;&gt;Status&lt;/span&gt; {
  3350. uefi::helpers::init().unwrap();
  3351. praise().unwrap();
  3352. boot::stall(&lt;span style=&quot;color: #ae81ff;&quot;&gt;100_000_000&lt;/span&gt;);
  3353. Status::SUCCESS
  3354. }
  3355. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If you’re following along at home and so interested, the final source is over at
  3356. &lt;a href=&quot;https://gist.github.com/paultag/60334e9f6c06388cc4b1c2cf12d85085&quot;&gt;gist.github.com&lt;/a&gt;.
  3357. We can go ahead and build it using &lt;code&gt;cargo&lt;/code&gt; (as is our tradition) by targeting
  3358. the UEFI platform.&lt;/p&gt;
  3359. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ cargo build --release --target x86_64-unknown-uefi
  3360. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;h1 id=&quot;testing-the-uefi-blob&quot;&gt;Testing the UEFI Blob&lt;/h1&gt;
  3361. &lt;p&gt;While I can definitely get my machine to boot these blobs to test, I figured
  3362. I’d save myself some time by using QEMU to test without a full boot.
  3363. If you’ve not done this sort of thing before, we’ll need two packages,
  3364. &lt;code&gt;qemu&lt;/code&gt; and &lt;code&gt;ovmf&lt;/code&gt;. It’s a bit different than most invocations of qemu you
  3365. may see out there – so I figured it’d be worth writing this down, too.&lt;/p&gt;
  3366. &lt;aside class=&quot;left&quot;&gt;
  3367. It's perhaps likely that you aren't using &lt;code&gt;doas&lt;/code&gt; with Debian.
  3368. Replace &lt;code&gt;doas&lt;/code&gt; with &lt;code&gt;sudo&lt;/code&gt; if that's your thing.
  3369. &lt;/aside&gt;
  3370. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ doas apt install qemu-system-x86 ovmf
  3371. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;code&gt;qemu&lt;/code&gt; has a nice feature where it’ll create us an EFI partition as a drive and
  3372. attach it to the VM off a local directory – so let’s construct an EFI
  3373. partition file structure, and drop our binary into the conventional location.
  3374. If you haven’t done this before, and are only interested in running this in a
  3375. VM, don’t worry too much about it, a lot of it is convention and this layout
  3376. should work for you.&lt;/p&gt;
  3377. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ mkdir -p esp/efi/boot
  3378. $ cp target/x86_64-unknown-uefi/release/*.efi &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3379. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; esp/efi/boot/bootx64.efi
  3380. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;With all this in place, we can kick off &lt;code&gt;qemu&lt;/code&gt;, booting it in UEFI mode using
  3381. the &lt;code&gt;ovmf&lt;/code&gt; firmware, attaching our EFI partition directory as a drive to
  3382. our VM to boot off of.&lt;/p&gt;
  3383. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ qemu-system-x86_64 &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3384. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; -enable-kvm &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3385. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; -m &lt;span style=&quot;color: #ae81ff;&quot;&gt;2048&lt;/span&gt; &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3386. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; -smbios type&lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt;0,uefi&lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt;on &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3387. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; -bios /usr/share/ovmf/OVMF.fd &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3388. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; -drive format&lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt;raw,file&lt;span style=&quot;color: #f92672;&quot;&gt;=&lt;/span&gt;fat:rw:esp
  3389. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;If all goes well, soon you’ll be met with the all knowing gaze of
  3390. Chosen One, Kier Eagan. The thing that really impressed me about all
  3391. this is this program worked first try – it all went so boringly
  3392. normal. Truly, kudos to the &lt;code&gt;uefi&lt;/code&gt; crate maintainers, it’s incredibly
  3393. well done.&lt;/p&gt;
  3394. &lt;div&gt;
  3395. &lt;img src=&quot;https://notes.pault.ag/boot2kier/boot2kier.png&quot; /&gt;
  3396. &lt;/div&gt;
  3397. &lt;h1 id=&quot;booting-a-live-system&quot;&gt;Booting a live system&lt;/h1&gt;
  3398. &lt;p&gt;Sure, we &lt;em&gt;could&lt;/em&gt; stop here, but anyone can open up an app window and see a
  3399. picture of Kier Eagan, so I knew I needed to finish the job and boot a real
  3400. machine up with this. In order to do that, we need to format a USB stick.
  3401. &lt;strong&gt;BE SURE /dev/sda IS CORRECT IF YOU’RE COPY AND PASTING&lt;/strong&gt;. All my drives
  3402. are NVMe, so &lt;strong&gt;BE CAREFUL&lt;/strong&gt; – if you use SATA, it may very well be your
  3403. hard drive! Please do not destroy your computer over this.&lt;/p&gt;
  3404. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-txt&quot; data-lang=&quot;txt&quot;&gt;$ doas fdisk /dev/sda
  3405. Welcome to fdisk (util-linux 2.40.4).
  3406. Changes will remain in memory only, until you decide to write them.
  3407. Be careful before using the write command.
  3408. Command (m for help): n
  3409. Partition type
  3410. p primary (0 primary, 0 extended, 4 free)
  3411. e extended (container for logical partitions)
  3412. Select (default p): p
  3413. Partition number (1-4, default 1):
  3414. First sector (2048-4014079, default 2048):
  3415. Last sector, +/-sectors or +/-size{K,M,G,T,P} (2048-4014079, default 4014079):
  3416. Created a new partition 1 of type 'Linux' and of size 1.9 GiB.
  3417. Command (m for help): t
  3418. Selected partition 1
  3419. Hex code or alias (type L to list all): ef
  3420. Changed type of partition 'Linux' to 'EFI (FAT-12/16/32)'.
  3421. Command (m for help): w
  3422. The partition table has been altered.
  3423. Calling ioctl() to re-read partition table.
  3424. Syncing disks.
  3425. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Once that looks good (depending on your flavor of &lt;code&gt;udev&lt;/code&gt; you may or
  3426. may not need to unplug and replug your USB stick), we can go ahead
  3427. and format our new EFI partition (&lt;strong&gt;BE CAREFUL THAT /dev/sda IS YOUR
  3428. USB STICK&lt;/strong&gt;) and write our EFI directory to it.&lt;/p&gt;
  3429. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-txt&quot; data-lang=&quot;txt&quot;&gt;$ doas mkfs.fat /dev/sda1
  3430. $ doas mount /dev/sda1 /mnt
  3431. $ cp -r esp/efi /mnt
  3432. $ find /mnt
  3433. /mnt
  3434. /mnt/efi
  3435. /mnt/efi/boot
  3436. /mnt/efi/boot/bootx64.efi
  3437. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;Of course, naturally, devotion to Kier shouldn’t mean backdooring your system.
  3438. Disabling Secure Boot runs counter to the Core Principals, such as Probity, and
  3439. not doing this would surely run counter to Verve, Wit and Vision. This bit does
  3440. require that you’ve taken the step to enroll a
  3441. &lt;a href=&quot;https://wiki.debian.org/SecureBoot#MOK_-_Machine_Owner_Key&quot;&gt;MOK&lt;/a&gt; and know how
  3442. to use it, right about now is when we can use &lt;code&gt;sbsign&lt;/code&gt; to sign our UEFI binary
  3443. we want to boot from to continue enforcing Secure Boot. The details for how
  3444. this command should be run specifically is likely something you’ll need to work
  3445. out depending on how you’ve decided to manage your MOK.&lt;/p&gt;
  3446. &lt;div class=&quot;highlight&quot;&gt;&lt;pre&gt;&lt;code class=&quot;language-sh&quot; data-lang=&quot;sh&quot;&gt;$ doas sbsign &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3447. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; --cert /path/to/mok.crt &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3448. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; --key /path/to/mok.key &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3449. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; target/x86_64-unknown-uefi/release/*.efi &lt;span style=&quot;color: #ae81ff;&quot;&gt;\
  3450. &lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;&lt;/span&gt; --output esp/efi/boot/bootx64.efi
  3451. &lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;I figured I’d leave a signed copy of &lt;code&gt;boot2kier&lt;/code&gt; at
  3452. &lt;code&gt;/boot/efi/EFI/BOOT/KIER.efi&lt;/code&gt; on my Dell XPS 13, with Secure Boot enabled
  3453. and enforcing, just took a matter of going into my BIOS to add the right
  3454. boot option, which was no sweat. I’m sure there is a way to do it using
  3455. &lt;code&gt;efibootmgr&lt;/code&gt;, but I wasn’t smart enough to do that quickly. I let ‘er rip,
  3456. and it booted up and worked great!&lt;/p&gt;
  3457. &lt;p&gt;It was a bit hard to get a video of my laptop, though – but lucky for me, I
  3458. have a Minisforum Z83-F sitting around (which, until a few weeks ago was running
  3459. the annual http server to control my &lt;a href=&quot;https://k3xec.com/christmas/&quot;&gt;christmas tree&lt;/a&gt;
  3460. ) – so I grabbed it out of the christmas bin, wired it up to a video capture
  3461. card I have sitting around, and figured I’d grab a video of me booting a
  3462. physical device off the boot2kier USB stick.&lt;/p&gt;
  3463. &lt;div&gt;
  3464. &lt;img class=&quot;note-pad&quot; src=&quot;https://notes.pault.ag/boot2kier/z83-boot2kier.gif&quot; /&gt;
  3465. &lt;/div&gt;
  3466. &lt;p&gt;Attentive readers will notice the image of Kier is smaller then the qemu booted
  3467. system – which just means our real machine has a larger GOP display
  3468. resolution than qemu, which makes sense! We could write some fancy resize code
  3469. (sounds annoying), center the image (can’t be assed but should be the easy way
  3470. out here) or resize the original image (pretty hardware specific workaround).
  3471. Additionally, you can make out the image being written to the display before us
  3472. (the Minisforum logo) behind Kier, which is really cool stuff. If we were real
  3473. fancy we could write blank pixels to the display before blitting Kier, but,
  3474. again, I don’t think I care to do &lt;em&gt;that&lt;/em&gt; much work.&lt;/p&gt;
  3475. &lt;h1 id=&quot;but-now-i-must-away&quot;&gt;But now I must away&lt;/h1&gt;
  3476. &lt;p&gt;If I wanted to keep this joke going, I’d likely try and find a copy of the
  3477. original
  3478. &lt;a href=&quot;https://www.youtube.com/watch?v=U6EUG22elbs&quot;&gt;video when Helly 100%s her file&lt;/a&gt;
  3479. and boot into that – or maybe play a terrible midi PC speaker rendition of
  3480. &lt;a href=&quot;https://www.youtube.com/watch?v=OsbxAsdR0QI&quot;&gt;Kier, Chosen One, Kier&lt;/a&gt; after
  3481. rendering the image. I, unfortunately, don’t have any friends involved with
  3482. production (yet?), so I reckon all that’s out for now. I’ll likely stop playing
  3483. with this – the joke was done and I’m only writing this post because of how
  3484. great everything was along the way.&lt;/p&gt;
  3485. &lt;p&gt;All in all, this reminds me so much of building a homebrew kernel to boot a
  3486. system into – but like, &lt;em&gt;good&lt;/em&gt;, though, and it’s a nice reminder of both how
  3487. fun this stuff can be, and how far we’ve come. UEFI protocols are light-years
  3488. better than how we did it in the dark ages, and the tooling for this is &lt;em&gt;SO&lt;/em&gt;
  3489. much more mature. Booting a custom UEFI binary is &lt;em&gt;miles&lt;/em&gt; ahead of trying to
  3490. boot your own kernel, and I can’t believe how good the &lt;code&gt;uefi&lt;/code&gt; crate is
  3491. specifically.&lt;/p&gt;
  3492. &lt;p&gt;Praise Kier! Kudos, to everyone involved in making this so delightful ❤️.&lt;/p&gt;</description>
  3493. <pubDate>Thu, 20 Feb 2025 14:40:00 +0000</pubDate>
  3494. </item>
  3495. <item>
  3496. <title>Balint Reczey: Wireshark on Ubuntu: Stay Ahead with the Latest Releases and Nightly Builds</title>
  3497. <guid isPermaLink="false">https://balintreczey.hu/blog/?p=1025</guid>
  3498. <link>https://balintreczey.hu/blog/wireshark-on-ubuntu-stay-ahead-with-the-latest-releases-and-nightly-builds/</link>
  3499. <description>&lt;div class=&quot;wp-block-media-text is-stacked-on-mobile&quot;&gt;&lt;figure class=&quot;wp-block-media-text__media&quot;&gt;&lt;img alt=&quot;&quot; class=&quot;wp-image-1035 size-medium&quot; height=&quot;300&quot; src=&quot;https://balintreczey.hu/blog/wp-content/uploads/2025/02/Wireshark_icon_new-with-ubuntu-logo-300x300.png&quot; width=&quot;300&quot; /&gt;&lt;/figure&gt;&lt;div class=&quot;wp-block-media-text__content&quot;&gt;
  3500. &lt;p&gt;Wireshark is an essential tool for network analysis, and staying up to date with the latest releases ensures access to new features, security updates, and bug fixes. While Ubuntu’s official repositories provide stable versions, they are often not the most recent.&lt;/p&gt;
  3501. &lt;/div&gt;&lt;/div&gt;
  3502.  
  3503.  
  3504.  
  3505. &lt;p&gt;Wearing both WiresharkCore Developer and Debian/Ubuntu package maintainer hats, I’m happy to help the Wireshark team in providing updated packages for all supported Ubuntu versions through dedicated PPAs. This post outlines how you can install the latest stable and nightly Wireshark builds on Ubuntu.&lt;/p&gt;
  3506.  
  3507.  
  3508.  
  3509. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Latest Stable Releases&lt;/strong&gt;&lt;/h2&gt;
  3510.  
  3511.  
  3512.  
  3513. &lt;p&gt;For users who want the most &lt;strong&gt;up-to-date stable&lt;/strong&gt; Wireshark version, we maintain a PPA with backports of the latest releases:&lt;/p&gt;
  3514.  
  3515.  
  3516.  
  3517. &lt;p&gt;&lt;img alt=&quot;🔗&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.0.3/72x72/1f517.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Stable Wireshark PPA:&lt;/strong&gt;&lt;br /&gt;&lt;img alt=&quot;👉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.0.3/72x72/1f449.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;a href=&quot;https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable&quot;&gt;https://launchpad.net/~wireshark-dev/+archive/ubuntu/stable&lt;/a&gt;&lt;/p&gt;
  3518.  
  3519.  
  3520.  
  3521. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Installation Instructions&lt;/strong&gt;&lt;/h3&gt;
  3522.  
  3523.  
  3524.  
  3525. &lt;p&gt;To install the latest stable Wireshark version, add the PPA and update your package list:&lt;/p&gt;
  3526.  
  3527.  
  3528.  
  3529. &lt;pre class=&quot;wp-block-preformatted&quot;&gt;sudo add-apt-repository ppa:wireshark-dev/stable&lt;br /&gt;sudo apt install wireshark&lt;/pre&gt;
  3530.  
  3531.  
  3532.  
  3533. &lt;h2 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Nightly Builds (Development Versions)&lt;/strong&gt;&lt;/h2&gt;
  3534.  
  3535.  
  3536.  
  3537. &lt;p&gt;For those who want to test new features before they are officially released, nightly builds are also available. These builds track the latest development code and you can watch them cooking on their &lt;a href=&quot;https://code.launchpad.net/~wireshark-dev/+recipe/wireshark-daily-master&quot;&gt;Launchpad recipe page&lt;/a&gt;.&lt;/p&gt;
  3538.  
  3539.  
  3540.  
  3541. &lt;p&gt;&lt;img alt=&quot;🔗&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.0.3/72x72/1f517.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;strong&gt;Nightly PPA:&lt;/strong&gt;&lt;br /&gt;&lt;img alt=&quot;👉&quot; class=&quot;wp-smiley&quot; src=&quot;https://s.w.org/images/core/emoji/15.0.3/72x72/1f449.png&quot; style=&quot;height: 1em;&quot; /&gt; &lt;a href=&quot;https://code.launchpad.net/~wireshark-dev/+archive/ubuntu/nightly&quot;&gt;https://code.launchpad.net/~wireshark-dev/+archive/ubuntu/nightly&lt;/a&gt;&lt;/p&gt;
  3542.  
  3543.  
  3544.  
  3545. &lt;h3 class=&quot;wp-block-heading&quot;&gt;&lt;strong&gt;Installation Instructions&lt;/strong&gt;&lt;/h3&gt;
  3546.  
  3547.  
  3548.  
  3549. &lt;p&gt;To install the latest development version of Wireshark, use the following commands:&lt;/p&gt;
  3550.  
  3551.  
  3552.  
  3553. &lt;pre class=&quot;wp-block-preformatted&quot;&gt;sudo add-apt-repository ppa:wireshark-dev/nightly&lt;br /&gt;sudo apt install wireshark&lt;/pre&gt;
  3554.  
  3555.  
  3556.  
  3557. &lt;p&gt;&lt;strong&gt;Note:&lt;/strong&gt; Nightly builds may contain experimental features and are not guaranteed to be as stable as the official releases. Also it targets only Ubuntu 24.04 and later including the current development release.&lt;/p&gt;
  3558.  
  3559.  
  3560.  
  3561. &lt;p&gt;If you need to revert to the stable version later, remove the nightly PPA and reinstall Wireshark:&lt;/p&gt;
  3562.  
  3563.  
  3564.  
  3565. &lt;pre class=&quot;wp-block-preformatted&quot;&gt;sudo add-apt-repository --remove ppa:wireshark-dev/nightly&lt;br /&gt;sudo apt install wireshark&lt;/pre&gt;
  3566.  
  3567.  
  3568.  
  3569. &lt;p&gt;Happy sniffing! 🙂&lt;/p&gt;
  3570.  
  3571.  
  3572.  
  3573. &lt;p&gt;&lt;/p&gt;</description>
  3574. <pubDate>Tue, 18 Feb 2025 09:57:30 +0000</pubDate>
  3575. </item>
  3576. <item>
  3577. <title>Alan Pope: Spotlighting Community Stories</title>
  3578. <guid isPermaLink="true">https://blog.popey.com/2025/02/spotlighting-community-stories/</guid>
  3579. <link>https://blog.popey.com/2025/02/spotlighting-community-stories/</link>
  3580. <description>&lt;p&gt;tl;dr I’m hosting a &lt;a href=&quot;https://anchore.zoom.us/j/84874186657&quot;&gt;Community Spotlight Webinar&lt;/a&gt; today at &lt;a href=&quot;https://anchore.com/&quot;&gt;Anchore&lt;/a&gt; featuring &lt;a href=&quot;https://www.linkedin.com/in/nicolas-vuillamy/&quot;&gt;Nicolas Vuilamy&lt;/a&gt; from the &lt;a href=&quot;https://megalinter.io/latest/&quot;&gt;MegaLinter&lt;/a&gt; project. &lt;a href=&quot;https://anchore.zoom.us/j/84874186657&quot;&gt;Register here&lt;/a&gt;.&lt;/p&gt;
  3581. &lt;hr /&gt;
  3582. &lt;p&gt;Throughout my career, I’ve had the privilege of working with organizations that create widely-used open source tools. The popularity of these tools is evident through their impressive download statistics, strong community presence, and engagement both online and at events.&lt;/p&gt;
  3583. &lt;p&gt;During my time at &lt;a href=&quot;https://canonical.com/&quot;&gt;Canonical&lt;/a&gt;, we saw the tremendous reach of &lt;a href=&quot;https://ubuntu.com/&quot;&gt;Ubuntu&lt;/a&gt;, along with tools like &lt;a href=&quot;https://canonical.com/lxd&quot;&gt;LXD&lt;/a&gt;, &lt;a href=&quot;https://cloud-init.io/&quot;&gt;cloud-init&lt;/a&gt;, and yes, even &lt;a href=&quot;https://snapcraft.io/&quot;&gt;Snapcraft&lt;/a&gt;.&lt;/p&gt;
  3584. &lt;p&gt;At &lt;a href=&quot;https://www.influxdata.com/&quot;&gt;Influxdata&lt;/a&gt;, I was part of the &lt;a href=&quot;https://www.influxdata.com/time-series-platform/telegraf/&quot;&gt;Telegraf&lt;/a&gt; team, where we witnessed substantial adoption through downloads and active usage, reflected in our vibrant &lt;a href=&quot;https://www.repotrends.com/influxdata/telegraf&quot;&gt;bug tracker&lt;/a&gt;.&lt;/p&gt;
  3585. &lt;p&gt;Now at &lt;a href=&quot;https://anchore.com/&quot;&gt;Anchore&lt;/a&gt;, we see widespread adoption of &lt;a href=&quot;https://github.com/anchore/syft&quot;&gt;Syft&lt;/a&gt; for &lt;a href=&quot;https://anchore.com/sbom&quot;&gt;SBOM&lt;/a&gt; generation and &lt;a href=&quot;https://github.com/anchore/grype&quot;&gt;Grype&lt;/a&gt; for &lt;a href=&quot;https://anchore.com/container-vulnerability-scanning/&quot;&gt;vulnerability&lt;/a&gt; scanning.&lt;/p&gt;
  3586. &lt;p&gt;What makes Syft and Grype particularly exciting, beyond their permissive licensing, consistent release cycle, dedicated developer team, and &lt;a href=&quot;https://en.wikipedia.org/wiki/List_of_computing_mascots#/media/File:Syft_mascot.svg&quot;&gt;distinctive&lt;/a&gt; &lt;a href=&quot;https://en.wikipedia.org/wiki/List_of_computing_mascots#/media/File:Grype_mascot.svg&quot;&gt;mascots&lt;/a&gt;, is how they serve as building blocks for other tools and services.&lt;/p&gt;
  3587. &lt;p&gt;Syft isn’t just a standalone SBOM generator - it’s a library that developers can integrate into their own tools. Some organizations even build their own SBOM generators and vulnerability tools directly from our open source foundation!&lt;/p&gt;
  3588. &lt;div class=&quot;highlight&quot;&gt;&lt;pre tabindex=&quot;0&quot;&gt;&lt;code class=&quot;language-bash&quot; data-lang=&quot;bash&quot;&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;$ docker-scout version
  3589. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;      ⢀⢀⢀             ⣀⣀⡤⣔⢖⣖⢽⢝
  3590. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ⡠⡢⡣⡣⡣⡣⡣⡣⡢⡀    ⢀⣠⢴⡲⣫⡺⣜⢞⢮⡳⡵⡹⡅
  3591. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;  ⡜⡜⡜⡜⡜⡜⠜⠈⠈        ⠁⠙⠮⣺⡪⡯⣺⡪⡯⣺
  3592. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ⢘⢜⢜⢜⢜⠜               ⠈⠪⡳⡵⣹⡪⠇
  3593. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ⠨⡪⡪⡪⠂    ⢀⡤⣖⢽⡹⣝⡝⣖⢤⡀    ⠘⢝⢮⡚       _____                 _
  3594. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;  ⠱⡱⠁    ⡴⡫⣞⢮⡳⣝⢮⡺⣪⡳⣝⢦    ⠘⡵⠁      / ____| Docker        | |
  3595. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ⠁    ⣸⢝⣕⢗⡵⣝⢮⡳⣝⢮⡺⣪⡳⣣    ⠁      | &lt;span style=&quot;color: #f92672;&quot;&gt;(&lt;/span&gt;___   ___ ___  _   _| |_
  3596. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;        ⣗⣝⢮⡳⣝⢮⡳⣝⢮⡳⣝⢮⢮⡳            &lt;span style=&quot;color: #ae81ff;&quot;&gt;\_&lt;/span&gt;__ &lt;span style=&quot;color: #ae81ff;&quot;&gt;\ &lt;/span&gt;/ __/ _ &lt;span style=&quot;color: #ae81ff;&quot;&gt;\|&lt;/span&gt; | | | __|
  3597. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ⢀    ⢱⡳⡵⣹⡪⡳⣝⢮⡳⣝⢮⡳⡣⡏    ⡀       ____&lt;span style=&quot;color: #f92672;&quot;&gt;)&lt;/span&gt; | &lt;span style=&quot;color: #f92672;&quot;&gt;(&lt;/span&gt;_| &lt;span style=&quot;color: #f92672;&quot;&gt;(&lt;/span&gt;_&lt;span style=&quot;color: #f92672;&quot;&gt;)&lt;/span&gt; | |_| | |_
  3598. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;  ⢀⢾⠄    ⠫⣞⢮⡺⣝⢮⡳⣝⢮⡳⣝⠝    ⢠⢣⢂     |_____/ &lt;span style=&quot;color: #ae81ff;&quot;&gt;\_&lt;/span&gt;__&lt;span style=&quot;color: #ae81ff;&quot;&gt;\_&lt;/span&gt;__/ &lt;span style=&quot;color: #ae81ff;&quot;&gt;\_&lt;/span&gt;_,_|&lt;span style=&quot;color: #ae81ff;&quot;&gt;\_&lt;/span&gt;_|
  3599. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;  ⡼⣕⢗⡄    ⠈⠓⠝⢮⡳⣝⠮⠳⠙     ⢠⢢⢣⢣
  3600. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ⢰⡫⡮⡳⣝⢦⡀              ⢀⢔⢕⢕⢕⢕⠅
  3601. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ⡯⣎⢯⡺⣪⡳⣝⢖⣄⣀        ⡀⡠⡢⡣⡣⡣⡣⡣⡃
  3602. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;⢸⢝⢮⡳⣝⢮⡺⣪⡳⠕⠗⠉⠁    ⠘⠜⡜⡜⡜⡜⡜⡜⠜⠈
  3603. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;⡯⡳⠳⠝⠊⠓⠉             ⠈⠈⠈⠈
  3604. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;
  3605. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;
  3606. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;
  3607. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;version: v1.13.0 &lt;span style=&quot;color: #f92672;&quot;&gt;(&lt;/span&gt;go1.22.5 - darwin/arm64&lt;span style=&quot;color: #f92672;&quot;&gt;)&lt;/span&gt;
  3608. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;git commit: 7a85bab58d5c36a7ab08cd11ff574717f5de3ec2
  3609. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;
  3610. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;$ syft /usr/local/bin/docker-scout | grep syft
  3611. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ✔ Indexed file system /usr/local/bin/docker-scout
  3612. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt; ✔ Cataloged contents f247ef0423f53cbf5172c34d2b3ef23d84393bd1d8e05f0ac83ec7d864396c1b
  3613. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ├── ✔ Packages                        &lt;span style=&quot;color: #f92672;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;274&lt;/span&gt; packages&lt;span style=&quot;color: #f92672;&quot;&gt;]&lt;/span&gt;
  3614. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ├── ✔ File digests                    &lt;span style=&quot;color: #f92672;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;1&lt;/span&gt; files&lt;span style=&quot;color: #f92672;&quot;&gt;]&lt;/span&gt;
  3615. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   ├── ✔ File metadata                   &lt;span style=&quot;color: #f92672;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;1&lt;/span&gt; locations&lt;span style=&quot;color: #f92672;&quot;&gt;]&lt;/span&gt;
  3616. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;   └── ✔ Executables                     &lt;span style=&quot;color: #f92672;&quot;&gt;[&lt;/span&gt;&lt;span style=&quot;color: #ae81ff;&quot;&gt;1&lt;/span&gt; executables&lt;span style=&quot;color: #f92672;&quot;&gt;]&lt;/span&gt;
  3617. &lt;/span&gt;&lt;/span&gt;&lt;span style=&quot;display: flex;&quot;&gt;&lt;span&gt;github.com/anchore/syft     v1.10.0     go-module
  3618. &lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/div&gt;&lt;p&gt;&lt;em&gt;(I find it delightfully meta to discover syft inside other tools using syft itself)&lt;/em&gt;&lt;/p&gt;
  3619.  
  3620.  
  3621. &lt;center&gt;&lt;a href=&quot;https://blog.popey.com/blog/images/2025-02-13/scooby-doo-meme.png&quot;&gt;&lt;img alt=&quot;A silly meme that isn't true at all :)&quot; src=&quot;https://blog.popey.com/blog/images/2025-02-13/scooby-doo-meme.png&quot; width=&quot;540&quot; /&gt;&lt;/a&gt;&lt;/center&gt;
  3622.  
  3623. &lt;p&gt;This collaborative building upon existing tools mirrors how &lt;a href=&quot;https://linuxmint.com/&quot;&gt;Linux&lt;/a&gt; distributions often build upon other &lt;a href=&quot;http://ubuntu.com/&quot;&gt;Linux distributions&lt;/a&gt;. Like Ubuntu and Telegraf, we see countless individuals and organizations creating innovative solutions that extend beyond the core capabilities of Syft and Grype. It’s the essence of open source - a multiplier effect that comes from creating accessible, powerful tools.&lt;/p&gt;
  3624. &lt;p&gt;While we may not always know exactly how and where these tools are being used (and sometimes, rightfully so, it’s not our business), there are many cases where developers and companies want to share their innovative implementations.&lt;/p&gt;
  3625. &lt;p&gt;I’m particularly interested in these stories because they deserve to be shared. I’ve been exploring public repositories like the GitHub network dependents for &lt;a href=&quot;https://github.com/anchore/syft/network/dependents&quot;&gt;syft&lt;/a&gt;, &lt;a href=&quot;https://github.com/anchore/grype/network/dependents&quot;&gt;grype&lt;/a&gt;, &lt;a href=&quot;https://github.com/anchore/sbom-action/network/dependents&quot;&gt;sbom-action&lt;/a&gt;, and &lt;a href=&quot;https://github.com/anchore/scan-action/network/dependents&quot;&gt;scan-action&lt;/a&gt; to discover where our tools are making an impact.&lt;/p&gt;
  3626. &lt;p&gt;The adoption has been remarkable!&lt;/p&gt;
  3627. &lt;p&gt;I reached out to several open source projects to learn about their implementations, and &lt;a href=&quot;https://www.linkedin.com/in/nicolas-vuillamy/&quot;&gt;Nicolas Vuilamy&lt;/a&gt; from &lt;a href=&quot;https://megalinter.io/latest/&quot;&gt;MegaLinter&lt;/a&gt; was the first to respond - which brings us full circle.&lt;/p&gt;
  3628. &lt;p&gt;Today, I’m hosting our first &lt;a href=&quot;https://anchore.zoom.us/j/84874186657&quot;&gt;Community Spotlight Webinar&lt;/a&gt; with Nicolas to share MegaLinter’s story. &lt;a href=&quot;https://anchore.zoom.us/j/84874186657&quot;&gt;Register here&lt;/a&gt; to join us!&lt;/p&gt;
  3629. &lt;p&gt;If you’re building something interesting with &lt;a href=&quot;https://github.com/anchore&quot;&gt;Anchore Open Source&lt;/a&gt; and would like to share your story, please &lt;a href=&quot;https://popey.me/&quot;&gt;get in touch&lt;/a&gt;. 🙏&lt;/p&gt;</description>
  3630. <pubDate>Thu, 13 Feb 2025 10:00:00 +0000</pubDate>
  3631. </item>
  3632.  
  3633. </channel>
  3634. </rss>
  3635.  

If you would like to create a banner that links to this page (i.e. this validation result), do the following:

  1. Download the "valid RSS" banner.

  2. Upload the image to your own server. (This step is important. Please do not link directly to the image on this server.)

  3. Add this HTML to your page (change the image src attribute if necessary):

If you would like to create a text link instead, here is the URL you can use:

http://www.feedvalidator.org/check.cgi?url=http%3A//planet.ubuntu.com/rss20.xml

Home · About · News · Docs · Terms

 
Copyright © 2002-9 Sam Ruby, Mark Pilgrim, Joseph Walton, and Phil Ringnalda