Language Selection

English French German Italian Portuguese Spanish

Ubuntu: Needs more QA

Filed under
Linux

I have been using Ubuntu extensively since 5.10. There are a lot of things I like about it, however here I will spend a few words about one thing that can definitively be improved: Quality Assurance. There are plenty of example of applications that are generally working but shows some bugs that are long since waiting to be fixed. Some are present in all releases, other in only the latests. I am not talking about minor bugs either. Here some:

  • ACPI (resume, suspend) is half-broken in many Centrino based laptops, which resume/suspend only at rare times. Very well documented bug, present in Edgy. People trying out Ubuntu on their new laptop are upsettly turned off by this.
  • System freeze when using ATI radeon 7000. It affects both Dapper and Edgy. A fix for Edgy is available, no sign for one in Dapper. Considering that Dapper offers Long Time Support, I would expect this bug to be fixed by now (it's been around since early 2005). Instead if you need a long time supported release and you use this graphic card (like my Poweredge server), Dapper just doesn't work. Nice.
  • VNC server 4 does not work in edgy. It is waiting for a trivial patch to be made upstream. While it works in Dapper, because of the change in fonts location in Edgy, it is badly broken in Edgy. For people using this tool to control remote machines we have to rely on older and slower versions of VNC.

You may say that those are really minor bugs, and I may agree. However they show not a great deal of care in quality assurance. Lots of resources are spent in improving the user interface, which is a good thing. However I often have the feeling that Canonical is going after new features, without spending too much time producing a really solid
release. I am not talking about exotic hardware, but pretty strightforward mainstream machines.
Am I wrong?

More in Tux Machines

Q4OS 1.4.7, Orion

Another update of Q4OS 'Orion' desktop is available, version 1.4.7. A complete Trinity repository has been added to the system as the main new feature. Access to all the Trinity software were given to users by default, there is no need to add external Trinity repositories anymore. Bunch of important packages updates and security patches has been delivered as usual. Read more

Slackware Live Edition – on its way to 1.0?

Last week the second Beta of the upcoming Slackware 14.2 was released. My goal was to have a new Beta of my liveslak ready by that time, so that I could provide new ISO images to test the Slackware Beta2 on a live medium. Unfortunately, there was an attack of the flu in my team at work and things got a bit busier than usual. There was a plus side to this: some last moment bug fixes which could be applied to my scripts – the result of having more evenings available to test. Therefore the new release is not labeled “0.5.0” but “0.5.1” Read more

Leftovers: KDE

  • Cantor migrating to Phabricator: which tools our contributors must to use
    Projects and software developed by KDE community are going to migrate for a new tool to manage our code, commits, reviews, tasks, and more. This tool is Phabricator and you can visit the instance for KDE projects in this address. Since November 2015 we are migrating Cantor to Phabricator. After our first successful review code some days ago, I decided to write a post about which tools our contributors must to use while the migration process is not finished.
  • Kdenlive's sprint report
    Last week-end, Vincent and me met in Lausanne for a Kdenlive sprint. One of our goal was to merge Gurjot Singh Bhatti's GSoC work on curves for keyframes. This was more work than expected and we spent many hours trying fix the curves and make keyframes behave correctly. Not much time was left for sleep, but we still managed to get outside to make a group (!) picture in the woods above Lausanne.
  • Jekyll 3.x
    I’ve found three different types of transition issues (it is cool to look at these in a project I do not upgrade on a daily basis like Plasma and the rest of the KDE software).
  • kdev-python on Windows: try it!
    I spent the last two or three days playing around with KDE on Windows, with the aim of getting my Python language plugin for KDevelop to run there. In the end, it wasn’t that hard to get this to work — not as hard as I would have expected it to be, anyways.

Manjaro ARM launched

Hi community, wonderful news in regard of architecture expanding within Manjaro Linux. It all started with a simple post on our developers mailing list. Somebody wants to do Manjaro for ARM … Just after one month of development our first alpha release is now ready. So what is this all about? Manjaro Arm is a project aimed to bring you the simplicity and customability that is Manjaro to ARM devices. These devices are growing in numbers and can be used for any number of applications. Most famous is the Raspberry Pi series and BeagleBoard series. Read more