Is still a development snapshot release and I uploaded it for testing reasons.
===========================================================================
aarf I tested opera 10.50 and 10.51 running from 431 live cd and got the same error in console. Probably I hadn't checked it from the console
But both of them opened and worked perfectly without any crash for as long as I used them.
I'm a bit confused now, does it crash to you all the time?
Because it is an X error, do you use xorg or xvesa? I'm using xorg.
I need some info about the settings you are using in X, even the color depth, resolution etc.
Actually I'm not sure the "Atom parameter" where it is referring to. The big problem with opera is that it's closed source and can't really see what's going on in it. I'm afraid that maybe I'll have to fill a bug report at the opera's developers for it.
Anyway test the latest one package and report back.
True isn't exactly static, it's just the closest term I can think of to describe it.technosaurus wrote:I don't think that it is a "static" build - just that they have switched to gtk2 support so that now you do not need to download qt. A static linked opera would require that the rest of opera be compatible with the licenses involved ... run ldd to verify, but I am pretty sure that is the case.
The new opera isn't only drop of the qt libraries and a switch to gtk2 but they developed from ground up a new graphical toolkit that can make opera either gtk or kde integrated, according to what's in the system. Also of course there is a new javascript engine, support of html5 and couple more new features.
Only problem is that opera is using a different html5 container (theora) than youtube and google chrome (x264) due to licenses reasons and I'm not sure what's gonna come out of that.