Caja Keyboard Shortcuts: Successfully Editing ACCELS If It Keeps Reloading

When adding (or editing) accelerators (keyboard shortcuts) for tasks in Caja by editing its accels file, you need to first
quit Caja, otherwise you’ll likely find it keeps trying to write to the file. And running caja -q is probably not enough, but using pkill -KILL caja should do the trick. And for most people defining new hotkeys for tasks in Caja, that’s all it takes.

HOWEVER, I had an absolute nightmare with this, because even with Caja killed, something (ie: Caja) was still trying to write to accels, as evidenced by:

… coming up while defining the accelerator. So even with reloading and saving, or choosing not to reload then saving, it wasn’t happening. I’d find the semi-colon and space I had deleted from the beginning of the line back again, and even when that stopped happening, the key I had assigned as the accelerator had been deleted. So, I was in this constant loop of editing the file and saving it, and instead of the shortcut working immediately, I was lucky if I got it recognised after a few minutes of this, and the worst was one that still didn’t stick after 2 days!

And I did try killing Caja more than once, but the results were random. So I decided to try killing Caja before editing accels, during multiple times, then after saving accels, and then finally the keyboard shortcuts worked immediately.

So if anyone else is having the difficulties getting custom keyboard shortcuts to work immediately, then the plan of attack is to open accels in one terminal, and have another terminal open to kill Caja, which you can then easily repeat by hitting the up-arrow and Enter:

First totally kill Caja:

pkill -KILL caja

Then open the accels file in another terminal window with:

pluma ~/.config/caja/accels

Totally kill Caja (AGAIN) – just hit the up-arrow to bring back the last command:

pkill -KILL caja

Remove the semi-colon and space from the beginning of the line you’re going to edit, then Save.

Totally kill Caja (AGAIN):

pkill -KILL caja

Add your accelerator to the end of the entry, then Save.

Totally kill Caja (AGAIN):

pkill -KILL caja

If your text editor says the file has changed, click the Reload button, check your edits are still there, and edit them again if not.

Totally kill Caja (AGAIN):

pkill -KILL caja

Now Save the file, exit, and finally:

Totally kill Caja (AGAIN):

pkill -KILL caja

All that killing Caja might seem excessive, and like I am being cheeky, but seriously it is quicker and easier to just have another terminal open, hit the up arrow, and repeat the kill command than go through the hellish alternative. Now you should find your new hotkey works immediately after starting Caja again.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

The tutorial above is TOTALLY FREE, and I hope you found it useful! But if this information really made your day, because it rescued you from hours of headache, or allowed you to accomplish something you thought was impossible, then please consider making a donation via PayPal, to buy me a donut, beer, or pizza for my time and effort! Many thanks in advance!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Firefox 29+: Move the Tab Bar to the Bottom (Below the Address Bar)

Firefox version 29 has had a nice make-over, but one thing that has greatly annoyed many users is that not only has the Tab bar been moved to the top above the Address bar, but that when going into Customize, there is no longer an option to move it back to where you want.

Move your Firefox Tab Bar back below the Address Bar

While you can install the Classic Theme Restorer Add-on to do this, you will still need to fidget with its settings to move the Tab bar, and it will revert to the old-style square tabs instead of the nice new rounded ones. But rather than install yet another add-on, which you then have to figure out how to use, and then loose the rounded corners on tabs, you can actually hack one of Firefox‘s config files – userChrome.css – to get your Tab bar to go back to the bottom.

To open your Firefox profile folder where the file is located, just go to Help > Troubleshooting Information, and in the Application Basics section on the config page that appears, next to Profile Directory click the Open Directory button (Show Folder in Windows, and Show in Finder in Mac OS X)

When the folder appears, open the chrome folder, right-click userChrome.css and choose to open it with a text editor. When the file is open, go to the bottom of the document and add the following code (if the end of the document is at the end of a line of code that was already there, then add a couple of blank paragraphs by hitting Enter twice):

#TabsToolbar{-moz-box-ordinal-group:10000!important}

Once you’ve saved and closed the file, go to File > Restart, and when Firefox reloads, the Tab bar will be below the Address bar, not above it.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Change Default Web Browser in Ubuntu (If Apport Bug Report Opens Opera, Chromium, Firefox Instead)

