Monday, July 5, 2010 3:00:00 PM
[Edit: Japanese users might want to read a translation of this posting
With the final release of 10.60 for Linux/FreeBSD large parts of our code has been rewritten. In addition to major changes as a result of the Libvega and Carakan work coming from our core layout team, the UNIX desktop team has had to rewrite many key parts of our basic functionality: fonts, printing, IME support, drag and drop, etc. The majority of this was done as part of our moving away from being a Qt based application.
Like all new software (and due to the rewrite large parts of Opera for *nix is new), some of these features are not without bugs. Currently I am looking at some the input (typing) problems that some of our users are encountering. Most of these are related to the new IME implementation, though there are also some problems with certain keyboard layouts.
Whilst we greatly appreciate all the feedback we received thus far, some of it is unfortunately lacking the detail we need to understand the problem or replicate it locally. Hence I thought it might be a good time to write a blog post that specifies exactly the information we need. With good clear bug reports we are able to fix outstanding issues faster. This benefits both Opera and you, our users.
Saturday, June 19, 2010 4:45:54 AM
Shortly after my last blog post
I realised that I couldn't get the IcedTea plugin working on my 64bit Ubuntu 10.04 installation. Then a little latter enzolatina commented that he couldn't get it working either
on 64bit Arch. After I made sure a bug was logged, I replied to him and confirmed that I could see what he meant.
Two things bothered and confused me though. Whilst we admittedly had focussed our attention on getting the Sun/Oracle Java plugin working first and foremost (since they are the primary Java authors and hence provide the point of reference), I was fairly sure we had done some
testing with OpenJDK/IcedTea. In fact I even had the vaguest recollection of having tested it myself!
Odder still the failure I received on 64bit Ubuntu was not the same as the error that enzolatina received! On my system the plugin wasn't even detected by Opera
so it couldn't even get to the stage of crashing.
Having now investigated this a little further I realise things are a lot more messy than they initially appeared. In fact I would now go so far as to suggest (Ubuntu) users drop IcedTea as their Java browser plugin of choice (for now at least) and I am beginning to wonder if we should put the effort in to get it working before Opera *nix hits its first Evenes final! This is despite the fact that IcedTea is the default Java plugin on Ubuntu 10.04 and the Oracle/Sun Plugin is only available after a user manually adds the partner repository or downloads directly from the Java website. Hence many new Ubuntu users would never even think to install anything other than IcedTea.
Friday, June 18, 2010 6:48:43 AM
Some users of the *nix 10.5x
+ Snapshots and Betas have mentioned having problems with Java after our recent switch to using the Java browser plugin rather than interfacing more directly with the JRE. Often this is because they did not have the browser plugin package installed and hence no browser on their system (except for older versions Opera) would work with Java. To remedy this a user needs to install one of the Java browser plugin packages.
Saturday, March 20, 2010 3:13:37 AM
Edit: If you are looking for a package read this
This blog post is primarily aimed at our intermediate to advanced UNIX users. If you are new to UNIX you may find this to be too much detail. However, if you are interested in packaging or just want to know a little bit more about what we changed behind the scenes read on! If you are a user of the install script bundled in the tarball packages, you should certainly read on as the changes are potentially biggest for you.
Wednesday, February 24, 2010 3:24:13 PM
With Windows on to its second Beta
and Mac getting ever closer to its first Beta
I'm sure that there are people out there wondering what is happening with UNIX. Users may also have noticed that myself and other UNIX employees have posted fewer comments of late on the relevant usenet groups, mailing lists, IRC channels and My Opera forums.
I wanted to give my readers (or anyone who stumbles across this) a quick heads up on the state on 10.50 for UNIX. I'll have to keep it very brief but hopefully this posting will give you a clearer understanding of how things are progressing.
Friday, January 22, 2010 8:20:09 AM
For video to work in 10.50 (Evenes) on Linux/UNIX, you need the the GStreamer Multimedia Framework, the Base Plugins package and the main Good libraries. This ensures that the following are available on your system: libgstautodetect.so, libgstogg.so, libgsttheora.so, libgstvorbis.so, libgstwavparse.so.
On some distros there is one GStreamer Good package that contains everything and on others this is split into two packages, GStreamer Good (the main libraries) and GStreamer Good Plugins (the plugin libraries).
If you don't have these installed and are unsure exactly which packages will provide these libraries for your distro, you can use your distro's favoured method of searching for packages. Typically this will be search options within your package manager, but it may also be a dedicated wesbite. Generally you can install the GStreamer Good Plugins package and your package manager's dependency resolution will ensure you get any further packages you need. If you have a distro that splits "Good", you can be more selective and just install the main Good libraries, leaving out the Good plugins.
Thursday, January 21, 2010 9:07:48 AM
You can't, or at least not yet [Edit: Ok now you can. Head over to this more recent post on Opera packages for Linux and FreeBSD
]. In the New Year's blog post
we said, "Because this is a pre-alpha release, we don't recommend you to install it over your existing Opera installation. This is why we are releasing only non-installable tarballs instead of installable packages.". Whilst this is
true it is actually only part
of the story.
Tuesday, December 22, 2009 8:59:36 AM
Edit: A public version of Opera 11.00 Linux is now available. If you are looking for an install package, read this
Edit: Whilst, looking through the logs for this blog post I noticed that many of the forums linking to it comment that we are moving to GTK. This is not the case
. To save you having to read through all the comments below, here is one of the key ones from one of our developers:
Originally posted by AVL:
Opera is not built with GTK, not now and not in the future. It uses its own toolkit (Quick). In Peregrine on Linux, that toolkit draws using Qt (but doesn't use it for a lot of other things); In Evenes, it only uses X11 drawing primitives.
However, if it's available, Evenes will load GTK and paint widget elements with it. Of course that doesn't make it a GTK application, and it still has to live within the rules of our toolkit. This is similar to how for example Firefox, OpenOffice and the Qt GTK skin engine work. Similarly, on Mac and Windows, we use their native toolkits to paint quick's widget elements.
Also to highlight one other key point, we are also working on KDE integration but we don't yet have a public build nor screen shots that we are happy to share yet. However, the idea is that if you run under KDE, the KDE native look will load, if you run it under other environments and the GTK libraries are available they will load and if neither GTK or Qt/KDE libraries are available Opera will still run using only its own toolkit. Hence there is no dependency on either GTK or Qt/KDE.Original Blog post:
Yes, Opera 10.50 does exist (internally) but it needs a bit more work before we can release something for our users as stripping out Qt is not an easy thing.
However, it will bring some real benefits. Whilst you wait here are three screenshots.