July 03, 2015

hackergotchi for SparkyLinux


SparkyLinux 4.0 Base & CLI Editions


SparkyLinux 4.0 Base and CLI Editions are available to download.

Sparky 4 is based on and fully compatible with Debian testing 9 “Stretch”.

Base Edition editions feature the core system, a lightweight desktop, wireless drivers and a few applications only.

The new iso images of Base Edition are available in 3 flavors, such as :
– Enlightenment (0.19.5)
– Openbox

CLI Edition (Command Line Interface) features the core system, wireless drivers and a few, text mode applications.
See HowTo: SparkyLinux CLI Edition

Sparky Base & CLI Editions are free of multimedia codecs and plugins.

Main keys of SparkyLinux 4.0 Base & CLI :
– full system upgrade from Debian testing repository as of 01/07/2015
– Linux kernel 4.0.5
– added support for the system installation on 32 bit machines with UEFI motherboard
– system rebranding, see HowTo: http://linuxiarze.pl/sparky-rebranding/
– new flat theme “Sparky4″ and a set of icons “Ultra-Flat-Icons”
– Tint2 panel updated up to version 0.12-rc5 (Openbox edition) from Tint2 git repos

The new default Sparky’s Enlightenment theme “Blu-Sky-Sparky” is based on work of Alberto “Duma” Verdoja and it’s licensed under CC-by. Alberto’s gallery: http://avduma.deviantart.com/gallery/

32 bit edition of SparkyLinux features Linux kernel i586 NON-PAE.
If you would like to install i686-pae kernel, you can do it via Sparky APTus-> Install-> Install i686-PAE Kernel. Just remember to refresh package list before.

The new iso images can be used to make fresh system installation.
In a case of any problem with the default installer (live-installer), try the older one (Bios machines only) via Menu-> System-> SparkyLinux (Old) Installer or launch it via the command:
sudo sparkylinux-installer gui
or (text mode)
sudo sparkylinux-installer

Live system user is: live
Password of the “live” user is: live
Password of ‘root’ (admin) of the Live system is blank (empty).

If you have SparkyLinux installed on a hard drive, make full system upgrade via ‘System Upgrade’, Synaptic or manually:
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install -f

Users of Sparky 3.6 should install ‘sparky-core’ package as well:
sudo apt-get update
sudo apt-get install sparky-core

Minimum system requirements to install SparkyLinux is:
* CPU i586 / amd64
* RAM memory:
– Enlightenment, Openbox, JWM – 256MB (recommended => 512 MB)
– CLI Edition – 128 MB (recommended => 256 MB)
– 512MB SWAP partition or bigger
* 8GB of hard drive or flash USB stick for installation
* 2GB of hard drive or flash USB stick for installation (CLI edition)
* an optical drive or an USB port

If you need a minimalistic desktop with minimal number of applications preinstalled to re-born an old computer – Sparky Openbox or JWM will be good choice:
– Sparky Opnebox 32 bit consumes ~100 MB RAM memory
– Sparky JWM 32 bit consumes ~80 MB RAM memory

Are you an owner of an old PC which can not boot Sparky from a DVD drive or USB disk?
Use Plop – See HowTo: http://sparkylinux.org/wiki/doku.php/boot_old

Live/Install iso images of Sparky 32 and 64 bit can be downloaded from our download page.

SparkyLinux Openbox


03 July, 2015 10:29PM by pavroo

hackergotchi for Ubuntu developers

Ubuntu developers

Sam Hewitt: Aeropress: My New Coffee Brewing Favourite

The Aeropress is rather a cult coffee brewer and few non-coffee-nuts know about it. But from the first cup of coffee I brewed with it, I was hooked. I now use it regularly for making coffee and my French press has been relegated to the back of the cupboard. #sorrynotsorry

The Aeropress' brilliance is in its simplicity and ease-of-brew. Measure in your coffee, briefly steep your grounds in the main chamber and then plunge the coffee through a paper filter directly into a mug. Cleanup is simple: unlock & remove the filter cap, press out the coffee puck + paper filter then rinse/wipe off the plunger. Simple.

As for brew quality, if you're consistent, it's consistent. It doesn't make the greatest cup I've ever had, but it does produce a nice, smooth cup of coffee and you can vary that quite a bit with ground levels and types.

The Aeropress' design is rather underwhelming which may make you skeptical of its capabilities. It is (to borrow a Jony Ive-ism) unapologetically plastic. Which, I suspect, makes it more durable and keeps it relatively inexpensive –you can get one for around 30$USD

The take away: it consistently brews a great cup of coffee, it takes only a few seconds to clean and it has a plethora of accessories and brewing variations –if you're into that.

03 July, 2015 09:55PM

The Fridge: Ubuntu 14.10 (Utopic Unicorn) reaches End of Life on July 23, 2015

Ubuntu announced its 14.10 (Utopic Unicorn) release almost 9 months ago, on October 23, 2014. As a non-LTS release, 14.10 has a 9-month month support cycle and, as such, the support period is now nearing its end and Ubuntu 14.10 will reach end of life on Thursday, July 23rd. At that time, Ubuntu Security Notices will no longer include information or updated packages for Ubuntu 14.10.

The supported upgrade path from Ubuntu 14.10 is via Ubuntu 15.04. Instructions and caveats for the upgrade may be found at:


Ubuntu 15.04 continues to be actively supported with security updates and select high-impact bug fixes. Announcements of security updates for Ubuntu releases are sent to the ubuntu-security-announce mailing list, information about which may be found at:


Since its launch in October 2004 Ubuntu has become one of the most highly regarded Linux distributions with millions of users in homes, schools, businesses and governments around the world. Ubuntu is Open Source software, costs nothing to download, and users are free to customise or alter their software in order to meet their needs.

Originally posted to the ubuntu-announce mailing list on Fri Jul 3 13:00:54 UTC 2015 by Adam Conrad, on behalf of the Ubuntu Release Team

03 July, 2015 09:40PM

hackergotchi for Xanadu developers

Xanadu developers

Un navegador hecho con amor

Todo lo que haces en línea tiene importancia, y cuando usas Firefox tienes el poder de mantenerlo personal. Bienvenidos a Firefox https://mozilla.org/firefox

Archivado en: Mozilla Tagged: firefox

03 July, 2015 02:30PM by sinfallas

hackergotchi for Ubuntu developers

Ubuntu developers


How to upgrade to Linux Mint 17.2

It is now possible to upgrade the Cinnamon and MATE editions of Linux Mint 17 and Linux Mint 17.1 to version 17.2.

If you’ve been waiting for this I’d like to thank you for your patience.

Upgrade for a reason

“If it ain’t broke, don’t fix it”.

You might want to upgrade to 17.2 because some bug that annoys you is fixed or because you want to get some of the new features. In any case, you should know why you’re upgrading.

As excited as we are about 17.2, upgrading blindly for the sake of running the latest version does not make much sense, especially if you’re already happy and everything is working perfectly.

Make sure to read the release notes and to known the new features so you have all the information you need before deciding whether you want to upgrade.

Be selective with updates

Upgrading to 17.2 will upgrade to Rafaela of course, but also apply all level 1 updates for you.

You do not need to apply level 2, 3, 4 or 5 updates to upgrade to the new version of Linux Mint, and doing so won’t apply these for you.

Level 4 and 5 updates are not recommended unless they bring solutions to issues you’re facing. Level 3 updates should be applied selectively and with precautions.


Upgrading to 17.2 is relatively easy:

In the Update Manager, click on the Refresh button to check for any new version of mintupdate and mint-upgrade-info. If there are updates for these packages, apply them.

Launch the System Upgrade by clicking on “Edit->Upgrade to Linux Mint 17.2 Rafaela”.

Follow the instructions on the screen.

Once the upgrade is finished, reboot your computer.

Additional info

  • The same upgrade path will be available for the Xfce and KDE editions, after they are released as stable 17.2.
  • Although Linux Mint 17.2 features a newer kernel, this upgrade does not change the kernel on your behalf. This is a decision only you should take. Should you decide to upgrade to 17.2’s recommended kernel you can do so by applying the “linux-kernel-generic” update, post-upgrade.
  • Your grub menu won’t be automatically updated on your behalf. After you rebooted the computer, you can trigger that update with the following command: “sudo update-grub”.

03 July, 2015 12:09PM by Clem

hackergotchi for Ubuntu developers

Ubuntu developers

Nekhelesh Ramananthan: Announcing the MX4 Challenge Winner

Hello everyone, I am thrilled to announce the winner of the Meizu MX4 Challenge! In the interest of being open, I thought I would share a bit on how we arrived at the winner. We received 10 submissions for the challenge and while that may not seem like a lot, I was personally looking for quality submissions, proven track-record of previous contributions and trying to bring developers and designers on the same playing field. And so in the process created strict rules and requirements that reduced the amount of people who could enter the challenge.

I reviewed the past contributions of the participants and checked whether they took the effort to present their apps nicely in the store and keep them updated. I observed that there were some apps that did not have screenshots or a proper description to help the user. Many a times I also found brilliant apps in the store that people start relying on, only later to notice that they have been abandoned. All these things affect users and I emphasised on them for this challenge.

It is not the amount of apps that you have in the store that matter, but rather the effort you put into making your app the best.

The contest submissions were reviewed by Alan Pope and myself. I must admit that at the end finding a winner was a bit difficult considering that a few of the participants and their submissions were quite good. Luckily I had Alan Pope to help me with breaking the tie.

I wish I had more devices to give away but alas there is just the one Meizu MX4 ;)

So without further ado,

Drum roll ... the winner is Brian Douglass!

Brian is the developer of the well know alternative ubuntu app store Uapp Explorer that we all have come to admire and is used by pretty much everyone to discover new apps, share public links to their apps.

For the contest, he created a UApp Explorer scope. You can check out the screenshots below.

image1 image2

Given the amount of time the developers and designers had to take part in the challenge, I am happy with the submissions and thank all the participants for their effort. I hope you would continue improving on the stuff that you worked on and help improve the Ubuntu Touch ecosystem.

03 July, 2015 12:05PM

hackergotchi for Tails


Tails 1.4.1 is out

Tails, The Amnesic Incognito Live System, version 1.4.1, is out.

This release fixes numerous security issues and all users must upgrade as soon as possible.


Upgrades and changes

  • Upgrade Tor Browser to 4.5.3, based on Firefox 31.8.0 ESR.

  • Upgrade Tor to

  • Upgrade Linux to 3.16.7-ckt11-1.

There are numerous other changes that might not be apparent in the daily operation of a typical user. Technical details of all the changes are listed in the Changelog.

Fixed problems

  • Have AppArmor deny Tor Browser access to the list of recently used files.

  • Fix automatic upgrades in Windows Camouflage mode.

Known issues

See the current list of known issues.

Download or upgrade

Go to the download page.

What's coming up?

The next Tails release is scheduled for August 11.

Have a look to our roadmap to see where we are heading to.

Do you want to help? There are many ways you can contribute to Tails. If you want to help, come talk to us!

03 July, 2015 10:34AM

hackergotchi for Ubuntu developers

Ubuntu developers

Mattia Migliorini: Install Balsamiq Mockups in Debian/Ubuntu

Balsamiq is one of the best tools for quick wireframes creation. It allows you to efficiently and quickly create mockups that give you an idea of how design elements fit in the page.

Some years ago there was a package available for the most popular Linux distributions, but since Adobe dropped support for Linux and Balsamiq is built on top of Adobe Air, nowadays they don’t support Linux neither.

As you can see from the downloads page of Balsamiq, though, it luckily works well with wine.

Install Balsamiq with WINE

First things first: install wine.

sudo apt-get install wine

Now, let’s proceed with an easy step-by-step guide.

  1. Download the Balsamiq Bundle that includes Adobe Air
  2. Open a terminal, unzip the bundle and move it to /opt (change the Downloads directory name according to your setup)
    cd Downloads
    unzip Balsamiq*
    sudo mv Balsamiq* /opt
  3. To make life easier, rename the .exe to simply balsamiq.exe
    cd /opt/Balsamiq_Mockups_3/
    mv Balsamiq\\ Mockups\\ 3.exe balsamiq.exe
  4. Now you can run Balsamiq Mockups by running it with wine
    wine /opt/Balsamiq_Mockups_3/balsamiq.exe

Add Balsamiq as an application

