Category Archives: Linux Stuff

Linux Stuff

How To Install GNOME 3.14 In Ubuntu GNOME 14.10

GNOME 3.14 was released back in September and it includes some interesting changes like multi-touch gestures for both the system and applications, re-worked default theme, new animations as well as various enhancements for the code GNOME applications. More information HERE.

GNOME 3.14 Ubuntu 14.10

Unfortunately, Ubuntu GNOME 14.10 (Utopic Unicorn) ships with GNOME 3.12 for the most part (there are even some GNOME 3.10 packages, like Gedit or Nautilus) but, as usual, you can install the latest GNOME (3.14) by using a PPA.

Unlike previous versions, installing GNOME 3.14 from the GNOME 3 Staging PPA in Ubuntu 14.10 doesn’t break Unity however, there are things that don’t work as they should, like:
  • very large icons for some apps in Unity Dash and other places – screenshot;
  • the default Ubuntu theme (Ambiance) doesn’t work properly with some applications (screenshot) and Adwaita doesn’t support Unity’s CSS window decorations so you’ll have to use a theme that supports GTK 3.14 and Unity, like Zukitwo, but even then you may encounter various issues like up/down arrows for indicators (screenshot);
  • Nautilus, Totem and Gedit use client-side decorations and the default GNOME menu, so they will look out of place in Unity.

And that’s just on a first look so there might be many other issues. That’s why I don’t recommend using this PPA if you’re using Unity!
As usual, the latest GNOME is available in the GNOME 3 Staging PPA and it’s not considered ready for general use (you will encounter bugs!), so make sure you read the PPA description before using it. Follow the instructions below on your own risk and only if you know how to fix your system in case something goes wrong!

There are two more things I should mention, so you’ll know what to expect:

  • on my laptop running Ubuntu 14.10, applications that use client-side decorations have a large shadow at the bottom (screenshot). This didn’t occur in the two virtual machines I’ve tested the GNOME 3.14 installation under Ubuntu 14.10, but you may encounter this bug, and I didn’t find out what’s causing it;
  • CSD applications have minimize and maximize buttons for some reason, even though GNOME doesn’t use this by default – you can disable them via GNOME Tweak Tool  > Windows > Titlebar Buttons.

Install GNOME 3.14 in Ubuntu GNOME 14.10

Warning: Please read the output before entering ‘Y’ for the “dist-upgrade” command below to make sure important packages won’t be removed and if the “dist-upgrade” command tries to remove important pages, abort the installation and remove the PPA! Also, it’s a good idea to save the list of packages upgraded by using the instructions below, in case you want to revert the changes and ppa-purge fails.
Currently, only the GNOME 3 Staging PPA is required to upgrade to GNOME 3.14 in Ubuntu 14.10 however, some packages might be moved to the GNOME 3 PPA later on and that might break things if you didn’t enable this PPA on your system, that’s why by following the instructions below, you’ll add both the GNOME 3 PPA and the GNOME 3 Staging PPA.

That said, let’s proceed

1. Install GNOME 3.14

To add the GNOME 3 and GNOME 3 Staging PPAs and upgrade to GNOME 3.14 in Ubuntu GNOME 14.10, use the following commands:

sudo add-apt-repository ppa:gnome3-team/gnome3-staging
sudo add-apt-repository ppa:gnome3-team/gnome3
sudo apt-get update
sudo apt-get dist-upgrade

During the GNOME 3.14 upgrade (or purge) process, you may encounter an issue similar to this:

(gtk-update-icon-cache-3.0:29077): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory

This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.

If that happens, firstly install libgdk-pixbuf2.0-dev:

sudo apt-get install libgdk-pixbuf2.0-dev

And then fix this issue by running the following commands:

– 32bit:

sudo -i
gdk-pixbuf-query-loaders > /usr/lib/i386-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

– 64bit:

sudo -i
gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache

2. Reboot (a simple logout / login may not be enough so to avoid any issues, reboot your system).
3. (Optional) Install GNOME 3 applications not available by default in Ubuntu GNOME 14.10.

