Category Archives: GNU/Linux

How to fix monitor problems (bugs?) on Ubuntu 12.04 and later versions – Linux

Starting from Ubuntu 12.04 we observed different graphics problems with “old” computers. When I say “old” I don’t mean obsolete hardware but PC with not more than three years of usage.

Many problems were especially noticed in systems with dual monitors or involving laptops. In few words, Ubuntu was not able to keep and memorize the correct video settings and it was necessary to set-up monitors configuration almost each time you logged on your OS. If you have the same problem and you are surfing the net to fix this “bug” don’t forget to search for solutions strictly connected to the laptop or graphic card you are really using. In fact in our experience there are more than few solutions possible and what it’s resolving for some hardware could become a real mess for different (but similar) machines.

The risk of damaging Ubuntu graphical interface while you try to fix the laptop – dual monitors problem is high. Or it has been in our experience because after some tests we were just able to use Ubuntu through the old line way in its safe mode boot. In any way, in our experience (IBM Thinkpad T43 and a HP L1950g monitor using Ubuntu 12.04 LTS with MATE as graphical interface) we solved all the matter just using Terminal and typing:

 sudo apt-get update

and

sudo apt-get install ubuntu-desktop

We are not able to explain why it works but it really fixed the bug. Probably, in one of the previous update one or more libraries conflicted with Ubuntu 12.04 configuration generating all the mess we fought against during the past months.

So, if you want to test our solution on your PC, do it at your risk, and type:

sudo apt-get install --reinstall ubuntu-desktop

sudo apt-get install --reinstall xubuntu-desktop

sudo apt-get install --reinstall kubuntu-desktop

sudo apt-get install --reinstall lubuntu-desktop

If you want to reinstall all (k)ubuntu-desktop dependencies:

sudo apt-cache depends ubuntu-desktop | awk -F ":" '{print $2}' | sed '/^$/d' | xargs sudo apt-get install --reinstall --install-recommends --yes

Don’t forget to choose your favourite k-x-l-u-buntu-desktop when you type all the above code in just one line and !

Good luck!…. and touch wood while you fix this really annoying bug…..

Leave a reply

Model B is interesting if you need a cheap PC that is able to run Linux (Debian GNU/Linux, Raspbian OS, Fedora, Arch Linux ARM, RISC OS, FreeBSD, Plan 9). When Model B will be upgraded to 1 GB RAM, we will have one of the most competitive computers for standard office tasks… ASFEE6HEF2PT

How to install Android on a Nook Color using a Linux OS – Practical Tips

1 Reply

First of all, I wanted to test one of the latest version of Android 4 but I didn’t want to spend money for a new device so I decided to use/sacrifice the Nook Color that I used rarely because I am a Kindle enthusiast.

Secondly I didn’t want to void the Nook warranty or permanently modify its ROM.

Last but not least I never pretended to discover a new way to modify the Nook but just find the most simple and practical tutorial into internet.

After some hours of internet surfing I found some interesting commercial solutions (e.g. n2acards) and a lot of good tutorial posts and my final choice was one by xda-developers.

I bought a class 4, 8 GB micro SD card and I followed the detailed instructions described into the xda-developers post…, but I had some practical problems because I didn’t read carefully all the text.

The xda-developers tutorial is really well done and full of right information but, as for my experience, it is best to focus your attention on some few points/steps.

In particular:

– you have to create a bootable micro SD card using these commands on Terminal:

sudo fdisk -l

(in this way you will discover the right address of your SD card, in my case was “sdc”. Pay attention! If you choose the wrong address you risk to wipe your hard disk)

sudo dd if=generic-sdcard-v1.3-CM7-9-10-larger-Rev5.img of=/dev/sdc

where generic-sdcard-v1.3-CM7-9-10-larger-Rev5.img is the the image file you find in the xda-developers webpage and sdc the right address of your SD card

– when you download the three necessary “software”, be sure to choose the right one for the CM you have chosen. I mean: if you choose to install CM 9 you need gapps-ics but, if you prefer CM 10, gapps-jb is the right software for you. If you don’t use the proper file, you will have this type of “error message” when you boot your new Android:

Unfortunately, Google services framework has stopped

Unfortunately, Setup Wizard has stopped

Adding the zip files suggested on the xda-developers guide you are now ready to test the Android 4 on your Nook. During the first boot up the Linux software on the SD card will inflate the proper files creating all the right folders and compiling the libraries. To complete this step you will need about 8/10 minutes and, at the end, the Nook will automatically shut down.

In my case I installed CM 10 and during my first boot-up, after I completed the installation, I was not able to use the Android Keyboard and I read this error message on the screen:

Unfortunately, Android keyboard (AOSP) has stopped

