Wednesday, 21 June 2017

Some random notes on losing my broadband connection

I first started using Ubuntu just a few weeks after Lucid Lynx was released and have used Ubuntu, Kubuntu, Xubuntu, Lubuntu and Ubuntu GNOME since then. Towards the end of 2016 I took early retirement and decided to curtail some of my Ubuntu related activities in favour of some long abandoned interests which went back to the 1960s. Although I had no intention of spending every day sat in front of a computer screen I still wished to contribute to Ubuntu but at a reduced level. However, recent problems relating to my broadband connection, which I am hoping are now over, prompted me to look closely at how I could continue to contribute to Ubuntu if I lost my "always on" internet.


Thanks to my broadband provider, whose high profile front man sports a beard and woolly jumpers, my connection changed from being one that was "always on" to one that was "usually off". There's a limit to how many times I'm prepared to reboot my cable modem on the advice of the support desk, be sent unnecessary replacement modems because the one I'm using must be faulty, to allow engineers into my home to measure signal levels, and be told the next course of action will definitely get my connection working only to find that I'm still off-line the next day and the day after. I kept asking myself: "Just how many engineers will they need to send before someone successfully diagnoses the problem and fixes it?"

Mobile broadband

Much of my recent web browsing, on-line banking, and updating of my Xubuntu installations has been done with the aid of two iPhones acting as access points while connected to the 3 and EE mobile networks. It was far from being an ideal situation, connection speeds were often very low by today's standards but "it worked" and the connections were far more reliable than I thought that they would be. A recent test during the night showed a download speed on a 4G connection to be comparable to that offered by many other broadband providers. But downloading large Ubuntu updates took a long time especially during the evening. As updating the pre-installed apps on a smart phone can quickly use up one's monthly data allowance I made myself aware of where I could find local Wi-Fi hotspots to make some of the important or large phone updates and save some valuable bandwidth for Ubuntu. Interestingly with the right monthly plan and using more appropriate hardware than a mobile phone, I could actually save some money by switching from cable to mobile broadband although I would definitely miss my 100Mb/s download speed that is most welcome when downloading ISO images or large Ubuntu updates.

ISO testing

Unfortunately these problems, which lasted for over three weeks, meant that I had to cease ISO testing due to the amount of data I would need to download several times each week. I had originally intended to get a little more involved with testing of the development release of Xubuntu during the Artful cycle but those plans were put on hold while I waited for my broadband connection to be restored and deemed to be have been fixed permanently. During this outage I still managed to submit a couple of bug reports and comment on a few others but my "always on" high speed connection was very much missed.

Connection restored!

How I continue with Ubuntu long-term will now depend on the reliability of my broadband connection which does seem to have now been restored to full working order. I'm finalising this post a week after receiving yet another visit from an engineer who restored my connection in just a matter of minutes. Cables had been replaced and signal levels had been measured and brought to within the required limits. Apparently the blame for the failure of the most recent "fix" was put solely on one of his colleagues who I am told failed to correctly join two cables together. In other words, I wasn't actually connected to their network at all. It must have been so very obvious to my modem/router which sat quietly in the corner of the room forever looking to connect to something that it just could not find and yet was unable to actually tell me so. If only such devices could actually speak....

Tuesday, 7 March 2017

Time for a change, some thanks and a return to Xubuntu

I've worked with Ubuntu for nearly seven years now and have recently realised that I have several other interests that I have been ignoring for some time. Some of those interests actually go back to the 1960s so I feel that it's now time to spend less time at the computer keyboard and, weather permitting, more time outdoors.

Ubuntu Weekly Newsletter

Last October, I received an email from Elizabeth K. Joseph informing me she was looking to cease her involvement with the Ubuntu Weekly Newsletter [UWN]. Although I was surprised at what she had to say I totally understood her reasons for wanting to move on. I know that she has worked on the newsletter from the most unusual of locations and at some very strange times of the day. What isn't always appreciated is that the current "team" is probably one of the smallest within the Ubuntu community. "Lyz" has generally held things together, guided the rest of us on what the newsletter should include, and taken ultimate responsibility for its "look and feel" and content. After contributing to over 140 issues myself, I'm also now bowing out, for a while at least.
Ubuntu Weekly Newsletter