GNOME 3.14 apps

You may also want to install the GNOME 3 apps which are not available by default in Ubuntu GNOME 14.10 (Polari, Bijiben, Clocks, Sound Recorder, etc.) – install them using the command below:
sudo apt-get install polari gnome-sound-recorder bijiben gnome-clocks gnome-music gnome-photos gnome-boxes

(Epiphany is still at version 3.12.0)

How to revert the changes

If for whatever reason you want to revert the changes made by adding the GNOME 3 and GNOME 3 Staging PPAs, you can purge them (purging a PPA downgrades all the packages from that PPA to the version available in the official Ubuntu repositories and disables the PPA) using ppa-purge:
sudo apt-get install ppa-purge
sudo ppa-purge ppa:gnome3-team/gnome3
sudo ppa-purge ppa:gnome3-team/gnome3-staging

Read More

Folder Color Gets Caja And Nemo File Managers Support, Other Changes

Folder Color is a file manager extension that allows you to easily change folders  icon color, useful for instance to organize your folders, make some important folder stand out, etc.
The latest Folder Color, which already supported Nautilus, adds support for Caja (the default MATE file manager) and Nemo (the default Cinnamon file manager):

Folder Color Caja
Folder Color for Caja file manager

Folder Color Nemo
Folder Color for Nemo (with icons enabled in menus)

Until now, I maintained an unofficial version of Folder Color for Nemo, but because the WebUpd8 Nemo PPA only works with Ubuntu, Linux Mint users couldn’t install it. Now that Folder Color officially supports Nemo, both Ubuntu and Linux Mint (Cinnamon) users can install this extension by using the official Folder Color PPA.

Other recent Folder Color changes include:

  • Folder Color is now themable, meaning that it is no longer restricted to the default Ubuntu / Linux Mint icon themes. Unfortunately, no icon themes support it for now, but Numix should support it soon;
  • support for small icon resolution (if for instance you’re using grid/list view with zoom out);
  • icons in submenu: you can now see the actual folder color in the submenu, but firstly you need to enable icons in menu by using the following command: gsettings set org.gnome.settings-daemon.plugins.xsettings overrides "{'Gtk/ButtonImages': , 'Gtk/MenuImages': }" (to revert it, simply use “0” instead of “1” for ButtonImages and MenuImages).

Install Folder Color for Caja, Nemo or Nautilus in Ubuntu or Linux Mint

Firstly, add the Folder Color PPA:

sudo add-apt-repository ppa:costales/folder-color
sudo apt-get update

Then, follow the instructions for your file manager:

a) To install the Folder Color Nautilus extension and restart Nautilus, use the following commands:
sudo apt-get install folder-color
nautilus -q

b) To install Folder Color for Nemo in Ubuntu or Linux Mint (Cinnamon edition) and restart Nemo, use the commands below:
sudo apt-get install folder-color-nemo
nemo -q

If Folder Color doesn’t show up in the Nemo context menu, you need to apply the fixes from HERE (step 4 only).

c) To install Folder Color for Caja and install it in Ubuntu (w/ MATE), Ubuntu MATE or Linux Mint (MATE edition) and restart Caja, use the following commands:
sudo apt-get install folder-color-caja
caja -q
If Folder Color doesn’t show up in the Caja context menu, fix it by using the following command:

– 32bit:

sudo ln -s /usr/lib/i386-linux-gnu/girepository-1.0/Caja-2.0.typelib /usr/lib/girepository-1.0/Caja-2.0.typelib

– 64bit:

sudo ln -s /usr/lib/x86_64-linux-gnu/girepository-1.0/Caja-2.0.typelib /usr/lib/girepository-1.0/Caja-2.0.typelib

thanks to Costales for the info!

Read More

Ubuntu Developer Tools Center 0.1 Released With Eclipse And Android ADT Support

