http://ubuntuforums.org/showpost.php?p=10775950&postcount=13

So basically there are three problems with this

1) The touchpad doesn’t work. Evidently, this post seems to solve that problem (but I never got that far)

2) The wireless doesn’t work. It runs on a Broadcom BCM4313 (rev 01) chipset which isn’t built into 10.04 LTS. Another Ubuntu Forums post details a way to solve this, involving compiling some new kernel drivers, however….

3) The ethernet doesn’t work either. To get it working, all you have to do is compile another kernel driver.

So you would have to download all of the necessary packages and source, then go from there. Have fun.

* An automatic file system check (fsck) of the root filesystem failed.  A manual fsck must be performed, then the system restarted. The fsck should be performed in maintenance mode with the root filesystem mounted in read-only mode.

So, basically, my main filesystem was broken somehow.  Adding insult to injury, of course, was the fact that the thing that was shown as causing the problem was S01E02 of Firefly, which I was considering watching soon.  Great. On a strange note, the other place that was giving me trouble was on /etc/acpi/suspend.d/10-thinkpad-standby-led.sh. As for the problem itself,  I know why it happened, of course–this server only goes down when the power goes out and I would imagine that the file reference didn’t get correctly written to the journal before the server crashed. So, after multiple “Multiply-claimed block(s) in inode: x: xxxx xxx” errors, it finally told me to reboot.  After doing so, it fscked the disk again and then had me reboot AGAIN.  Awesome.  That finally let it work though, so I can’t complain.  Now to get a new CMOS battery…

Getting Adobe AIR for Ubuntu 8.10 couldn’t be easier.  Visit the Adobe AIR download page and it’ll automatically detect your system type from your browser’s settings.  The file is a .bin file which means you don’t have to compile it.  Assuming you download it with firefox, simply fire up your terminal, change to your download directory (probably ~/Desktop) and issue

nuke@nuke-laptop:~/Desktop$ chmod +x AdobeAIRInstaller.bin 
nuke@nuke-laptop:~/Desktop$ sudo ./AdobeAIRInstaller.bin

Note: I was getting a very nondescript error when I ran that command saying that Adobe AIR couldn’t be installed and, of course, that was about all of the information I got.  I found out it was because I had the Adobe AIR 1.1 beta installed, which I needed to uninstall.  If you get that, simply run the following command (on Ubuntu):

nuke@nuke-laptop:~/Desktop$ sudo dpkg -r adobeair-enu

and you’ll be fine. If you’re still having problems,definitely look at Adobe’s short FAQ on AIR 1.5.  It will give you a few things to try.  I also had to uninstall my previous AIR stuff with the following commands:

nuke@nuke-laptop:~$ rm .appdata/ -rf
nuke@nuke-laptop:~$ rm .adobe/AIR/ -rf
nuke@nuke-laptop:~$ rm .macromedia/Flash_Player/www.macromedia.com/bin/air* -rf

Then, to get things working, I had to go to the Flash Player download site and download the newest version of Flash!  Also, for anything else that I had installed for AIR (such as twhirl) I had to go in and manually remove it from Ubuntu’s package system.  Now, with most AIR apps, they name the package $appname.air.123o1u4831414323 or somesuch.  However, with twhirl, it installs it as de.makesoft.twhirl.0ea062bc275e7ed1e6ec3762effd73c7158adf33.1 (at least for me) so I had to run

nuke@nuke-laptop:~$ sudo dpkg -r de.makesoft.twhirl.0ea062bc275e7ed1e6ec3762effd73c7158adf33.1

That let me reinstall twhirl. If you can’t find that exact app but have the same problem, try autocompleting (tab) in the terminal after you type “de.makesoft”.  After all of that work, it was working great.  Finally!