The last optional step can save you a lot of time in launching Balsamiq, because it saves you the hassle of writing the command in point 4 above every time you want to launch it (and remembering the Balsamiq executable location). This simply consists in creating a new desktop entry for Balsamiq, which will add it to the applications list of your operating system.

Create the file ~/.local/share/applications/Balsamiq.desktop with the following content:

[Desktop Entry]
Name=Balsamiq Mockups
Exec=wine /opt/Balsamiq_Mockups_3/balsamiq.exe

If you are on Ubuntu with Unity, you can add the following lines too:


Now, just save and have a look at your Dash or Activity Panel to see if it works.

The post Install Balsamiq Mockups in Debian/Ubuntu appeared first on deshack.

03 July, 2015 09:16AM

hackergotchi for Grml developers

Grml developers

Markus Rekkenbeil: Trivago hackathon 2015

Last weekend I was in Duesseldorf (NorthRhine-Westphalia) and attended the Trivago hackathon 2015. It was my first time as a participant and not as a guest.
I’m not a developer more an administration guy. So, it was for me a completely new challenge.
The topic for the hackathon was “a new way of travelling”.
After a good breakfast and a friendly welcome by the organizers, we started to make teams for different ideas.
I joined a spontaneously team, which formed themself after a breakfast discussion.
We were 4 members – Daniel, Jens, Tobias and me.
We made the hackathon project “firefly” (http://visitfirefly.de). A website, who will help you to find good hidden photo spots. Our goal wasn’t to make a search for only most tourist-liked places.
We decided to use the Flickr Photo API, Google JavaScript API for Headmap layering and our own RestAPI search.
After 2 days we had a running prototype. Not a very solid solution, but for us a good prototype.
Sorry for the creepy frontend design, but we aren’t frontend or CSS wizards. 😉
I met old friends and new friends. I talked about very interesting projects and ideas.
For me was the weekend a good experience! Big thanks to my team!

03 July, 2015 08:43AM

hackergotchi for HandyLinux


Les travaux en cours.


De retour de mon escapade Russe et après avoir fait connaissance avec le "peuple de Vladimir" je vois que certains membres de l'équipe redoublent d'imagination et de création.

Si vous vous rendez dans la section "Propositions et logiciels recommandés ", vous verrez que de nombreux outils "made in France HandyLinux" sont proposés, discutés, testés.

Si vous aussi vous vous sentez l'âme d'un explorateur à la découverte de nouvelles sensations, je vous présente ici 2 applications qui sont actellement proposées à la communauté.

La loupe utilisée actuellement est très pratique mais n'est pas issue d'un "paquet officiel Débian" qui fournit tous les critères de sécurité.
De plus cette application pourrait être réalisée "sur mesure" en fonction des remarques des utilisateurs.
Les détails des fonctionnalités sont sur ce fil de discssion .

Une petite application simple permettant de copier dans le presse papier des morceaux de texte pré-enregistrés.
En plus thuban vous a fait une vidéo là .

Merci encore une fois à thuban pour tous ces petits outils qui seront intégrés (ou pas) dans HandyLinux. A vous de nous dire :).

A bientôt

HandyLinux - la distribution Debian sans se prendre la tête...

03 July, 2015 08:41AM by fibi

hackergotchi for Ubuntu developers

Ubuntu developers

July 02, 2015

Brendan Perrine: lxrandr new dual screen options

One new update in Lubuntu 15.04 that hasn't got much attention is there was an update in lxrandr to 0.3.0 Has improved multiple montior support with quick options to allow you to show different screens either above or to the right of the primary monitor or a simple checkbox to for example select only show external monitor if you plug laptop into a new monitor with a much higher resolution, for example , 1920x1080 than a 1366x768 screen built into my aging over 5 year old laptop. For previous or even more complicated setups previously I had used the heavier resource wise arandr which is a quite nice application for setting up dual screen displays but written in python2 and gtk2. I remember being at ubucon at scale in 2014 and tihnking hmm it would be easier if the presenter was using arandr to setup the multiple monitor setup. Although even among people that love arandr if you install it there is also an unxrandr command that gives your current screen configuration and outputs how to recreate it with xrandr which If you bind it to a key for a multiple monitor setup could be conbient. This function needs the functionality of arandr and cannot easily be released as a standalone program.

This makes it a lot easier to set up mulitple monitors or even have just use the external one if it is much bigger and multiple monitors of different sizes doesn't appeal to you.


This is a view of a simple screenshot of this new interface. Although the manual test for lxrandr never got updated I think I started on work on that but never finished.

02 July, 2015 08:13PM

hackergotchi for Xanadu developers

Xanadu developers

Estamos a la mitad del año 11111011111

Hoy estamos en el 0 de nuestro año capicúa, atrás quedó la primera mitad del año 11111011111 (2015 en binario) y delante de nosotros queda exactamente la misma cantidad de tiempo que ha transcurrido desde el inicio del año (182 días y 12 horas), disfruten los días que quedan hasta el próximo cambio de año :D


Archivado en: Geekstuff Tagged: capicua, festividades

02 July, 2015 04:29PM by sinfallas

hackergotchi for Ubuntu developers

Ubuntu developers

hackergotchi for ArcheOS


The archaeometric excavation

Last year, on November 28, Arc-Team joined the conference "Lo scavo archeometrcio: scienza e tecnologia applicate allo scavo archeologico" (en: "The archaeometrcic excavation: science and technology applied to the archaeological excavation"), which was held in Rovereto (Italy) at the Museo Civico.
During the meeting we gave a presentation titled "Professional archaeology. Innovations and best practice with free technology. Toward an Open Research." Today I uploaded on our server the slides, so that we can share this work (like always under Creative Commons Attribution - CC BY).
As usual the presentation has been done with impress.js through the Graphical User Interface Strut (both GPL licensed) and it is optimized for Firefox or Iceweasel (better visualized here).

Here is a little explanation regarding the single slides:

A fast presentation regarding Arc-Team.
An animation representing the importance of geocoding in archaeology (from space to site).

Differential GPS and Total Station: the main tools needed by archaeologists on the field (to georeference every single element of the archaeological record).

Some examples of geocoding in archaeology: everyday work, project in extreme conditions and missions abroad...

... survay and excavations

In survay projects the geocoding tolerance for archaeology is higher, so that we are testing alternative solutions to build a low-cost and open source GPS with centimetric accuracy, using the software RTKLIB (or its port in Android)

All the recorded data (in 2D and 3D) can be imported into an open source GIS.

For aerial archaeology it since 2008 we are working with open source DIY UAV, like the UAVP or the KKcopter (in the slide).

Our last UAV prototype and an example of 3D pointcloud form aerial pictures.

Since 2014 we are testing DIY camera (using the filter of Public Lab) for NDVI and NGB pictures in archaeological remote sensing.

Just removing the IR filter, a normal camera can be used for endoscopic prospections in low light conditions.

In the field of geophysical prospections we use a DIY  machine for Electrical Resistivity Imaging. The data can be visualized in a GIS (e.g. GRASS GIS in the slide), using the east and north and the resistivity values.

Some geoarchaeological analyses can be performed directly on the field, like the settlement test (using the soil triangle) for the texture or the lithologic recognition for the skeleton.

Also some basic analytical chemistry can help during the excavation (giving indications on the ancient use of the soil), to verify the presence/absence of phosphates or of organic remains.

Other preliminary laboratory (flotation and sieving) analyses can prepare the samples for further investigation. Also in this case we use a DIY machine.

Colorimetry can be performed in many ways. Currently we are testing different options, like the open source spectrometer of Public Lab.

For some laboratory geoarchaeological analysis (e.g. microscopic morphology) we use normal optic microscopes, while for more advanced studies we externalize the service (e.g. SEM or energy dispersive x-ray spectroscopy)

Currently we are testing the potentialities of the FLOSS MorphoJ to speed up the process in carpological remains recognition

To document archaeozoological remains in the field, we use the standard digital documentation techniques (in 2 and 3D), with FLOSS (e.g. bidimensional photomapping with the Aramus method or 3D recording through SfM and MVSR)

In the evolutionary anthropology field we developed a new technique (anatomical deformation) thanks to the FLOSS Blender

The same software (Blender) is used in the process of archaeological forensic facial reconstruction

Open source GIS (e.g. GRASS) are the main software we use to process and manage the recorded data

Thanks to open source UAV and Blender we experimented new ways to disclose archaeological data in a four-dimensional way (x,y,z,t)

A more detailed explanation of the entire presentation will come soon with the related article. For the topics which were already discussed in AOTR, I suggest to read the related post (see the above bibliography). For the latest experiment (e.g. near infrared, NDVI and NGB; Electrical Resistivity Imaging; Sedimentation test; litologic recognition on the field; flotation and sieving; colorimetry; microscopic morphology; MorphoJ;), we will try to write something as soon as possible.

Bibliography (from ATOR):

3D and 4D GIS

SfM and MVSR

Aerial 3D documentation

Archaeological endoscopy



Evolutionary anthropology
Anatomical Deformation Technique (ADT): validation; ADT Paranthropus boisei; ADT Homo rodhesiensis;

Archaeological Forensic Facial Reconstruction (AFFR); Digital AFFR: technique validation; AFFR: state of the arts; AFFR: poster;

Archaeological dissemination
Caldonazzo Castle 4D (case of study);

02 July, 2015 02:38PM by Luca Bezzi (noreply@blogger.com)

hackergotchi for Ubuntu developers

Ubuntu developers

Costales: BQ E4.5 | BQ E5 | Meizu MX4 - ¿Cual comprar?

Cada vez disponemos de más móviles para comprar con Ubuntu Phone.
He tenido la suerte de poder probar los 3 modelos. Dispones de las reviews correspondientes aquí: BQ E4.5, BQ E5 y Meizu MX4.

Con esta perspectiva, ¿Qué modelo comprar?

E5 | MX4 | E4.5

El BQ E4.5 es el que tiene el sistema operativo más fluido y es que salir 5 meses antes que los otros dos influye.

Yo personalmente compraría el MX4 por un sólo motivo: Su extraordinaria cámara. También sobresale por su pantalla con una resolución envidiable.

Si se busca duración de batería, el E5 es el que mejor resultado obtiene, pues su procesador es igual que el E4.5 pero con más mAh de batería.

Por precio, compraría el E5, por 30€ más se obtienen muchas más prestaciones que el E4.5.

E5 | MX4 | E4.5

Por diseño: MX4
Por pantalla: MX4
Por cámara trasera: MX4
Por cámara delantera (para selfies): E5
Por conectividad de datos: MX4
Por batería: E5
Por precio: E4.5
Por almacenamiento: E5
Por potencia (CPU+RAM): MX4

Este última valoración por potencia, puede que sea importante a medio plazo, para usar el móvil como CPU con un monitor.

Fotografías por David Castañón bajo licencia CC BY 3.0.

02 July, 2015 02:06PM by Marcos Costales (noreply@blogger.com)

hackergotchi for Grml developers

Grml developers

Michael Prokop: HAProxy with Debian/squeeze clients causing random “Hash Sum mismatch”

Update on 2015-07-02 22:15 UTC: as Petter Reinholdtsen noted in the comments:

Try adding /etc/apt/apt.conf.d/90squid with content like this:

Acquire::http::Pipeline-Depth 0;

It turn off the feature in apt confusing proxies.

” – this indeed avoids those “Hash Sum mismatch” failures with HAProxy as well. Thanks, Petter!