Ubuntu Developer Tools Center (UDTC) 0.1 was released today and it includes support for Eclipse as a standalone IDE, Android ADT support (through Eclipse) and more. 

Ubuntu Developer Tools Center Eclipse

A couple of months ago, Canonical released Ubuntu Developer Tools Center (UDTC), a project to “enable quick and easy setup of common developers needs on Ubuntu”. Using it, you can easily install Android Studio and the Android SDK in Ubuntu and, with the latest version, Eclipse and Android ADT (for Eclipse).
In the release announcement, Didier Roche, Software Engineer at Canonical, mentioned that for now, Canonical is focusing on Android developers, but more will follow, like Go developers, web developers, Dart and more.

Changes in Ubuntu Developer Tools Center 0.1:

  • added Eclipse support as a standalone IDE. Usage: udtc ide eclipse;
  • added Android ADT support (through Eclipse). Usage: udtc android eclipse-adt;
  • adb and other Android tools are now added to user path while installing an Android framework;
  • UDTC now supports framework removal. If you installed a framework and want to remove it, just use: udtc android android-studio –remove;
  • enabled loading of local framework. They are controlled by UDTC_FRAMEWORKS env variable which can point to any path containing local frameworks;
  • added support for reinstallation in different folder than the origin one, cleaning the original directory;
  • DownloadCenter now support redirections;
  • added support for decompressing zip files in Decompressor;
  • new and refresh translations: de, en_AU, en_CA, en_GB, es, eu, fr, hr, it, pl, ru, te, zh_CN, zh_HK;
  • improved i18n support;
  • protect against mistyping with multiple frameworks;
  • framework support refactoring to avoid code duplication;
  • tests fixes and refactoring for better scalability;
  • fixed logging support during test runs;
  • reshape docker files to have fewer layers;
  • don’t raise any Exception for unexpected CLI args.

Install Ubuntu Developer Tools Center

The latest Ubuntu Developer Tools Center 0.1 is available in the Ubuntu 15.04 Vivid Vervet repositories. 
For Ubuntu 14.10 and 14.04, you can install the latest Ubuntu Developer Tools Center by using a PPA:
sudo add-apt-repository ppa:didrocks/ubuntu-developer-tools-center
sudo apt-get update
sudo apt-get install ubuntu-developer-tools-center

That’s it. You can now use UDTC to install Android Studio, Android SDK, Eclipse and add Android adt support (through eclipse).
Install Android Studio and Android SDK by using the following command:
udtc android
Then, choose the installation path (or use the default path), accept the license (“a”) and UDTC will do the rest, installing Android Studio and Android SDK. UDTC will even add Android Studio to the Unity Launcher.

To install Eclipse (Eclipse Luna 4.4 at the time I’m writing this article), simply use the command below:
udtc ide eclipse
After installing it (just like with Android Studio), UDTC will add Eclipse to the Unity Launcher.

For Android ADT support (through Eclipse), use the following command:

udtc android eclipse-adt

If you want to remove a framework, simply append “–remove” to the commands above. For example, to remove Eclipse, use the following command:
udtc ide eclipse --remove

If you want to help with the Ubuntu Developer Tools Center development, report bugs, etc., check out its GitHub page.

Read More

Turn your Android tablet into color fidelity multitool with ArgyllPRO ColorMeter

Graeme Gill has just announced immediate availability of ArgyllPRO ColorMeter, a commercial Android app that allows using colorimeters and spectrophotometers directly via the USB on-the-go port.

What is it good for? Graeme lists a number of possible use cases:

Use your X-Rite Eye-One Display Pro to make accurate measurements of ambient, spot or display light levels and color temperature for Photography or Lighting design. Measure and calibrate Televisions and Projectors using a Klein K10-A. Check print samples using your ColorMunki spectrometer or Eye-One Pro 2 in the field. Obtain accurate sample measurements to incorporate into your documents or web pages, and find the closest matching color swatch instantly. Check movie theater certification using a JETI specbos 1211 — ArgyllPRO ColorMeter has you covered.

