Ubuntu Summit 2023

I am currently attending the Ubuntu Summit 2023 in Riga, Latvia. This is the first time I have deliberately attended an Ubuntu event. Back in 2013, I accidentally walked through what I believe was the last Ubuntu Developers Summit in Copenhagen, when I was showing some friends around Bella Sky in Copenhagen.

This time I was asked by Erich Eickmeyer if I would like to join him as a member of the Ubuntu Studio team. It has been fantastic to meet him and Eylul Dogruel from the Ubuntu Studio team. It was also fantastic to meet or see in person other members of the Linux Audio community, and other Ubuntu and Canonical people that have helped me with my Ubuntu contributions along the way.

Here are the talks I attended and meetings I had related to Ubuntu Studio:

50 things you did not know you could do with Ardour , Dr Robin Gareus (Ardour, Linux Audio)

Making a standalone effects pedal system based on embed Linux, Filipe Coelho

Live Mixing with PipeWire and Ardour/Harrison Mixbus, Erich Eickmeyer (Ubuntu / Ubuntu Studio)

Art and ownership – the confusing problem of owning a visual idea, Eylul Dogruel (Ubuntu Studio)

Ubuntu Flavour Sync meeting, Aaron Prisk (Canonical), Ana Sereijo (Canonical), Daniel Bungert (Canonical), Mr Mauro Gaspari (Canonical), Michael Hudson-Doyle (Canonical), Oliver Smith (Canonical), Mr Tim Holmes-Mitra (Canonical)

I believe talks will be uploaded onto You Tube at some point, so look out for them!

Installing Ubuntu Studio alongside Windows 10

I recently installed Ubuntu Studio 17.10 Artful Aardvark on a spare USB disk for my son. His computer had Windows 10, but there was no space inside the case for an extra internal disk. I selected the option during the install process to boot Ubuntu Studio with the Windows Boot Manager. But unfortunately, after the installation completed the computer would only ever boot into Windows – there was no Grub menu.

There was plenty of information online about this problem. As usual with these type of problems, some of the information seemed trust worthy, and some not! I thought I would record here what worked for me, in case I ever get stuck again.

It turned out that I had to go into Windows and use the command  line to point the Windows Boot Manager at the right EFI file.

As I didn’t trust the advice at first, I ran the command with the Windows “help” option (which I had forgotten after not using Windows for many years) to find out what the command did:

C:\Windows\system32>bcdedit /?

This showed me the command to investigate what the current setting was:

C:\Windows\system32>bcdedit /enum

Windows Boot Manager

——————–

identifier {bootmgr}

device partition=\Device\HarddiskVolume2

path \EFI\Microsoft\Boot\bootmgfw.efi

description Windows Boot Manager

locale da-DK

inherit {globalsettings}

default {current}

resumeobject {9c35ad51-1f6a-11e7-aeb5-f52aab87eca4}

displayorder {current}

toolsdisplayorder {memdiag}

timeout 30

Windows Boot Loader

——————-

identifier {current}

device partition=C:

path \Windows\system32\winload.efi

description Windows 10

locale da-DK

inherit {bootloadersettings}

recoverysequence {9c35ad53-1f6a-11e7-aeb5-f52aab87eca4}

recoveryenabled Yes

isolatedcontext Yes

allowedinmemorysettings 0x15000075

osdevice partition=C:

systemroot \Windows

resumeobject {9c35ad51-1f6a-11e7-aeb5-f52aab87eca4}

nx OptIn

bootmenupolicy Standard

I could then see that Windows Boot Manager was still loading the old EFI file (bootmgfw.efi). This gave me the confidence to run the magic command found on the internet to point Windows Boot Manager at the right EFI file:

C:\Windows\system32>bcdedit /set {bootmgr} path \EFI\ubuntu\shimx64.efi

After a brief panic that maybe that the installer had not installed the EFI file with that exact name, or that it had not installed Grub at all, and that I was about to brick my son’s computer (and never here the end of it), I rebooted.

Voila! Grub appeared, and I could boot into both Windows and Ubuntu Studio. Now all I have to do is buy a USB MIDI/Audio interface so we can hook up the computer to his electronic drum kit, and my old Roland keyboard.

My FOSS activities for August & September 2017

I am writing this from my hotel room in Bologna, Italy before going out for a pizza. After a successful Factory Acceptance Test today, I might also allow myself to celebrate with a beer. But anyway, here is what I have been up to in the FLOSS world for the last month and a bit.

