That's no longer the case thanks to the Proprietary GPU Drivers PPA, which offers stable proprietary Nvidia graphics driver updates, without updating other libraries to unstable versions (some libraries may still be updated using this PPA, if they are needed by the drivers, but there's nothing unstable in the PPA).
Despite its name, the PPA only provides proprietary Nvidia graphics drivers updates, with no support for AMD or Intel.
Even though the PPA is probably the most stable way of upgrading to the latest proprietary Nvidia drivers version in Ubuntu, it's still considered in testing. That means issues may still occur (though I didn't encounter any and I've been using it for some time), so you should only use this PPA if you have experience with recovering your system from a failed graphics driver upgrade.
I should also mention that the PPA provides packages for all supported Ubuntu versions (16.10, 16.04, 15.10, 14.04 and 12.04). At the time I'm writing this article, the PPA provides the latest long lived branch version (367.27) of the Nvidia graphics drivers for Ubuntu 16.10 and 16.04 and the latest short lived branch version (364.19) for Ubuntu 15.10, 14.04 and 12.04.
You can check the latest Nvidia Linux graphics drivers version by visiting THIS page.
Install the latest Nvidia graphics drivers in Ubuntu via PPA
1. Add the PPA.
Before proceeding, please read the PPA description!
To add the Proprietary GPU Drivers PPA in Ubuntu and update the software sources, use the following commands:sudo add-apt-repository ppa:graphics-drivers/ppa
sudo apt update
2. Install (and activate) the latest Nvidia graphics drivers
From System Settings or directly from the menu / Dash, open Software & Updates, click on the "Additional Drivers" tab, select the driver you want to use, and click "Apply changes":
After the driver is downloaded and installed, restart your system. That's it!
You can also install the latest drivers using Synaptic or from the command line. To see the available versions, you can use:apt-cache search nvidiaor:
apt search nvidiaAnd look for the packages called "nvidia-VERSION", for instance "nvidia-367" for the latest 367.27 graphics drivers, and install it ("sudo apt install nvidia-VERSION").
i3-hud-menu allows searching and navigating through an application's menu using the keyboard, with the use of dmenu (dmenu doesn't have mouse support by default). Here's how it looks like in Xubuntu 16.04:
And in Linux Mint 17.3 Cinnamon:
i3-hud-menu works with GTK2, GTK3 (but not client-side decorated apps) and Qt4 applications.
The tool is buggy with Qt5 applications as well as LibreOffice - see the limitations / issues section below for more information.
Important: issues and limitations
i3-hud-menu has quite a few issues / limitations but I decided to post an article about it anyway since some of you might still find it useful.
Also, I'm hoping someone reading this article might be able to fix or at least come up with some workarounds for some of the issues below. If you do, please let us know in the comments!
i3-hud-menu limitations / issues:
- it doesn't work with client-side decorated applications;
- it doesn't work with Firefox or Thunderbird;
- it doesn't work with Qt5 apps (make sure appmenu-qt5 and libdbusmenu-qt5 are not installed or else you won't have a menu for Qt5 apps, such as VLC in Ubuntu 16.04 - if you do install those packages, you can use the menu via i3-hud-menu, but the actual menu won't be visible in the application);
- using it, LibreOffice no longer has a menu if the "libreoffice-gtk" package is installed - this package is used for GTK+ integration (though using i3-hud-menu, you can search the menu, but actually using the menu items doesn't work for some reason);
- to get i3-hud-menu to work with Java swing applications, you'll need JAyatana;
- probably more.
It appears that the LibreOffice and the Qt5 applications issue occur because "APPMENU_DISPLAY_BOTH=1" is not respected. Furthermore, using "UBUNTU_MENUPROXY=" (for example, using "UBUNTU_MENUPROXY= libreoffice --writer") or blacklisting it via Dconf Editor (com > canonical > unity-gtk-module > blacklist) doesn't get the LibreOffice menu to show up.
On Arch Linux (possibly in other Linux distributions as well), which requires the unity-gtk-module-standalone-bzr package, you need to run the following command (or change this via Dconf Editor: com > canonical > unity-gtk-module, set gtk2-shell-shows-menubar to "false") and reboot to ensure that menus are displayed in GTK applications:
gsettings set com.canonical.unity-gtk-module gtk2-shell-shows-menubar false
Install and configure i3-hud-menu
Important note: I included exact instructions for Xubuntu, Ubuntu MATE and Linux Mint Cinnamon edition, but this should work with any Ubuntu or Linux Mint flavor (14.04 and newer only). It may also work in other Linux distributions, as long as you can install unity-gtk-module and appmenu-qt.
1. Install the required dependencies: python3, python-dbus, dmenu, appmenu-qt and unity-gtk-module.
In Ubuntu (14.04 and newer), use the following command (will also install "wget", required under step 2):sudo apt install python3 python-dbus dmenu appmenu-qt unity-gtk2-module unity-gtk3-module wget
2. Download and install i3-hud-menu
To download and install J.A. McNaughton's i3-hud-menu fork from the command line, use the following commands:
tar -xvf master.tar.gz
sudo mkdir -p /opt/i3-hud-menu
sudo cp -r i3-hud-menu-master/* /opt/i3-hud-menu/
If you want to install it yourself, grab the code from GitHub (but note that the instructions below assume that you've installed i3-hud-menu in /opt/i3-hud-menu/)
3. Load the Unity gtk module
Open ~/.profile with a text editor (".profile" is a hidden file in your home folder so use Ctrl + H to see hidden files in your gile manager), paste the following at the end of the file:export APPMENU_DISPLAY_BOTH=1
if [ -n "$GTK_MODULES" ]
if [ -z "$UBUNTU_MENUPROXY" ]
export UBUNTU_MENUPROXY... and save the file.
If after completing all the steps below, i3-hud-menu doesn't work, you can try to paste the lines above in ~/.bashrc instead of ~/.profile.
4. Add i3-appmenu-service.py to startup
The next step is to add i3-appmenu-service.py to the system startup. If you've installed i3-hud-menu using the commands above, this file should be located in /opt/i3-hud-menu/
Xubuntu: To add i3-appmenu-service.py to startup, launch Session and Startup from the menu / System Settings, and on the "Application Autostart" tab click "Add", enter "i3 menu service" under "Name", and "/opt/i3-hud-menu/i3-appmenu-service.py" (without the quotes) under "Command":
Ubuntu MATE: launch Control Center and open Startup Applications, click "Add", use "i3 menu service" under "Name", and "/opt/i3-hud-menu/i3-appmenu-service.py" (without the quotes) under "Command", and click "Add":
Linux Mint (Cinnamon): launch Startup Applications from the menu, click Add > Custom Command, use "i3 menu service" under "Name", and "/opt/i3-hud-menu/i3-appmenu-service.py" (without the quotes) under "Command", and click "Add":
5. Assign a keyboard shortcut to i3-hud-menu.py
The keyboard shortcut you assign to i3-hud-menu.py will be used to open i3-hud-menu and search through an application's menu. Here's how to configure it in some Ubuntu flavors and Linux Mint (Cinnamon).
Xubuntu: open "Keyboard" from the menu / System Settings, and on the "Application Shortcuts" tab, click "Add". Use "/opt/i3-hud-menu/i3-hud-menu.py" (without the quotes; if you've installed i3-hud-menu to a different location, make sure you use the correct path) for the command, click "OK:
... and assign it a keyboard shortcut:
You can even use "Alt", like in Ubuntu (with Unity), but I don't recommend it as you won't be able to use other shortcuts that use Alt. You can use something like Alt + 1 or any other keyboard shortcut that's not already in use.
Ubuntu MATE: from Control Center open Keyboard Shortcuts, click "Add", under "Name" enter "i3-hud-menu" (without the quotes), and use "/opt/i3-hud-menu/i3-hud-menu.py" (without the quotes; if you've installed i3-hud-menu to a different location, make sure you use the correct path) for "Command":
... and assign it a keyboard shortcut. Note that unlike Xubuntu, Ubuntu MATE doesn't allow assigning Alt as a shortcut. You can use something like Alt + 1 or whatever other keyboard shortcut you want, but make sure it's not already in use.
Linux Mint (Cinnamon): launch Keyboard from the menu, click "Add custom shortcut", enter "i3-hud-menu" (without the quotes) under "Name", "/opt/i3-hud-menu/i3-hud-menu.py" (without the quotes; if you've installed i3-hud-menu to a different location, make sure you use the correct path) under "Command" and click "Add":
... and assign it a keyboard shortcut.
6. And finally, restart the session (logout/login), focus an application and use the keyboard shortcut you set in step 5 to open i3-hud-menu.
via / further reference:
Oomox supports GTK3 and GTK2, and it includes Openbox and Xfwm4 themes. Unity is also supported, though changing the window buttons color is not yet supported.
The required GTK version is 3.16 or newer - as far as Ubuntu is concerned, that means Oomox supports Ubuntu (and derivatives: Ubuntu GNOME, Xubuntu, Ubuntu MATE and Lubuntu) 15.10 and 16.04.
The latest Oomox 0.17.0, released recently, brings options for roundness and gradient, along with various other improvements. Also, to make it easier to install in Ubuntu, I uploaded it to the main WebUpd8 PPA (based on the AUR package).
Changes in Oomox 0.17.0:
- new presets: gnome-colors monovedek-gray and superdesk;
- implement roundness for gtk2;
- make roundness configurable for GTK+ 3 themes;
- make gradient configurable for GTK+ 3 themes;
- make spacing configurable for GTK+ 3 themes;
- added preview for roundness and gradient in the user interface;
- creation of dark GTK+3 theme version is optional now;
- gnome-colors shiki-noble-dark preset uses lighter buttons now;
- don't include dark variant for dark colorschemes;
- fix export just after overriding default colorscheme;
- fix export to unexisting dir;
- multiple GTK 3.20 fixes;
A complete changelog can be found on GitHub.
Here are the new monovedek-gray and superdesk presets in action:
superdesk preset in GNOME Shell (Ubuntu GNOME 16.04)
monovedek-gray preset in Unity (Ubuntu 16.04)
Download / install Oomox
Ubuntu 16.04 and 15.10 / Linux Mint 18 users can install Oomox by using the main WebUpd8 PPA. To add the PPA and install Oomox, you can use the following commands:sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt update
sudo apt install oomoxIf you don't want to add the PPA, you can download the deb from HERE.
To use Oomox, simply launch it from the menu / Dash, select the preset or change the colors individually, and click "Export theme". Once the theme is exported, use an application such as GNOME Tweak Tool or Unity Tweak Tool to change the theme.
Oomox can also be used from the command line, as long as you know the name of the preset you want to build, by using "oomox-cli", if you've used the PPA or the AUR package (use "./change_color.sh" if you're running Oomox downloaded from GitHub). For example, to build the "gnome-colors/shiki-brave" preset, use:oomox-cli ./colors/gnome-colors/shiki-braveFor the correct preset name / path, see the Oomox installation folder (/opt/oomox if you've used the PPA).
Arch Linux users can install Oomox via AUR.
For installing Oomox in other Linux distributions, see the instructions on GitHub.
qBittorrent is a BitTorrent client that aims to provide a free software alternative to μTorrent, available for Linux, Windows, Mac OS X and FreeBSD.
The application comes with an integrated search engine, web interface, sequential download support, bandwidth scheduler, advanced RSS support with download filters, torrent creation tool, IP filtering and other useful features.
The latest qBittorrent 3.3.5 ships with useful new feature: torrent management mode. If you set this mode to automatic and you change the category or save path, the torrent is relocated to the new category folder / new save path:
Other changes in qBittorrent 3.3.5 include:
- sort labels with natural sort algorithm in the right-click menu;
- add option to automatically remove .torrent files upon adding;
- display notifications when a torrent is added;
- new cookies management dialog and various related fixes;
- use unique temp directories;
- add option to bind directly to an IP instead of using a network Interface;
- add detailed tooltips on the progress and availability bars in the General button of each torrent;
- let user able to specifiy a filter when choosing an IP filter file;
- improve usability of "Run External Program". Users can now write shell scripts;
- implement setting/removing/showing categories;
- add command to get the logs;
- expose Add trackers feature;
- implement search filters in the proxy model;
- various UI cleanups and optimizations;
- fix Torrentz, Mininova, LegitTorrents, PirateBay plugins;
- various other improvements and bug fixes.
A complete changelog can be found HERE.
Download qBittorrent (binaries available for Windows, Mac and multiple Linux distributions as well as source)
qBittorrent is available in the official Ubuntu repositories, but it's an old version. Ubuntu 16.04 provides version 3.3.1, Ubuntu 15.10 has qBittorrent 3.2.3, while Ubuntu 16.04 (and thus, Linux Mint 17.x) still uses the old qBittorrent 3.1.8.
If you don't care about using the latest version, you can install it from the repositories by searching for it in Ubuntu Software, Synaptic, or by using the following command:sudo apt install qbittorrent
To install the latest qBittorrent 3.3.5 in Ubuntu 16.04, 15.10 or 14.04 / Linux Mint 18 or 17.x and derivatives, you can use the official qBittorrent PPA. Add the PPA and install the application using the following commands:sudo add-apt-repository ppa:qbittorrent-team/qbittorrent-stable
sudo apt update
sudo apt install qbittorrentReport any bugs you may encounter @ GitHub.
GNOME Shell supports grouping applications in app folders, and there are two such predefined folders, "Utilities" and "Sundry". Some might not know how to create custom app folders, so here are two ways of achieving this.
Create and edit GNOME Shell app folders with GNOME AppFolders Manager
GNOME AppFolders Manager is a tool to create and edit app folders in GNOME Shell.
The application is fairly easy to use - in the left section, you can create, delete or edit app folders, while in the right section you can add (or remove) applications to app folders.
Once you've added the applications you want to an app folder, click the save button. That's it! Here's a custom GNOME application folder I created using GNOME AppFolders Manager:
To install GNOME AppFolders Manager in Ubuntu GNOME 16.04, 15.10 or 15.04 (the app requires GNOME 3.12+, while Ubuntu 14.04 uses GNOME 3.10), you can use the main WebUpd8 PPA. Add the PPA and install the app using the following commands:sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt update
sudo apt install gnome-appfolders-manager
Arch Linux users can install GNOME AppFolders Manager via AUR.
For other Linux distributions, see the application installation page.
Report any bugs you may find @ GitHub.
Add applications to app folders using GNOME Software
Note that in my test, the instructions below did not work in Ubuntu 16.04 with GNOME 3.18 and GNOME Software 3.20 (no error was displayed, the appfolder simply wasn't created). It didn't work in Fedora 24 with GNOME 3.20 either, but it did work in Fedora 22 with GNOME 3.16.
Also, GNOME Software is not available in the official repositories for Ubuntu versions older than 16.04. So for Ubuntu and for GNOME versions in which this functionality is broken, use GNOME AppFolders Manager.
If you're using GNOME Software, you can easily add applications to app folders and create new app folders. To do this, launch GNOME Software, switch to the "Installed" tab and click the select button (top right):
Then, select the applications you want to add to a folder and click "Add to Folder":
And finally, simply select the app folder you want to add the applications to, or click "+" to add a new app folder, and click "Add":
In the same way, you can also remove or move applications from app folders.
Here's the result:
Snap packages are not an Ubuntu-only thing any more. Developers from multiple Linux distributions and companies, including Dell, Samsung, the Linux Foundation, and more, announced the collaboration on the snap universal Linux package format, which allows using a single package on any Linux desktop, server, cloud or device.
Right now, snap packages work natively on Ubuntu (with Unity), Kubuntu, Lubuntu, Ubuntu GNOME, Ubuntu Kylin, Ubuntu MATE, and Xubuntu, as well as Arch Linux, Debian, and Fedora. According to the press release, snaps are currently being validated on CentOS, elementary OS, Gentoo, Linux Mint, openSUSE, OpenWrt, and RHEL.
"Most vendors target Ubuntu because of its popularity. [...] Snaps bring those apps to every Linux desktop, server, device or cloud machine, giving users freedom to choose any Linux distribution while retaining access to the best apps".
- Mark Shuttleworth
What's a snap package?
A snap package is a single binary that contains all its dependencies. That means developers no longer have to build a package for each Linux distribution and each version, and instead, they can use a single, unmodified package, and distribute it across all the platforms that support snaps.
"Maintaining .deb packages in a private repository was complex and time consuming, snaps are much easier to maintain, package and distribute. Putting the snap in the store was particularly simple, this is the most streamlined app store I have published software in".
- Boudewijn Rempt, project lead at the Krita Foundation
Krita 3.0, released recently, is already available via Ubuntu Software as a snap package that will be updated automatically once new versions are out.
That's because a snap package can be updated or rolled back automatically if needed. Furthermore, snap packages are strictly confined and sandboxed to safeguard your data and system.
Also, since snaps are basically self-contained zip files, they are also easier to create.
"Our objective is to make LibreOffice easily available to as many users as possible. Snaps enable our users to get the freshest LibreOffice releases across different desktops and distributions quickly, easily and consistently. As a bonus, it should help our release engineers to distribute a more up-to-date LibreOffice that is not based on a bespoke, home-grown Linux build solution, using a toolchain that is collectively maintained".
- Thorsten Behrens, founder and board member of The Document Foundation
Snaps were initially created by Canonical for Snappy Ubuntu Core, a cloud-optimized Ubuntu edition, but were later adopted on the Ubuntu desktop and server, with the latest Ubuntu 16.04 LTS.
Snaps are complementary to existing Linux packages, not created to replace them
Snaps won't replace the native packages used by various Linux distributions. For instance, Ubuntu (desktop and server) will continue to support the .deb format, and deb archive will be available to use and distribute software.
Snaps only complement the base OS with universal apps that cannot interfere with the base OS or one another.
For more about snap packages, see snapcraft.io
elementary OS is an Ubuntu-based Linux distribution (with Loki being based on Ubuntu 16.04), which ships with its own desktop environment, called Pantheon, a Mutter-based window manager, called Gala, Pantheon Dock (built on the foundation of Plank dock), and its own custom applications for the most part, which integrate tightly with the desktop.
The official elementary OS 0.4 Loki release notes do not provide a complete list of changes and new features for users. For now, the release announcement lists major changes for developers. Among these are:
- the Ayatana AppIndicator API is no longer supported by Wingpanel. The announcement notes that the proper way to have quick application actions is to use the FreeDesktop Actions spec, and have the quick actions appear in the dock, when right clicking apps in the applications menu, and in the applications menu search. That means AppIndicators like Dropbox, Psensor, Calendar Indicator, Weather Indicator and so on, are no longer displayed on Wingpanel;
- there's no default app for handling .deb packages in Loki, and the "add-apt-repository" command is not available by default, though they are available to install from the repositories. The reason behind this decision is to promote "secure software installation methods";
I tested the latest elementary OS 0.4 Loki beta in a virtual machine and here's a list of changes I noticed on a first look:
- a new software store, called "AppCenter", is available by default. The application provides categories, search, application descriptions, and screenshots. It also allows updating packages. Right now, AppCenter doesn't support user ratings or reviews;
- a new notifications indicator was added to Wingpanel, which displays a list of important notifications, and allows enabling the "Do Not Disturb" mode, clear all notifications, and access notification settings;
- Epiphany has replaced Midori as the default web browser;
- redesigned Mouse & Touchpad and Power Switchboard (system settings) plugs;
- new Switchboard plugs: Online Accounts, Printers (replacing the old plug), Sharing, and Parental Control (which allows limiting computer use, accessed websites and or access to certain applications).
Note that since there are no official release notes for users, some new features and changes, including possibly important ones, may not be listed above. We'll see all the goodies that come with the latest elementary OS 0.4 Loki once the final release is out.
Here are a few screenshots with some of these changes:
Updated Mouse & Touchpad Switchboard plug
Updated Power Switchboard plug
Online Accounts Switchboard plug
Parental Control Switchboard plug
Sharing Switchboard plug
elementary OS 0.4 "Loki" beta is based on Ubuntu 16.04 LTS, and it ships with GTTK 3.18, Vala 0.32, Xorg server 1.18.3, Mesa 11.2.0, and Linux 4.4, along with other updated libraries and applications.
Test elementary OS 0.4 Loki Beta
elementary OS 0.4 Loki is currently in beta, so it may contains incomplete features and various bugs. Use it for testing purposes only!
Download elementary OS 0.4 Loki beta (64bit only) | please read the release announcement (and more importantly, the known issues part)
The issue occurs with the Dropbox packages in the official Ubuntu repositories (called "nautilus-dropbox", which doesn't depend on Nautilus and can be used to install Dropbox on any desktop environment) as well as the Dropbox package downloaded from its official website.
It does not occur with the caja-dropbox package available in the official Ubuntu MATE 16.04 repository though (but it does occur in older Ubuntu MATE versions if you've enabled AppIndicators), because it was patched with a fix similar to the one in this article.
Below you'll find a fix / workaround for this issue. Important: using the instructions below, Dropbox will use a tray (notification area) icon instead of an AppIndicator.
Here's a screenshot with the issue (taken in Xubuntu 16.04):
And another screenshot taken after using the fix below:
Tested in Xubuntu 16.04, Xubuntu 14.04, Lubuntu 16.04, Ubuntu MATE 16.04 (the issue does not occur with the caja-dropbox package in this Ubuntu MATE version) and Ubuntu MATE 14.04.
To fix it, you need to add "dbus-launch" before the actual command for the "Exec" line in both the application autostart file and launcher. For Dropbox this is a bit tricky because it overwrites any modifications to its autostart file. So here's what you need to do to fix this Dropbox issue:
- if you've installed Dropbox by downloading the .deb from its website or by using the nautilus-dropbox package from the repositories:
- rename the Dropbox autostart file, located in ~/.config/autostart/, and edit the file, changing the "Exec" line to "Exec=dbus-launch dropbox start -i";
- copy the Dropbox desktop file, located under /usr/share/applications/, to ~/.local/share/applications/, so it's not overwritten when updating the package, and change the "Exec" line to "Exec=dbus-launch dropbox start -i"
- disable the built-in Dropbox autostart (because it automatically creates an autostart file) using the "dropbox autostart n" command.
- for the caja-dropbox package (except for Ubuntu MATE 16.04 which doesn't have this issue):
- rename the dropbox-caja autostart file, located in ~/.config/autostart/, and edit the file, changing the "Exec" line to "Exec=dbus-launch caja-dropbox start -i";
- copy the caja-dropbox desktop file, located under /usr/share/applications/, to ~/.local/share/applications/, so it's not overwritten when updating the package, and change the "Exec" line to "Exec=dbus-launch caja-dropbox start -i";
- disable the built-in Dropbox autostart (because it automatically creates an autostart file) using the "caja-dropbox autostart n" command.
This sounds a bit complicated on a first look, right? Well, it's not, but to make it easier, you can use the following commands to apply the changes I mentioned above.
If you've installed Dropbox by downloading the .deb from its website or by using the nautilus-dropbox package, you can fix the broken Dropbox appindicator icon and menu by using the following commands:cp ~/.config/autostart/dropbox.desktop ~/.config/autostart/start_dropbox.desktop
sed -i 's/^Exec=.*/Exec=dbus-launch dropbox start -i/' ~/.config/autostart/start_dropbox.desktop
dropbox autostart n
mkdir -p ~/.local/share/applications/
cp /usr/share/applications/dropbox.desktop ~/.local/share/applications/
sed -i 's/^Exec=.*/Exec=dbus-launch dropbox start -i/' ~/.local/share/applications/dropbox.desktop
For Ubuntu MATE (except 16.04), if you've used the dropbox-caja package to install Dropbox, you can fix the broken Dropbox appindicator icon and menu by using the following commands:cp ~/.config/autostart/caja-dropbox.desktop ~/.config/autostart/start_caja-dropbox.desktop
sed -i 's/^Exec=.*/Exec=dbus-launch caja-dropbox start -i/' ~/.config/autostart/start_caja-dropbox.desktop
caja-dropbox autostart n
mkdir -p ~/.local/share/applications/
cp /usr/share/applications/caja-dropbox.desktop ~/.local/share/applications/
sed -i 's/^Exec=.*/Exec=dbus-launch caja-dropbox start -i/' ~/.local/share/applications/caja-dropbox.desktop
Then restart the session (logout/login) and the Dropbox icon and menu should work correctly.
via / thanks to: TuxDiary and AskUbuntu
The application looks pretty much abandoned, with the latest release dating back to 2013 however, GitHub user slacka forked it, fixed most of its bugs, and updated it to support both wxWidgets 2 and 3.
A few months ago I tried using the original WinUSB to create a bootable Windows 10 pendrive, but it failed. I'm not sure if that's because of the changes in Windows 10, in Ubuntu (which I used to create the USB) or both, but using slacka's WinUSB fork worked, although I did encounter a small issue (see below).
I tested slacka's WinUSB fork to create a bootable Windows 10 USB on Ubuntu 16.04, and while using the GUI, I got an error (already reported) near the end of the process. However, I was still able to use the resulted bootable USB to install Windows 10:
The error doesn't occur when creating a Windows USB stick using WinUSB from the command line.
I should add that I only tested the WinUSB fork with Windows 10 on Ubuntu 16.04, but it should work with Windows 7 and Windows 8 / 8.1 (and older Ubuntu versions) as well. Also, I performed the Windows 10 installation in VirtualBox, and not on real hardware.
If you want to test the bootable Windows USB you've created using WinUSB, before installing it on real hardware, you can use VirtualBox. To be able to boot from USB in VirtualBox, see THIS AskUbuntu answer (make sure your username is added to the "vboxusers" and "disk" groups, or it won't work - you'll find the commands to do this in the AskUbuntu link above, under "EDIT").
Install WinUSB fork in Ubuntu or Linux Mint
I uploaded slacka's WinUSB fork to the main WebUpd8 PPA, to make it easier to install in Ubuntu (16.04, 15.10, 15.04 and 14.04 or Linux Mint (17.x or 18) and derivatives. To add the PPA and install WinUSB, use the following commands:sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt update
sudo apt install winusbIf you don't want to add the PPA, you can grab the deb from HERE.
Arch Linux users can install slacka's WinUSB fork via AUR.
For other Linux distributions, download it from GitHub.
The original WinUSB is also available in a PPA (provides packages up to Ubuntu 14.10 only!).
Create a bootable Windows 10 USB install stick using WinUSB
A. Create a bootable Windows USB install stick using the WinUSB GUI
Simply launch WinUSB from the menu / Dash, select the Windows 10 (again, it probably also works with Windows 7 and 8 / 8.1) ISO or DVD,, then select the USB drive under "Target device" and click "Install".
Remember that you may encounter THIS issue while using the GUI (however, in my test, the bootable Windows 10 USB worked despite of that).
B. Create a bootable Windows USB install stick from the command line using WinUSB
If you want to create a bootable Windows USB from the command line, you must first determine what the USB physical drive is. You can easily find this out from the WinUSB GUI (you'll find it under "Target device" - in my case it's "/dev/sdc"). You can also find the device using GNOME Disks, or from the command line, using "lsblk" and so on.
Important: make sure you use the correct USB device because it will be formatted!
Once you know the device and the path to the ISO, to create a bootable Windows USB stick from the command line, use:sudo winusb --format </path/to/windows.iso> <device>Here's an example:
sudo winusb --format /home/andrei/Downloads/win10.iso /dev/sdc
The PPA currently provides MATE 1.14.1 (Ubuntu MATE 16.04 ships with MATE 1.12.x by default), which includes changes such as:
- client-side decoration apps now render correctly in all themes;
- touchpad configuration now supports edge and two-finger scrolling independently;
- python extensions in Caja can now be managed separately;
- all three window focus modes are selectable;
- MATE Panel now has the ability to change icon sizes for menubar and menu items;
- volume and Brightness OSD can now be enabled/disabled;
- many other improvements and bug fixes.
MATE 1.14 also includes improved support for GTK+3 across the entire desktop, as well as various other GTK+3 tweaks however, the PPA packages are built with GTK+2 "to ensure compatibility with Ubuntu MATE 16.04 and all the 3rd party MATE applets, plugins and extensions", mentions the Ubuntu MATE blog.
A complete MATE 1.14 changelog can be found HERE.
Upgrade to MATE Desktop 1.14.x in Ubuntu MATE 16.04
To upgrade to the latest MATE Desktop 1.14.x in Ubuntu MATE 16.04 using the official Xenial MATE PPA, open a terminal and use the following commands:sudo apt-add-repository ppa:ubuntu-mate-dev/xenial-mate
sudo apt update
sudo apt dist-upgrade
Note: mate-netspeed applet will be removed when upgrading. That's because the applet is now part of the mate-applets package, so it's still available.
Once the upgrade finishes, restart your system. That's it!
How to revert the changes
If you're not satisfied with MATE 1.14, you encountered some bugs, etc., and you want to go back to the MATE version available in the official repositories, you can purge the PPA and downgrade the packages.
To do this, use the following commands:
sudo apt install ppa-purge
sudo ppa-purge ppa:ubuntu-mate-dev/xenial-mate
After all the MATE packages are downgraded, restart the system.
via Ubuntu MATE blog
The module was updated to version 3 recently and it includes quite a few improvements:
- added bash completion support for gtk3-nocsd wrapper;
- added custom CSS for cosmetic improvements of the header bar look when CSDs are disabled (should be largely theme-agnostic, but tested against Adwaita);
- drop compositor trick in Gtk+3 3.16.1 or higher; the set_titlebar function is reimplemented there anyway, and this should solve some possible issues with newer GTK3 versions;
- selectively disable decorations: don't drop the application menu icon by using set_show_close_button (FALSE), but instead replace the decoration_layout string of header bars to remove the "icon", "minimize", "maximize" and "close" buttons. This should fix issues with missing GNOME menu (with gThumb 3.4.x as an example);
- also override GtkDialog's GtkBuildable->add_child and the instance initializer of GtkShortcutsWindow; previously CSDs weren't removed from all windows because of that;
- added a test that verifies that no Glib/Gtk symbols are imported during link time (to make sure preloading works with BINDNOW binaries that don't use Gtk);
- Improvements to the documentation.
gtk3-nocsd was included in the Debian (sid and stretch) repositories about 2 months ago and it's also available in the Ubuntu 16.10 Yakkety Yak repositories. These official packages enable gtk3-nocsd automatically in non GNOME desktops (except Unity), without requiring any configuration.
The gtk3-nocsd packages in the main WebUpd8 PPA now include the official Debian packaging however, I've modified it slightly to allow the module to work without any configuration in Unity, like it does for other non-GNOME desktops.
Here's a screenshot with gtk3-nocsd enabled (and thus, client-side decorations disabled) in Ubuntu 14.04:
Ubuntu 16.04 (with Unity) supports client-side decorations so you don't really need gtk3-nocsd, but if you want to use it for whatever reason (consistency would be one), note that it won't look that good with the default Ambiance theme. You can try something like Numix theme instead:
For installing gtk3-nocsd in Ubuntu and its optional configuration, see our initial (updated) article: How To Disable GTK3 Client-Side Decorations (Header Bars)
The application only includes options that are supported by the mouse hardware, like changing the DPI, scan frequency (polling rate) and led colors. So for instance if the hardware doesn't support button remapping, Razercfg won't offer this option. That also means that Razercfg doesn't support macros.
Razercfg also allows saving and easily switching between profiles (Desktop, FPS gaming, RPG gaming, etc.).
The latest stable Razercfg doesn't ship with a tray applet / AppIndicator, though such a feature should be added in the next release (0.34), and you'll be able to use it to quickly switch between profiles.
Razercfg supports the following devices:
- Razer DeathAdder Classic
- Razer DeathAdder 3500 DPI
- Razer DeathAdder Black Edition
- Razer DeathAdder 2013
- Razer DeathAdder Chroma
- Razer Krait
- Razer Lachesis Classic
- Razer Naga Classic mouse
- Razer Naga 2012 mouse
- Razer Naga 2014 mouse
- Razer Naga Hex mouse
- Razer Taipan mouse
The following mice are listed as stable, but missing minor features:
- Razer Boomslang CE
- Razer Copperhead
- Razer Lachesis Classic
For a complete list of hardware features for each mouse, see the Razercfg homepage.
I also managed to add basic support for Razer Ouroboros mice (for both wired and wireless modes), based on this bug report, by using the Taipan code as a base (only basic features: enable/disable the leds and change the DPI and scan frequency). This is available if you use the packages available in the main WebUpd8 PPA or by downloading the Debian packaging (you'll find the patch in the debian/patch folder).
Don't report bugs related to the Ouroboros on the Razercfg GitHub page since the app doesn't officially support it yet.
Install Razercfg in Ubuntu
Note that I only tested the packages in Ubuntu 16.04, which uses systemd, so I'm not sure if it will work in Ubuntu 14.04.
Razercfg is available in the main WebUpd8 PPA, for Ubuntu 16.04, 15.10, 15.04 and 14.04. Add the PPA and install the application using the following commands:sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt update
sudo apt install razercfgAdding the PPA is not required (but you won't receive any updates) - you can download the deb from HERE.
If the application doesn't detect your mouse (and the device is listed as supported), try restarting the system and also see the first note below.
- if your system has an xorg.conf file (/etc/X11/xorg.conf), you'll need to make sure it doesn't specify a device (you can comment out the "Device" section) or configure it to use a generic device. The Razercfg GitHub page explains this in detail;
- if the settings are not saved between system restarts, you can edit the /etc/razer.conf configuration file to specify various options and initial hardware configuration settings.
For other Linux distributions, see the Razercfg GitHub page.
Also see: How To Change The Mouse Scroll Wheel Speed In Linux Using imwheel.