[ S O L V E D ] - bz2 library (bz2 compression) not found Note: You might have the lib but not the headers

This is a guide to properly install the bzip2-devel library under Ubuntu.

After trying for a while looking for the bzip2-devel on the internet I figured it out that the proper name for the bz2 library was "libbz2-dev"

I was trying to compile using scons an application. In my case it was linuxdc++

here is the full log with the error

Checking for g++ >= 3.4...(cached) yes
Checking for pkg-config... yes
Checking for gtk+-2.0 >= 2.8... yes
Checking for gthread-2.0 >= 2.4... yes
Checking for libglade-2.0 >= 2.4... yes
Checking for C header file time.h... yes
Checking for C header file signal.h... yes
Checking for C header file unistd.h... yes
Checking for C library pthread... yes
Checking for C library z... yes
Checking for C library bz2... no
bz2 library (bz2 compression) not found
Note: You might have the lib but not the headers

so, after typing on a terminal.

$ sudo apt-get install libbz2-dev

the problem was solved....

Linux find command Permision or Access Denied error message.

Excluding the  "permission denied" or "Access denied" message is quite simple.

When the find command is executed with lack of permissions, all the errors saying "permission denied"  are sent to the stderr.

There is a way of redirecting all this errors to the void. that's the /dev/null device.

example of a find execution:

find ./ -iname '*.jpg' -print 2> /dev/null

./2012/07/08/DSC_0113.JPG

./2012/07/08/DSC_0103.JPG

./2012/07/08/DSC_0124.JPG

./2012/07/08/DSC_0107.JPG

./2012/07/08/DSC_0115.JPG

And that's it ! ! !

here is the video of this exact example




No more permission-related errors.

This is a good practice if you are coding in linux using the find command for bash scripting or perhaps you want to create your own find GUI.

Thank you for stopping by.

[ S O L V E D ] - WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring pkcs11: No such file or directory

THIS FIX MAKES THE gnome-keyring-pkcs11.so LOAD AT STARTUP FOR THE LXDE SESSION

This is one of them, now fixed....Warning message, it's an error message cause it is not letting the command to run. "WARNING: gnome-keyring:: couldn't connect to: /tmp/keyring-<SOMEGENERATEDSTRING>/pkcs11: No such file or directory "This is caused because of a module: gnome-keyring-pkcs11.so that is not being loaded when you log into an LXDE session. (this problem is analog to other sessions too, in this case I am using LXDE but could be KDE, GNOME etc... see the solution to understand how).

Here is the FIX!!!:

add "LXDE;" (without the double quotes and plus the semicolon, didn't try without it) 

to this file "/etc/xdg/autostart/gnome-keyring-pkcs11.desktop"  by editing it with whatever text editor you preffer, I'll use "nano" 

1 - in a terminal type (as root or with sudo): nano /etc/xdg/autostart/gnome-keyring-pkcs11.desktop

[Desktop Entry]

Type=Application

Name=Certificate and Key Storage

Comment=GNOME Keyring: PKCS#11 Component

Exec=/usr/bin/gnome-keyring-daemon --start --components=pkcs11

OnlyShowIn=GNOME;Unity;LXDE;

X-GNOME-Autostart-Phase=Initialization

X-GNOME-AutoRestart=false

X-GNOME-Autostart-Notify=true

X-GNOME-Bugzilla-Bugzilla=GNOME

X-GNOME-Bugzilla-Product=gnome-keyring

X-GNOME-Bugzilla-Component=general

X-GNOME-Bugzilla-Version=3.2.2

NoDisplay=true

X-Ubuntu-Gettext-Domain=gnome-keyring

2 - after editing, make sure you save the changes

3 - RESTART YOUR PC

CHEERS!

PLEASE PRESS THE LIKE BUTTON, THANK YOU A LOT!

[ S O L V E D ] Sound Blaster Audigy 2 subwoofer crashes

SOLVED - Sound Blaster Audigy 2 subwoofer crashes after playing a song ! ! ! (stands for 3.1 5.1 and 7.1)

the next workaround is Sound Blaster Audigy independant, so it will probably work with other soundcards, try it out and send me your experiences.

 # UBUNTU  9.04 9.11 10.04 10.11 11.04 11.11 12.04 subwoofer died everytime It changes songs with whatever player....

I removed pulseaudio and installed it again with

STEP 1

run this on a terminal

sudo apt-get purge pulseaudio

sudo apt-get install pulseaudio

optional

(if you created the /home/yourusername/.asoundrc remove it or rename it or it won't take effect.)
mv ~/.asoundrc ~/.asoundrc-backup

STEP 2

Add  to /etc/pulse/daemon.conf

enable-lfe-remixing = yes

STEP 3

kill pulseaudio.

sudo killall pulseaudio

STEP 4

reboot or run pulseaudio as a normal user

run this on a terminal if not rebooting.

pulseaudio &

STEP 5 

run pavucontrol to choose and customize your 

STEP 6

E  N  J  O  Y  !  !  !


I spent too much time looking for a solution to this problem, that' s why I am sharing it with you.
See ya.

[ S O L V E D ] - CodeBlocks "It seems that the project has not been built yet" error.

After creating a project and making a file the running point of it we will face a dead end loop message saying: "It seems that the project has not been built yet error. Do you want to build it now ?."  It is preety easy to fix, in the project go to Properties > Build Targets. And select the running point, in my case it is the main.cpp file. Sometimes it switches from Debug mode to Release mode, well in that case you will have to make sure both configurations have an entry point. (a main method).

Images below.

SOLVED ! ! !