While there are ways to change the default web browser via a GUI, this command-line method is even quicker. Also, while your email program and other apps might know which browser to open URLs with, you might find that Apport – Ubuntu‘s bug reporting system – looks to another browser you have installed. This is especially true if the other browser was at one point the default, and most notably this happens with Opera, though could also happen with Chromium/Google Chrome, Firefox, or any other browser you’ve installed before.

While Apport generally carries on with the bug reporting silently once you’ve clicked to continue, occasionally it require you to log into Launchpad, and will fire up the wrong browser, quite often it being Opera.

But it’s easy to remedy this by entering the following into the terminal:

sudo update-alternatives --config gnome-www-browser

As you’ll see, all you have to do is enter the number corresponding to the browser you want to be the default (in this case 2 for Firefox). To complete the process, enter this command:

sudo update-alternatives --config x-www-browser

… and do the same there. That’s it – you’ll no longer have Apport or any other app open the wrong browser again.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

How to Disable KDE Wallet (KWALLET) Pop-ups in Chromium/Google Chrome

If you’re a Kubuntu user (or, like me, an Ubuntu user with multiple desktop environments installed, including KDE), you may have noticed that every time you start Chromium (or Google Chrome) web browser, KDE Wallet pops up and asks for authentication. While you can just exit that without having to enter your password, one can be forgiven for finding it irritating to have to do so every time the browser is opened. But it’s actually quite easy to disable, and all you have to do is enter the following into a terminal:

gedit ~/.kde/share/config/kwalletrc

Once the file opens, hit Ctrl+End to go to the bottom of the file, hit Enter a couple of times (so there will be a blank paragraph between the last entry and the test you’ll be pasting), and add the following:

[Auto Deny]
kdewallet=Chromium

(substitute “Google Chrome” instead of “Chromium” if using the former)

Save and exit the file. Log out and back in again for the changes to take effect, or simply enter the following into the terminal:

killall -9 kwalletd

That’s it – the next time you open Chromium/Google Chrome, kwallet will no longer appear to annoy you.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Ubuntu 13.10 Missing Audio Fix: No Sound, Only Device is “Dummy Output”

If you’ve upgraded your Ubuntu system to 13.10 and found that you no longer have any sound, you may have noticed in your sound preferences you now only have an audio device called “Dummy Output“. And you can’t change the device to your actual sound card, as it is no longer there (in KDE’s sound preferences, it will probably be listed as a device, yet will be greyed out, meaning you can’t select it). The problem isn’t your sound card, or needing new drivers for it, but a problem with ALSA – and hopefully will be easily fixed with the info in this article.

First, you need to check that your sound card is recognised by running this command in a terminal:

sudo aplay -l

It will then list the devices it finds (in the case of the following output, it finds the built-in audio [which is disabled in the BIOS] as well as the actual sound card I use):