Many of you might know apt’s “Hash Sum mismatch” issue and there are plenty of bug reports about it (like #517874, #624122, #743298 + #762079).

Recently I saw the “Hash Sum mismatch” usually only when using “random” mirrors with e.g. httpredir.debian.org in apt’s sources.list, but with a static mirror such issues usually don’t exist anymore. A customer of mine has a Debian mirror and this issue wasn’t a problem there neither, until recently:

Since the mirror also includes packages provided to customers and the mirror needs to be available 24/7 we decided to provide another instance of the mirror and put those systems behind HAProxy (version 1.5.8-3 as present in Debian/jessie). The HAProxy setup worked fine and we didn’t notice any issues in our tests, until the daily Q/A builds randomly started to report failures:

Failed to fetch http://example.org/foobar_amd64.deb Hash Sum mismatch

When repeating the download there was no problem though. This problem only appeared about once every 15-20 minutes with random package files and it affected only Debian/squeeze clients (wheezy and jessie aren’t affected at all). The problem also didn’t appear when directly accessing the mirrors behind HAproxy. We tried plenty of different options for apt (Acquire::http::No-Cache=true, Acquire::http::No-Partial=true,…) and also played with some HAProxy configurations, nothing really helped. With apt’s “Debug::Acquire::http=True” we saw that there really was a checksum failure and HTTP status code 102 (‘Processing‘, or in terms of apt: ‘Waiting for headers‘) seems to be involved. The actual problem between apt on Debian/squeeze and HAProxy is still unknown to us though.

While digging deeper into this issue is on my todo list yet, I found a way to avoid those “Hash Sum mismatch” failures: switch from http to https in sources.list. As soon as https is used the problem doesn’t appear anymore. I’m documenting it here just in case anyone else should run into it.

02 July, 2015 10:17AM

hackergotchi for Ubuntu developers

Ubuntu developers

Riccardo Padovani: My opensource contributions in Jun 15

June has been a great month. A new Ubuntu device, the Meizu MX4, reached the market. I wrote a little review about it, and now I use it as mainly phone.

Also, I went to the Hello Tomorrow Conference. An incredible [experience][htc15].

And last but not least, the Discerning Duck scope had an update.

But now let’s see what I did in the last month for the opensource world :-)


In June I received 5 euros of donations. I’ll spare them to renew the VPS later this year.

If you find valuable my contribute to opensource world, please consider to make me a donation.

What I did

In June I focused mainly on webbrowser. Now there are 8 branches waiting for a review ready to land in the browser app, with little and big improvements!

I also created a new branch for Oxide, should be merged in next days.

Other than that, I did a lot of code reviews, both for the webbrowser, to have the best experience possible, and for some core apps (calculator and reminders).

Also, I’m working on a new app that I hope to publish in a couple of weeks ;-)

If you like my work and want to support me, just send me a Thank you! by email or offer me a beer:-)


02 July, 2015 10:00AM

Joe Liau: What Happens When: Deranged DIYs and Humbled How-Tos


dah-di-dah what?

Whiskey Hotel Whiskey

You have just downed a bottle of whiskey. You go to hotel, and then you have some more whiskey. These steps, while extremely repeatable, will have drastically different outcomes for each person. One of these outcomes is a Do-It-Yourself disaster. Another is “How to get a hangover… or worse,” depending on what else is brought into the mix.

So, what happens when you follow this recipe?

The culture of the internet world is changing. Creation is shifting to curation. With so much information right at your fingertips, almost anyone can learn how to do almost anything. A quick g00gle search will already tell you how to get 6-pack abs, and build a flame thrower. i.e. You don’t need to re-write that and create more GI. However, what we don’t know, and possibly want to know, is what happens/happened when you got your abs and made a dangerous weapon. This is unique information that only you can produce. Thus, we should continue to create.

DIY ain’t dead. You should absolutely do things yourself for the learning experience. This also does not mean that you should not write How-Tos; there are tonnes of things that we don’t know how to do, or have learned how to do incorrectly.

But, don’t stop there (or do if it has been over done). Teach us about your experience. Tell us What Happens When (WHW).

What? So What? Now What?

WHW as performance art?

WHW as performance art?

Robots are better than I am at my job, or they soon will be. In education, many kids have lost motivation and can’t concentrate. The internet is a better teacher than I am. Children know what they are supposed to learn, and in general they understand why they are supposed to learn it (they just saw it all online yesterday). However, a frequently missed component in education is what we can or should actually do with that knowledge. i.e. What happens when I apply this information?

I was recently taught this process of inquiry:

What: What are you taking about?
So What: Why are you talking about it?
Now What: What do you do about it?

The last piece is really what still makes community and classrooms relevant, but sometimes we forget to teach that. Maybe it’s because of our consumption-only habits. Maybe it’s because someone wants to keep us under control. Maybe it’s because we keep stopping at “maybe,” and only choose to watch from behind the glass.

Technology is here.
It will can help us.
Now what do we do with it?

Caveat Emptor Rex


I’m Steggers

“What part of recreating dinosaurs and putting them in a theme park was a good idea?”

Many story premises are ridiculous, but it is undeniable that they are also entertaining. If we wrote a story exclusively about “how to extract dinosaur DNA,” then we might be sorely disappointed; however, we can’t help but wonder WHW we bring dinosaurs back to life and put them in close proximity to people. (SPOILER ALERT: things get ate).

The Jurassic world in which we live has an appetite of curiosity. In some cases, our brains are still quite primitive. We do a lot of stupid things all the time that slip through the systems unobstructed. So, Mr. Chricton’s premise is actually extremely insightful, and is an extreme example of the primal nature that continues to run the world today. Not to mention, it’s extremely interesting. Extreme!

If you bought into the idea of adding more value to the things that we create, then we must also be aware of the underlying dangers that are already present.

WHW is actually responsible for some of the dino dung that we’re facing today. When we keep feeding our ancient reptilian brains with consumer urges, we just perpetuate the problem. WHW we make it bigger, faster, scarier? (SPOILER ALERT: things get ate bigger, faster, scarier). Sometimes the consumer doesn’t know what’s best for itself; what it wants (or has been trained to want), isn’t always what it needs.

We need to run the scenarios in our heads first. We need to focus on what benefits the whole rather than what gets me more tokens. We need to then make those things happen.

When we get involved in the outcome, then we can get out of the “safety” of our voyeuristic tendencies that lead to destructive demands and curmudgeonist complaints.

We need a deep sense of community.

OUR Situation

Hello there

Hello there

The Obvious Ubuntu Relevance is right in front of our faces. That circle of friends is severely effected by the action or inaction of each member.

I have bought an Ubuntu device because it’s awesome, but what am I going to do with it?

I have joined an Ubuntu circle because I need community, but what am I going to contribute?

I know how to do these things. But, WHW I actually do something with this knowledge?

It’s cool to sit back and gain confidence—be rational—before producing something in the community, but it’s important that we don’t get stuck at the instructional stage. Furthermore, our contributions need not be that extreme!

Consistent application, experience, and collaboration should lead to progress.

A little less. A little more. (source)

A little less… A little more… (source)

02 July, 2015 03:54AM

Nicholas Skaggs: Have you tried writing a testsuite?

It's never been easier to write tests for your application! I wanted to share some details on the new documentation and other tidbits that will help you ensure your application has a nice testsuite. If you've used the SDK in the past, you understand how nice it can make your development workflow. Writing code and running it on your desktop, device, or emulator is a snap.

Fortunately, having a nice testsuite for your application can also be just as easy. First, you will notice that now all of the wizards inside the SDK now come with nice testsuites already in place. They are ready for you to simply add-on more tests. The setup and heavy lifting is done. See for yourself!

Secondly, developer.ubuntu.com has a great section on every level of testing; no matter which language you use with the SDK. You'll find API references for the tools and technology used, along with helpful guides to get you in the proper mindset.

For autopilot itself, there's also API documentation for the various 'helpers' that will make writing tests much easier for you. In addition, there's a guide to running autopilot tests. This has been made even easier by the addition of Akiva's Autopilot plugin inside the SDK. I'll be sharing details on this as soon as it's packaged, but you can see a sneak peek in this video.

Finally, you will find a guide on how to structure your functional tests. These are the most demanding to write, and it's important to ensure you write your tests in a maintainable way. Don't forget about the guide on writing good functional tests either.

No matter what language or level you write tests for, the guides are there to help you. Why not trying adding a test or two to your project? If you are new, check out one of the wizards and try adding a simple testcase. Then apply the same knowledge (and templated code!) to your own project. Happy test writing!

02 July, 2015 03:16AM by Nicholas Skaggs (noreply@blogger.com)

Nicholas Skaggs: Snappy Open House!

Introducing Snappy Open Houses! Snappy represents some new and exciting possibilities for ubuntu. A snappy open house is your chance to get familiar with the technology while helping test and break things ! We plan to do an open house before each release as a chance for everyone to interact and provide feedback and help with testing. As such, this is a great way to get started in the snappy world!

So what exactly do I mean by an open house? We want to encourage the community to test with us, explore new features, check for possible regressions and exercise the documentation.  An open house is a chance to come and meet the snappy team developers and help QA test the new image.

During the open house, we'll host a live broadcast on ubuntuonair.com. As part of the broadcast, we'll speak with some of the developers behind snappy and show off new features in the upcoming release. We'll also demonstrate how to flash and test the new release so you can follow along and help test. Finally we'll answer any questions you have and stick around on IRC for a bit to discuss any issues found during testing.

In other words, it's time intended for you to come and try out snappy! I know what you are thinking, "I don't have a cool IoT device to run snappy with". You are in luck! You can run snappy on your desktop and laptop. You don't need a device as you can install snappy on your local machine via kvm. If you do have a device, bring it and prepare to have some fun!

The first of these snappy open houses will be July 7th at 1400 UTC. Please stop by and help test with us, try out snappy, and meet the snappy team!

You can find out more information on the wiki. Mark your calendars and see you next Tuesday!

02 July, 2015 02:54AM by Nicholas Skaggs (noreply@blogger.com)

July 01, 2015

Sebastian Kügler: Convergence through Divergence

It’s that time of the year again, it seems: I’m working on KPluginMetaData improvements.

In this article, I am describing a new feature that allows developers to filter applications and plugins depending on the target device they are used on. The article targets developers and device integrators and is of a very technical nature.

Different apps per device

This time around, I’m adding a mechanism that allows us to list plugins, applications (and the general “service”) specific for a given form factor. In normal-people-language, that means that I want to make it possible to specify whether an application or plugin should be shown in the user interface of a given device. Let’s look at an example: KMail. KMail has two user interfaces, the desktop version, a traditional fat client offering all the features that an email client could possibly have, and a touch-friendly version that works well on devices such as smart phones and tablets. If both are installed, which should be shown in the user interface, for example the launcher? The answer is, unfortunately: we can’t really tell as there currently is no scheme to derive this information from in a reliable way. With the current functionality that is offered by KDE Frameworks and Plasma, we’d simply list both applications, they’re both installed and there is no metadata that could possibly tell us the difference.

Now the same problem applies to not only applications, but also, for example to settings modules. A settings module (in Frameworks terms “KCM”) can be useful on the desktop, but ignored for a media center. There may also be modules which provide similar functionality, but for a different use case. We don’t want to create a mess of overlapping modules, however, so again, we need some kind of filtering.

Metadata to the rescue

Enter KPluginMetaData. KPluginMetaData gives information about an application, a plugin or something like this. It lists name, icon, author, license and a whole bunch of other things, and it lies at the base of things such as the Kickoff application launcher, KWin’s desktop effects listing, and basically everything that’s extensible or uses plugins.

I have just merged a change to KPluginMetaData that allows all these things to specify what form factor it’s relevant and useful for. This means that you can install for example KDevelop on a system that can be either a laptop or a mediacenter, and an application listing can be adapted to only show KDevelop when in desktop mode, and skipping it in media center mode. This is of great value when you want to unclutter the UI by filtering out irrelevant “stuff”. As this mechanism is implemented at the base level, KPluginMetaData, it’s available everywhere, using the exact same mechanism. When listing or loading “something”, you simply check if your current formfactor is among the suggested useful ones for an app or plugin, and based on that you make a decision whether to list it or skip it.

With increasing convergence between user interfaces, this mechanism allows us to adapt the user interface and its functionality in a fully dynamic way, and reduces clutter.

Getting down and dirty

So, how does this look exactly? Let’s take KMail as example, and assume for the sake of this example that we have two executables, kmail and kmail-touch. Two desktop files are installed, which I’ll list here in short form.

For the desktop fat client:

Comment=Fat-client for your email

For the touch-friendly version:

Comment=Touch-friendly email client

Note that that “FormFactors” key does not just take one fixed value, but allows specifying a list of values — an application may support more than one form-factor. This is reflected throughout the API with the plural form being used. Now the only thing the application launcher has to do is to check if the current form-factor is among the supplied ones, for example like this:

foreach (const KPluginMetaData &app, allApps) {
    if (app.formFactors().count() == 0 || app->formFactors().contains("desktop")) {

In this example, we check if the plugin metadata does specify the form-factor by counting the elements, and if it does, we check whether “desktop” is among them. For the above mentioned example files, it would mean that the fat client will be added to the list, and the touch-friendly one won’t. I’ll leave it as an exercise to the reader how one could filter only applications that are specifically suitable for example for a tablet device.

What devices are supported?

KPluginMetaData does not itself check if any of the values make sense. This is done by design because we want to allow for a wide range of form-factors, and we simply don’t know yet which devices this mechanism will be used on in the future. As such, the values are free-form and part of the contract between the “reader” (for example a launcher or a plugin listing) and the plugins themselves. There are a few commonly used values already (desktop, mediacenter, tablet, handset), but in principle, adding new form-factors (such as smartwatches, toasters, spaceships or frobulators) is possible, and part of its design.

For application developers

Application developers are encouraged to add this metadata to their .desktop files. Simply adding a line like the FormFactors one in the above examples will help to offer the application on different devices. If your application is desktop-only, this is not really urgent, as in the case of the desktop launchers (Kickoff, Kicker, KRunner and friends), we’ll likely use a mechanism like the above: No formfactors specified means: list it. For devices where most of the applications to be found will likely not work, marking your app with a specific FormFactor will increase the chances of it being found. As applications are being adopted to respect the form-factor’s metadata, its usefulness will increase. So if you know your app will work well with a remote control, add “mediacenter”, if you know it works well on touch devices with a reasonably sized display, add “tablet”, and so on.


We now have basic API, but nobody uses it (a chicken-and-egg situation, really). I expect that one of the first users of this will be Plasma Mediacenter. Bhushan is currently working on the integration of Plasma widgets into its user interface, and he has already expressed interest in using this exact mechanism. As KDE software moves onto a wider range of devices, this functionality will be one of the cornerstones of the device-adaptable user interface. If we want to use device UIs to their full potential, we do not just need converging code, we also need to add divergence features to allow benefiting from the difference of devices.

01 July, 2015 10:53PM

Costales: Review Meizu MX4 Ubuntu Edition - The beast!

Un móvil que lo defino con sólo una palabra: IMPRESIONANTE.

Meixu MX4 Ubuntu Edition

En una sobria caja blanca se presenta el móvil más potente gobernado por Ubuntu: El Meizu MX4.


La primera vez que lo coges sorprende su diseño, muy elegante, de líneas redondeadas y con un peso de sólo 147gr. para un tamaño de 144 x 75,2 x 8,9mm.


Lo que más llama la atención es su portentosa pantalla de 5,36", con resolución 1920 x 1152 (418PPI) y cristal: Gorilla Glass 3. Esta pantalla ofrece una calidad extraordinaria. Se ve muy bien y una vez que te habitúes a este tamaño, te aseguro que no querrás un móvil más pequeño.


Es el único móvil Ubuntu con 4G. En mis móviles anteriores sólo disponía de 3G. El 4G se nota y mucho: Cualquier página o aplicación que use datos cargará en el acto.


Pero lo que personalmente más aprecio es su excepcional cámara trasera, no sólo por sus 20,7 mp protegidos también por un cristal Gorilla Glass 3, si no por el contraste, definición y color conseguido en sus fotografías.

 Este es un ejemplo que disparé este fin de semana:

Ejemplo de calidad fotográfica

La batería tiene mucha capacidad: 3100mAh, aunque aún tiene que afinarse por parte de Canonical.

More than better!

El resto de hardware habla por si sólo: CPU dual quadcore (ARM A17 2.2GHz x 4 + ARM A7 1.7GHz x 4), RAM de 2 GB y 16GB de almacenamiento interno (no dispone para expansión por microSD).


Su precio: 299€. Nada caro para ser un gama alta y actualmente, el buque insignia de Ubuntu.

Puedes comprar el Meizu MX4 aquí.

Fotografías por David Castañón bajo licencia CC BY 3.0.

01 July, 2015 03:15PM by Marcos Costales (noreply@blogger.com)

hackergotchi for Qlustar


Dive into Qlustar World at ISC 15

The ISC 2015 conference in Frankfurt is only a few days away. When preparing your show schedule, make sure to reserve some time to visit the Qlustar team at the Q-Leap Networks booth #654. Don't miss our demonstration of the brand-new Qlustar 9.1 release capable of:

  • Dead-easy OpenStack deployment out of the box.
  • Ceph storage clusters easily to be configured.
  • Bootstrapping Lustre farms as simple as it can get.
  • Setting up BeeGFS in record time as an alternative to Lustre.
  • Performance-tuned BioInformatics codes using Qlustar BioStack.
  • Running data analytics workloads with the new Hadoop module.
  • QluMan 2.1 highlights
    • New secure, purely certificate based login, getting rid of passwords.
    • New powerful cluster connection manager.
    • Much more fine-grained configuration management of nodes.
  • and a lot more ...

Our 4 Petabyte demo cluster loaded with Lustre, BeeGFS, OpenStack and Ceph will give you a taste, how Qlustar will simplify your life, even when dealing with the most demanding workloads. Contact us now, to reserve a meeting time-slot for the show and grab the opportunity for your in-depth individual presentation of Qlustar, the True HPC - Storage - Cloud Cluster OS and its ever-growing capabilities.

Next to the Q-Leap booth, the team from the University of Hamburg chose Qlustar as their Cluster OS for the second time, to compete for the junior HPC crown at the Student Cluster Competition organized by the HPC Advisory Council.

Go Hamburg, go ... we keep our fingers crossed for you.

01 July, 2015 03:05PM by root

hackergotchi for Xanadu developers

Xanadu developers

XI Ciclo UPM TASSI 2015. Conferencia 4: eCrime evolution

Conferencia presentada el 12 de marzo de 2015 en el Campus Sur de la Universidad Politécnica de Madrid, España, por D. Marc Rivero (CyberSOC Deloitte) y D. Dani Creus (Kaspersky Labs), en el XI Ciclo de Conferencias UPM TASSI. Una actividad docente de la asignatura Temas Avanzados en Seguridad y Sociedad de la Información TASSI.

Enlace al vídeo en Youtube

Puede descargar la presentación utilizada por el ponente desde aquí.

Archivado en: General Tagged: ecrime, TASSI-2015, video

01 July, 2015 02:30PM by sinfallas

hackergotchi for Ubuntu developers

Ubuntu developers

Ubuntu App Developer Blog: Add a C++ backend to your QML UI

Whether you are creating a new app or porting an existing one from another ecosystem, you may need more backend power than the QML + JavaScript duo proposed in the QML app tutorial.

Let's have a peek at how to to add a C++ backend to your application, using system libraries or your own, and vastly increase its performance and potential features.

In this tutorial, you will learn how to use and invoke C++ classes from QML and integrate a 3rd party library into your project.

Read the tutorial

01 July, 2015 02:13PM by David Callé (david.calle@canonical.com)

June 30, 2015

Serge Hallyn: Tiling windows in Unity

Using the compiz grid plugin, Unity supports placing windows, one at a time, in a tiled-like fashion. However, there is no support for tilling a workspace in one fell stroke. That is something which users of dwm, wmii, i3, xmonad, awesome, qtile etc come to expect.

A few years ago I ran across a python script called stiler which tiled all windows, mainly using wmctrl. I’ve made a few updates to make that work cleanly in Unity, and have been using that for about a week. Here is how it works:

windows-enter is mapped to “stiler term”. This starts a new terminal (of the type defined in ~/.stilerrc), then tiles the current desktop. windows-j and windows-k are mapped to ‘stiler simple-next’ and ‘stiler simple-prev’, which first call the ‘simple’ function to make sure windows are tiled if they weren’t already, then focuses the next or previous window. So, if you have a set of windows which isn’t tiled (for instance you just exited a terminal), you can win-j to tile the remaining windows. Windows-shift-j cycles the tile locations so that the active window becomes the first non-tiled, etc.

This is clearly very focused on a dwm-like experience. stiler also supports vertical and horizontal layouts, and could easily be taught others like matrix.

If this is something that anyone but me actually wants to use, I’ll package properly in ppa, but for now the script can be found at
http://people.canonical.com/~serge/stiler .

30 June, 2015 08:30PM

hackergotchi for Blankon developers

Blankon developers

Sokhibi: Dengan BlankOn Kita Move On

Akhir bulan Juni 2015 Sahabat BlankOn Semarang bekerjasama dengan Universitas PGRI Semarang mengadakan acara Talk Show dengan tema Ngoprek Linux Dengan BlankOn kita Move On yang dilaksanakan di Gedung Pascasarjana lantai 5 Pendidikan Teknologi Informasi Universitas PGRI Semarang.

Adapun materi yang dibahas pada acara ini antara lain adalah: Perkenalan Komunitas BlankOn Semarang, pengenalan BlankOn Linux, Aplikasi Office, dan Aplikasi Grafis.

Di bawah  liputan singkat yang berhasil saya rangkum

Acara dimulai pukul 14,03 WIB yang dibuka oleh panitia Universitas PGRI Semarang dengan mengucapkan Bismillahirrahmanirrahim

Kemudian acara dilanjutkan dengan sambutan oleh Kajur PTIK UPGRIS yang disampaikan secara langsung oleh Bapak Wijanarko yang pada intinya beliau sangat mendukung acara semacam ini, beliau juga berharap acara tersebut ke depannya dapat berjalan secara berkelanjutan dengan tema yang lebih mendalam dan spesifik lagi.

Sebelum acara di lanjut ke tema utama, seperti biasa, yang mana pihak kampus memberikan Cindera mata kepada kami Komunitas BlankOn Semarang, seperti gambar di bawah ini

Acara berikutnya adalah perkenalan Sahabat BlankOn Semarang yang dibwakan oleh Om Mas Mahardhika Nugraha, pada sesi ini beliau memperkenalkan apa itu Sahabat BlankOn Semarang, apa saja  kegiatannya, bagaimana cara bergabung menjadi anggota komunitas ini, dan apa saja keuntungan jika menjadi anggota komunitas.

Pada acara ini, Selain menjadi pembicara Om Mas Mahardhika Nugraha sekaligus sebagai moderator acara.

Sesi selanjutnya adalah pengenalan BlankOn Linux yang dibawakan oleh bapak Suntoro, pada sesi ini beliau menjelaskan apa itu BlankOn Linux, bagaimana distro ini dikembangkan, siapa saja yang mengambangkannya, pada sesi ini tidak lupa beliau juga menjelaskan secara singkat cara bergabung menjadi pengembang dan apa saja syaratnya untuk jadi pengembang BlankOn Linux.

Setelah sesi pengenalan BlankOn linux selesai dibawakan oleh pak Suntoro, maka acara dilajutkan oleh Mas Mustofa yang mana pada sesi ini beliau menjelaskan aplikasi perkantoran (office) dalam hal ini tentanga LibreOffice.

Pada sesi ini mas Mustofa menjelaskan bahwa penggunaan aplikasi office pada berbagai sistem operasi pada dasarnya sama, agar peserta yang mengikuti acara ini lebih yakin lagi maka beliau meminta salah seorang peserta untuk memperagakan (praktek langsung) menggunakan aplikasi LibreOffice, dan hal ini terbukti dengan lancarnya peserta dapat menggunakan LibreOffice seperti menggunakan Aplikasi Office milih OS sebelah.

Di bawah ini adalah beberapa gambar peserta yang sempat kami abadikan

Eh ternyata ada juga peserta dari luar Semarang yang menyusup jadi peserta acara ini, mereka adalah tim GrombyangOS, di bawah ini adalah gambar desktop Linux mereka

Sesi terakhir pada acara ini adalah pengenalan Aplikasi Grafis yang di sampaikan oleh ketua Sahabat BlankOn Semarang, pada sesi ini pembicara mengenalkan dan menjelaskan berbagai Aplikasi Grafis di BlankOn Linux yang dapat digunakan, tidak lupa pembicara juga menampilkan berbagai contoh hasil karya desainer dunia yang dibuat dengan aplikasi Grafis berbasis OpenSource.

Di sesi ini pembicara juga menjelaskan bahwa di Indonesia masih jarang ditemukan buku panduan penggunaan Aplikasi Grafis OpenSource dalam bahasa Indonesia sehingga pembicara akhirnya punya ide untuk menulisnya sendiri, salah satu buku yang sudah diterbitkan adala buku Desain Grafis dengan Inkscape.

Pukul 17.59 WIB acara Talk Show dengan tema Ngoprek Linux Dengan BlankOn kita Move On selesai di laksanakan dengan ditutup ucapan Alhamdulillah oleh panitia yang diikuti oleh semua peserta.

Seperti acara lain pada umumnya, setelah acara selesai bak orang-orang penting kami juga tidak lupa foto bareng.

Oh ya, karena acara ini dilaksanakan pada bulan Ramadhan, maka pihak panitia mengajak kami untuk buka bersama, acara buka bersama dilaksanakan setelah Sholat Maghrib bertempat di Waroeng Steak & Shake (jalannya saya gak tahu)

 Demikian liputan singkat acara Talk Show dengan tema Ngoprek Linux Dengan BlankOn kita Move On yang dapat saya tulis kali ini, sampai jumpa pada liputan lainnya.

30 June, 2015 06:24PM by Istana Media (noreply@blogger.com)

hackergotchi for Cumulus Linux

Cumulus Linux

Testing Open Networking

Over the last couple of weeks, the networking industry has made some significant steps in the right direction, the open networking direction. At the Open Networking Summit (ONS), we heard some great news about the disaggregated network and how open networking is now everywhere from hyperscale to the enterprise to startups to telcos. As exciting as that is, that’s not the news I’m referring to — I’m referring to the announcement of the Open Networking Testing Consortium.

To illustrate why this is big news, I’ll give some background on how open networking has been operating for most people. Up until a few years ago, the way you purchased a bare metal switch was through select APAC sources and a wire transfer. A few weeks later, you’d receive your equipment and it was then up to you, the end user, to perform interoperability testing with your cables and optics manufacturers while on the phone with support, along with bootstrapping your OS to these boxes. Eventually you had both a CapEx and OpEx saving solution that you controlled from end to end.

One the first bare metal switches, Google PlutoOne the first bare metal switches, Google Pluto

Luckily for most of you, that experience has now been refined significantly to the same method by which compute and storage are purchased: through tier one system providers like Dell, HP, Supermicro and many others. But in order to increase adoption of open networking components, we have to change how some things are done in the industry, such as component validation, interoperability testing and compliance with industry standards and protocols to build solid open networking solutions.

open_networking_testing_bare-metalA typical bare metal switch today running ONIE

For the past 9 months we in the OCP Networking Group have been working on exactly that. We started by creating component validation for ONIE (the Open Network Install Environment), supporting more than just the 9 vendors in the ONIE repository as well as more than 40 network devices, and moving towards interop testing where Cumulus Linux is just one of the many NOSs (network operating systems) supporting this hardware. For the OCP Networking group, interop testing consists of taking OCP and non-OCP components such as switches, cables, optics and NOSs, then ensuring they all work together as if end users bought them all from a single vendor.

IOL students hard at workUniv. of New Hampshire – InterOperability Lab students hard at work

You are probably asking, “So what?!? How’s this different than what my current vendor does?”. Good question, but does your vendor test with other vendors’ equipment? Or better yet, does your vendor make all test plans and reports publicly available without a paywall so that anyone can reproduce them? Because that’s exactly what we are doing.

In the server world there are a variety of standards like x86 processors, PXE, MBR/GPT disk layouts, SMBIOS, ACPI and many more alphabet soup acronyms that act as “the glue” to make your computer function reliably without the end user having to think about it much.  However, it’s a different experience in the network world, where ISVs like Cisco, lock down or perform proprietary enforcement of a closed ecosystem.

When vendors have walled gardens, there is no interoperability, and thus, less choice for end users. This is the exact opposite from open networking where we thrive on offering users freedom of choice with unlocked hardware, unbundled software and configuration management, enabling users to choose the best of breed for their needs.

OCP MSX1710 from Mellanox with Avago AOC and 3M ready to goOCP MSX1710 from Mellanox with Avago AOC and 3M ready to go

In recent months, a group of hardware, cable and optics vendors have been meeting regularly to create a test plan to ensure proper interoperability. These meetings have been open to any interested party participating within OCP, a true collaboration that is open and transparent. When we got to a point where we needed to do a dry run, we performed a “plugfest” to ensure the accuracy of the testing procedures. This usually meant 6 or more vendors would meet at UNH – IOL for a week of testing. The first plugfest was held at the end of February before the OCP Summit, where a number of NOS vendors participated. Cumulus Networks conducted the second one a couple weeks ago (June 15 – 19) with optics and cable suppliers 3M, Avago, Amphenol, Finisar, JDSU and Mellanox.

open_networking_testing_cables2Bare metal switches with Cumulus Linux and Amphenol cables

We are at the point where the test plan is solid and we are launching our interop compliance program in September. But we are not stopping there; later this year we will launch “Consumer Reports for Open Networking,” a publicly available website where end users can look up which devices are compliant with which cables/optics running a particular NOS. We expect to have a MVP (Minimum Viable Product) of the site running by end of this year.

Everything we just described — open testing and open reporting — is an industry first where a complete network solution is being validated end to end. The end goal for our interop testing is to cover the whole space, from the NIC on a server to a pluggable to a switch through a routing protocol and back down the stack.

I want to thank the following vendors for participating in our dry run plugfests:

  • 3M – Much props to Dinah for saving our bacon with last minute supplies.
  • Accton – Big ups to Jeff and Pete.
  • Amphenol – Erdem, you’re awesome.
  • Avago – Chris, John, and Steve, we couldn’t have done this without y’all.
  • Big Switch Networks – Thanks Paul for helping us out on the first plugfest.
  • Cumulus Networks – Much Grass to Shrijeet, Nolan, JR, Matt, and everyone who supported them. The industry wouldn’t be the same without y’all.
  • Fidelity – Bob and Mark, A big Thank You for keeping us in line with testing and compliance goals that are useful to end users.
  • Finisar – Craig, Dave, Larry, Mitch, and Steve, thank y’all for y’all’s guidance and participation.
  • JDSU – Many thanks to Chen, Georg, and Rob.
  • Mellanox – A big shout out to the folks across the pond: Amir, Ben, Idan and Tomer.  Keep rocking.
open_networking_testing_plugfest_teamThe Plugfest #2 team

I would like to also give a huge THANK YOU to Chris Dube and her team at IOL for putting together this test plan and shepherding all of us through the process of neutral interop testing.

To celebrate the start of this interop program, a plugfest is planned for mid-September where we expect even more cables, optics, switches and NOS vendors to participate.

2015 is going to end with a big bang for open networking!


The post Testing Open Networking appeared first on Cumulus Networks Blog.

30 June, 2015 05:25PM by Carlos Cardenas

hackergotchi for Ubuntu developers

Ubuntu developers

Ubuntu Kernel Team: Kernel Team Meeting Minutes – June 30, 2015

Meeting Minutes

IRC Log of the meeting.

Meeting minutes.


20150630 Meeting Agenda

Release Metrics and Incoming Bugs

Release metrics and incoming bug data can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kt-meeting.txt

Status: CVE’s

The current CVE status can be reviewed at the following link:
– http://kernel.ubuntu.com/reports/kernel-cves.html

Status: Stable, Security, and Bugfix Kernel Updates – Precise/Trusty/Utopic/Vivid

Status for the main kernels, until today:

  • Precise – Verification & Testing
  • Trusty – Verification & Testing
  • Utopic – Verification & Testing
  • Vivid – Verification & Testing

    Current opened tracking bugs details:

  • http://kernel.ubuntu.com/sru/kernel-sru-workflow.html
    For SRUs, SRU report is a good source of information:
  • http://kernel.ubuntu.com/sru/sru-report.html


    cycle: 13-Jun through 04-Jul
    12-Jun Last day for kernel commits for this cycle
    14-Jun – 20-Jun Kernel prep week.
    21-Jun – 04-Jul Bug verification; Regression testing; Release

Open Discussion or Questions? Raise your hand to be recognized

No open discussion.

30 June, 2015 05:11PM

hackergotchi for Maemo developers

Maemo developers

2015-06-16 Meeting Minutes

Meeting held 2015-06-16 on FreeNode, channel #maemo-meeting (logs)

Attending: Jussi Ohenoja (juiceme), Peter Leinchen (peterleinchen)

Partial: Gido Griese (Win7Mac)

Absent: Oksana Tkachenko (Oksana/Wikiwide), William McBee (gerbick), Alexander Kozhevnikov (MentalistTraceur)

Summary of topics (ordered by discussion):

  • Referendum and Elections announcement

p>(Topic Referendum and Elections announcement):

  • Juiceme agreed that the 3rd draft of the referendum is OK for publishing.
  • Both the referendum on council tasks and election of the new council will be run concurrently as to maximise the awareness of the ongoing actions and have as large as possible vote count.

Action Items:
  • old items:
    • The selected Code of Conduct (KDE) still needs to be published on TMO.
    • Looking into automatic calculation of election results ...
    • Contacting freemangordon and merlin1991 about auto-builder: CSSU-thumb target, GCC versions?
    • Getting maemo trademark registration (everywhere?) renewed (and transferred to MCeV) by the end of February (or within six months since expiry date).
    • Archiving Ovi/Nokia store, especially for Harmattan.
    • Contacting Daphne Won on Facebook and LinkedIn to get administrator rights on Facebook for a Maemo member to migrate the plugin to v2.0 API and maintain it in the future.
  • new items:

0 Add to favourites0 Bury

30 June, 2015 04:11PM by Jussi Ohenoja (juice@swagman.org)


Linux Mint 17.2 “Rafaela” MATE released!

The team is proud to announce the release of Linux Mint 17.2 “Rafaela” MATE.

Linux Mint 17.2 Rafaela MATE Edition

Linux Mint 17.2 is a long term support release which will be supported until 2019. It comes with updated software and brings refinements and many new features to make your desktop even more comfortable to use.

New features at a glance:

For a complete overview and to see screenshots of the new features, visit: “What’s new in Linux Mint 17.2 MATE“.

Important info:

To be aware of issues and read about explanations and possible solutions related to this release, visit: “Release Notes for Linux Mint 17.2 MATE

System requirements:

  • 512MB RAM (1GB recommended for a comfortable usage).
  • 9GB of disk space (20GB recommended).
  • Graphics card capable of 800×600 resolution (1024×768 recommended).
  • DVD drive or USB port.


  • The 64-bit ISO can boot with BIOS or UEFI.
  • The 32-bit ISO can only boot with BIOS.
  • The 64-bit ISO is recommend for all modern computers (Almost all computers sold in the last 10 years are equipped with 64-bit processors).

Upgrade instructions:

  • If you want to upgrade from Linux Mint 17.2 RC, simply launch the Update Manager and install any Level 1 update available.
  • If you want to upgrade from Linux Mint 17 or Linux Mint 17.1, please wait for a few days while we release a new version of the Update Manager to you. In the meantime, you do not need to download or to reinstall anything. We’ll make announcements next week when this is ready.

Download:Md5 sum:


HTTP Mirrors for the 32-bit DVD ISO:

HTTP Mirrors for the 64-bit DVD ISO:

Alternative downloads:

No-codecs images:

Distributors and magazines in Japan, USA and countries where distributing media codecs is problematic can use the “No Codecs” ISO images.  These images will be made available next week, for both the MATE and Cinnamon edition in 32-bit and 64-bit at the following address:


OEM images:

Manufacturers can pre-install Linux Mint on their computers using the OEM installation images. These images will be made available next week, for both the MATE and Cinnamon edition in 64-bit at the following address:



We look forward to receiving your feedback. Thank you for using Linux Mint and have a lot of fun with this new release!

30 June, 2015 10:58AM by Clem

Linux Mint 17.2 “Rafaela” Cinnamon released!

The team is proud to announce the release of Linux Mint 17.2 “Rafaela” Cinnamon.

Linux Mint 17.2 Rafaela Cinnamon Edition

Linux Mint 17.2 is a long term support release which will be supported until 2019. It comes with updated software and brings refinements and many new features to make your desktop even more comfortable to use.

New features at a glance:

To be aware of issues and read about explanations and possible solutions related to this release, visit: “Release Notes for Linux Mint 17.2 Cinnamon

System requirements:

  • 512MB RAM (1GB recommended for a comfortable usage).
  • 9GB of disk space (20GB recommended).
  • Graphics card capable of 800×600 resolution (1024×768 recommended).
  • DVD drive or USB port.


  • The 64-bit ISO can boot with BIOS or UEFI.
  • The 32-bit ISO can only boot with BIOS.
  • The 64-bit ISO is recommend for all modern computers (Almost all computers sold in the last 10 years are equipped with 64-bit processors).

Upgrade instructions:

  • If you want to upgrade from Linux Mint 17.2 RC, simply launch the Update Manager and install any Level 1 update available.
  • If you want to upgrade from Linux Mint 17 or Linux Mint 17.1, please wait for a few days while we release a new version of the Update Manager to you. In the meantime, you do not need to download or to reinstall anything. We’ll make announcements next week when this is ready.


Md5 sum:


HTTP Mirrors for the 32-bit DVD ISO:

HTTP Mirrors for the 64-bit DVD ISO:

Alternative downloads:

No-codecs images:

Distributors and magazines in Japan, USA and countries where distributing media codecs is problematic can use the “No Codecs” ISO images.  These images will be made available next week, for both the MATE and Cinnamon edition in 32-bit and 64-bit at the following address:


OEM images:

Manufacturers can pre-install Linux Mint on their computers using the OEM installation images. These images will be made available next week, for both the MATE and Cinnamon edition in 64-bit at the following address:



We look forward to receiving your feedback. Thank you for using Linux Mint and have a lot of fun with this new release!

30 June, 2015 10:58AM by Clem

hackergotchi for Ubuntu developers

Ubuntu developers

Serge Hallyn: Publishing lxd images

While some work remains to be done for ‘lxc publish’, the current support is sufficient to show a full cycle of image workload with lxd.

Ubuntu wily comes with systemd by default. Sometimes you might need a wily container with upstart. And to repeatedly reproduce some tests on wily with upstart, you might want to create a container image.

# lxc remote add lxc images.linuxcontainers.org
# lxc launch lxc:ubuntu/wily/amd64 w1
# lxc exec w1 -- apt-get -y install upstart-bin upstart-sysv
# lxc stop w1
# lxc publish --public w1 --alias=wily-with-upstart
# lxc image copy wily-with-upstart remote:  # optional

Now you can start a new container using

# lxc launch wily-with-upstart w-test-1
# lxc exec w-test-1 -- ls -alh /sbin/init
lrwxrwxrwx 1 root root 7 May 18 10:20 /sbin/init -> upstart
# lxc exec w-test-1 run-my-tests

Importantly, because “–public” was passed to the lxc publish command, anyone who can reach your lxd server or the image server at “remote:” will also be able to use the image. Of course, for private images, don’t use “–public”.


30 June, 2015 03:20AM

Elizabeth K. Joseph: Contributing to the Ubuntu Weekly Newsletter

Super star Ubuntu Weekly Newsletter contributor Paul White recently was reflecting upon his work with the newsletter and noted that he was approaching 100 issues that he’s contributed to. Wow!

That caused me to look at how long I’ve been involved. Back in 2011 the newsletter when on a 6 month hiatus when the former editor had to step down due to obligations elsewhere. After much pleading for the return of the newsletter, I spent a few weeks working with Nathan Handler to improve the scripts used in the release process and doing an analysis of the value of each section of the newsletter in relation to how much work it took to produce each week. The result was a slightly leaner, but hopefully just as valuable newsletter, which now took about 30 minutes for an experienced editor to release rather than 2+ hours. This change was transformational for the team, allowing me to be involved for a whopping 205 consecutive issues.

If you’re not familiar with the newsletter, every week we work to collect news from around our community and the Internet to bring together a snapshot of that week in Ubuntu. It helps people stay up to date with the latest in the world of Ubuntu and the Newsletter archive offers a fascinating glimpse back through history.

But we always need help putting the newsletter together. We especially need people who can take some time out of their weekend to help us write article summaries.

Summary writers. Summary writers receive an email every Friday evening (or early Saturday) US time with a link to the collaborative news links document for the past week which lists all the articles that need 2-3 sentence summaries. These people are vitally important to the newsletter. The time commitment is limited and it is easy to get started with from the first weekend you volunteer. No need to be shy about your writing skills, we have style guidelines to help you on your way and all summaries are reviewed before publishing so it’s easy to improve as you go on.

Interested? Email editor.ubuntu.news@ubuntu.com and we’ll get you added to the list of folks who are emailed each week.

I love working on the newsletter. As I’ve had to reduce my commitment to some volunteer projects I’m working on, I’ve held on to the newsletter because of how valuable and enjoyable I find it. We’re a friendly team and I hope you can join us!

Still just interested in reading? You have several options:

And everyone is welcome to drop by #ubuntu-news on Freenode to chat with us or share links to news we may found valuable for the newsletter.

30 June, 2015 02:29AM

June 29, 2015

hackergotchi for SparkyLinux


Budgie Desktop updated


There is an update of Budgie Desktop 8.2-20150629 in our repository.

One of updates came from Debian testing removed ‘libmutter0e’ package and Budgie Desktop as well.
So the Budgie Desktop has been re-built and uses ‘libmutter0f’ as one of its dependencies now.

If you haven’t upgraded the previous version of Budgie Desktop yet, you can do it now or install it if you’d like:

sudo apt-get update
sudo apt-get install budgie-desktop


29 June, 2015 01:03PM by pavroo

hackergotchi for Ubuntu developers

Ubuntu developers

Costales: ¿Por qué comprar un Ubuntu Phone? Léase, ventajas de un Ubuntu Phone

En la review del BQ E5, un lector me hacía una pregunta tan concisa como interesante: ¿Qué ventajas tiene un móvil con Ubuntu?

Lo cierto es que no lo había pensado detenidamente. Llevo usando Ubuntu Phone durante 5 meses porque personalmente prefiero que Ubuntu sea el sistema operativo en mi móvil y ese para mi, es un factor de peso más que suficiente.

Meizu MX4 Ubuntu Edition

Tras pensarlo un rato, en mi opinión, Ubuntu Phone destaca por estos motivos:

  • Servicios, no aplicaciones: Ubuntu Phone está enfocado a que usemos servicios y no tanto las aplicaciones. ¿Cómo? Mediante los scopes, que marcan una disrupción original y única en los sistemas operativos móviles actuales. Lo mejor es ver este vídeo, para entender qué son los scopes y su potencial:
  • Libertad: Un sistema operativo 100% libre y la gran mayoría de aplicaciones, también libres.
  • Ubuntu en tu bolsillo: Un sistema operativo 100% Linux, sin emulaciones.
  • Cierra el círculo: Podrás usar Ubuntu en Desktop + Servidor + Nube + Móvil.
  • Evitar al Gran Hermano en los que se convirtieron Google y Apple: Y la NSA que añadió posteriormente la guinda al pastel.
  • Diseño sencillo, a la vez que elegante. Aunque para gustos, colores :)
  • Sin fragmentación: Con actualizaciones OTA mensuales para todos los móviles.
  • Un "Ubuntu" Phone: Canonical está totalmente volcada en Ubuntu Phone y la sensación es de que tienes un móvil de Ubuntu, más que tener un móvil BQ o Meizu.
  • Gestos: Unity muestra todo su potencial táctil. Sencillo, rápido e intuitivo.
  • Desarrollo: Un buen SDK y muchísimas posibilidades de desarrollo: QML, HTML5 (incluído cordova), webapps... Y una buena tienda (¡por fin!) desde donde descargarlas/descubrirlas.

BQ Ubuntu Edition

Obviamente no todo es perfecto. Echo en falta:
  • Aplicaciones: Hay muchas, pero faltan aplicaciones importantes para muchos usuarios.
  • tethering: Recordemos que Android lo sacó en la versión 2.2
  • bluetooth: No funciona aún como debería.
Cada usuario es un mundo. Pero yo estoy totalmente satisfecho con mi Ubuntu Phone :)