Luckily, I was not the first user to have this kind of problem and I read the right tip into another xda-developer blog. I had to come back at the beginning of the Tutorial and change the gapps zip file to an older version, more precisely the 2012-10-11. After this, the new installation the Android 4 run properly on the Nook Color.

For my experience, the Android 4 on the Nook Color is slowest than I supposed but it is not so slow to force me to come back to an older Android version. When I installed a couple of free apps, Startup Manager and Memory Booster, the speed improved and Android was more fluid.

AuctionSieve: the best multiplatform (Linux, MAC OS, Windows) software to manage your ebay searches

Leave a reply

AuctionSieve Christmas time! And you want to buy some presents… ebay could represent a good option to save some money but it needs a lot of time because you want to be sure you are bidding at the right price to the best (used or not) item.

The web is full of websites which help you to discover and follow items on ebay but, in the real world, from the moment you find something to the end of a winning auction many days pass and often you have not time to follow and properly bid for your “catches”.

The software I use and recommend for ebay auctions is AuctionSieve. This software is written in Java and consequently it is multiplatform. In the Download Page you can always find the right version for the OS you are using.

On Linux, download AuctionSieve, extract the file and save it to (e.g.) Home. Open the folder you created and give the permission to execute as program to auctionsieve.jar (right button on the mouse –> Properties –> Permission –> Allow executing file as program”). Then open it with (in my case) -OpenJKD Java 6 Runtime-.

AuctionSieve is intuitive but you have to “play” with it for a couple of hours before dominating all its features. You can save your searches, focus on just one category, filter items using “catch” or “trash” words options, create personal watchlists and evaluate the price of a particular item using the “Price History” tab. If you repeat a specific search you did in the past, you can decide to automatically exclude all the items you have already seen before and you will spare more time examining the results. Moreover, when you begin a “New Sieve”, you can also import the same search criteria you created and selected during a previous search you did.

Let me suggest you to read the AuctionSieve Tour page before using it. In this way you will skip all the most common mistakes that beginners usually make.

How to configure Firestarter to use VPN services on Linux

2 Replies

VPN Linux In my experience Firestarter is a effective firewall and, on Linux, it starts automatically every time we boot up Ubuntu. But, when I decided to use a VPN tunnel through openvpn, I had some connection problems. In fact I was able to initialize my VPN services but, after a while, all the internet connections were mysteriously shut down.

The “problem” was Firestarter which cut off the connection as forbidden considering my inbound/outbound Policy.

To solve this matter you have to open a tunnel on Firestarter to allow VPN working:

1- open the configuration file my VPN provider gives to its users (generally its a text file containing all the configuration info used, in my case, by openvpn) and I searched for the IP address of the default starting connection used to authenticate the VPN services (e.g. 177.458.563.25). Save somewhere or memorize this VPN IP address.

2- open a Terminal and type:

sudo nautilus

3- using nautilus go to File System (it’s before home folder) and open etc–>firestarter and open the file user-pre using Gedit (or your preferred text editor)

4- the user-pre file is usually empty so don’t panic and write these lines into it:

iptables -A INPUT -j ACCEPT -s xxx.xxx.xxx.xxx -p esp
iptables -A INPUT -j ACCEPT -s xxx.xxx.xxx.xxx -p udp -m multiport -sports isakmp,10000
iptables -A INPUT -j ACCEPT -i tun+
iptables -A OUTPUT -j ACCEPT -d xxx.xxx.xxx.xxx -p esp
iptables -A OUTPUT -j ACCEPT -d xxx.xxx.xxx.xxx -p udp -m multiport -dports isakmp,10000
iptables -A OUTPUT -j ACCEPT -o tun+

Now you have to substitute the xxx.xxx.xxx.xxx with the VPN IP address you have found at step 1 (in my example was 177.458.563.25).

5- Save the user-pre file and close Gedit and Nautilus

6- open a new Terminal and restart Firestarter typing:

sudo /etc/init.d/firestarter restart

That’all! Now your VPN works on your Linux computer and Firestarter has accepted a new Routed IP Tunnel into its allowed policies configuration.

Solve audio troubleshooting on Ubuntu and start planning to migrate to another Linux OS

1 Reply

It was just a simple system update which dropped off audio on my Ubuntu 12.04. It was really strange to admit that I had experienced a crash (better: an audio crash) on a Linux but the 12.04 Ubuntu actually caused similar problems to a numerous bunch of long-term aficionados around the world.

The real problem with the last Ubuntu versions is that this OS is not supporting properly “old” hardware as it did previously during so many years. Reading some other bug reports on the web I discovered that these audio troubleshooting crashes happen principally to “old” IBM ThinkPad and Dell. I hope Ubuntu developers will consider to solve immediately these kind of issues or many users certainly migrate to other Linux version.

