Major Upgrade This Evening, Downtime

Both the Linux-laptop I name ‘Klystron’, and the server of this Web-site, this server being named ‘Phoenix’, received a major update this evening. On ‘Phoenix’, a total of 78 packages needed to be updated, including a Kernel-Update, and a Graphics-Driver Update. This collective update effectively converted both computers from Debian 8.7 to Debian 8.8 systems. And both updates appear to have succeeded, at first glance without breaking anything.

However, this was an update that required a reboot for ‘Phoenix’, even though this is my Web-server, and so my site was also down briefly, from approximately 20h40 until 20h50.

I am happy to say however, that ‘Phoenix’ had been running for 58 days straight, without requiring any reboot whatsoever until tonight.

Oh, but I must disappoint some of my readers with the fact that performing these updates also required I restart my ‘memcached‘ service, which means that pages or postings the readers like to visit most often will be a bit slower to fetch, until this server-side caching is replenished.

Dirk

 

Routine WordPress update this morning went smoothly.

I host this blog on my own server, thereby maintaining a version of WordPress which is a combination of the Debian / Jessie packaged version, and of plug-ins from WordPress.org . It is therefore often a source of stress for me when Debian pushes-through an update, but rather than for the reason a previous update was botched, because such an update might not be compatible with my localization of the software.

This afternoon starting from 12h04, such an update took place, putting my WordPress version at ‘4.1+dfsg-1+deb8u13‘ officially.

Thankfully, the update went smoothly, and did not appear to break anything.

Dirk

 

Unattended Upgrades Resumed Running Normally Again, This Morning.

In This earlier posting only yesterday, I had written that for an unknown reason, my unattended upgrades not only did not run automatically, but that the responsible ‘cron.daily‘ script refused to run them, when invoked manually as root.

Well today, the unattended upgrades ran normally again, and also installed numerous updates. Routinely, without apparent errors.

Dirk

 

Further Updates to Tone & Talk App

In This earlier posting, I had written about an update which was made to the “” App on Google Play, that is meant to be use with my ‘‘ Bluetooth headphones. The main new behavior which I had written about, was the fact that as of that update, I was no longer able to force the app to use the System Default Text-To-Speech Voice, which is already installed on my phone, and which happened to be higher-quality than the voice which the app had started using.

A further fact about that update was its main intention, to introduce new features. Therefore, it now has a feature, as well as enhancements to some other features, which it already had in a more-basic way.

Well since February 16, LG has released several follow-up updates, some of which may have had as purpose to fix bugs, which inevitably crop up whenever major new features are first implemented. And somewhere along the way, the voice also switched back, to the system-selected voice.

Aside from the Voice-Dictation feature, there have been enhancements to how the app uses the generated voice to send notifications to the user. But while I use the Notifications feature often, I have made no attempt to use the Voice-Dictation feature, for which reason I cannot comment on how well that works.

What I find is that if I am required to learn many new codes, for how many times I can tap, or long-press, on a small number of buttons physically on the headphones, in order to activate a certain feature, then all of that tends to become a distraction to me, personally, rather than a benefit. And so what makes me happy, is when the app continues to support features I am used to, without requiring me to relearn how to use those. And it does continue to support the old usage that way.

One oddity about this sequence of updates is the fact that I cannot be certain, whether the temporary switch to a different voice was in fact accidental or by design. The company could have switched the voice back to the way it was before, either because the first change was a bug, or simply because many users had urged them to do so.

Anyhow, I can now enjoy all the familiar features of this app, including the more-refined, 3rd-party TTS Voice.

Dirk