29 June, 2015 09:22AM by Marcos Costales (noreply@blogger.com)

Ted Gould: Just Say It!

While I love typing on small on screen keyboards on my phone, it is much easier to just talk. When we did the HUD we added speech recognition there, and it processed the audio on the device giving the great experience of controlling your phone with your voice. And that worked well with the limited command set exported by the application, but to do generic voice, today, that requires more processing power than a phone can reasonably provide. Which made me pretty excited to find out about HP's IDOL on Demand service.

I made a small application for Ubuntu Phone that records the audio you speak at it, and sends it up to the HP IDOL on Demand service. The HP service then does the speech recognition on it and returns the text back to us. Once I have the text (with help from Ken VanDine) I set it up to use Content Hub to export the text to any other application that can receive it. This way you can use speech recognition to write your Telegram notes, without Telegram having to know anything about speech at all.

The application is called Just Say It! and is in the Ubuntu App Store right now. It isn't beautiful, but definitely shows what can be done with this type of technology today. I hope to make it prettier and add additional features in the future. If you'd like to see how I did it you can look at the source.

As an aside: I can't get any of the non-English languages to work. This could be because I'm not a native speaker of those languages. If people could try them I'd love to know if they're useful.

29 June, 2015 04:29AM

June 28, 2015

Riccardo Padovani: The most inspiring week of my life