In any case the best and complete guide to solve audio troubleshooting has been developed by Ubuntu itself. The guide is very detailed but, if you want to definitively solve this bug, you have to spend more or less 40 (forty…. sic!) minutes and follow all the 17 (seventeen… sic!) steps.

In my case the audio was back after the first step and I decided not to follow the other instructions but the audio troubleshooting comes back, more or less, every two months. Just to you if you want to spend 40 minutes only one time or a couple of minutes every two/three months.

When I consider all the problems I had with Ubuntu on “old” hardware starting from the 12.04 version, my advice is to start thinking about a migration to another Linux OS. I am testing some Ubuntu alternatives and in the next weeks I will post something about the tests I’m doing on old laptops. Stay connected!

Linux Day 2012

Leave a reply

Today we post a particular Linux informative video to celebrate the 2012 edition of the Linux Day: a special event dedicate to promote the Linux culture in Italy. The Linux Day 2012, organized under the supervision of the Italian Linux Society, will be carried on today (October, 27) thanks to the active support and the logistic framework offered by the Italian User Groups in more than 100 Italian cities and villages. Akhela (http://www.akhela.com/it) and SUSE Italia (https://www.suse.com/it-it/) are the proud sponsors of this event.

Source: youtube.com via Galigio on Pinterest

How to install Ubuntu 12.04 on old computers with non PAE CPU

2 Replies

When I tried to install Ubuntu 12.04 on an old ThinkPad X40 I was surprised to discover this warning on my screen:

This kernel requires the following features not present on the CPU:
pae. Unable to boot - please use a kernel appropriate for your CPU.

In few words I wasn’t able to install Ubuntu 12.04 because the kernel on Ubuntu 12.04 was not supporting my CPU and I was really upset because I have always promoted Linux distributions as the most versatile and appropriate OS to keep using “old” hardware.

Sincerely, as described in an older post, I previously decided to install MATE desktop environment because the graphic cards on many laptops didn’t support Unity and Gnome 3 but this was the first time I had to renounce the installation of Ubuntu. I didn’t want to surrender to this difficulty (that appeared to me as a bug)!

First of all, I discovered that pae is “a feature to allow 32-bit x86 processors to access a physical address space (including random access memory and memory mapped devices) larger than 4 gigabytes“. After I clarified this point, I was not sure that my processor was totally inadequate to support Ubuntu 12.04.

After some web surfing I discovery that there are two easy solutions to avoid this problem.

1 – As first solution you can install Lubuntu (my choice) or Xubuntu on your computer then you can install the ubuntu-desktop using the Package Manager.

2 – If you prefer not to use the Package Manager you can install Ubuntu 11.04 or 11.10 and then upgrade Ubuntu to 12.04.

More in general, it is also possible to assume that if you have a non PAE CPU, your hardware could not be able to support the Unity desktop. For this reason you can keep your Lubuntu – Xubuntu (based on the light but effective LXDE desktop) or switch your desktop environment to Gnome (the Classic, of course) installing the gnome package instead of ubuntu-desktop.

In any case, if you want to know if your CPU supports pae you have to open a Terminal and type:

grep --color=always -i PAE /proc/cpuinfo

If something like “flags: fpu vme de pse tsc msr pae mce cx8…” outputs on your Terminal, you have a pae CPU otherwise your CPU doesn’t support pae.

The good third choice: MATE desktop environment. The traditional but rock solid solution for the Unity unhappy users (when also Gnome fails)…

2 Replies

My first Linux OS was a Knoppix but I had so many problems with the hardware drivers, the LAN configuration and the monitor settings that I was really discouraged. After many tests I decided that Ubuntu was the right OS for my notebooks and I continued to use it without any particularly matters till Unity.

Unity is nice to see, intuitive but if you use your OS in a stressful way (I mean doing three or four different tasks all together: reading emails, talking with Skype and writing on LibreOffice), you spend too much time looking for the icon you need to launch the right program. The vertical monitor space has not enough room to visually show all the icons related to programs I use everyday. Surely this is my personal matter but I actually prefer the “old” graphic interface. For this reason I decided to install Gnome 3 but my vetust IBM Thinkpad crashed a couple of time in a week.

To my surprise also the Gnome Classic option encountered some crashes due to the amount and diversity of the software I installed on my laptop during the last years.

As usual, after some web searches I found a solution: MATE. This particular desktop environment is a fork of Gnome 2 and it really looks very intuitive and easy to use. If some software conflicts with the MATE environment, a pop-up message will appear on your sceeen and, if you have the patience to read the Details contained in it, you will able to solve your problems. In my particular case (don’t ask me why) it helped me to focus my attention on Conduit which caused the crashes on Gnome.

To easily install MATE, on almost every Linux distribution, you can read its wiki dedicated page or directly follow the below instruction if you use Ubuntu 12.04.

– open Terminal and type these command lines:

sudo add-apt-repository "deb http://repo.mate-desktop.org/ubuntu oneiric main"

sudo apt-get update

sudo apt-getinstall mate-archive-keyring

sudo apt-get update

sudo apt-get install mate-core

sudo apt-get install mate-desktop-environment

When the Terminal finishes all the upgrade stuff, reboot your Ubuntu 12.04 and select MATE on the login screen (click on the upper right “gear” and choose MATE).

That’s all! Have a good week!

How to launch Pogoplug online services (as local disk) on Ubuntu 12.04 LTS

10 Replies

I confess that I use Pogoplug as cloud server for my external hard disks because it is really simple to configure and trustful. Unfortunately the Linux version of the Pogoplug management software is not so simple to configure and has fewer features than the Windows and MAC versions.

Running Ubuntu 12.04 LTS I can manually mount the drives I connected to my Pogoplug device, following the path Network –> Windows –> etc.., but sometimes this way is not so fast and moreover I cannot access to Pogoplug Cloud.

Waiting for an updated software from the producer I decided to use the current version to automatize the process and mount the drives connected to the Pogoplug and its cloud as if they were physically attached to my Ubuntu 12.04 LTS.

After a “classic” Google search on this topics I found different suggestions. Unfortunately I also had more than few problems to configure the software provided by Pogoplug because some tips were not so clear or easy as I desired.

By my experience, the fastest and reliable way to configure Pogoplug drives on Ubuntu 12.04 is the following:

– open Terminal and type sudo apt-get install fuse-utils

– open Synaptic Package Manager and be double sure you have yet installed these packages: fusesmb, fusedav, fuseext2, fusefat

– download the Linux software provided into the Downloads section of Plogoplug website, unzip it and save the file in your Home folder

– open Terminal and type: sudo usermod -a -G fuse $(id -u -n)

– log out and then log in again on your Ubuntu account to be sure that Fuse is correctly running

– open Terminal again and create a directory (in Media) to be used as mount point: sudo mkdir /media/pogoplug

– then type: sudo chown root:fuse /media/pogoplug

– and: sudo chmod 0775 /media/pogoplug

– in Terminal launch this command:

/home/yourusernameonubuntu/pogoplugfs --password yourpassword 
--mountpoint /media/pogoplug --user yourusername

where:

1. yourusernameonubuntu means you have to insert the name of User profile you use when you log in Ubuntu on your computer

2. yourusername and yourpassword are the username and password you use on the Plogoplug Website

Now, after some seconds an many automatic text lines, an icon named Pogoplug will appear on your desktop and you will be able to manage the online Pogoplug features as a local disk.

Don’t forget that you have to use keys -control+c- in Terminal if you want to disconnect from Pogoplug.

At this point the work is done but you might create a launcher icon in your (e.g.) Applications menu following this instructions:

– go to: System Tools –> Preferences –> Main Menu and click on the group (menu) where you want to create your new launcher (in my case simply was Applications)

New Item –> Create Launcher

Then fill the required fields with:

Type = Application in Terminal

Name = Pogoplug

Command =

/home/yourusernameonubuntu/pogoplugfs --password yourpassword 
--mountpoint /media/pogoplug --user yourusername

(as for the example above)

If you want to personalize the button you can also choose your favorite icon clicking on the picture on the left high corner.

On my side I also preferred to automatize the launch of Pogoplug command at each boot up in this way:

– go to: System Tools –> Preferences –> Startup Applications
– click on Add

– fill the fields:

Name = Pogoplug

Command = Same command line you used to start Pogoplug drive:

/home/yourusernameonubuntu/pogoplugfs --password yourpassword 
--mountpoint /media/pogoplug --user yourusername

(as for the example above)

So, starting now, you will have your Pogoplug drive connected each time you boot Ubuntu. You will not have any annoying Terminal lines.

Security Warnings: don’t forget that the data you move to and back Pogoplug, are directed through the web. This means that they could potentially be intercepted (and read) by third parties but it’s also necessary to specify that, if you configure it on the website Settings area, Pogoplug uses SSL (HTTPS) to encrypt the connection with its servers.

Anyway, don’t forget that the data you store into Pogoplug are not encrypted. If you want to join a better level of security you can encrypt previously your data or your disks using different softwares as TrueCrypt or the command dm-crypt (for more details on this topic also visit http://archlinuxarm.org/forum/viewtopic.php?t=1761&p=9723).