[SOLVED] Media Playing issues in VLC in Ubuntu 10.10 Maverick Meerkat

I had problems with playing media files in VLC in Maverick Meerkat. Other players (SMPlayer) seemed to work fine. VLC gave errors like:

“No suitable decoder module: VLC does not support the audio or video format “XVID”. VLC Unfortunately there is no way for you to fix this.”

And

“No suitable decoder module: VLC does not support the audio or video format “H264”. VLC Unfortunately there is no way for you to fix this.”

Found this solution written by my friend khattam but it didn’t solve my issue. It still gave errors.

I solved the errors after removing libavutil-extra-49, libavutil-extra-50 and installing libavutil50, libavutil49.

sudo apt-get install libavutil50 libavutil49

This will automatically remove the libavutil-extra-49 and libavutil-extra-50 and install libavutil50 and libavutil49 over it. It solved the issue for me.

Click here if this doesn’t solve your issue.

Cheers!

[SOLVED] Blank screen while booting Lucid Lynx on older ATI graphics

I had tried the beta version of Lucid Lynx few weeks back but it didn’t boot, it gave me blank screen with no cursor everytime I tried to boot up. Even the menu didn’t show. I thought there must be a bug since its beta. When final version released day before yesterday, I quickly downloaded and burned a CD only to find the same problem while booting. I couldn’t even see the menu. The problem is thought to be associated with ATI cards… mine is ATI x1250.

After doing some searches on google and some experimenting I found a solution to this problem. Adding a nomodeset parameter while booting solves the problem. For my even the menu wasn’t appearing, but pressing F6 made it appear for me.

As soon as you see this screen press F6 to bring the language selection menu. Select appropriate language and press enter. Now, you’ll see the boot menu. Press F6 to bring another menu to select kernel parameters and select nomodeset from the menu. Here’s what it would look like:

Now, press Esc and press enter to boot. If you’ve done everything right, it’ll boot right into the desktop or ubiquity-installer… whatever you’ve chosen.

However, after installation you may face this problem again. To solve that edit the file /etc/default/grub.
Find the line:

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash”

and change it to:

GRUB_CMDLINE_LINUX_DEFAULT=”quiet splash nomodeset”

Save the file.

After this execute sudo update-grub2 in terminal to make changes to grub.cfg automatically

Feel free to comment if you have any questions/doubts.

Cheers!

[Solved] Unable to enumerate USB device (Disabling ehci_hcd)

Some hardware just don’t work with ehci_hcd on Karmic Koala. My memory stick from transcend refused to work no matter what I did. After plugging the device nothing happened, doing dmesg showed me the following error:

Apr 18 10:59:04 dpac-laptop kernel: [73668.388060] usb 1-2: new high speed USB device using ehci_hcd and address 5
Apr 18 10:59:04 dpac-laptop kernel: [73668.473034] hub 1-0:1.0: unable to enumerate USB device on port 2

After searching a lot, I came to a conclusion that my device doesn’t work with USB 2.0. So I disabled the ehci_hcd to make it work.

Since Karmic doesn’t use ehci_hcd as a module, modprobe -r ehci_hcd no longer works. The module is compiled into kernel. To disable it execute the following commands in terminal:

cd /sys/bus/pci/drivers/ehci_hcd
ls

You will see a file with 0000:00:xx.x format. Execute the following command:

sudo sh -c 'echo -n "0000:00:xx.x" > unbind'

Replace the xx.x with the numbers displayed on your file. It should disable the ehci_hcd.

I plugged in my memory stick, and it worked.

Please note that you’ll have to do all this each time you restart.

UPDATE
You can now use the following script to disable ehci_hcd. It is far more simpler since it just needs you copy pasting the commands instead of a manual action. Here it goes:

cd /sys/bus/pci/drivers/ehci_hcd/
sudo sh -c 'find ./ -name "0000:00:*" -print| sed "s/\.\///">unbind'

Cheers!