If you read my blog you already know that since April I’ve a job as developer at Archon. It’s a thing I enjoy a lot, and the last week has been awesome.

Archon joined the Hello Tomorrow Conference 2015, so last week I travelled to Paris.

And there I met some of the best people of the world, those that change the world, not only in the computer science world, but in every field.

Here some of things most inspired me, I hope they could inspire you too, and give you energy to be the change you want to see in the world.

Archon Team

First of all thanks to guys that were with me in Paris: Davide Venturelli, the CEO, works at NASA and is currently in charge of surveying the scientific investigations performed at the Quantum Artificial Intelligence Laboratory. What he does it’s incredible, and he motivated me a lot to follow my dreams now.

You can watch his pitch at the conference on Youtube (recorded by my Ubuntu Phone). Seriously, find 8 minutes today and watch it, so you can understand what Archon is about, and why I like it.

Giovanni Landi is our 3D expert, and has a lot of different passions. I had a lot of fun working with him at our stand, and I learned a lot of things about art (one of his passions).

Roberto Navoni is our hardware expert, and his life should be an inspiration for every Italian. He’s an entrepreneur, has created a company in Italy and despite the difficulties he didn’t expatriate.

Davide Ghezzi is our CFO. Unfortunately he was able to join us only for the first day, but he did a lot of things. I have no idea on how is possible a single man has so much energies, but wow!

The stand

I spent most of the time at our stand, where I explained what is our product to both potentially investors and casual visitors. As you can read, my English isn’t so good, so I was quite surprised everyone understood what I was saying.

Anyway, meet so many people from all around the world was amazing, everyone with incredible experiences and cool backgrounds. I spent a lot of time talking about the future, and how to do things that could impact the world. I listened to a lot of stories, and I remember each of them, because everyone was incredible.

The keynotes

During the event I was able to take a look to a couple of keynotes (I spent the rest of the time at the stand), and both were something you don’t see everyday.

The first one was by Obi Felten, moonshots at Google[X]. I don’t agree with a lot of Google’s policies, but the energies these guys have in trying to build something beautiful, and how they work hard with open minds is something that deserves deep respect and admiration.

The second one was by the CEO of G-Therapeutics. They have developed a working (but still in development) technology that helps paralyzed people walk again. Let me repeat: a stimulation system to rehabilitate individuals with spinal cord injury.

The presentation was the most moving thing I’ve ever seen, and it has earned minutes of applause.

The companies

Other than Archon, there were a lot of other interesting companies, both for what they do or for the stories of their founders.

I leave here a little list about the ones that I liked more, which it is far from complete (you can read the entire list on the Hello Tomorrow website).

  • Blitab is a braille tablet helping blind people. I love howntechnologies nowadays could help less lucky people to live a better life
  • BioCarbon Engineering is changing the world 1 billion trees at a time. They use drones to make precision planting and optimize reforestation. You know, trees don’t give free wifi, but they give oxigen, so they are useuful. Indeed, BioCarbon won the competition.
  • Artomatix builds a software to automating the generation of art, to enable digital graphic artists to focus on being creative, in addition to reducing project times and costs. Ok, it’s not a world changer, but the gamer that is in me loves the software, so I really hope they could have success
  • Solenica is building Lucy. Lucy’s mirror follows the sun and reflects sunlight into your rooms, creating a beautiful natural glow. Other than the product (they allow you to reduce your carbon footprint by up to 1 ton/year by saving electricity, I like things that help the ecology), I like the story of the startup, founded by 3 Italians. It’s sad they had to go to the U.S. to follow their dream, but I love their stubbornness in going forward. Only people as their go forward, and make the world a better place.