**** List of PLAYBACK Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC883 Analog [ALC883 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 0: Intel [HDA Intel], device 1: ALC883 Digital [ALC883 Digital]
Subdevices: 1/1
Subdevice #0: subdevice #0
card 1: Audigy2 [SB Audigy 2 ZS [SB0360]], device 0: emu10k1 [ADC Capture/Standard PCM Playback]
card 1: Audigy2 [SB Audigy 2 ZS [SB0360]], device 2: emu10k1 efx [Multichannel Capture/PT Playback]
card 1: Audigy2 [SB Audigy 2 ZS [SB0360]], device 3: emu10k1 [Multichannel Playback]
card 1: Audigy2 [SB Audigy 2 ZS [SB0360]], device 4: p16v [p16v]

If you see something like that, then all should be well, but if you want to make sure, copy and paste this rather lengthy command into the terminal:

echo "Sound cards recognized by the system:"; lspci -nn | grep --color=none '\[04[80][13]\]'; echo "Sound cards recognized by ALSA:"; lspci -nn | grep '\[04[80][13]\]' | while read line; do lspci -nnk | grep -A 3 '\[04[80][13]\]' | grep -e 'Kernel modules: ..*' -e '\[04[80][13]\]' | grep --color=none -F "$line"; done; echo "Sound cards recognized by ALSA, and activated:"; lspci -nn | grep '\[04[80][13]\]' | while read line; do lspci -nnk | grep -A 3 '\[04[80][13]\]' | grep -e 'Kernel drivers in use: ..*' -e '\[04[80][13]\]' | grep --color=none -F "$line"; done

The output should be something like:

Sound cards recognized by the system:
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
05:01.0 Multimedia audio controller [0401]: Creative Labs SB Audigy [1102:0004] (rev 04)
Sound cards recognized by ALSA:
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
05:01.0 Multimedia audio controller [0401]: Creative Labs SB Audigy [1102:0004] (rev 04)
Sound cards recognized by ALSA, and activated:
00:1b.0 Audio device [0403]: Intel Corporation 82801I (ICH9 Family) HD Audio Controller [8086:293e] (rev 02)
05:01.0 Multimedia audio controller [0401]: Creative Labs SB Audigy [1102:0004] (rev 04)

Once again, everything seems fine, other than the fact you can’t enable your sound card as an audio device. Hopefully, the following command will rectify the situation:

sudo alsa force-reload

You will probably see no change until you reboot, so do so and when you login again, your sound should be back. If it isn’t, you may need to go back into the sound preferences and make the sound card the default audio device, after which all should be well.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

If the problem still persists, you can try the following command which has worked for some (replace “yourusername” with your actual username):

sudo usermod -aG audio,video,pulse,pulse-access yourusername

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Ubuntu 13.10 Permissions Fix: “This operation cannot continue since proper authorization was not provided” Halts Software Updater, Shutdown, Drive Mounting, DVD Playback, etc

If you’ve upgraded your Ubuntu system only to find you don’t have permission to do pretty much anything, as I did after upgrading to 13.10, it can be pretty annoying even for an advanced user, and downright scary for a novice. The symptoms are pretty obvious, as when you go to install updates, all you get is an error message saying “This operation cannot continue since proper authorization was not provided“. And using the Shutdown button seems to do nothing, and even using a terminal command to power off might see the shutdown process halt half-way through, forcing you to use the PC’s power button.

On top of that, even mounting removable drives (or other partitions on your internal drive) ends in being told you can’t, and even trying to play a DVD ends with “Unable to access “DVDVIDEO”. Not authorized to perform operation.”

While there are ways around all of these situations for more advanced users, those less experienced with Ubuntu/Linux would find it all quite daunting, and pretty much look at their system as unusable. And one shouldn’t have to go through the bother of manually mounting drives through the terminal, or invoking the Software Updater as superuser, or any other thing we usually take for granted.

Luckily, the fix – which involves PAM (Pluggable Authentication Modules) – is actually quite simple, and should have everything back to normal in no time.

In a terminal, enter the following command to edit the PAM authentication file for the LightDM display manager:

gksu gedit /etc/pam.d/lightdm

Under the first line “#%PAM-1.0” paste the following 2 lines:

session required pam_loginuid.so
session required pam_systemd.so

Save and exit the file, then log out and back in again, and all should now be fine (you shouldn’t need to reboot).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Another method, which fixed the problem for some (but not in my case, and many others) is to run:

sudo pam-auth-update --force

This opens PAM‘s config within the terminal, at which you either check or uncheck items, or just hit Tab to go to OK, and hit Enter.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

If need be, like you have GDM installed and it is interfering with LightDM, run dpkg-reconfigure gdm and select lightdm (you may need to reboot).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Kubuntu 13.10 Fix: KDE Login Failure “Could not start D-Bus. Can you call qdbus?”

If you’ve tried to login to your KDE desktop but only received an error message saying “Could not start D-Bus. Can you call qdbus?“, like I did after upgrading my system to 13.10, then this guide should help you. While this login failure may look ominous, it’s actually easily remedied by simply installing the package qdbus. If you have other login options than KDE, like Ubuntu/Unity, Gnome or another desktop environment, log into that and in a terminal run:

sudo apt-get install qdbus

You should be able to log into KDE after logging out of the desktop you were in (if not, all should be well after a reboot).

If you only have Kubuntu‘s KDE as a login option, then use Ctrl+Alt+F1 to go to a different TTY (teletype terminal), where you’ll be prompted to enter your username, then password, and at the command prompt you end up at, run the above command. Once qdbus is installed, enter sudo shutdown -r now (or sudo reboot) to reboot your computer, and you should now be able to reach your KDE desktop.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Ubuntu 13.04/Nautilus 3.6 Fix: Open Selected Folder in Image Viewer or Movie Player with Nautilus-Actions

If you’ve upgraded to Ubuntu 13.04, you may have noticed that its file manager, Nautilus, has lost some of its functionality. One of the glaring omissions in the 3.6x versions (the current is 3.6.3) is the Open With sub-menu when right-clicking a selected folder. Previously, you could use it to open a folder with a program, like Movie Player (now called Videos, though technically it’s totem) to open a folder full of video clips, or a folder full of pictures with Image Viewer (or eog – Eye Of Gnome – to be precise).

In this guide I’ll show you how to do both, but you can of course apply this to any program you want, as long as it has the ability to open a folder starting with the first file. In the case of Image Viewer, it will open the first file within the folder and continue to cycle through the rest as you use your arrow keys; in the case of Videos, it will open the media player with all videos from the selected folder in its playlist, in alphanumerical order.

To get around the missing Open With option, you will first need to install Nautilus Actions. To do so, run the following command in the terminal:

sudo apt-get install nautilus-actions

Once installed, you can use the Nautilus-Actions Configuration Tool to define your own actions (in Unity’s Dash menu, just start typing the name; in Gnome Classic, it will be in Applications > System Tools).

New Menu Item for Image Viewer:

In the Nautilus-Actions Configuration Tool, click the Define a new action button and name that action to what you want to appear in the menu (eg: Open with Image Viewer; whatever name you choose will also appear in the Context label: field in the first tab in the right-pane, Action).

Making sure that the new action is selected in the left-pane, in the right-pane go to the second tab – Command – where you define what that menu option will do. For the Path: enter eog (or the full path /usr/bin/eog), for Parameters: enter %b (for first basename), and finally for Working directory: enter %d (for first base directory). While there are a bunch of other tabs in the tool, that is all you should need to do.

If you want to add an icon for that menu option, you will see Icon: in the Action tab, where you can browse for an icon to use.

Once you’re finished, click the Save button, and exit the tool. You will find your new action in the Nautilus-Actions actions sub-menu in your context menus.

(OPTIONAL: If you also want this action to appear in context menus for locations – in other words, not just the selected folder, but when you right-click an empty area of the folder you’re currently in – check the box next to Display item in location context menu in the Action tab)

New Menu Item for Movie Player (Videos):

In the Nautilus-Actions Configuration Tool, click the Define a new action button and name that action to what you want to appear in the menu (eg: Open with Movie Player or Play Movies in Folder; whatever name you choose will also appear in the Context label: field in the first tab in the right-pane, Action).

Making sure that the new action is selected in the left-pane, in the right-pane go to the second tab – Command – where you define what that menu option will do. For the Path: enter totem (or the full path /usr/bin/totem), for Parameters: enter %b (for first basename), and finally for Working directory: enter %d (for first base directory). While there are a bunch of other tabs in the tool, that is all you should need to do.

If you want to add an icon for that menu option, you will see Icon: in the Action tab, where you can browse for an icon to use.

Once you’re finished, click the Save button, and exit the tool. You will find your new action in the Nautilus-Actions actions sub-menu in your context menus.

(OPTIONAL: If you also want this action to appear in context menus for locations – in other words, not just the selected folder, but when you right-click an empty area of the folder you’re currently in – check the box next to Display item in location context menu in the Action tab).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Ubuntu 13.04/Nautilus 3.6 Fix: Open Selected Folders in New Windows with Nautilus-Actions

If you’ve upgraded to Ubuntu 13.04, you may have noticed that its file manager, Nautilus, has lost some of its functionality. One of the glaring omissions in the 3.6x versions (the current is 3.6.3) is the ability to open selected folders in their own windows.

Nautilus 3.6 Options for Selected Folders

Currently, the only options available when you right-click selected folders are to create a new folder containing whatever is selected, or to open them in new tabs. The Open option simply mimics the next option, which is to open them in new tabs. The only way at all to open another (single) folder in a new window is if you right-click the breadcrumb in the toolbar.

Right-clicking Pictures while in a sub-folder lets me choose to “Open in New Window”

However, there is a way around this: Nautilus Actions. To install it, run the following command in the terminal:

sudo apt-get install nautilus-actions

Once installed, you can use the Nautilus-Actions Configuration Tool to define your own actions (in Unity’s Dash menu, just start typing the name; in Gnome Classic, it will be in Applications > System Tools).

In the Nautilus-Actions Configuration Tool, click the Define a new action button and name that action to what you want to appear in the menu (eg: Open in New Window; whatever name you choose will also appear in the Context label: field in the first tab in the right-pane, Action).

Making sure that the new action is selected in the left-pane, in the right-pane go to the second tab – Command – where you define what that menu option will do. For the Path: enter nautilus (or the full path /usr/bin/nautilus), for Parameters: enter %b (for first basename), and finally for Working directory: enter %d (for first base directory). While there are a bunch of other tabs in the tool, that is all you should need to do.

If you want to add an icon for that menu option, you will see Icon: in the Action tab, where you can browse for an icon to use.

Once you’re finished, click the Save button, and exit the tool. You will find your new action in the Nautilus-Actions actions sub-menu in your context menus.

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »

Rhythmbox Fix: Restore Album Cover Art in Left Pane in Ubuntu 13.04

Up until Rhythmbox version 2.96 (the current version in Ubuntu 13.04 is 2.98), the bottom section of the left-hand pane where your devices and playlists are was reserved for the current album’s cover art. Since then, that has been removed and a much smaller version of the cover appears left of the song info in the top toolbar. While this is merely a cosmetic issue, and nothing to get too upset over, nonetheless it was pretty cool seeing a nice-sized picture of the cover appear at the bottom of the left pane.

But fret not, as there is a way to get this back, via the Cover art display plugin for Rhythmbox. And while it currently isn’t in the software repos for Raring Ringtail 13.04, I’ll show you how to get around that too, and install it easily.

First, you’ll need to add the plugins PPA to your software sources, which you can do by pasting the following command into the terminal:

sudo add-apt-repository ppa:fossfreedom/rhythmbox-plugins

Once that’s done, update your software sources list with:

sudo apt-get update

Now to install the plugin (if there is a current version of the plugin that can be installed):

sudo apt-get install rhythmbox-plugin-artdisplay

If you’re informed that the package could not be found, it means there is still no version ready for 13.04, but this is no real problem, as we can just install the 12.10 version. To fix this, you’ll need to edit the Rhythmbox plugins sources list:

sudo gedit /etc/apt/sources.list.d/fossfreedom-rhythmbox-plugins-raring.list

… then copy the line that should be at the top of the file deb http://ppa.launchpad.net/fossfreedom/rhythmbox-plugins/ubuntu raring main and paste it at the bottom of the file, then replace “raring” with “quantal“. Once you’ve saved and closed the file, the sources list for plugins will specify to look for both 13.04 (Raring Ringtail) and 12.10 (Quantal Quetzal) versions, and when you sudo apt-get update again, all the available plugins will be listed in your package manager. You can then install this plugin and others via Ubuntu Software Center or Synaptic Package Manager, or just run the install command again (sudo apt-get install rhythmbox-plugin-artdisplay).

Once it’s installed, all you have to do is enable it. Go to Edit > Plugins and enable the Cover art display plugin. Your cover art should now be in the left pane, with the smaller one still in the toolbar near the song title.

If for some reason you don’t want the smaller cover in the toolbar any more (I say have both, but that’s up to your tastes), you can disable that by going to the View menu and un-checking Album Art.

☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢☢

Note: If you’re reading this in Ubuntu 13.10 or above, and there is no current version after adding the PPA, edit the sources file accordingly, meaning substitute the word relating to your current version with that of the previous one. In other words, in Raring Ringtail 13.04 we had to replace “raring” with “quantal” for Quantal Quetzal 12.10, in Saucy Salamander 13.10 you would replace “saucy” with “raring“, and so forth (and if all fails, just replace that with “quantal“, which definitely has a version of the plugin).

☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻☻

Did this information make your day? Did it rescue you from hours of headache? Then please consider making a donation via PayPal, to buy me a donut, beer, or some fish’n’chips for my time and effort! Many thanks!

Buy Ubuntu Genius a Beer to say Thanks!

Read Full Post »