A quick note about using newer version of Ubuntu: From 8.10 (Intrepid Ibex) on, Ubuntu doesn’t come with a g77 package. g77 is not used for GEANT4 specifically, but with CERN’s ROOT, which is an amazing statistical analysis package. You won’t NEED this for GEANT4, but it allows you to do some cool stuff.  Anyhow, instead of g77, Intrepid (8.10) comes with ‘gfortran’ which is not the same code, it seems.  Now, there are two ways on handling it.  I, personally, advise sticking to 8.04 and the g77 it comes with.  However, you can use a newer version of Ubuntu (or its variants) and either use Hardy packages or install from source.  Either way, it’s nice to have ROOT installed for statistical analysis.

As a side note, I’m hoping to (eventually) post a complete walkthrough of the process I go through when compiling CLHEP, GEANT4, and ROOT on a 8.04 machine.  It’ll probably be a while before I manage to get it written up, but it sure would be nice…

After a bit of searching, though, I’ve found a nice updated program called Back in Time.  I really like a lot of the features it supports.  It’s written in python and uses rsync and diff to do its magic.  One of the nice features of Back in Time is that it only updates files that have been updated since the last backup.  This doesn’t seem like that huge of a thing, but it does it well.  The only problem I’ve found is that the it won’t accept symlinks that link to outside of its directories–you’ll have to manually include that directory to be included.  Other than that, it’s great!  Check it out.

Exception in thread "main" java.lang.UnsatisfiedLinkError:
Can't load library: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so

The exact error being:

Exception in thread "main" java.lang.UnsatisfiedLinkError: Can't load library: /usr/lib/jvm/java-6-openjdk/jre/lib/i386/xawt/libmawt.so
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1666)
at java.lang.Runtime.load0(Runtime.java:787)
at java.lang.System.load(System.java:1022)
at java.lang.ClassLoader$NativeLibrary.load(Native Method)
at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1767)
at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1684)
at java.lang.Runtime.loadLibrary0(Runtime.java:840)
at java.lang.System.loadLibrary(System.java:1047)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:67)
at sun.security.action.LoadLibraryAction.run(LoadLibraryAction.java:47)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.Toolkit.loadLibraries(Toolkit.java:1610)
at java.awt.Toolkit.<clinit>(Toolkit.java:1632)
at java.awt.Component.<clinit>(Component.java:568)
at CreditSystem.main(CreditSystem.java:17)

The solution I found was to issue the following command

sudo update-java-alternatives -s java-6-sun

That will update your files and fix it. Fun fun…

The first thing that I realized with this upgrade was that it was going to take a long time.  I had to download and upgrade 1800+ packages.  I started the process at about 9 in the morning.  By 12:30, all of my packages had downloaded and installed.  I was ready to reboot and give it a try!

Fixing a Kubuntu Login Screen and Gnome not being default

One major problem I always seem to run into was that, at some point in my past, I installed KDE4 to try it out and, in doing so, it took over my system.  Now anytime I get a system update I have to reinstall the official Ubuntu bootup screen and tell GDM to boot into Gnome, not KDE, for my system.  This is how to fix the bootup screen.

System -> Administration -> StartUp-Manager -> "Appearance" Tab

Change "Usplash Theme" to 'usplash-theme-ubuntu'

To fix the Gnome problem, simply select Gnome from the “Options -> Session” menu on your login page.

Make the Trackpoint work again!

Another problem I was having is that my Trackpoint would not right click or scroll with the middle button.  Seeing as that ‘clit mouse‘  that is the only thing I use, it was absolutely killing me.  After a small amount of googling, however, I found this post which gave me the solution:

Edit: /etc/hal/fdi/policy/mouse-wheel.fdi and add

<match key="info.product" string="TPPS/2 IBM TrackPoint">
 <merge key="input.x11_options.EmulateWheel" type="string">true</merge>
 <merge key="input.x11_options.EmulateWheelButton" type="string">2</merge>
 <merge key="input.x11_options.XAxisMapping" type="string">6 7</merge>
 <merge key="input.x11_options.YAxisMapping" type="string">4 5</merge>
 <merge key="input.x11_options.ZAxsisMapping" type="string">4 5</merge>
 <merge key="input.x11_options.Emulate3Buttons" type="string">true</merge>