If you’ve been wondering, how Graeme is supposed to get compensation for his passionate professional-level work on free/libre color management tools for the past decade, this might just be it: a commercial app for the Android platform where there is virtually no competition between color management related tools.

Ambient lighting measurement

Here’s a quick reality check:

Spectropocket is a lot like ColorMeter (or vice versa), but you are paying for additional hardware ($1,299 for the whole solution), and measurement devices support is limited to i1Pro, i1Pro 2, and ColorMunki Design.

X-Rite ColorTRUE doesn’t connect to the actual device and focuses primarily on adjusting display output for particular tasks at hand (like softproofing) and lighting conditions using desktop/laptop-generated ICC profiles. It’s also limited to ColorMunki Display and i1Display Pro devices.

Datacolor SpyderGALLERY, in return, seems to be an app whose developers were of two minds what they were going to do with it. This is both a calibration/profiling app, hardcoded to use Spyder 4 colorimeters only, and a photo gallery viewer with a CMS on/off switch (the same applies to X-Rite ColorTRUE, really).

As you can see, ColorTRUE/SpyderGALLERY vs. ColorMeter/Spectropcket are a bit like apples and oranges. And between the four of them only ColorMeter is truly omnivore in terms of vendors and models supported.

Spot reflectance measurement

It took Graeme two years to complete and roll out the first public release, given that it was a one-person project, as well as all the work involved with supporting ArgyllCMS and writing new features for it, such as video profiling & 3D LUT creation support. Developing for an entirely new platform wasn’t easy either. Graeme shares:

I had instruments working two weeks after I got my Nexus 7, but the learning curve was fierce — it was 9 months before I felt I knew my way around the UI code to some degree, and I needed to put enough into the app to at least show the potential of it. Inventing pinch-zoom graphs with automatically scaling non-linear axe labels takes time.

The Android API is both good/easy & hard/buggy. Do it in just the right way, and everything is easy. It mostly works as advertised. Stray off that path, and you’re grepping through the Android source code, desperately trying to figure if it’s your misunderstanding or bug, or whether it’s a bug in Android. Stackoverflow is the absolutely vital resource in all that.

Android is missing things you would think should be built in, like gesture sortable lists, or automatic feature scaling with screen size, so I had to invent my own code to do this sort of thing.

It’s important to note that the will be no iOS version for those of us with iPads, because Apple doesn’t make it easy to access USB devices. Over to Graeme again:

I suspect [X-Rite & DataColor] are a bit stumped by iOS not having USB. They can’t bring themselves to give up on 60% of the USA market. X-Rite is big enough to solve the problem with brute force — either fit new instruments with WiFi/Blue tooth, or make a USB host adapter and join Apples HW development program. They may well be working on such a thing, so I was keen to beat them to a release.

At AU$110, the app is not exactly cheap, although the unique combination of features and platform they are available on might just make up for the price to you. And there is a demo version of the app that is “fully functional, except that it shows a sequence of 8 pre-determined readings instead of the true measurement values from your instrument”.

You might have already seen a similar revenue model with e.g. LibRaw which is the base for RawDigger and FastRawViewer — all three projects being made by LibRaw LLC. This keeps the company afloat (although, frankly, both LibRaw LLC developers have other successful businesses), and GPL makes it possible for projects like digiKam to provide reliable support for RAW files.

It’s going to be interesting to see how getting into the mobile development business with ArgyllPRO ColorMeter will work for Graeme who’s among very few people responsible for making color management on Linux just work.

Read More

ownCloud Ubuntu Package Affected By Multiple Critical Security Issues, Nobody To Fix It


ownCloud developer Lukas Reschke has sent an email to the Ubuntu Devel mailing list, requesting that ownCloud (server) is removed from the Ubuntu repositories because the package is old and there are multiple critical security bugs for which no fixes have been backported. He adds that:

“Those security bugs allows an unauthenticated attacker to gain complete control about the web server process”.