13 cool themes for Linux

Those of who are bored of the dull themes of Linux, I found 13 cool new themes for Linux.

Bisigi Themes provide 13 free themes, each has its own icon-set, wallpaper, and color scheme. Just a few terminal commands are needed to install them.

Installation instructions of Bisigi Themes

Few people have complained that the link above does not open, so I’ll give the instructions here as well.

Add the key for repository:

gpg –keyserver hkp://keyserver.ubuntu.com:11371 –recv-key 881574DE && gpg -a –export 881574DE | sudo apt-key add –

Add the repository in sources.list. Open the terminal and fire the command:
sudo gedit /etc/apt/sources.list

Copy and paste the following lines at the bottom and save the file and exit.

## Thèmes du projet bisigi
deb http://ppa.launchpad.net/bisigi/ppa/ubuntu karmic main
deb-src http://ppa.launchpad.net/bisigi/ppa/ubuntu karmic main

Note:Replace karmic with jaunty or hardy if you are using 9.04 or 8.04 respectively.

Update your software sources and install the themes:

sudo apt-get update
sudo apt-get install bisigi-themes

You’ll be prompted to choose your desktop resolution during installation. Choose the correct one for continuing the installation.

You can access the themes by going to System->Preferences->Appearance

Cheers!

[Solved] Unable to boot due to GNOME Power Manager error

If you are getting the following error while booting into ubuntu, its most likely due to low disk space in root drive:

“The configuration defaults for GNOME Power Manager have not been installed correctly. Please contact your computer administrator.”

Behavior:
After you enter the password on login screen, it takes you back to login screen making you unable to log in.

Solution:
However, you can still get to terminal. Press Ctrl+Alt+F1 to drop to terminal from login screen. Enter your username and password and execute the following command:

sudo apt-get clean

This will clean up the package cache freeing up lots of disk space. If you don’t have anything in the cache you’ll have to move your files to another partition. You can use mv for the purpose.

mv source destination

For eg;

mv ./file.zip /media/disk-3/file.zip

This will move the file – file.zip to /media/disk-3.

For people who still have the same error can try some alternate fixes as mentioned below:

  • Chmodding /tmp to 0777 have worked for many people.
    chmod 0777 /tmp
  • Try to reconfigure your packages.Source
    sudo dpkg --configure -a
  • Manually create the directory /var/lib/gconf/default/. Source
    mkdir /var/lib/gconf/default
  • Reinstall GNOME and dependencies
    sudo apt-get --reinstall install ubuntu-desktop
    

    Note that this command will remove some settings. Source

Cheers!

Guitar Pro alternative in Ubuntu

I am a big guitar freak. I play guitar all the time. A good friend for guitar learners is Guitar Pro on windows. Guitar pro is basically a tool which shows musical notations, plays them, show the notation on guitar tabs, change tempo etc. It helps beginners a lot.

Today, I felt the need to use it again, but I didn’t want to logon to windows for doing that. I knew there had to be an alternative in Ubuntu (Geeks play guitar too :D). Fortunately, I found two packages in repos which could work similar and better than guitar pro. Best of all, they are free.

To install them, type the following in terminal:

For tuxguitar:

$ sudo apt-get install tuxguitar

For kguitar (It is for Kubuntu/KDE users):

$ sudo apt-get install kguitar

I found tuxguitar to be more feature-rich and bug free. Try ’em both to see what suits you.

Cheers!

Recovering GRUB2 after hard-drive upgrade

I upgraded to a 500GB hard-drive and installed windows 7 on it. I then moved my current ubuntu installation from the older HDD to the newer one on another partition, but of course there was no bootloader to load it. I had GRUB2 on older hard drive. I googled about how to recover GRUB2 but couldn’t find one. All I could find was solutions to fix corrupt Grub. So, I just reinstalled grub and then upgraded it to Grub2.

Here’s how to do it:

Boot into Ubuntu Live CD.
Mount the root disk (Disk on which Ubuntu is installed).