Debian

• Uploaded gramps (4.2.6) to stretch-backports & jessie-backports-sloppy.
• Started working on the latest release of node-tmp. It needs further work due to new documentation being included etc.
• Started working on packaging the latest goocanvas-2.0 package. Everything is ready except for producing some autopkgtests.
• Moved node-coffeeify experimental to unstable.
• Updated the Multimedia Blends Tasks with all the latest ITPs etc.
• Reviewed doris for Antonio Valentino, and sponsored it for him.
• Reviewed pyresample for Antonio Valentino, and sponsored it for him.
• Reviewed a new parlatype package for Gabor Karsay, and sponsored it for him.

Ubuntu

• Successfully did my first merge using git-ubuntu for the Qjackctl package. Thanks to Nish for patiently answering my questions, reviewing my work, and sponsoring the upload.
• Refreshed the gramps backport request to 4.2.6. Still no willing sponsor.
• Tested Len’s rewrite of ubuntustudio-controls, adding a CPU governor option in particular. There are a couple of minor things to tidy up, but we have probably missed the chance to get it finalised for Artful.
• Tested the First Beta release of Ubuntu Studio 17.10 Artful and wrote the release notes. Also drafted my first release announcement on the Ubunti Studio website which Eylul reviewed and published.
• Refreshed the ubuntustudio-meta package and requested sponsorship. This was done by Steve Langasek. Thanks Steve.
• Tested the Final Beta release of Ubuntu Studio 17.10 Artful and wrote the release notes.
• Started working on a new Carla package, starting from where Víctor Cuadrado Juan left it (ITP in Debian).

My Debian & Ubuntu work from April to mid-August 2017

Okay, so I have been slack with my blogging again. I have been travelling around Europe with work quite a bit, had a short holiday over Easter in Denmark, and also had 3 weeks of Summer Holiday in Germany.

Debian

• Tidied up the packaging and tried building the latest version of libdrumstick, but tests had been added to the package by upstream which were failing. I still need to get back and investigate that.
• Updated node-seq (targeted at experimental due to the Debian Stretch release freeze) and asked for sponsorship (as I did not have DM rights for it yet).
• Uploaded the latest version of abcmidi (also to experimental), and again.
• Updated node-tmp to the latest version and uploaded to experimental.
• Worked some more on bluebird RFP, but getting errors when running tests. I still haven’t gone back to investigate that.
• Updated node-coffeeify to the latest version and uploaded to experimental.
• Uploaded the latest version of node-os-tmpdir (also to experimental).
• Uploaded the latest version of node-concat-stream (also to experimental).
• After encouragement from several Debian Developers, I applied to become a full Debian Developer. Over the summer months I worked with Santiago as my Application Manager and answered questions about working in the Debian Project.
• A web vulnerability was identified in node-concat-stream, so I prepared a fix to the version in unstable, uploaded it to unstable, and submitted a unblock request bug so that it would be fixed in the coming Debian Stretch release.
• Debian 10 (Stretch) was released! Yay!
• Moved abcmidi from experimental to unstable, adding an autopkgtest at the same time.
• Moved node-concat-stream from experimental to unstable. During the process I had to take care of the intermediate upload to stretch (on a separate branch) because of the freeze.
• Moved node-tmp to unstable from experimental.
• Moved node-os-tmpdir from experimental to unstable.
• Filed a removal bug for creepy, which seems to be unmaintained upstream these days. Sent my unfinished Qt4 to Qt5 porting patches upstream just in case!
• Uploaded node-object-inspect to experimental to check the reverse dependencies, then moved it to unstable. Then a new upstream version came out which is now in experimental waiting for a retest of reverse dependencies.
• Uploaded the latest version of gramps (4.2.6).
• Uploaded a new version of node-cross-spawn to experimental.
• Discovered that I had successfully completed the DD application process and I was now a Debian Developer. I celebrated by uploading the Debian Multimedia Blends package to the NEW queue, which I was not able to do before!
• Tweaked and uploaded the node-seq package (with an RC fix) which had been sitting there because I did not have DM rights to the package. It is not an important package anyhow, as it is just one of the many dependencies that need to be packaged for Browserify.
• Packaged and uploaded the latest node-isarray directly to unstable, as the changes seemed harmless.
• Prepared and uploaded the latest node-js-yaml to experimental.
• Did an update to the Node packaging Manual now that we are allowed to use “node” as the executable in Debian instead of “nodejs” which caused us to do a lot of patching in the past to get node packages working in Debian.