However, packages can’t be removed from the Ubuntu repositories for an Ubuntu version that was already released, that’s why the package was removed from Ubuntu 14.10 (2 days before its release) but it’s still available in the Ubuntu 14.04 and 12.04 repositories (ownCloud 6.0.1 for Ubuntu 14.04 and ownCloud 5.0.4 for Ubuntu 12.04, while the latest ownCloud version is 7.0.2).

Furthermore, the ownCloud package is in the universe repository and software in this repository “WILL NOT receive any review or updates from the Ubuntu security team (you should see this if you take a look at your /etc/apt/sources.list file) so it’s up to someone from the Ubuntu community to step up and fix it. “If nobody does that, then it unfortunately stays the way it is“, says Marc Deslauriers, Security Tech Lead at Canonical.

You can follow the discussion @ Ubuntu Devel mailing list.

So, until (if) someone fixes this, if you’re using ownCloud from the Ubuntu repositories, you should either remove it or upgrade to the latest ownCloud from its official repository, hosted by the openSUSE Build Service:

For Ubuntu 14.04:

sudo sh -c "echo 'deb /' >> /etc/apt/sources.list.d/owncloud.list"
sudo apt-get update
sudo apt-get install owncloud

For Ubuntu 12.04:

sudo sh -c "echo 'deb /' >> /etc/apt/sources.list.d/owncloud.list"
sudo apt-get update
sudo apt-get install owncloud

Read More

Fix Brightness Getting Reset (To A Very Low Value Or Maximum) On Reboot In Ubuntu

If your laptop’s brightness is not saved and is set to a very low value or to maximum, each time you reboot and / or when you log out, read on for a fix / workaround.

Ubuntu brightness

In both Ubuntu 14.04 and 14.10, my laptop’s brightness is not saved between sessions and is reset to a very low value after every reboot or logout. I found a workaround (that works for both this issue as well as another issue which is basically the opposite: the brightness is set to maximum after restarting Ubuntu), but it was a bit confusing so I thought I’d improve the steps and share it with you.

Basically, the fix / workaround is to automatically set a custom brightness value each time you boot into Ubuntu. Let’s proceed.

1. The first thing you need to do is to find out which ACPI interface (acpi_video) controls the brightness. This can be done by looking into your Xorg log file to see which acpi_video was loaded. To do this via command line, simply use the following command:
grep acpi_video /var/log/Xorg.0.log

The command above should display an output similar to this:

[     7.385] (--) intel(0): Found backlight control interface acpi_videoX (type 'firmware') for output LVDS1
where “acpi_videoX” is “acpi_video0” or “acpi_video1”. This is the acpi_video that controls the brightness, so remember it for the next steps.

If the command above doesn’t display any output and you have a folder called “intel_backlight” under “/sys/class/backlight/”, then use “intel_backlight” as the ACPI interface for the next steps.

2. Next, set (via keyboard Fn + brightness keys) your laptop’s brightness to the level you want Ubuntu to use after when it starts.

3. Now we’ll have to get the actual brightness value you set under step 2. To do this, run the following command:
cat /sys/class/backlight/acpi_videoX/brightness
where “acpi_videoX” is the ACPI interface which controls your laptop’s brightness, which you find out under step 1.

Remember this value for the next step.

4. The next step is to create a file (as root) called fixbrightness.conf in your /etc/init/ directory – I’ll use Gedit below:
gksu gedit /etc/init/fixbrightness.conf

And in this file, paste this:

description "Sets brightness after graphics device is loaded"

start on graphics-device-added
exec /bin/echo BRIGHTNESS_VALUE > /sys/class/backlight/acpi_videoX/brightness

here, you need to:

  • replace BRIGHTNESS_VALUE with the brightness value you got under step 3;
  • replace acpi_videoX with the ACPI Interface that controls your laptop’s brightness, which you found out under step 1.

Then save the file.

5. Reboot and the low or maximum brightness issue after reboot / logout should be fixed.

via AskUbuntu but I tried to improve the instructions

Read More