Other than the inspiration, in that week I had also the confirmation I’m on the right path to do something in my life to help the world to be a better place. A lot of people incited me to continue on that way, and you know, public recognition of your work is important.


28 June, 2015 10:56PM

Riccardo Padovani: Thoughts on Meizu MX4

10 days ago I switched my phone, I dismissed the BQ Aquaris E4.5 and started to use the Meizu MX4 (both with Ubuntu for Phones). On Internet there are a lot of reviews about hardware and software, written by people more prepared than me and in a better English. What I want to do here is to highlight how it fits my user case and why it’s 9 months I don’t use a smartphone if it doesn’t have Ubuntu.


A couple of premises

I use Ubuntu as only system on my smartphone since Sep ‘14. I started with a Nexus 4, until Feb ‘15, when I switched to the BQ Aquaris, and then to Meizu MX4 a couple of weeks ago. All three devices have been given to me by Canonical, the company which develops Ubuntu, to thank me the support in the development of the system.

Despite this, they didn’t ask me to do a good review, or else, but just to be honest. And I’ll do, as I did back in February.

Also, I’m happy with Ubuntu, but that doesn’t mean it is the best system on the market (hint: it isn’t), or it has the best hardware (hint: it hasn’t), or the best applications (hint: no way). But I like it, I love to improve it, and I’m so happy there is an opensource system on the market (yes, there is Firefox OS too, but I prefer Ubuntu). So don’t buy it if you aren’t sure about what you’re doing.

The good

The screen

The screen of this phone is something so beautiful, so perfect, so whatever positive adjective you can think, that I fall in love with it. It was the worst thing on the BQ, and it’s the best here: lateral borders are little, the screen is big, there are so much pixels you don’t see them, and everything is so perfect sized. You know, size matters ;-)

The performances

It definitely has better performances than the BQ. Especially browser and Telegram. Browser has a very fast rendering, and Telegram is so better than on the BQ that I’m not sure it is at the same version on two phones. I asked to developers and they said yes, but I swear I’m not convinced yet, it’s definitely faster, it never freeze, and it’s really nice to use it.

And no, it’s not because I use it little. In fact, I receive more than 500 messages every day (guys, to abandon Android I had to persuade all my friends to switch to Telegram).

The system

I really love the system: good performance, long battery life, every time there is an update you see so many changes, and I help to shape it writing code (and this is one of the greatest satisfactions that there may be).

After the last update OTA-4 it’s a wonderful world where to live, and it’s opensource. And this is the fundamental thing.

The bad

The optimization

Considering how smoothly Ubuntu runs on the Aquaris, I definitely expect better things from this phone. I have to recharge it every day (while I was recharging Aquaris one every two days) and sometimes the system freezes. Developers are working on all the bugs, so I’m sure they will be fixed and in future the optimization will be better, but the system is definitely better optimized for the Aquaris than for the MX4

The price

Considering the hardware, the maturity of the system and the optimization (see above) it’s overpriced. While I suggest you to buy the Aquaris if you want to try Ubuntu, I cannot suggest to buy this one. At least, until another update fix all issuses I highlighted before.

I really like the screen, so I’ll continue to use this one, but if you aren’t huge fans of large screens, there is no reason to buy this over the Aquaris at the moment I’m writing (end of Jun ‘15), but I hope the situation will improve with OTA-5 (ETA: end of Jul ‘15).

The home button

We don’t need buttons. More screen and less buttons, please.

The dream

Canonical and community are working together to make a dream possible. We want opensource runs the world, we want to create a better place with software.

I don’t know if we will be successful, or if we will change the world, but at least we’re trying. So don’t settle down, continue to write code, report bugs, translate apps. At the end, good deeds are always rewarded.

As Alan Kay wrote, The best way to predict the future is to invent it.

Someone says I’m wasting my little free time doing things for free for a commercial company. But I’m not wasting my time, I’m building a better future, and so do you every time you do something for the opensource world.

Do you like this article? Please consider to buy me an English course, so I can improve it or just send me a feedback at riccardo@rpadovani.com.


28 June, 2015 05:45PM

Stuart Langridge: Availability

Some very interesting discussions happened at Edgeconf 5, including a detailed breakout session on making your web apps work for everyone which was well run by Lyza Danger Gardner. We talked about performance, and how if your page contains HTML then your users see your interface sooner. About fallbacks, and how if you’re on a train with a dodgy 3g connection the site should work and that’s a competitive advantage for you, because your competitors’ sites probably don’t. About isomorphic JavaScript and how the promise of it is that your Angular website won’t have to wait until it’s all downloaded before showing anything. About Opera Mini’s 250 million users. It’s about whether the stuff you build is available to the most people. About your reach, and you being able to reach more than the others.

In the past, we’ve called this “progressive enhancement”, but people don’t like that word. Because it sounds hard. It sounds like you’re not allowed to use modern tools in case one user has IE4. Like you have to choose between slick design and theoretical users in Burma.

Much rhetorical use has been made of the gov.UK team’s results of people not getting the script on their pages. The important part of that result was that 0.9% of visits didn’t run the client side scripting even though they should have done. It’s not people with JavaScript turned off, it’s people with browsers that for some reason didn’t run it at all. Did you open a hundred web pages yesterday? I probably did. So for every hundred web pages opened by someone, one of them didn’t work. Maybe they were in a tunnel and the 3g cut out. Maybe they were on hotel WiFi. Maybe the CDN went down for ten seconds. Maybe the assets server crashed. But, for whatever reason, some of your site didn’t work. Did that make your site unavailable to them? Not if it was written right, written to be available.

And “written right” does not mean that you have double the work to build a version of your WebGL photo editor that works in Lynx. If you do this by having isomorphic JS, so your node server provides HTML which makes your pages load before your 2MB of bower JS arrives, that’s fine. Because you’re available to everybody; a Macbook user in a cafe, a finance director on her Windows desktop, a phone-using tween in a field with no coverage, and yes even Opera Mini users in Burma.

It’s not about giving up your frameworks to cater for fictional example users with scripting disabled. It is true that not everyone has JS and that sometimes that’s you, so let’s work out how to do this without regressing to 1998.

So I’m not going to be talking about progressive enhancement any more. I’m going to be talking about availability. About reach. About my web apps being for everyone even when the universe tries to get in the way.

(Also, more on why availability matters, with smiling diagrams!)

28 June, 2015 02:20PM

Charles Profitt: Dell XPS 13 (9343) Making the Transition to a Smaller Laptop

When I first left desktops behind for a laptop (Lenovo T500) it was a tough step. I was used to building my own desktops from the components I selected. I was used to the power of a desktop. Converting to using a laptop was an exercise in compromises. The transition from a 15″ laptop to a smaller lighter laptop is similar, but this is the first time I have taken a step back in the area of memory. I am converting from a Lenovo T530 to a Dell XPS 13 (9343) Developer Edition. This article will cover accessories I own or am considering purchasing to replace some of the lost features of the larger laptop.

main_256Video Out
If you use your laptop to present or would like to have a larger monitor at your desk then you will want to have an adapter from mini-displayport to some other input (VGA, DVI or Displayport). In my case I went with the MDP-HDMI from Puggable which converts from mini-displayport to HDMI. Most of the presentations I do get displayed on large screen television with HDMI inputs which make this solution ideal. Linux does not have support for USB 3.0 Display Link device, but you could also choose to utilize a USB 2.0 docking station. As long as you do not have USB 3.0 drives or a need for 1000MB Ethernet connections that would be a possible solution.

Wireless works great when you are mobile and fairly well even when you are not. For most people there is no need for wired connections, but if you move large files then having a gigabit connection is a must have. For this I use a Pluggable Model USB3-E1000 device. Moving large files at 118 MB/s is much more enjoyable than 35 MB/s.

main_256USB 3.0 Hub
With only two USB ports a hub can make it easier to attach multiple devices. In my case since I decided to use the USB3-E1000 device I would only have one available USB port. I have the Plugable USB3-HUB7A which has seven ports. This USB hub has not been stable for me with either the the Lenovo T530 nor the Dell XPS 13 (9343). I am not sure if there is a firmware issue or something else. The current issues are that devices plugged in to the hub are not always recognized. That said this hub still allows me to use three devices directly attached and another two through a second USB 2.0 hub.


28 June, 2015 02:07AM

June 27, 2015

hackergotchi for HandyLinux


HandyLinux dans LinuxUser Allemagne

bonjour à toutes et à tous.

une tite brève car nous avons le plaisir d'apprendre que le magazine LinuxUser en Allemagne met 3 distributions Linux à l'honneur dans le numéro de juillet 2015 : Fedora, KaliLinux et ... et HandyLinux !!

voilà, on est super fier comme des gosses !
merci @toutes&tous

un petit edit car HandyLinux est aussi dispo chez nos amis russes : 6 distributions en DVD : HandyLinux, Mint, Netrunner, Kodi, Scientific Linux, Tails, Tiny Core!

l'est pas belle la vie ?
HandyLinux - la distribution Debian sans se prendre la tête...

27 June, 2015 08:22PM by arpinux

hackergotchi for Ubuntu developers

Ubuntu developers

Kubuntu Wire: Looks as if Wily got Plasma 5.3.1.

Setting up plasma-desktop (4:5.3.1-0ubuntu3) …



No backports PPA required.

Plasma 5.3.1.

Daily Wily Images.

27 June, 2015 02:40PM

Colin King: Static code analysis on kernel source

Since 2014 I have been running static code analysis using tools such as cppcheck and smatch against the Linux kernel source on a regular basis to catch bugs that creep into the kernel.   After each cppcheck run I then diff the logs and get a list of deltas on the error and warning messages, and I periodically review these to filter out false positives and I end up with a list of bugs that need some attention.

Bugs such as allocations returning NULL pointers without checks, memory leaks, duplicate memory frees and uninitialized variables are easy to find with static analyzers and generally just require generally one or two line fixes.

So what are the overall trends like?

Warnings and error messages from cppcheck have been dropping over time and "portable warnings" have been steadily increasing.  "Portable warnings" are mainly from arithmetic on void * pointers (which GCC handles has byte sized but is not legal C), and these are slowly increasing over time.   Note that there is some variation in the results as I use the latest versions of cppcheck, and occasionally it finds a lot of false positives and then this gets fixed in later versions of cppcheck.

Comparing it to the growth in kernel size the drop overall warning and error message trends from cppcheck aren't so bad considering the kernel has grown by nearly 11% over the time I have been running the static analysis.

Kernel source growth over time
Since each warning or error reported has to be carefully scrutinized to determine if they are false positives (and this takes a lot of effort and time), I've not yet been able determine the exact false positive rates on these stats.  Compared to the actual lines of code, cppcheck is finding ~1 error per 15K lines of source.

It would be interesting to run this analysis on commercial static analyzers such as Coverity and see how the stats compare.  As it stands, cppcheck is doing it's bit in detecting errors and helping engineers to improve code quality.

27 June, 2015 10:13AM by Colin Ian King (noreply@blogger.com)

Ronnie Tucker: Android equivalents on the Ubuntu phone

The idea behind this video is to show Ubuntu equivalents for my most used Android apps.

Ubuntu apps shown:
HERE / OSMtouch
File Manager

Honourable Mentions:

EDIT: The small font bug in OSMscout (on the MX4) is now fixed. Yay!

27 June, 2015 09:17AM

June 26, 2015

Costales: Review BQ E5 Ubuntu Edition

Desde hace casi medio año uso el BQ E4.5 Ubuntu Edition. Narré el acto de presentación, la entrevista a su CEO, una review a su hardware, al sistema operativo, a las aplicaciones, calidades de foto y batería, funda e incluso a la percepción en el día a día y tras un mes de uso.

Pero la apuesta de BQ no sólo ha quedado en ese modelo. La empresa española sigue apostando muy fuerte por nuestro sistema operativo móvil favorito, en esta ocasión con su buque insignia, el BQ E5, un móvil con una de las mejores calidades/prestaciones/precio del mercado.


El modelo E5 se nos presenta en una caja muy parecida a la del E4.5. Las letras rojas sobre negro ya nos indica qué joya alberga en su interior.
Exteriormente el móvil tiene líneas simples y elegantes, de tacto suave.
Internamente disponemos de doble SIM (podemos usar 2 números de teléfono simultáneamente) y soporte para ampliar el almacenamiento interno de 16GB con una microSD de hasta 32GB.