Ubuntu

• Did a freeze exception bug for ubuntustudio-controls, but we did not manage to get it sponsored before the Ubuntu Studio Zesty 17.04 release.
• Investigated why Ardour was not migrating from zesty-proposed, but I couldn’t be sure of what was holding it up. After getting some help from the Developer’s mailing list, I prepared “no change rebuild” of pd-aubio which was sponsored by Steve Langasek after a little tweak. This did the trick.
• Wrote to the Ubuntu Studio list asking for support for testing the Ubuntu Studio Zesty release, as I would be on holiday in the lead up to the release. When I got back, I found the release had gone smoothly. Thanks team!
• Worked on some blueprints for the next Ubuntu Studio Artful release.
• As Set no longer has enough spare time to work on Ubuntu Studio, we had a meeting on IRC to decide what to do. We decided that we should set up a Council like Xubuntu have. I drafted an announcement, but we still have not gone live with it yet. Maybe someone will have read this far and give us a push (or help). 🙂
• Did a quick test of Len’s ubuntustudio-controls re-write (at least the GUI bits). We better get a move on if we want this to be part of Artful!
• Tested ISO for Ubuntu Studio Xenial 16.04.3 point release, and updated the release notes.
• Started working on a merge of Qjackctl using git-ubuntu for the first time. Had some issues getting going, so I asked the authors for some advice.

My March 2017 Activities

March was a busy month, so this monthly report is a little late. I worked two weekends, and I was planning my Easter holiday, so there wasn’t a lot of spare time.

Debian

•  Updated Dominate to the latest version and uploaded to experimental (due to the Debian Stretch release freeze).
• Uploaded the latest version of abcmidi (also to experimental).
• Pinged the bugs for reverse dependencies of pygoocanvas and goocanvas with a view to getting them removed from the archive during the Buster cycle.
• Asked for help on the Ubuntu Studio developers and users mailing lists to test the coming Ubuntu Studio 17.04 release ISO, because I would be away on holiday for most of it.

Ubuntu

• Worked on ubuntustudio-controls, reverting it back to an earlier revision that Len said was working fine. Unfortunately, when I built and installed it from my ppa, it crashed. Eventually found my mistake with the bzr reversion, fixed it and prepared an upload ready for sponsorship. Submitted a Freeze Exception bug in the hope that the Release Team would accept it even though we had missed the Final Beta.
• Put a new power supply in an old computer that was kaput, and got it working again. Set up Ubuntu Server 16.04 on it so that I could get a bit more experience with running a server. It won’t last very long, because it is a 32 bit machine, and Ubuntu will probably drop support for that architecture eventually. I used two small spare drives to set up RAID 1 & LVM (so that I can add more space to it later). I set up some Samba shares, so that my wife will be able to get at them from her Windows machine. For music streaming, I set up Emby Server. I wold be great to see this packaged for Debian. I uploaded all of my photos and music for Emby to serve around the home (and remotely as well). Set up Obnam to back up the server to an external USB stick (temporarily until I set up something remote). Set LetsEncrypt with the wonderful Certbot program.
• Did the Release Notes for Ubuntu Studio 17.04 Final Beta. As I was in Brussels for two days, I was not able to do any ISO testing myself.

Other

• Measured up the new model railway layout and documented it in xtrkcad.
• Started learning Ansible some more by setting up ssh on all my machines so that I could access them with Ansible and manipulate them using a playbook.
• Went to the Open Source Days conference just down the road in Copenhagen. Saw some good presentations. Of interest for my previous work in the Debian GIS Team, was a presentation from the Danish Municipalities on how they run projects using Open Source. I noted how their use of Proj 4 and OSGeo. I was also pleased to see a presentation from Ximin Luo on Reproducible Builds, and introduced myself briefly after his talk (during the break).
• Started looking at creating a Django website to store and publish my One Name Study sources (indexes).  Started by creating a library to list some of my recently read Journals. I will eventually need to import all the others I have listed in a cvs spreadsheet that was originally exported from the commercial (Windows only) Custodian software.

Plan status from last month & update for next month

Debian

For the Debian Stretch release:

• Keep an eye on the Release Critical bugs list, and see if I can help fix any. – In Progress

Generally:

• Package all the latest upstream versions of my Debian packages, and upload them to Experimental to keep them out of the way of the Stretch release. – In Progress
• Begin working again on all the new stuff I want packaged in Debian.

Ubuntu

• Start working on an Ubuntu Studio package tracker website so that we can keep an eye on the status of the packages we are interested in. – Started
• Start testing & bug triaging Ubuntu Studio packages. – In progress
• Test Len’s work on ubuntustudio-controls – Done
• Do the Ubuntu Studio Zesty 17.04 Final Beta release. – Done
• Sort out the Blueprints for the coming Ubuntu Studio 17.10 release cycle.

Other

• Give JMRI a good try out and look at what it would take to package it. – In progress
• Also look at OpenPLC for simulating the relay logic of real railway interlockings (i.e. a little bit of the day job at home involving free software – fun!). – In progress

Resurrecting my old Drupal Site

As I have previously blogged, I recently managed to resurrect my old Drupal site that ran in the Amazon AWS cloud, and get it working again on a new host. I have just written up a summary of how I battled through the process, which can be found here.

Unfortunately, I took a long time to write it up. So it is not as detailed as I originally intended. But if like me you run a Drupal site, or you did and it is also broken, then feel free to follow the link for a read. It may at least give some ideas to follow up. I made heavy use of DrupalVM. If you are just starting out with a Drupal website, and you have more than FTP access to your hosting, I recommend using  DrupalVM (which is built with Vagrant & Ansible) for local development and testing.

February 2017 – My Free Software activities summary

When I sat down to write this blog, I thought I hadn’t got much done in February. But as it took  me quite a while to write up, there must have actually been a little bit of progress. With my wife starting a new job, there have been some adjustments in family life, and I have struggled just to keep up with all the Debian and Ubuntu emails. Anyway……..

Debian

• Backported Gramps 4.2.5 to Jessie Backports.

Ubuntu

• Tested Ubuntu Studio 16.02.2 point release, marked as ready, and updated the Release Notes.
• Started updating my previous Gramps backport in Ubuntu to Gramps 4.2.5. The package builds fine, and I have tested that it installs and works. I just need to update the bug.
• Prepared updates to the ubuntustudio-default-settings & ubuntustudio-meta packages. There were some deferred changes from before Yakkety was released, including moving the final bit of configuration left in the ubuntustudio-lightdm-theme package to ubuntustudio-default-settings. Jeremy Bicha sponsored the uploads after suggesting moving away from some transitional ttf font packages in ubuntustudio-meta.
• Tested the Ubuntu Studio 17.04 First Beta release, marked as ready, and prepared the Release Notes.
• Upgraded my music studio Ubuntu Studio computer to Yakkety 16.1o.
• Got accepted as an Ubuntu Contributing Developer by the Developer Membership Board.

Other

• After a merge of my Family Tree with the Family Tree of my wife in Gramps a long way back, I finally started working through the database merging duplicates and correcting import errors.
• Worked some more on the model railway, connecting up the other end of the tunnel section with the rest of the railway.

Plan status from last month & update for next month

Debian

For the Debian Stretch release:

• Keep an eye on the Release Critical bugs list, and see if I can help fix any. – In Progress

Generally:

• Finish the Gramps 5.2.5 backport for Jessie. – Done
  
• Package all the latest upstream versions of my Debian packages, and upload them to Experimental to keep them out of the way of the Stretch release.
• Begin working again on all the new stuff I want packaged in Debian.

Ubuntu

• Finish the ubuntustudio-lightdm-theme, ubuntustudio-default-settings transition including an update to the ubuntustudio-meta packages. – Done
• Reapply to become a Contributing Developer. – Done
• Start working on an Ubuntu Studio package tracker website so that we can keep an eye on the status of the packages we are interested in. – Started
• Start testing & bug triaging Ubuntu Studio packages. – In progress
• Test Len’s work on ubuntustudio-controls – In progress
• Do the Ubuntu Studio Zesty 17.04 Final Beta release.

Other

• Give JMRI a good try out and look at what it would take to package it. – In progress
• Also look at OpenPLC for simulating the relay logic of real railway interlockings (i.e. a little bit of the day job at home involving free software – fun!). – In progress

My Monthly Update for January 2017