mkdir /media/root
mount /dev/sda7 /media/root

where /dev/sda7 is your disk.

If you don’t know which disk the ubuntu is installed on, you can fdisk

sudo fdisk -l

Now, when you can install grub using grub-install

sudo grub-install –root-directory=/media/root /dev/sda –recheck

This will install the grub on the mounted disk. You can now reboot and get into your Ubuntu and upgrade it to GRUB2.

If this doesn’t work, you will have to change the root to the hard disk and install grub. To do that,

Unmount your boot partition (I’ll take sda7 as the example again) before proceding.

mkdir /mnt/root
mount /dev/sda7 /mnt/root
mount -o bind /proc /mnt/root/proc
mount -o bind /dev /mnt/root/dev
chroot /mnt/root

You may need to run these as root/superuser. If successful, you’ll get the terminal access to your boot partition. You can now install the grub using apt-get.

apt-get install grub
update-grub

But since, this is a new hard-drive, uuid won’t match. Hence, booting will fail.
To address this issue, you can install the grub2 without restarting

apt-get install grub2
grub-mkdevicemap
update-grub2

Reboot. Grub2 should be installed now.

[Solved] Ath5k wifi module not working in Karmic Koala

I noticed was my wifi (Atheros AR5001/5007EG) stopped working after I upgraded to Karmic Koala. I searched endlessly on Google without any answer. Then, I remembered that Karmic comes with newer kernel 2.6.31. And ath5k kernel module hasn’t been loaded yet into this newer kernel.

So, I simply executed

modprobe ath5k

in the terminal.
And in an instant, I saw my wifi connected to my access point.
The command loaded the module into the kernel.

Hope, this helps.

Cheers!

Recovering from corrupt upgrade from Jaunty to Karmic

I was excited for the Karmic Koala (v. 9.10) which came out yesterday and I happily started the download and kept the computer switched on overnight for the download to complete. When I woke up, surely the download was completed and I went on to install the downloaded packages. Which the installation was taking place, power went off and computer switched off abruptly. I was in shock and feared I wouldn’t be able to boot into Ubuntu again.

My fears came true when booting process stopped at “waiting for /dev/sda6″. I waited for quite a while but it would never proceed to next step. I pressed Esc and I was dropped into root terminal. I at once did

dpkg –configure -a

That didn’t help much. It gave me error “Read-only file system”. So, I made the file-system writable by doing

mount -n -o remount,rw -t ext3 /dev/sda7 /

where
-n = dont write to /etc/mtab because the system is already read-only
-o remount,rw = remount the filesystem in read-write (rw) mode
-t ext3 = this is explicitly specifying the type of filesystem the root folder has. It is optional
/dev/sda7 = partition which is meant to be mounted
/ = location to mount it upon

After, this I again executed

dpkg –configure -a

I didn’t get any errors this time. It took around 2-3 minutes to reconfigure all the settings automatically. Then, I installed the not-installed packages of Karmic by executing

sudo aptitude install

Then, I rebooted the computer and voila!, I booted into Karmic.

Cheers!

Killing Xorg, when things get out of control

Today I experienced a rather strange problem in Ubuntu. It crashed. Actually it wasn’t completely crashed, the mouse clicks weren’t working, I couldn’t switch using Alt+Tab, I could only use the program which was on the screen. The panels weren’t working, though the shortcut keys were. Fortunately enough, I had assigned shortcut key to open the terminal and it was working, so I could even access the terminal.

Fortunately, firefox  (shiretoko) was running as the frontmost application and I was able to access the internet. I searched for How to kill X and was presented with many solutions.

I tried killall X in  terminal but it didn’t work. Suddenly, I remembered that X was called Xorg in jaunty. I did this:

sudo killall Xorg

and instantly the X restarted, and presented me the login screen. And after logging in everything was as good as rebooted :D.

I love Ubuntu, I love linux.

Cheers!