Feeds:
Posts
Comments

Archive for the ‘Ubuntu’ Category

As mentioned earlier, my ‘Grive2’ solution stopped working around November 25, and that is still true today. I have copied the daily updates by hand for a few days, but that is not a permanent solution.

That left me no choice: I needed to find another tool to replace ‘Grive2’. Luckily I had already been experimenting with ‘Jdrivesync‘ somewhere in 2018. The scripts I created at the time should still have worked today (I had kept everything in place), but a first attempt failed with an unclear exception message about OAuth.

Just to be thorough I checked the app access settings on my Google account. I found no sign of ‘Grive2’, just mention of an ‘Ubuntu’ app. So I thought: let’s get rid of that and try again. But that didn’t improve the situation. Strange, because in theory ‘Jdrivesync’ was now supposed to ask for a new authorisation key, and it did not do so.

Looking in my home directory on the Xubuntu I quickly found the culprit: the file .jdrivesync does contain the accessToken and refreshToken required by Google/OAuth. Deleting the file finally did what I wanted: Jdrivesync requested a new authorisation code and ran as it is supposed to do. Nice, although I should point out that Google again complained about not having verified Jdrivesync and did I really want to continue whit that app? Of course I do!

Now I just have to adapt crontab ;-)

PS. I will also keep an eye on the ‘google-drive-ocamlfuse‘ project. That would allow me to mount the Google Drive file system on the Xubuntu machine, giving me an opportunity to learn how to use rsync… But that’s for another time!

Read Full Post »

I have been using Grive2 for a couple of years, to help me get the numbers from our photovoltaic panels into Google Drive storage. That has been going very well… until today.

The new or updated files from my panels did not show up today, although they had been created correctly on the EeePC. When I tried the Grive2 synchronisation by hand, the tool reported a 401 error: access not allowed. I suspected an issue with the Apps authorisation for the Google account concerned, so I deleted the existing ‘grive’ App and launched a new registration request. Alas, to no avail; this is what Google had to say:

Why, oh why, Google?

All I can say is: come on, Google! This has been working fine for a couple of years – why cut it off now? If you really had to cut off access, why not alert the its users first? And what is “temporarily”: a day? a week? forever?

I will copy the files by hand for a few days, but that solution won’t last long. After all, we automate processes so we don’t have to remember doing them, the more so when the process is tedious. Copying files by hand is tedious, and error-prone too…

Read Full Post »

We’re six years later, and I still haven’t gotten around to any kind of “Tinkering With The Raspberry Pi“. That does not mean that I still have to write down the production numbers from our solar panels by hand, however. The Asus eeePC, running Xubuntu and a bit of software a former colleague of mine and I hacked together, takes care of that. In doing so, it constructs a number of text files: one for each day, listing the current production in Wh every ten minutes, and one for each year, detailing the total production for each day. The backup of these files is made every day by a tool called ‘grive2‘ (but I’ll write about that later).

The setup works fine, almost all the time. But somehow the SMA Sunny Boy gets confused and creates ‘yearly’ files for years other than the current calendar year. Those files are utterly useless and clutter the hard disk as well as the backup, so I decided to get rid of them automatically. To prepare for the first days of a new year, the script should also be able to leave the file for the previous year in place – there may be two valid ‘yearly’ files in January, should I fail to archive the old year on New Year’s eve or on Jan. 1st.

To exercise my *nix shell skills, I decided to do that in ‘bash‘ rather than extend the current Python tools.

As is my habit, I decided to start with a demo script that does what I want on dummy data. For demo purposes the JDoodle website is a great resource, at least for ‘bash’ scripting (I did not try any of the 67 other languages available on the site). This allowed me to work on the code on my Mac-with-big-screen, and take the necessary screenshots for this post.

Here is the code I came up with:

Click on the image to get it in the form of a PDF file,
ready for copy/paste operations.

Nothing spectacular, as shown by the output. Now all I have to do is turn this into a little non-demo script and add it my crontab on the eeePC… Come and see in six years or so ;-)

PS. I’m just dabbling in bash scripting, so if there are better solutions for my problem, don’t hesitate to explain them to me, please.

Read Full Post »