It has been a quiet start to the year due to work keeping me very busy. Most of my spare time (when not sitting shattered on the sofa) was spent resurrecting my old website from backups. My son had plenty of visitors coming to visit as well, which prompted me to restart work on my model railway in the basement. Last year I received a whole heap of track, and also a tunnel formation from a friend at work. I managed to finish the supporting structure for the tunnel, and connect one end of it to the existing track layout. The next step (which will be a bit harder) is to connect the other end of the tunnel into the existing layout. The basement is one of the favourite things for me to keep my son and his friends occupied when there is a visit. The railway and music studio are very popular with the little guests.

Debian

• Packaged latest Gramps 4.2.5 release for Debian so that it will be part of the Stretch release.
• Package latest abcmidi release so it too would be part of Stretch. The upstream author had changed his website, so it took a while to locate a tarball.
• Tested my latest patches to convert Cree.py to Qt5, but found another Qt4 – Qt5 change to take into account (SIGNAL function). I ran out of time to fully investigate that one, before Creepy was booted out of testing again. I am seriously considering the removal of Cree.py from Debian, as the upstream maintainer does not seem very active any more, and I am a little tired of being upstream for a project that I don’t actually use myself. It was only because it was a reverse dependency of osm-gps-map that I originally got involved.
• Started preparing a Gramps 5.2.5 backport for Jessie, but found that the tests I enabled in unstable were failing in the Jessie build. I need to investigate this further.

Ubuntu

• Announced the Ubuntu Studio 16.02.2 point release date on the Ubuntu Studio mailing lists asking for testers. The date subsequently got put back to February the 9th.
• Upgraded my Ubuntu Studio machine from Wily to Xenial.

Other

• Resurrected my old Drupal Gammon One Name Study website. I used Drupal VM to get the site going again, before transferring it to the new webhost. It was originally a Drupal 7 site, and I did not have the required versions of Ansible & Vagrant on my Ubuntu Xenial machine, so the process was quite involved. I will blog about that separately, as it may be a useful lesson for others. As part of that, I started on a backport of vagrant, but found a bug which I need to follow up on.
• Also managed to extract my old WordPress blog posts from the same machine that had the failed Drupal instance, and import them into this blog. I also learnt some stuff in that process that I will blog about at some point.

Plan status from last month & update for next month

Debian

Before the 5th February 2017 Debian Stretch hard freeze I hope to:

• Convert Cree.py from QT4 to QT5 to allow it to re-enter Stretch. – Failed

For the Debian Stretch release:

• Keep an eye on the Release Critical bugs list, and see if I can help fix any.

Generally:

• Finish the Gramps 5.2.5 backport for Jessie.
• Package all the latest upstream versions of my Debian packages, and upload them to Experimental to keep them out of the way of the Stretch release.
• Begin working again on all the new stuff I want packaged in Debian.

Ubuntu

• Finish the ubuntustudio-lightdm-theme, ubuntustudio-default-settings transition including an update to the ubuntustudio-meta packages. – Still to do (actually started today)
• Reapply to become a Contributing Developer. – Still to do
• Start working on an Ubuntu Studio package tracker website so that we can keep an eye on the status of the packages we are interested in. – Started
• Start testing & bug triaging Ubuntu Studio packages. – Still to do
• Test Len’s work on ubuntustudio-controls – Still to do

Other

• Try and resurrect my old Gammon one-name study Drupal website from a backup and push it to the new GoONS Website project. – Done
  
• Give JMRI a good try out and look at what it would take to package it. – In progress
• Also look at OpenPLC for simulating the relay logic of real railway interlockings (i.e. a little bit of the day job at home involving free software – fun!).

Happy New Year – My Free Software activities in December 2016

So that was 2016! Here’s a summary of what I got up to on my computer(s) in December, a check of how I went against my plan, and the TODO list for the next month or so.

With a short holiday to Oslo, Christmas holidays, Christmas parties (at work and with Alexander at school, football etc.), travelling to Brussels with work, birthdays (Alexander & Antje), I missed a lot of deadlines, and failed to reach most of my Free Software goals (including my goals for new & updated packages in Debian Stretch – the soft freeze is in a couple of days). To top it all off, I lost my grandmother at the ripe old age of 93. Rest in peace Nana. I wish I could have made it to the funeral, but it is sometimes tough living on the other side of the world to your family.

Debian

• Worked on bootstrapping bluebird. Almost have it ready for sponsoring.
• Worked on converting Cree.py to Qt5.
• Packaged node-file-sync-cmp. The upload was sponsored by Pirate Praveen.

Ubuntu

