Testing Lubuntu

This section is dedicated to the development version of Lubuntu. As with all alphas and non-stable betas they are not suitable for a production environment, please take the time to read Common Questions for Testing

Ubiquity (the installer) will ask you for keyboard configuration. Be sure to say No, so you will be able to configure your keyboard properly and select your layout. Otherwise, you may not be able to use your keyboard after the reboot.

It is recommended that you join the Lubuntu mailing-list so you keep notified of changes and bugs. As always, please try to use the torrent download and keep uploading. Torrent Download shares the work between several computers and should be much faster. As it's free software, you don't need to worry about legal issues.

Lubuntu Natty 11.04 Beta 1 Released

• Announcement email with feature list

You can download from the torrent and direct download link below. We would prefer it if you used the torrent.

• Torrent Download

• Direct Download

• MD5 Checksum

Iso name: lubuntu-natty-beta1.iso

Minimal Installation and 64 Bit

• By using 32 Bit minimal or 64 Bit minimal. You can add the lubuntu-desktop package, or the lubuntu-core package. Minimal Install Instructions is where to get further details, along with a work-around for the "Unmanaged connection" bug.

General Testing

• During the release cycle, things will get broken. You can really reduce these occurrences by taking the time to read Partial Upgrades.

PPA management

• During the testing phase you may be asked via the mailing list to help test software by adding a test PPA. Sometimes it does not go too well and you need to reverse the changes. A great tool for this is apt. It's installed by default as the terminal package manager.

Usage is quite simple, just issue the following command:

sudo apt-add-repository -r ppa:Name_of_ppa

E.g., if the ppa is test/ppa the command would be:

sudo apt-add-repository -r ppa:test/ppa

Known Issues

All the known issues are mentioned in the Announcement email.

Manual test of iso and cd

• Using LXTerminal navigate to the directory with the iso file in it and issue

md5sum name_of_iso.iso

Note: iso name can be found in the released section

• It should report back the corresponding value of the MD5 Checksum file. If it does not, the download is corrupt.

• After confirming that the file has downloaded okay, you can then burn the cd (help on this can be found at Burning an ISO, there is a screen cast for using xfburn at Burning CDs/DVDs (using XFBurn)). Always burn at a slow speed (4X, or slower). Using LXTerminal issue

dd if=/dev/cdrom bs=2048 count=339675 | md5sum 

• Again it should report back the corresponding value of the MD5 Checksum file. Any other result means that the cd has not burned correctly.

Reporting bugs

• You can find information on how to report bugs at Reporting Bugs

Specific Testing

QA tests

You can do more specific tests, like ones done for the Ubuntu ISO : http://iso.qa.ubuntu.com/qatracker/test/5090

You can also test specific programs :

• PCmanFM

• LXPanel

• LXSession

• LXTerminal

• LXAppearance

• LXTask

• LXInput

• LXRandR

Performance tests

You can test the performance with the following programs :

• gtkperf : Test the performance of the gtk theme.
• phoronix-test-suite: General benchmarks and tests suit.
• bootchart: Test boot process.