Monday, March 3, 2008

AnOpera with OpenSuse

The straight "click on rpm and sit back" routine did not solve the Opera installation problem. The solution, or what passes for it, involved a circuitous route.

After extracting the gz file, which by the way has the most amazingly complicated filename which is the result of "opera" appended with a verion number and probably a creation data and some letters more thrown in with a few hyphens and periods, one is left with a folder containing among other things an install.sh and an opera.sh executable file.

Getting a terminal requires navigating through the start up menu. After fiddleing with the file manager for a while, I discovered the Show terminal here option, which made it easier to open a terminal in that location without having to cd all the way to it from the default user path.

Once here, running the install script generated a message that the command is incomplete. Running the opera command was more promising. At first it created an error that there was no language specified. The english language file was present under the Locale folder. After adding this path along with the opera command, a few errors later, the Opera window popped up.

Relief was short lived though. A badly miscoloured window containing a few words first showed up. To view the words I had to select the text. The message seemed that some shortcut keys in Opera would be disabled since they were also shared by KDE, the windows manager being used. The miscolouration continue through out with all menus and other control items being indistinguishable. I could type out an address in the address bar and access a few sites, though. Further tweaking needed. Or is KDE to blame?

No comments: