Category: Troubleshooting

Shutter Bug: Can’t edit

digitaleagle Troubleshooting, Uncategorized 5 Comments

I just upgraded to Lucid (Ubuntu 10.04), and I reinstalled Shutter.  I had found it not too long ago, and it does a great job with screenshots.  One of my favorite features is the way you can edit the screenshots and draw circles to point out things in the shot.  It’s great for documentation.

Problem is, in Ubuntu 10.04, the Edit button is disabled.  I found this bug post: Editing disabled in Ubuntu Lucid.

Solution: install the package: libgoo-canvas-perl

It was that easy, and now it is working like a charm!

Power Problems

digitaleagle Troubleshooting, Ubuntu, Uncategorized Leave a comment

I have been having trouble with my battery not charging.  The battery seems to have good capacity — I just replaced it a few months ago.  But, I can run it down, plug the laptop in, and then hours later the battery is still dead.

I found this article that seemed like it might help:

Ubuntu Productivity: Battery always 0% in Ubuntu 10.04

I tried the two things suggested on the blog:  I pressed the power button for a couple of seconds while the battery and power cord were out, and I tried to start upower.  I didn’t have upower as an option even for installing probably because I am still on Ubuntu 9.10.

What I haven’t tried yet is recompiling libusb as suggested in the related forum topic.

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.

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?

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.


Getting MceUsb Remote to Work on Mythbuntu 10.04

digitaleagle Troubleshooting, Uncategorized 3 Comments

I have been trying to get my remote to work on my new Mythbuntu installation — so far no luck.  So, don’t expect and answer at the end of this.  I will try to post an answer when I get one.

Here is first clue:

sudo /etc/init.d/lirc restart verbose
* Stopping remote control daemon(s): LIRC                               [ OK ]
* Loading LIRC modules                                                  [ OK ]
* Unable to load LIRC kernel modules. Verify your
* selected kernel modules in /etc/lirc/hardware.conf
sudo /etc/init.d/lirc restart verbose
* Stopping remote control daemon(s): LIRC                               [ OK ]
* Loading LIRC modules                                                  [ OK ]
* Unable to load LIRC kernel modules. Verify your
* selected kernel modules in /etc/lirc/hardware.conf

So, I found this article with the same problem.  The solution was to install a generic kernel, so I wanted to check a few other threads.  Then, I found this article.  I went with it since it was a more recent version. It calls for these two commands:

skp@gabriel:~$ sudo mv /lib/modules/2.6.32-21-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko ~/.
[sudo] password for skp:
skp@gabriel:~$ sudo dpkg-reconfigure lirc-modules-source
Package `lirc-modules-source' is not installed and no info is available.
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
/usr/sbin/dpkg-reconfigure: lirc-modules-source is not installed

Since it said I didn’t have the package installed, I tried to install it:

skp@gabriel:~$ sudo apt-get install lirc-modules-source
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
  kernel-source
The following NEW packages will be installed:
  lirc-modules-source
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 273kB of archives.
After this operation, 1,204kB of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu/ lucid/universe lirc-modules-source 0.8.6-0ubuntu4 [273kB]
Fetched 273kB in 1s (159kB/s)
Selecting previously deselected package lirc-modules-source.
(Reading database ... 160587 files and directories currently installed.)
Unpacking lirc-modules-source (from .../lirc-modules-source_0.8.6-0ubuntu4_all.deb) ...
Setting up lirc-modules-source (0.8.6-0ubuntu4) ...
Loading new lirc-0.8.6 DKMS files...
First Installation: checking all kernels...
Building only for 2.6.32-22-generic
Building for architecture x86_64
Building initial module for 2.6.32-22-generic
Done.

lirc_dev.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_atiusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_bt829.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ite8709.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_i2c.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_igorplugusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_imon.ko:
Running module version sanity check.

Error! Module version 0.6 for lirc_imon.ko
is not newer than what is already found in kernel 2.6.32-22-generic (0.6).
You may override by specifying --force.

lirc_it87.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_mceusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ttusbir.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_sasem.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_serial.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_sir.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_streamzap.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ene0100.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_wpc8769l.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

depmod........

DKMS: install Completed.

With that complete, I checked to make sure it reinstalled that module:

skp@gabriel:~$ ls -l /lib/modules/2.6.32-21-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko
ls: cannot access /lib/modules/2.6.32-21-generic/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko: No such file or directory

Nope, but maybe this isn’t my kernel:

skp@gabriel:~$ uname -r
2.6.32-22-generic

So, let’s try that again with the uname -r in place:

skp@gabriel:~$ sudo mv /lib/modules/`uname -r`/kernel/ubuntu/lirc/lirc_imon/lirc_imon.ko ~/.
skp@gabriel:~$ sudo dpkg-reconfigure lirc-modules-source
Removing all DKMS Modules
Done.
Loading new lirc-0.8.6 DKMS files...
Building only for 2.6.32-22-generic
Building for architecture x86_64
Building initial module for 2.6.32-22-generic
Done.

lirc_dev.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_atiusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_bt829.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ite8709.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_i2c.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_igorplugusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_imon.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_it87.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_mceusb.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ttusbir.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_sasem.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_serial.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_sir.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_streamzap.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_ene0100.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

lirc_wpc8769l.ko:
Running module version sanity check.
 - Original module
 - Installation
   - Installing to /lib/modules/2.6.32-22-generic/updates/dkms/

depmod....

DKMS: install Completed.

It worked, time to test:

skp@gabriel:~$ sudo /etc/init.d/lirc restart verbose
 * Stopping remote control daemon(s): LIRC                               [ OK ]
 * Loading LIRC modules                                                  [ OK ]
 * Unable to load LIRC kernel modules. Verify your
 * selected kernel modules in /etc/lirc/hardware.conf

Still no luck.

Resources

3D Acceleration for VMWare Player

digitaleagle How To, Troubleshooting, Ubuntu, Uncategorized, Virtualization 4 Comments

I noticed a message saying that I did not have 3d acceleration in my virtual image with VMWare player. I didn’t really need it as all I was doing was using the PeopleSoft IDE and a web browser, but I wondered if it would improve performance. I will probably never know if it made a difference other than get rid of the message.

The fix was to install driconf and enable “S3TC texture compression even if software support is not available”.

Installing driconf was as easy as:
sudo apt-get install driconf

Run driconf from the command line with the command:
driconf

Go to the “Image Quality” tab, and click “Yes” for “Enable S3TC texture compression even if software support is not available”

driconf

Resources

3D Acceleration on Intel X3100

WebEx working again in Ubuntu 9.10-64bit!

digitaleagle Install Help, Troubleshooting, Ubuntu, Uncategorized, WebEx 13 Comments

It seems like this is the pattern with me and WebEx.  I tinker to get it working, I upgrade, it breaks, repeat.  Well, my most recent fling through this cycle started with a broken hard drive.  Actually, several things started it.  First, I originally thought my laptop had a 32-bit processor.  When I found out the new version of PeopleSoft requires a 64-bit OS, I did some research and found that it was actually a 64-bit processor.  Then, when I sent the laptop off to have the hard drive replaced, I figured that was the time to put 64-bit Ubuntu on it.

So, that is how it started, and then, I couldn’t get WebEx to work.  I got Eclipse to work on 64-bit Java, Java worked in the browser, and everything was fine.  I didn’t want to try to pull it all out and reinstall the 32-bit Java just to get WebEx working.  So, I decided to attempt to try to install the 64-bit and 32-bit versions side by side.  With some help, I got it to work:

Ubuntu Forums: 32-bit and 64-bit Firefox at the same time

The first step was installing Java.  It was pretty simple and straight forward.  I downloaded it from Sun’s website.  Essentially, you just extract it and set your environment variables to use it.  The path I chose was $HOME/bin/java.

Next, I found that you cannot use the 32-bit version of Java with the 64-bit version of Firefox.  Firefox throws out all of the 32-bit plugins with this message: “wrong ELF class”.    So, I installed Firefox by downloading it from Firefox’s website.  I extracted it to $HOME/bin/java/firefox.

The next key was linking the Java plugin in the path where Firefox would see it.  First, I linked the plugin into plugins directory:

ln -s $JAVA_HOME/lib/i386/libnpjp2.so libnpgp2.so

Once in the Firefox plugins directory, you have to make sure Firefox knows where the plugins directory is with the MOZ_PLUGIN_PATH variable.

So, to recap, I have:

  • Java installed at $HOME/bin/java
  • Firefox installed at $HOME/bin/java/firefox
  • Java pluing installed at $HOME/bin/java/firefox/plugins from $HOME/bin/java/jdk…/lib/i386/libnpjp2.so

Then, I created an environment script that sets all of the paths and variables to make it work:

#!/bin/sh


export PATH=~/bin/java/firefox:~/bin/java/jdk1.6.0_18/jre/bin/:~/bin/java/jdk1.6.0_18/bin/:$PATH


export JAVA_HOME=~/bin/java/jdk1.6.0_18/jre


export MOZ_PLUGIN_PATH=~/bin/java/firefox/plugins

Finally, I created a script to launch firefox:

#!/bin/bash

cd ~/bin/java
. ./env.sh
firefox --no-remote -P WebEx

And, it worked!

WebEx Error

digitaleagle Troubleshooting, Uncategorized, WebEx 1 Comment

I have been struggling to get WebEx to work now that I have upgraded to Ubuntu 9.04.  I get the error below, and it failes to continue loading.  If anyone has any ideas, please let me know.  I did just upgrade to Firefox 3.5, but that didn’t fix the problem.  I also did a search on Google, and that didn’t turn up anything.

java.io.EOFException
at java.io.DataInputStream.readInt(DataInputStream.java:375)
at sun.security.provider.JavaKeyStore.engineLoad(JavaKeyStore.java:628)
at sun.security.provider.JavaKeyStore$JKS.engineLoad(JavaKeyStore.java:38)
at java.security.KeyStore.load(KeyStore.java:1185)
at com.sun.deploy.security.DeploySigningCertStore$1.run(DeploySigningCertStore.java:154)
at java.security.AccessController.doPrivileged(Native Method)
at com.sun.deploy.security.DeploySigningCertStore.loadCertStore(DeploySigningCertStore.java:137)
at com.sun.deploy.security.DeploySigningCertStore.load(DeploySigningCertStore.java:107)
at com.sun.deploy.security.DeploySigningCertStore.load(DeploySigningCertStore.java:92)
at com.sun.deploy.security.ImmutableCertStore.load(ImmutableCertStore.java:43)
at com.sun.deploy.security.TrustDecider.isAllPermissionGranted(TrustDecider.java:245)
at com.sun.deploy.security.TrustDecider.isAllPermissionGranted(TrustDecider.java:218)
at com.sun.deploy.security.TrustDecider.isAllPermissionGranted(TrustDecider.java:208)
at sun.plugin.security.PluginClassLoader.getPermissions(PluginClassLoader.java:150)
at java.security.SecureClassLoader.getProtectionDomain(SecureClassLoader.java:192)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:124)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:260)
at java.net.URLClassLoader.access$000(URLClassLoader.java:56)
at java.net.URLClassLoader$1.run(URLClassLoader.java:195)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at sun.applet.AppletClassLoader.findClass(AppletClassLoader.java:171)
at java.lang.ClassLoader.loadClass(ClassLoader.java:307)
at sun.applet.AppletClassLoader.loadClass(AppletClassLoader.java:143)
at java.lang.ClassLoader.loadClass(ClassLoader.java:252)
at sun.applet.AppletClassLoader.loadCode(AppletClassLoader.java:682)
at sun.applet.AppletPanel.createApplet(AppletPanel.java:785)
at sun.plugin.AppletViewer.createApplet(AppletViewer.java:2315)
at sun.applet.AppletPanel.runLoader(AppletPanel.java:714)
at sun.applet.AppletPanel.run(AppletPanel.java:368)
at java.lang.Thread.run(Thread.java:619)

I did check to make sure I had the ubuntu-restricted-extras and the libstdc++5 installed from this earlier post.