Muy buen diseño: sobrio y elegante
Su pantalla de 5" HD 720 x 1280 (294 HDPI) sobresale especialmente y es muy útil porque disponemos de un teclado más ancho para escribir más fácil. Tras probar el E5 una semana, al volver al E4.5 me parecía pequeño...

La pantalla, por resolución y tamaño es la mejor característica del dispositivo
La cámara de 13 Mp es mejor que la del E4.5. No sólo por más resolución, si no por más calidad de foto en color, contraste y luz:


Este par de fotos están hechas en el mismo sitio y a la misma hora:

BQ E4.5 Ubuntu Edition BQ E5 Ubuntu Edition

Su batería de 2500 mAH se nota y mucho. Dando para más horas que la del E4.5.

Pesa poco para la gran batería que tiene

¿Cual comprar? ¿E4.5 ó E5?
El E4.5 cuesta 169,9€ y el E5 cuesta 199,9€.
Si prefieres pagar lo mínimo y un móvil con pantalla normal tirando a grande y batería normal, el E4.5 te será perfecto.
Yo personalmente compraría el E5. Por sólo 30€ de diferencia, la calidad y tamaño de pantalla, cámara, batería y almacenamiento interno, merece la pena.


Puedes comprar el BQ E5 aquí. Puedes comprar el BQ E4.5 aquí.

Fotografías por David Castañón bajo licencia CC BY 3.0.

26 June, 2015 08:00PM by Marcos Costales (noreply@blogger.com)

hackergotchi for SparkyLinux


SparkyLinux 4.0


I am happy to announce SparkyLinux 4.0 code name “Tyche”.
Sparky 4 is based on and fully compatible with Debian 9 testing “Stretch”.

The new iso images feature a set of applications for daily usage, wireless drivers, multimedia codecs and plugins, and they are available in a few flavors, such as :
– LXQt
– Xfce

Following Wikipedia, “Tyche” – the new Sparky 4 code name means:

Tyche is the nickname given to a hypothetical gas giant located in the Solar System’s Oort cloud. Tyche (Τύχη, meaning “fortune” or “luck” in Greek) was the Greek goddess of fortune and prosperity.

The most important changes between Sparky 3.6 and 4.0 :
– full system upgrade from Debian testing repository as of 22/06/2015
– Linux kernel 4.0.5
– added support for the system installation on 32 bit machines with UEFI motherboard
– Razor-Qt Edition has been dropped
– added two new editions: KDE and LXQt
– system rebranding, see HowTo: http://sparkylinux.org/sparky-rebranding/
– new flat theme “Sparky4″ and a set of icons “Ultra-Flat-Icons”
– added Pipelight repository and the public key
– Gnome-Alsamixer has been replaced by Pulse Audio Mixer (LXDE & LXQt editions)
– Mplayer2, Gnome-player and Gecko-player have been removed
– VLC is the default video player now
– added vlc-mozilla-plugin for Iceweasel

Sparky APTus features a few new options:
– Liquorix kernel installation
– i686-pae kernel installation for 32 bit systems
– office suite installation (via ‘sparky-office’ package):
— AbiWord & Gnumeric
— Calligra
— LibreOffice
— MS Office OnLine (Menu shortcuts)
— OpenOffice
— WPS Office

Sparky APTus Extra has gotten options to let you install Google Chrome and Google Earth.

Sparky LXQt features two window managers of your choice:
– lightweight Openbox
– Kwin which lets you enable 2D and 3D desktop’s visual effects
To swith to KWin, go to: Menu-> Preferences-> LXQt Settings-> Session Settings
Then log out and log in back.

32 bit edition of SparkyLinux features Linux kernel i586 NON-PAE.
If you would like to install i686-pae kernel, you can do it via Sparky APTus-> Install tab-> Install i686-PAE Kernel. Just remember to refresh package list before.

Starting from Sparky 4.0, the live images offer support for installation the system on 32 bit machines with UEFI motherboard.
As an addition, all the traditional ‘grub-efi’ files have been removed from the live iso images and replaced by own, custom ‘efi.img’ files built by MoroS using his custom script.

The new iso images can be used to make fresh system installation.
In a case of any problem with the default installer (live-installer), try the older one (Bios machines only) via Menu-> System-> SparkyLinux (Old) Installer or launch it via the command:
sudo sparkylinux-installer gui
or (text mode):
sudo sparkylinux-installer
If you have SparkyLinux installed on a hard drive, make full system upgrade via ‘System Upgrade’ tool, Synaptic or manually:
sudo apt-get update
sudo apt-get dist-upgrade
sudo apt-get install -f

Users of Sparky 3.6 (and older) should install ‘sparky-core’ package as well:
sudo apt-get update
sudo apt-get install sparky-core

Users of Sparky 4.0 RC should make full system upgrade.

Users of Sparky 4.0 RC KDE can fix the layout of the default Sparky’s window’s theme:
sudo apt-get update
sudo apt-get remove sparky-theme-root-kde
sudo apt-get install sparky-theme-root sparky-kde-colors

Then open KDE System Settings-> Application Appearance-> Colors and choose Sparky.

Minimum system requirements to install SparkyLinux:
* CPU i586 / amd64
* RAM memory:
– LXDE, LXQt – 256MB (recommended 512MB or bigger)
– MATE, Xfce – 512MB (recommended 1GB)
– KDE – 1GB (recommended 2GB)
* 512MB SWAP partition or bigger
* 10GB of hard drive or flash USB stick for installation
* an optical drive or USB port

The Live/Install iso images of Sparky 32 and 64 bit can be downloaded from download page.

SparkyLinux LXDE

Other Sparky’s Editions “Base”, “CLI” and “GameOver” will be released soon as well.

Informacja o wydaniu w języku polskim-> http://linuxiarze.pl/sparkylinux-4-0


26 June, 2015 05:44PM by pavroo

hackergotchi for Ubuntu developers

Ubuntu developers

Nekhelesh Ramananthan: Approaching the Meizu MX4 Challenge Deadline

The Meizu MX4 Challenge deadline is approaching fast with just a few days to go. July 1st is the last day for submissions to be accepted for the challenge.


Registering your submission

To register your submission for the judges review, you will need a couple of minutes to fill in the registration form. You can find the registration form here.

Scope Submissions

Please submit your scopes to the store. The upload workflow is exactly the same as for apps, and with automated reviews it takes just a few minutes from upload to your scope being available for everyone on the Ubuntu Software Store. When you're ready to start the upload, you can follow the 5-step process to get it published.

Design Submissons

The challenge was also targeted at designers to showcase their design mockups to improve the UX experience of apps and scopes in the UT ecosystem. Feel free to upload your work to any publicly accessible sites like Google Drive, Dropbox, G+ etc.

If you have any questions, feel free to contact me by email or in IRC #ubuntu-app-devel (nik90, popey).

Good Luck!

26 June, 2015 04:10PM

Ronnie Tucker: Full Circle #98 has arrived!



Full Circle – the independent magazine for the Ubuntu Linux community are proud to announce the release of our ninety-eighth issue.

This month:
* Command & Conquer
* How-To : Conky Reminder, LibreOffice, and Programming JavaScript
* Graphics : Inkscape.
* Chrome Cult
* Linux Labs: Midnight Commander
* Ubuntu Phones
* Review: Saitek Pro Flight System
* Book Reviews: Automate Boring Stuff With Python, and Teach Your Kids To Code
* Ubuntu Games: Minetest, and Free to Play Games
plus: News, Arduino, Q&A, and soooo much more.

Get it while it’s hot!

26 June, 2015 02:53PM

Ubuntu Podcast from the UK LoCo: S08E16 – The Hottie & the Nottie - Ubuntu Podcast

It’s Episode Sixteen of Season Eight of the Ubuntu Podcast! Alan Pope, Mark Johnson, Laura Cowen, and Martin Wimpress are all together again and speaking to your brain.

In this week’s show:

That’s all for this week, please send your comments and suggestions to: show@ubuntupodcast.org
Join us on IRC in #ubuntu-podcast on Freenode
Follow us on Twitter
Find our Facebook Fan Page
Follow us on Google+

26 June, 2015 12:34PM

June 25, 2015

hackergotchi for Whonix


Why I prefer PGP/INLINE over PGP/MIME in Thunderbird/Enigmail

Due to the recent Enigmail security issue, where e-mail drafts could end up unencrypted on IMAP servers. (You might wonder, no, Whonix was luckily not affected by this, because the version in Debian wheezy did not have that bug.)

In the PGP/INLINE example I can be more assured, that the text was that it really converted to encrypted ciphertext before sending – because I can see it.


As opposed to PGP/MIME, where I need to trust more, that Enigmail won’t mess that up.


Using option ‘Confirm, before sending’ set to ‘Always’, that I highly recommend to prevent messing up.

The post Why I prefer PGP/INLINE over PGP/MIME in Thunderbird/Enigmail appeared first on Whonix.

25 June, 2015 10:47PM by Patrick Schleizer

hackergotchi for Ubuntu developers

Ubuntu developers

The Fridge: Wily Werewolf Alpha 1 Released

"I’m getting really sick of being misquoted in release announcements."
– Oscar Wilde, probably.

The first alpha of the Wily Werewolf (to become 15.10) has now been released!

This alpha features images for Kubuntu, Lubuntu, Ubuntu MATE, UbuntuKylin and the Ubuntu Cloud images.

Pre-releases of the Wily Werewolf are *not* encouraged for anyone needing a stable system or anyone who is not comfortable running into occasional, even frequent breakage. They are, however, recommended for Ubuntu flavor developers and those who want to help in testing, reporting and fixing bugs as we work towards getting this release ready.

Alpha 1 includes a number of software updates that are ready for wider testing. This is quite an early set of images, so you should expect some bugs.

While these Alpha 1 images have been tested and work, except as noted in the release notes, Ubuntu developers are continuing to improve the Wily Werewolf. In particular, once newer daily images are available, system installation bugs identified in the Alpha 1 installer should be verified
against the current daily image before being reported in Launchpad. Using an obsolete image to re-report bugs that have already been fixed wastes your time and the time of developers who are busy trying to make 15.10 the best Ubuntu release yet. Always ensure your system is up to date before reporting bugs.


Kubuntu uses KDE software and now features the new Plasma 5 desktop.

The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/kubuntu/releases/wily/alpha-1/

More information on Kubuntu Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/Kubuntu


Lubuntu is a flavour of Ubuntu based on LXDE and focused on providing a very lightweight distribution.

The Alpha 1 images can be downloaded at: http://cdimage.ubuntu.com/lubuntu/releases/wily/alpha-1/

More information on Lubuntu Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/Lubuntu

Ubuntu MATE

Ubuntu MATE is a flavour of Ubuntu featuring the MATE desktop environment.

The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/ubuntu-mate/releases/wily/alpha-1/

More information on Ubuntu MATE Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/UbuntuMATE


UbuntuKylin is a flavour of Ubuntu that is more suitable for Chinese users.

The Alpha-1 images can be downloaded at: http://cdimage.ubuntu.com/ubuntukylin/releases/wily/alpha-1/

More information on UbuntuKylin Alpha-1 can be found here: https://wiki.ubuntu.com/WilyWerewolf/Alpha1/UbuntuKylin

Ubuntu Cloud

Ubuntu Cloud images can be run on Amazon EC2, Openstack, SmartOS and many other clouds.


Regular daily images for Ubuntu can be found at: http://cdimage.ubuntu.com

If you’re interested in following the changes as we further develop Wily, we suggest that you subscribe to the ubuntu-devel-announce list. This is a low-traffic list (a few posts a week) carrying announcements of approved specifications, policy changes, alpha releases and other interesting events.


A big thank you to the developers and testers for their efforts to pull together this Alpha release!

Originally posted to the ubuntu-devel-announce mailing list on Thu Jun 25 18:35:35 UTC 2015 by Adam Conrad on behalf of the Ubuntu Release Team,

25 June, 2015 08:02PM

Kubuntu: Kubuntu Wily Alpha 1

The first Alpha of Wily (to become 15.10) has now been released!

The Alpha-1 images can be downloaded from: http://cdimage.ubuntu.com/kubuntu/releases/wily/alpha-1/

More information on Kubuntu Alpha-1 can be found here: https://wiki.kubuntu.org/WilyWerewolf/Alpha1/Kubuntu

25 June, 2015 07:54PM