</match>

This should let you use your Trackpoint. That’s a great thing.

Make Compiz the default Window Manager!

For whatever reason, I’ve never had compiz as the default window manager.  I wanted this so I found this solution.  Edit the file  “~/.gnomerc”   and add:

export WINDOW_MANAGER=/usr/bin/compiz

From there you can reboot and compiz should be the default Window Manager!

Fix keyboard problems

For whatever reason, upgrading borked my keyboard. Volume controls no longer worked, arrow keys turned into the PrintScreen button, etc.  This is, obviously, a pain.  The program “thinkpad-keys” works for me to fix these keys.  To add it to run every time, do the following:

System -> Preferences -> Sessions -> Add

Name: "Thinkpad Keys"

Command: "thinkpad-keys"

Add it and close.

Now your keys are fixed!

Those are all of the fixes I have right now, but I’ll post if I find them.

Just for the record, my computer is running Ubuntu Gutsy on a T61 14.1″.  The graphics card is the Intel X3100, running the default Ubuntu drivers.  The wine version used was Wine 1.1.2.

First of all, Wine has always been a really big problem for me. I never seem to get anything working properly.  In fact, up until today I had been running a year old version of Wine because any newer version somehow wouldn’t let me run the few applications I still emulated with Wine (mainly MS Office 2003).  Well, today I decided that I would bite the bullet and attempt to install WoW under wine.  Installing it, at least for me, was not unique–Copy the Installer.mpq files from each of the four discs, run the installer under Wine, and go for it.  After the initial game was installed (at version 1.0) the game ran perfectly–well, at least it booted up and went to the login screen perfectly.  After a series of what seemed like endless patches, I finally ended up at version 2.4.3, which is the current version at the time of writing this.

Now, I did something stupid: I assumed.  I assumed that since WoW had started up initially (v1.0) that it would start up after patches (v2.4.3).  After all, I looked through patch notes and there was nothing about breaking wine compatibility (I completely stole that joke from Jeff.  Proper credit is due). But, when I started the program under default settings (DirectX), it didn’t want to work anymore.  It showed my screen slightly mangled and had a cursor, but nothing would work (not even killing the X server or attempting to SSH/VNC in) to stop it.  After a few hard reboots, I attempted to open it with the command

wine Wow.exe -opengl

I assumed that since I was running in Linux and OpenGL was native, that would be a much better solution.  What did I get for my assumption?

The OpenGL version of the WoW login screen

Yes, that’s correct.  A completely messed up version of WoW’s login screen.  Maybe, though, it’s just a problem with the login screen.  Sometimes various things in menus don’t work in games under Wine and it’s just a matter of getting into the game itself.  I assumed this was one of those cases, so I went for it.  My result?

A new graphical pack for WoW that Blizzard pushed just to me!

That’s right.  An AWESOME version of the WoW interface. Great. At this point, I was getting fairly frustrated.  I’m going to cut out the hour or two of me surfing the internet for any semblence of a solution and tell you the final setup I used to get it to work.

This is my solution.  Your results may vary.

• In the ‘winecfg’ program, uncheck the box that says “Allow Pixel Shader (if supported by hardware)“.
• Add the following lines to your Config.wtf (located in ~/.wine/drive_c/Program Files/World of Warcraft/WTF/)

• SET UIFaster "2"

  SET ffxDeath "0"

  SET ffxGlow "0"

  SET gxWindow "1"

  SET SoundOutputSystem "1"

  SET SoundBufferSize "150"

• Keep the display on DirectX (wine Wow.exe -d3d) and remove any references to OpenGL in your Config.wtf file.  I could not get it to work with OpenGL, but DirectX worked.

I doubt this solution will work for everyone, but I thought I may as well put it up to keep others from the same headache I suffered through.  This is what I got in the end:

My final result after lots of hacking with Wine