The Ubuntu Budgie team is delighted to announce an Ubuntu Testing Week from April 2nd to April 8th with other flavors in the Ubuntu family.
April 2nd is the beta release of what will become Ubuntu Budgie 20.04, and during this week, there will be a freeze on changes to features, the user interface and documentation. Between April 2nd and final release on April 23rd, the Ubuntu Budgie team and community will focus on ISO testing, bug reporting, and fixing bugs. Please join the community by downloading the daily ISO image and trying it out, even beginning today.
Downloads
Ubuntu Budgie ISO Download: http://cdimage.ubuntu.com/ubuntu-budgie/daily-live/current/
Other flavor downloads: http://cdimage.ubuntu.com/
QA Tracker
QA tracker: http://iso.qa.ubuntu.com/qatracker/milestones/411/builds
From this main page, click on the ‘Ubuntu Budgie Desktop amd64’ link to arrive
at the test cases page (But we encourage you to test as many Flavors as you are
willing!).
On the test cases page, you can download the ISO by clicking the ‘Link
to the download information’ and report test results to the
various test cases for Ubuntu Budgie.
If you see other flavors needing testing
on the main page, please test for them as well.
Getting Help or Discussing
Chat live on IRC (#ubuntu-quality on Freenode) or telegram (UbuntuTesters: https://t.me/UbuntuTesters) if you like, during this time of pandemic social distancing.
We can also discuss here in this thread as needed as well.
Test Targets
If you have no spare computer to use for testing, no problem! You can test without changing your system by running it in a VM (Virtual Machine) with software like Virtualbox or running it in the live session from a USB or DVD, so you can also test if your hardware works correctly. We encourage those that are willing, installing it either in a VM or on physical hardware–requires at least 6GB of hard disk space–and use it continuously for a few days, as more bugs can be exposed and reported this way.
Reporting Bugs
The easy way to report a bug is to open up Tilix (or whichever terminal you are
using) and then typing:
ubuntu-bug packagename
The packagename
is the program or application where you experience the bug.
Using ubuntu-bug
will automatically upload error logs and other files to Launchpad that developers need to fix the bug.
How Do I Find the Package Name?
Here is a beautiful youtube video showing the entire process, including one way to figure out what packagename
is appropriate.
https://www.youtube.com/watch?v=CjTyzyY9RHw
Notable Packages
The installer’s packagename
is ubiquity
. Experience tells us that it is the most useful packagename
to know for ISO testing when things go wrong with the installation. The live session software package is casper
, should you encounter bugs affecting the live session itself, not programs.
Other programs with bugs should be filed against their packages, for instance, firefox
, nemo
, vlc
, etc. Only the bug number is needed when reporting the results of a test on the QA tracker.
Applications
Please test programs/applications that you regularly use, so you can identify bugs and regressions that should be reported.
ISOs
New ISO files are built every day; always test with the most up-to-date ISO. It is easier and faster to update an existing daily ISO with the command below (first right-click on the ISO’s folder in Nemo and select Open in Terminal
) or open Tilix and cd path-to-ISO-folder
.
Zsync downloads only changes, so it’s swift.
$ zsync http://cdimage.ubuntu.com/ubuntu-budgie/daily-live/current/focal-desktop-amd64.iso.zsync
Note - You may need to install Zsync. THe can be done in the terminal with sudo apt install zsync
Thank You!
We all thank you for any help and testing provided as we all march towards a solid release.