My most recent contributions to UWN were made on a somewhat casual short term basis as I had formally left the team some months previously. I made a commitment to help with a dozen or so issues leading up to issue 500 and thought that that issue would be my last. However, for the benefit of another team member I decided to provide some assistance with issue 501. I wish the remaining members of the team well in producing future editions of the newsletter and hope that new contributors decide to join the team as anyone interested in writing article summaries is always especially welcome.

Thank you Lyz for your all your help and guidance over the past four years.


Last summer I started to reassess my needs for a personal finance application. For many years I had used Microsoft Money but switched to KMyMoney when I started using Kubuntu. As I didn't want to add numerous KDE dependencies to my Ubuntu, Ubuntu GNOME or Xubuntu installations I decided to look for a small GTK based program and found Homebank in the Ubuntu repositories. The program is developed by Maxime Doyen.

Homebank v5
Homebank v5
Unfortunately there were a number of annoying bugs in the first versions of the program that I used but I am pleased to report that the latest releases have fixed virtually all of the known and confirmed bugs. Homebank has been a pleasure to use and has been a great help over the last few months while I have been planning for my retirement and managing my very much reduced income. However, I recommend using the latest version from the official PPA as the releases in the Ubuntu repositories have become out of date and don't include the latest bug fixes.

Thank you Maxime for this superb program.


I'm currently using XubuntuUbuntu GNOME and Ubuntu Server on three laptops and a VPS hosted at DigitalOcean.

Xubuntu 16.04 LTS on my Toshiba C-50B
Xubuntu 16.04 LTS on my Toshiba C-50B
My Toshiba C-50B laptop, shown above, is for the time being my main machine but is now running what will become Xubuntu 17.04 Zesty Zapus. Although the release is still in development, it has restored a certain amount of functionality and performance that was previously lacking when running Ubuntu or Ubuntu GNOME. In due course I plan to run Xubuntu on all of my PCs or laptops as it so much lighter on resources than some of the other Ubuntu flavours that I have been using recently, a factor which is very important on my ageing or inferior hardware.

Thank you the Xubuntu team for producing what has now become my favourite Ubuntu flavour.

--- oOo ---

Of course I will continue to use Ubuntu, or one of its flavours, to keep in touch with people through email and IRC, and to manage my personal files, photographs and documents. For the time being Ubuntu will be something that I use to organise my other interests rather than being an interest that has taken up so much of my time since I first installed Ubuntu 10.04 in May 2010.

Sunday, 6 November 2016

My Ubuntu week - old hardware, a VPS and Ubuntu GNOME


I started the week with four fully functional and working laptops running Ubuntu 16.04, Ubuntu GNOME 17.04, Xubuntu 16.04 and Kubuntu 14.04. During the evening I successfully set up a VPS with DigitalOcean with the aim of staying logged on to IRC without leaving a local PC running continually. I also set up my holding pages for various domains that I use for email and dealt with various security requirements such as the firewall.

However, I was unprepared for what happened the following day.


Recently I've been using Ubuntu 16.04 on a Dell Inspirion N7110, an installation that has served me well but unfortunately during the evening I saw a number of indications that the hard disk was failing. After backing up all my personal data to my other laptops and a backup drive I started to investigate the problem by making various comparisons with another laptop. The SMART data for the disk was worrying and not unsurprisingly a few hours later the drive failed as I feared it would. Hooray for the backups!


So now down to three laptops I turned my attention to my Samsung R720 on which Kubuntu 14.04 was installed. As KDE 4 is now looking a little dated I decided to replace it with Ubuntu GNOME, a flavour that I had been testing on yet another laptop.


Although Ubuntu GNOME was running reasonably well it was too slow for my liking but at least I was on-line and able to do what I wanted or needed to do each day.


Due to the less than perfect performance of Ubuntu GNOME on my R720 I decided to install Xubuntu and later tried a live session of Ubuntu MATE but clearly the hardware is too old to successfully run a second monitor with recent releases of these flavours with an "out-of-the-box" installation. A subsequent bad install of Ubuntu meant that I'm now down to just two working machines. I'm going to have to rethink what I do with the R720 but a full reformat and installation of a flavour yet to be decided is something that I'm leaving for a rainy day.


