Lirc Remote Revisited

digitaleagle Troubleshooting, Uncategorized Leave a comment

Back in May, I had posted an issue with lirc, Mythbuntu, and my MceUsb2 Remote.  The final solution ended up being just waiting some time, running the update manager to update the machine, and trying again.

If you didn’t see the comments, Orlovsky did post a helpful link to a bug.  My attempt was going to be to try to remove the old kernels and see if that would fix it.  But, like I said, some update fixed it in the meantime — I am grateful to the community.

To be complete, my remote is AVS Gear GP-IR02BK Vista 2 channel IR Remote Control.  It seems to work pretty well with Mythbuntu.  MythTV.org has a good resource for configuring the remote.

Linux at Google

digitaleagle Great Links, Uncategorized Leave a comment

In catching up on my RSS feeds, I found a flurry of articles about Google switching away from Windows because of the Chinese hack.  This sounds exciting to me because it probably means that the Linux community will grow.

The articles say that Google employs more than 10,000 people.  They have a choice of going to Apple, but surely a decent number of them will choose Linux.  The other encouraging thing is that many of them are probably programmers.  So, I would hope that this would mean more contributions to the desktop features of Linux.

Articles:

Possibly related?

Updated MonoDevelop Repository

digitaleagle Gnome-RDP, Mono, Troubleshooting, Uncategorized Leave a comment

I have been trying to work with MonoDevelop and GnomeRDP.  I couldn’t get it to open the project because I needed the newer version of Monodevelop as described here.  I figured out how to install MonoDevelop manually.  The problem with all of this is that you have to get all of the dependencies yourself.

So, instead I finally found a repository with Monodevelop 2.2 in it:

How to install MonoDevelop 2.2 on Ubuntu 9.10?

Errors Opening Gnome-RDP Project

digitaleagle Gnome-RDP, Mono, Uncategorized 1 Comment

I ran into an error opening the Experimental branch of Gnome-RDP, and I wanted to post it in case anyone else ran into the same problem.  Here is what the error looked like:

screenshot_143

Here is the text:

Could not load solution: <solution path>.  Could not set property ‘Policies’ in type ‘Solution’.

Load operation failed. Could not set property ‘Polieis’ in type ‘Solution’

Error while trying to load the project ‘<project path>’: Could not set property ‘Policies’ in type ‘DotNetProject’

Error while trying to load the project ‘<project path>’: Could not set property ‘Policies’ in type ‘DotNetProject’

The solution apparently, as found in this bug post, is to install a new version of Mono-Develop.  I see now that the post has a repository that you can use.  I ran across these instructions, and I detailed my execution of those instructions on my previous posts.

Installing an Alternate MonoDevelop

digitaleagle Gnome-RDP, Mono, Uncategorized 2 Comments

I needed a newer version of Monodevelop, and I couldn’t find  a repository that would allow me to just update it with apt-get.  Rather than change all the libraries that other programs might be using, I thought these instructions might provide a safe solution anyway.  So, I embarked on installed a standalone version self-contained in this directory:

/home/skp/app/blog

The first step settings up your environment variables to separate your environment out.  Like the instructions, I created a mono-dev-env file: gedit mono-dev-env.  Here is my file:

#!/bin/bash
MONO_PREFIX=/home/skp/app/blog
GNOME_PREFIX=/home/skp/app/blog
export DYLD_LIBRARY_PATH=$MONO_PREFIX/lib:$DYLD_LIBRARY_PATH
export LD_LIBRARY_PATH=$MONO_PREFIX/lib:$LD_LIBRARY_PATH
export C_INCLUDE_PATH=$MONO_PREFIX/include:$GNOME_PREFIX/include
export ACLOCAL_PATH=$MONO_PREFIX/share/aclocal
export PKG_CONFIG_PATH=$MONO_PREFIX/lib/pkgconfig:$GNOME_PREFIX/lib/pkgconfig
PATH=$MONO_PREFIX/bin:$PATH
PS1="[mono] \w @ "

Then make sure that you source it in:

. ./mono-dev-env

I downloaded the various packages mostly from this page.  I setup a special directory called “downloads” for those file that I downloaded.

[mono] ~/app/blog @ mkdir downloads


[mono] ~/app/blog @ cd downloads

Next, I downloaded libgdiplus from the releases page.  I uncompressed it and installed it with these commands:

wget http://ftp.novell.com/pub/mono/sources/libgdiplus/libgdiplus-2.6.4.tar.bz2
tar -xjvf libgdiplus-2.6.4.tar.bz2
cd libgdiplus-2.6.4
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed mono from the releases page with these commands:

wget http://ftp.novell.com/pub/mono/sources/mono/mono-2.6.4.tar.bz2
tar -xjvf mono-2.6.4.tar.bz2
cd mono-2.6.4
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed gtk-sharp from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/gtk-sharp212/gtk-sharp-2.12.10.tar.bz2
tar -xjvf gtk-sharp-2.12.10.tar.bz2
cd gtk-sharp-2.12.10
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed mono-tools from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/mono-tools/mono-tools-2.6.2.tar.bz2
tar -xjvf mono-tools-2.6.2.tar.bz2
cd mono-tools-2.6.2
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed mono-addins from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/mono-addins/mono-addins-0.4.zip
unzip mono-addins-0.4.zip
cd mono-addins-0.4
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed monodevelop from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/monodevelop/monodevelop-2.2.2.tar.bz2
tar -xjvf monodevelop-2.2.2.tar.bz2
cd monodevelop-2.2.2
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed gnome-sharp from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/gnome-sharp2/gnome-sharp-2.24.1.tar.bz2
tar -xjvf gnome-sharp-2.24.1.tar.bz2
cd gnome-sharp-2.24.1
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed gnome-desktop-sharp from the same releases page:

wget http://ftp.novell.com/pub/mono/sources/gnome-desktop-sharp2/gnome-desktop-sharp-2.24.0.tar.bz2
tar -xjvf  gnome-desktop-sharp-2.24.0.tar.bz2
cd gnome-desktop-sharp-2.24.0
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed gnome-keyring-sharp.  With the help of a link or two, I found I could download it here:

wget http://ftp.novell.com/pub/mono/sources/gnome-keyring-sharp/gnome-keyring-sharp-1.0.0.tar.bz2
tar -xjvf  gnome-keyring-sharp-1.0.0.tar.bz2
cd gnome-keyring-sharp-1.0.0
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed Mono.Cairo.  With the help of this page, I found I could download it here:

wget http://cairographics.org/releases/cairo-1.8.10.tar.gz
tar -xzvf cairo-1.8.10.tar.gz
cd cairo-1.8.10
./configure --prefix=$MONO_PREFIX
make
make install

Next, I installed DBusSharp.  I found I could download it here:

wget http://www.ndesk.org/archive/dbus-sharp/ndesk-dbus-0.6.0.tar.gz
tar -xzvf ndesk-dbus-0.6.0.tar.gz
cd ndesk-dbus-0.6.0
./configure --prefix=$MONO_PREFIX
make
make install

Now, for the time of reconing — start monodevelop:

monodevelop

So, here is the About dialog:

screenshot_142

Installing Mono Dependencies

digitaleagle Gnome-RDP, Troubleshooting, Uncategorized Leave a comment

I pulled the latest version of Gnome-RDP, and ran into a few errors when compiling.

screenshot_134

Here is how I solved the problems:

For the “Reference ‘Mono.Cairo’ not found on system”, I found a tutorial page with links to the download.  I downloaded the latest version from the releases page.

I uncompressed the download into “cairo-1.8.8”, and opened a command-line into that directory.  I ran the configure with my custom path because I have a specially compiled version of MonoDevelop that I am using:

./configure --prefix=$MONO_PREFIX

Then, I compiled and installed:

make
make install

Finally, my project was requiring a specific version, and I downloaded a newer version.  So, I just unchecked the require version flag:

screenshot_141

For the “Assembly ‘NDesk.DBus'” error, I downloaded the library from the DBusSharp page.  Then, I uncompressed it into the folder “ndesk-dbus-0.6.0”.  Again, I added the prefix option because I had a special path for MonoDevelop:

./configure --prefix=$MONO_PREFIX

Then, I compiled and installed:

make
make install

Finally, the /tmp/tmp22c1daf8.tmp problem was caused by this message:

** (/home/skp/app/gnome-rdp/monodevelop/lib/mono/2.0/gmcs.exe:4434): WARNING **: The following assembly referenced from /home/skp/app/gnome-rdp/gnome-rdp-temp/gnome-rdp/gnome-rdp-dockyplugin/References/Docky.Items.dll could not be loaded:


Assembly:   notify-sharp    (assemblyref_index=17)


Version:    0.4.0.0


Public Key: 2df29c54e245917a


The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/home/skp/app/gnome-rdp/gnome-rdp-temp/gnome-rdp/gnome-rdp-dockyplugin/References/).

** (/home/skp/app/gnome-rdp/monodevelop/lib/mono/2.0/gmcs.exe:4434): WARNING **: The following assembly referenced from /home/skp/app/gnome-rdp/gnome-rdp-temp/gnome-rdp/gnome-rdp-dockyplugin/References/Docky.Items.dll could not be loaded:     Assembly:   notify-sharp    (assemblyref_index=17)     Version:    0.4.0.0     Public Key: 2df29c54e245917aThe assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/home/skp/app/gnome-rdp/gnome-rdp-temp/gnome-rdp/gnome-rdp-dockyplugin/References/).

I found the library’s home page, but I didn’t see a release yet.  So, I had to download from the repository.  First, I had to have the hg command installed:

sudo apt-get install mercurial

Then, I used the command from the homepage to download the code:

hg clone http://hg.circular-chaos.org/notify-sharp

But, that is a broken link.  Well, I am running out of time for this one on my lunch break, so I will have to come back to it.  I found a post suggesting to pull it from Gnome-Do.  I probably already have it installed somewhere.


VMWare on Linux

digitaleagle Uncategorized, Virtualization Leave a comment

After the latest kernel update, it struck me that VMWare has come a long ways.  I remember when I had to go to the command-line and run the configure program.  That would go through the whole kernel module compile process.  It worked, but it was kind of ugly.

Well, now it looks pretty slick:

screenshot_080

Everything just worked.  No problems to work through or worry whether I had everything in place.

Thanks, VMWare for the great work!