It’s something I need to remember: how do I install an old PyUSB package on Xubuntu (or a similar Debian-based OS). Why, you ask? Because I need that old version 0.4.3 for the little script that reads the solar energy numbers from the SMA Sunny Beam.

Image of the SMA Sunny Beam monitor for our solar panel installation

The SMA Sunny Beam monitor for our solar panel installation

Luckily, it isn’t too hard to do. This is my context:

Step one is to make sure you have the required header files to compile the PyUSB package. So you open up a terminal session and execute

sudo apt-get install libusb-dev
sudo apt-get install python-dev

Step two: Extract the root folder and all the files from the PyUSB archive, and make that folder your current directory in the terminal session.

Step three: compile and install the package with this command:

sudo python setup.py install

That’s it. When all goes well, you’ll be able to verify the existence of two new files on your system, in a directory called “/usr/local/lib/python2.7/dist-packages“:

usb.so
pyusb-0.4.3.egg-info

Done!

Read Full Post »

A few weeks ago I had trouble with some of the sd-cards in my camera’s. Taking pictures was not the problem, but the cards would not show up in the Finder or on the Desktop of my Mac Mini. Having no clue as to why those cards remained invisible, I booted my preferred alternative: Xubuntu.

Again, the cards did not show their contents, but at least Xubuntu told me what was going on: “unknown filesystem type 'exfat'“. The cards were formatted in exFAT – I suppose the Fuji X20 did that. A quick search instructed me on what to do, and a few minutes later I could see (and backup) my photos. So for those of you who found themselves in the same situation, here’s “How to Mount and Use an exFAT Drive on Linux“. Easy and very useful!

Trying out my new smartphone ;-)

Trying out my new smartphone ;-)

Since then, somehow that same sd-card is now handled like any other on the Mac. Did the Mini need the latest MacOS update, or was it just the reboot that did the trick? I’ll never know, but I did learn again that Xubuntu (or Linux in general) is more than just a toy for IT geeks – it can be very useful. But you all knew that, no?

Read Full Post »

For my own comfort I am documenting this little (but essential) tidbit on my blog: How to “Remove Old Kernels In Ubuntu With One Command“. It’s a post from 2010, but it should work, according to the comments. I will admit, however, that I handled my current problem using the (manual) instructions I found on “Ask Ubuntu”.

Here's what I saw

Here’s what I saw (with a larger number)

I have been updating my system regularly, as it should, since the initial installation. Using the manual instructions mentioned, I managed to delete all 4.2 kernels and more.

Admittedly, I also issued these commands:

> sudo apt-get clean

and

> sudo apt autoremove

Yes, that last one uses ‘apt and not ‘apt-get‘ – that’s how it was spelled somewhere, and it cleaned up a lot of stuff! I’m not sure if it’s best or safest way to make sure you’re only running the latest installed kernel, though. I know Linux is for geeks <grin />, but I can’t help agreeing with one of the commenters on the post mentioned: “There’s no excuse Ubuntu doesn’t do some kind of automatic cleanup…“, or at least does so with a single, simple command or tool.

Read Full Post »

As predicted in my previous post, I installed the Ice application from the Peppermint Linux distribution on my Xubuntu PC. Although is part of the PeppermintOS distribution, installation in Xubuntu (and presumably Ubuntu as well) is quite simple. I followed the instructions from the Ubuntu Forums thread “How to get a program called “ice” from Peppermint OS 6“. In a nutshell (make that a real shell in your Terminal, please):

cd ~/Downloads
wget https://launchpad.net/~peppermintos/+archive/ubuntu/p6-release/+files/ice_5.0.1_all.deb
sudo dpkg -i ice_5.0.1_all.deb

For good measure, you should check the latest Peppermint OS release packages to make sure you have the latest stable edition of Ice – just replace ‘ice_5.0.1_all.deb‘ with the name of the latest version.

The link to my PVOutput.org site works OK in Xubuntu. But you must remember that all Ice-generated applications use the same cookies etc. as the Chromium browser they are based on. That may not be 100% what you need, but I haven’t yet found a solution for that problem (other than writing your own application).

Read Full Post »

Older Posts »