Nearly two years ago I purchased a cheap Toshiba C-50B for testing development versions of various Ubuntu flavours. Although a little slow it runs Ubuntu, Xubuntu and Ubuntu GNOME very well. I've been testing Ubuntu GNOME on this laptop for some time and it appears to offer what I want from a modern operating system although it takes some getting used to after using Ubuntu, Kubuntu and Xubuntu for so long. I quickly reconfigured the machine to run a second monitor, plugged in a mouse and external keyboard, and then sat back and said to myself: "It works!"


With Xubuntu 16.04 available on an old Samsung R620 I'm thinking that I'm not beaten yet. It seems that the purchase of a new machine whether a laptop or a desktop is now long overdue.

Old hardware seems to work fine with the right flavour of Ubuntu until you push it to its limits but it's nice to know that if one Ubuntu flavour doesn't work for you then you can always try another.

Tuesday, 18 October 2016

More on bug reports, September 1973 and a jumping mouse

Incomplete bug reports

Since writing an earlier post on the subject I've continued to monitor new bug reports. I have been very disappointed to see that so many have to be marked as being "incomplete" as they give little information about the problem and don't really give anyone an incentive to work on and help fix. So many are very vague about the problem being reported while some are just an indication that a problem exists. Reports which just say something along the lines of:
  • help
  • bug
  • i don't know
  • dont remember
don't do a lot to point to the problem that is being reported. May be some information can be gleaned from any attached log files but please bug reporters, tell us what the problem is as it will greatly increase the chances of your issue being fixed, investigated or (re)assigned to the correct package. Reporters need to reply when asked for further information about the bug or the version of Ubuntu being used even if it is to say that, for whatever reason, the problem no longer affects them. And I say to all novice reporters: "Please don't keep the Ubuntu version or flavour that you are using a secret!"

Bug report or support request?

Some reports are probably submitted as a desperate measure when help is needed and no-one is around to help. Over the last couple of months I've seen dozens of bug reports being closed as they have "expired" because there has been no response to a request for information within 59 days of the request being made, Obviously Ubuntu users are having problems but are their issues being resolved? Are those users moving back to Windows or to another Linux distribution because they aren't getting help they need and don't know how to ask for it?

Many of the issues that I'm referring to should have been posted initially as support requests at the Ubuntu ForumsAsk Ubuntu or Launchpad Answers and then filed as bug reports once sufficient help and guidance had been obtained and the presence of a bug confirmed.

A bug with the bug reporting tool ubuntu-bug?

Sometimes trying to establish the correct package against which to file a bug is a difficult task especially if you are not conversant with the inner workings of Ubuntu. Launchpad can often guide the reporter but it seems many reports are being incorrectly filed against the xorg package in error. Bug #1631748 (ubuntu-bug selects wrong category) seems to confirm this widespread problem. If a bug is reported against the wrong package and no description of the issue is given there is no chance of the issue being investigated.

Further reading

The following links will give those who are new to bug reporting some help in filing a good bug report that can be worked on by a bug triager or developer.

How to Report Bugs
How to Report Bugs Effectively
Improving Ubuntu: A Beginners Guide to Filing Bug Reports
How do I report a bug?

To the future and some events of September 1973

In just a couple of weeks I'll no longer have to worry about getting up early for work, fighting my way though the local traffic and aiming for an 8 o'clock start which is something that I seldom manage to achieve these days. No doubt I'll be able to devote much more time to work on Ubuntu and who knows I may well revisit some of the teams and projects that I've left over the past couple of years.

Looking at Mark Shuttleworth's Wikipedia page it seems that he was born just a week or two after I started my working life in September 1973. A lot has changed since then. We didn't have personal computers or mobile phones and as far as I can remember we managed perfectly well without them. Back then I had very different interests, some of which I've recently returned to but obviously I had no idea what was in store for me around 40 years later.

Thanks for everything so far Mark!

zz = Zesty Zapus, a mouse that jumped

So we now have a code-name for the next Ubuntu release which Mark has confirmed will be Zesty Zapus, Apparently a zapus is a North American mouse that jumps. So, now that we've reached the end of the alphabet, what next?

Prediction: There will be much discussion about the code-name for the 17.10 release and it's announcement will probably be the most anticipated yet.

Saturday, 2 July 2016

Does Ubuntu have too many bugs or just too many bug reports?

As I'm now somewhat of a floating contributor to the Ubuntu project I've found myself with some spare time that I can devote to looking at some of the bug reports that are currently live on Launchpad and are awaiting attention and fixing.

Examples of poor reporting

It's great to see users taking the time to report any bugs that they find but disappointing to find so many of those reports are of such poor quality that they will never be worked on. Unfortunately, many reporters fail to respond to requests for further information and invariably their bug report is closed without any action being taken at all.

Bug titles such as:
  • i do not know
  • hhh
  • bugs
  • oops
  • reporting
  • I'm unaware of problem
are not very helpful. Bug descriptions that also have minimal content are even less so. Sometimes missing information can be gleaned from the supporting log files but that is not always the case.

I've found many many bug reports filed against the wrong package or against the Ubuntu project in general. I'm not criticising the reporters of those bugs but just commenting on something which many casual reporters seem to find difficult, that is finding the right package to file their bug against. The Bug Squad's Find the Right Package wiki page helps greatly but there is a lot there to read through and even then sometimes it is not clear unless you have a good understanding of how the various pieces of Ubuntu  and its various flavours fit together.

Corrective action

I've spent many hours over the last couple of weeks re-tasking reports and asking the reporters of numerous bugs to add information to their reports that will help see their problem addressed or at least investigated. Unfortunately, that seldom happens as often the bug report is so old that the reporter has either moved on to a later release of Ubuntu or has lost interest in the bug that they reported many months ago especially if the problem was a "one-off" problem. I have had some success refiling bugs against the correct package which has led to a developer offering to help but inevitably that just leads to a request for further information which is more often that not ignored by the reporter of the bug.

All software has bugs. We need users of software to report those bugs. Bugs need to be fixed. In order to fix the bugs developers need useful and meaningful bug reports and have their questions or requests answered. But every six months a new version of Ubuntu is released and software is updated. Bug reports can quickly become out of date and may soon refer to what is then an unsupported release.

Bug 1568604

Bug 1568604 is an excellent example of multiple reports against many packages due to the lack of knowledge of the reporter and although this bug has been confirmed by over 300 users there is little sign of this bug being fixed in the near future. I know that I'm not alone in wondering whether this bug has been reported against the correct package or not and thus brought to the attention of someone who is able to fix it.

The Bug Squad's Knowledge Base offers an enormous amount of help in creating useful bug reports but it takes a great deal of time to read though all the possibilities of how a report should be filed and against which package.

So, do we have a problem?

I'm not going to try to offer a solution to the problem of poor or incomplete bug reports, I'm hardly an expert myself. Bug reporting is not necessarily an easy process to master. Bug reports are required to be reported using English, not an easy task if you don't even speak the language that many of us take for granted. Most Launchpad users are not developers or have a detailed knowledge of the inner workings of Ubuntu and its various flavours but rely on their input to Launchpad to direct bug reports to the correct Ubuntu package and development team. Such users no doubt feel lost when they experience a problem, think they have found a bug and wait in anticipation for a reply which inevitably doesn't arrive until long after they've moved on or upgraded to a newer version of Ubuntu.

Are all bug reports actually bug reports?

I've noticed that some of these very minimal bug reports are filed by users that have just signed up to Launchpad. Are these users wondering how to file their first report? Or are these users trying to appear as a legitimate Ubuntu user? I've marked a number of reports as being "Invalid" when it's clear that the report has been filed for reasons which I won't mention here. I try to treat all reports fairly until I can ascertain that the reason for filing the bug report is not the result of the reporter actually finding a bug but some just leave me wondering.

Want to contribute to Ubuntu?

This post was not written to criticise but to draw attention to the large number of poorly filed bug reports that currently reside on Launchpad awaiting attention and marked "for expiration in xx days if no further activity occurs."

Are you thinking of how you can contribute to Ubuntu? Then please consider joining the Bug Squad and lending a hand.

Sunday, 24 April 2016

Some thoughts about Xenial development, an annoying bug and Yakkety Yak

Xenial development

Having recently relieved myself of various Ubuntu related commitments I've now become somewhat of a "floating contributor." Over the last few months I've spent a lot of time submitting and commenting on bug reports, testing ISOs and generally keeping abreast of what has been happening amongst various Ubuntu flavours especially Xubuntu. I continue to be very impressed by the hard work and enthusiasm of the "flavour" development teams who are of course all  unpaid volunteers.

