Tuesday, December 11, 2007
Saturday, December 1, 2007
I had run into an issue getting Java Runtime Environment to run on openSUSE 10.3, using Firefox 22.214.171.124. I have arrived at a solution and wanted to share what I had encountered and done.
I wanted to use an applet at school from Blackboard. In order to use it, I needed to download and enable JRE. When attempting to load the applet on Blackboard, Firefox let me know that a plugin was missing. I clicked on a button to install the missing plugin, but an automatic installation was not available. I was directed to Sun Website to obtain the latest JRE, which was 1.6.0_03 (release 6 update 3). I downloaded the file jre-6u3-linux.i586-rpm.bin and extracted it in the recommended location /usr/java using root priviledges. The autoextracting rpm file installed without errors. Following the directions I made a symbolic link to the plugin, which came with the JRE package. I placed the link in /usr/lib/firefox/plugins - where I also found a null plugin lubnullplugin.so. I linked the recommended Mozilla 1.4 or higher plugin by executing ln -s /usr/java/jre1.6.0_03/plugin/i386/ns7/libjavaplugin_oji.so
I launched reloaded Firefox, but the applet at school did not load. I went to Sun Website <http://www.java.com/en/download/installed.jsp> to verify the installation. The verification took over a minute and failed. So I thought maybe I could use a different location for the plugin link. I tried /usr/lib/browser-plugins and /home/voitek/.mozilla/plugins location without much luck. I looked at the Firefox plugin registration file pluginreg.dat in the Firefox directory in my home folder at the following location: /home/voitek/.mozilla/firefox/. I saw that the plugin was registered, and it looked something like this:
Java(TM) Plug-in 1.6.0_03:$
Java(TM) Plug-in 1.6.0_03-b05:$
I made certain that Java was enabled in Firefox by going to Edit menu > Preferences > Content tab. I had disabled it and tried verifying the installation using the Sun website. The Webpage informed me that I should enable Java and cookies before trying to verify it. At least I knew the OFF switch on that Content tab was working properly. I re-enabled the Java option by checking the checkbox and verified the installation again using the Sun Website. Verification failed again.
I hit the Web in search for answers and came up empty many times. I just could not think of a set of keywords that would get me some information. It had seemed as if I were the only one with this issue. Then finally I got lucky and found a reference on a Mandriva discussion forum somewhere. Someone had a similar issue. In one of the replies to the original post someone suggested that he download the Java package using the Mandriva package manager. I decided to give that a try on my openSUSE 10.3 using YaST. I found JRE 1.6-sun and -plugin packages. So I dumped the /usr/java directory and installed Java from the package manager.
Installation proceeded without issues. My new Java Runtime Environment package installed to /usr/lib/jvm/java-1.6.0.u3.sr2-sun-1.6.0.u3 along with the other Java packages. I had at least two, but neither one had the plugin I needed for Firefox. When selecting the Java download from YaST I also selected the plugin package. This installed the libjavaplugin_oji.so plugin to /usr/lib/jvm/java-1.6.0.u3.sr2-sun-1.6.0.u3/jre/plugin/i386/ns7 directory. I linked the .so library file to my home directory ~/.mozilla/plugins, launched Firefox, and voilla - everything worked fine.
This is the second time openSUSE community taught me a lesson on using the package manager. I had once tried installing the .docx converter for openoffice, and even though the installation files and instructions came from a Novell Website, the converter did not work. I never got this feature to work manually. Then finally I used the openSUSE updater, and it found an openoffice update with this .docx format converter, installed it automatically, and openoffice was able to read and write .docx Microsoft Word format going forward.
Monday, November 12, 2007
Then it dawned on me. When I was installing 10.2, the setup was asking whether I wanted to create a separate /home partition. I am the kind of guy who does not like to create many partitions, whether C: D: E: on Windows or elsewhere. I thought creating /home on a separate partition was dumb, but I went along with what openSUSE 10.2 suggested, which was to create /home on a separate partition. Staring at the 10.3 install screen it occurred to me why in the hell anyone would create a separate /home partition. It is precisely for situations like the one I was just sitting in. I could format my root partition and keep all my files and settings on my separate /home partition.
Interestingly, openSUSE 10.3 auto partition config wanted to format my /home partition and not format anything else. I had to choose manual setup and told the system to format only the root and leave the other two (swap and home) untouched. I had actually initially specified not to format anything, but openSUSE complained that it might not work; that is, installing a new OS onto an already existing partition OS might not work. I thought about this for a minute and agreed that would be pretty messed up. So I chose to format the root and leave the other partitions as they were.
During setup, my session switched to a tty terminal twice. I thought if I didn't know how to return to the graphical interface, I'd be screwed (ctrl+alt+F1, F2... F7... etc.). The setup progressed fairly quickly without any other issues. The system rebooted properly and noticeably faster. However, I did not get a GUI. Instead, YaST started in text mode. There, I was presented with some choices of repositories and downloaded several packages. When the process completed, I was kicked out into a terminal session with no GUI.
Well, I was there before (after 10.2 installation), so I learned how to recover from it. Interestingly though, the liveCD correctly identified my video cards and started X on the right one without any issues. I wonder why this couldn't be repeated on my newly installed system.
I started Sax2. It did not start. I punched in sax2 -p to see which chip was which, and my NVIDIA card was 0. Thus, I restarted sax2 with the option -c0. It took off that time. I was presented with a default 1600x1200 resolution and saved settings to xorg.conf or whatever the configuration file was.
Back at the terminal, I typed rcxdm to start the X server session. It came up with no issues, and even some of the apps I had open during my last 10.2 session opened up when I logged in. When OpenOffice opened itself, it complained that user (me) from another machine was accessing the file. The other machine was, of course, the removed 10.2 system. I just thought it was cool how it remembered the file was being accessed, even thought the machine no longer existed.
Pretty much right after the installation I opened YaST. I heard it was supposed to be faster, and it was. It seemed "lighter." I searched for several apps I had installed on 10.2, and YaST found them faster than it would on 10.2. I installed those and went for a reboot to see if everything would completely and properly start up. The machine booted up again, noticeably faster, and this time it went all the way into the KDE session. Sweet!
I already mentioned some of the improvements of 10.3 over 10.2 in my previous post. What I didn't mention was the mutli-column display in Konqueror. It works much nicer in that the entire filename is displayed. The thumbnails also load faster.
All in all, the upgrade from openSUSE 10.2 to openSUSE 10.3 was by far the simplest, fastest, most pleasant and satisfying upgrade I've ever done on any Linux distro, still despite few small issues encountered. I was up and running in under an hour, which was absolutely fantastic.
Sunday, November 11, 2007
I am really excited about the Shift Switcher plugin for Compiz-Fusion. It is more fun to use than the cube, and much more practical too. I also just discovered a ring switcher plugin (not pictured in this post). The ring switcher basically places all windows from the front cube face against the desktop image and arranges them in a ring. Super+TAB rotates the ring--kick ass.
Compiz Fusion screen shots on openSUSE 10.3
I also wanted to mention why I upgraded from 10.2 to 10.3. It's been almost a year since 10.2 release, so naturally when 10.3 was released I hit the Web in search of reasons to upgrade. All of the reviews I found gave no good reason to upgrade. If it ain't broke, don't fix it type of mentality. I just couldn't believe there wasn't a single good reason to upgrade, so I downloaded the liveCD and booted it to see for myself.
After 30 seconds of using openSUSE 10.3, my mind was made up to upgrade as soon as possible. Immediately, several of the annoyances of 10.2 that I tried so hard to ignore and work around were addressed. There were numerous small improvements that caught my eye and took to my liking immediately:
1. Mouse pointer--it just looks awesome. It's the same pointer style used in Ubuntu and probably many other new distributions. What I disliked most about the pointer in 10.2 was the hand. It was just fugly. In 10.3, the hourglass, the hand, arrow and the rest are very nice looking.
2. Open office sheet view is c e n t e r e d when the application is maximized. In 10.2 it was hugging the left side of the window, which was absolutely annoying.
3. I thought I saw smaller system tray icons during my boot session. I am always up for higher information density on the screen; however, after I upgraded I didn't notice the icons getting any smaller. Oh well.
4. Boot time is noticeably faster.
5. There are many improvements to YaST. Holly cow, it is so much faster. I would say on average, on my machine, the entire process takes about a fourth of the time it took on 10.2.
6. One click install. Not only is it there, it actually works! I installed several apps and plugins using this feature, including my NVIDIA video drivers.