• Added the Ubuntu Studio testsuites to the package tracker, and blogged about running the Manual Tests.

Other

• Finished converting my Family History Website to Jekyll.
• Had play with JMRI. Thinking of using it in the basement, and maybe packaging it for Debian.

Plan status & update for next month

Debian

Before the 5th January 2017 Debian Stretch soft freeze I hope to:

• Ensure node-tape makes it through into Stretch. – failed
• Work on all the dependencies needed to get kosmtik into Stretch. – failed
• Convert Cree.py from QT4 to QT5 to allow it to re-enter Stretch. – In progress

For the Debian Stretch release:

• Keep an eye on the Release Critical bugs list, and see if I can help fix any.

Ubuntu

• Add the Ubuntu Studio Manual Testsuite to the package tracker, and try to encourage some testing of the newest versions of our priority packages. – Done
• Finish the ubuntustudio-lightdm-theme, ubuntustudio-default-settings transition including an update to the ubuntustudio-meta packages. – Still to do
• Reapply to become a Contributing Developer. – Still to do
• Start working on an Ubuntu Studio package tracker website so that we can keep an eye on the status of the packages we are interested in. – Still to do
• Start testing & bug triaging Ubuntu Studio packages.
• Test Len’s work on ubuntustudio-controls

Other

• Continue working to convert my Family History website to Jekyll – Done
  
• Try and resurrect my old Gammon one-name study Drupal website from a backup and push it to the new GoONS Website project.
• Give JMRI a good try out and look at what it would take to package it.

Manual Tests of Ubuntu Studio Packages

We have been caught out a few times in the lead up to some of the recent releases of Ubuntu Studio, where we discovered very late that there were problems with a particular package. If you are an experienced Ubuntu Studio user, or you would like to begin helping out in the Ubuntu Studio Developers Team, why not start testing packages for the next release (Zesty 17.04)?

Step 1 – Install the Ubuntu Studio Development Release

It is not recommended to install the development release on a computer where you cannot afford to loose important data. In order of preference, install it on:

1. A spare computer with lots of audio/video hardware plugged in.
2. A spare computer.
3. Your main desktop/laptop computer with a spare hard disk plugged in.
4. A Virtual Machine on your main desktop/laptop (not really suitable for audio/video applications).

Instructions for installing the Ubuntu Studio Development Release can be found here.

Step 2 – Choose a package to test

The list of Test Cases for Ubuntu Studio Zesty 17.04 can be found on the QA Package Tracker.

Step 3 – Check package versions

It is a good idea to note down the version number of the package in the Ubuntu development release (you will need it when reporting any bugs you find), and also in Debian (and also upstream if you are keen). Let us in the Ubuntu Studio Development Team know if our package is way out of date so that we can look into what is blocking the newer version.

To find the version in Ubuntu use the search form at the bottom of this page. For Debian, use the search form at the bottom of this page. Make sure you search in the right distribution (Ubuntu – Zesty at the moment, Debian – unstable).

Step 4 – Run the test

Click on the package you want to test in the QA package tracker (see screenshot above), and the test case should appear.

Follow the steps of the test case. It is as simple as that. If you are an experienced user of that package, feel free to test further functions. The more bugs we find early in the release cycle, the more chance they will be fixed before the release.

Step 5 – Record the results & report bugs

For this step you will need to have a Launchpad login. Log into the package tracker. You can see the button on the above screen-shot. Record your results (hopefully a “pass”) in the bottom of the tracker. The results will be stored, so feel free to come back and test the same package later and add another result. If you spot a minor bug, then see if it has already been reported in Launchpad, and if not then report it. Add the bug number to the applicable column in your test result. If you cannot complete the test case due to a bug, please mark the test as failed (and add the bug number to the report). Feel free to add as many comments to the test result as you like. In particular, we are interested in your test environment (e.g. laptop/desktop/Virtual Machine), and the version of the package when you tested it.

Step 6 – Improve the Test Cases

If you have got this far, and finished a test, then well done and thank you! You deserve a break. But why stop there? Test a different package. We also need help maintaining the Test Cases. If you spot a mistake in a Test Case, or a note a possible improvement, then report a bug against the manual-tests in Launchpad. If you think we are missing a Test Case for an Ubuntu Studio package, then please also report a bug (after checking that there isn’t already one).

You could also help out further by actually correcting, or creating the Test Case yourself. There are excellent documents on how to do this on the QA wiki here:

Contributing Manual Test Cases