Xubuntu 16.04 LTS
Xubuntu 16.04 LTS
During the latter stages of the Xenial development cycle I tried to bring certain bugs to the attention of the developers and also provided the Xubuntu team with feedback about bugs specific to their flavour. I wish I could have done a lot more but I do have other interests and commitments especially at weekends when the sun is shining and I decide I'd rather be outdoors.

An annoying Ubuntu bug

Back in May 2015, Charles Profitt wrote a blog post entitled "Ubuntu Trash Bug", in which he stated that he would not upgrade to Ubuntu 15.04 because a bug bothered him so much.

I recently remembered reading his post and thought that after working with the development version of Ubuntu 16.04 LTS for several months I've also seen a number of trivial bugs that have also bothered me greatly. They've been reported on Launchpad, added to the ISO Tracker numerous times yet Xenial Xerus has been released with a number of these bugs still very evident.

For me, the most annoying bug in Ubuntu Xenial Xerus is bug #1521302 where gnome terminal windows that have been maximised in a Unity session cannot be restored to their original size. As a keen user of the command line I really hope that this bug, which of course is affecting many more users now that 16.04 has been released, will be fixed by the time of the first point release later in the year. Sadly the bug report is starting to attract adverse comments from users who just wish to express their opinion about the general usability, as they see it, of the latest release.

My recommended alternative for now is terminator which isn't affected by this bug.

Yakkety Yak

I'm sure that I was not alone in thinking that that next release of Ubuntu might be called Yakkety Yak but then thought that there's no way that Mark Shuttleworth would ever chose such an obvious codename. Of course I was wrong.

However, Yakkety Yak, or however you might want to spell it, will always remind me of this:

Sunday, 17 April 2016

Problems with domain privacy

Over the last couple of months several of my unused domains have been due for either renewal or deletion which reminds me that about a year ago a domain that I used to receive important email was suspended. I discovered that this was due to the registrar creating fictitious contact details in order to offer domain privacy. So I moved all my domains from one registrar, based in the UK, to another but based elsewhere.

The move went well but a after making a change to my contact details I received an email from the new registrar asking for proof of my identity as Nominet, the UK domain registry, required me confirm my name and address as their checks had proved unsuccessful. They informed me that if I didn't comply with the request then my domain would be suspended after 30 days.

For the next week I frantically tried to convince the registrar that I was who I said I was but they refused to accept most of the evidence that I offered them as they insisted on having sight of an national identity card, a passport or a driving licence, none of which I currently hold. I was eventually told that my domain would be suspended and that there was nothing that they could do to help as they were merely carrying out Nominet's request.

So I contacted Nominet by telephone and asked them why they couldn't verify my name against an address that I have been living at for more than 20 years. They explained that as I had requested domain privacy from a registrar they didn't actually hold my address as it had been replaced in their database by the address of the registrar. I immediately realised that the cause of the the problem was yet again domain privacy and that providing the registrar with proof of my identity was a manual workaround to updating Nominet's database correctly. It was suggested that I logged into an account that the registrar had created but that I never knew existed, changed the contact address to reflect my own and then wait up to 24 hours for my details to be automatically checked by their systems. In just a few hours I found that my identity had been verified and the threat of the domain being suspended had been removed.

For domain privacy to work on .uk domains for registrant type "UK Individual", the registrar doesn't need to replace their customer's address with their own as address details can be suppressed by changing a flag in Nominet's database. In this way, Nominet are still aware of the registrant's real address and can still make any verification checks that they feel that they need to do. WHOIS queries then show: "The registrant is a non-trading individual who has opted to have their address omitted from the WHOIS service."

By writing this post I'm warning or at least reminding others that if a domain registry has special procedures that need to followed then the registrar not only needs to be aware of those procedures but have the appropriate systems in place. It shouldn't have been necessary for me to contact Nominet by telephone, something that may not have been practical or possible if the registry had been based overseas or only spoke in a language other than English.

A quick look at the domain privacy page on Wikipedia shows that there are several other country based registries that might also have their own peculiarities relating to what options might be available regarding the display of a domain registrant's contact details.

As a result of this very frustrating experience I moved my .uk domains to another UK based registrar which naturally understood Nominet's domain privacy procedures.