Tiny Core Linux

Off-Topic => Off-Topic - Tiny Tux's Corner => Topic started by: roberts on June 08, 2010, 02:29:22 AM

Title: Opera
Post by: roberts on June 08, 2010, 02:29:22 AM
What happened to Opera 10.5x for Linux?
Now I see a 10.60 alpha for Linux. Am using it now.

With the 10.5x and 10.60 no need for Gtk or Qt only fontconfig dependency.
But then along comes flash10 and all of its dependencies.

Still hoping for a smaller, faster Opera for Linux.
Title: Re: Opera
Post by: maro on June 08, 2010, 02:51:27 AM
I've been using the various alpha and beta releases of Opera 10.5x (and now 10.6x) after I posted these remarks (http://forum.tinycorelinux.net/index.php?topic=5730.msg30456#msg30456). Initially only to see whether the bugs I had lodged were cleared.

It used to crash a fair bit but since the last 2-3 weeks it has become the only browser I ever use with TC (obviously typing this message using "opera-10.60-6347.i386.linux"). So far so good, but the flash dependencies are such a drag that I only load them occasionally. That would be a dream to have a minimal dependency flash plug-in. Surely not from Adobe, the "masters of bloat".
Title: Re: Opera
Post by: curaga on June 08, 2010, 03:17:29 AM
They couldn't finish 10.5x for *nix before 10.6 for the main platforms (Win, Mac) came up.

Thus there's not going to be 10.5 for unix at all, they target the next stable after 10.10 for 10.60.
Title: Re: Opera
Post by: curaga on June 08, 2010, 03:21:15 AM
Any of the replacements aren't that light on deps either; gnash is near identical to Adobe's, and the new lightspark one needs llvm and opengl.
Title: Re: Opera
Post by: curaga on July 05, 2010, 05:42:11 AM
So, 10.60 final is out. Though, based on my and other's experiences it still isn't as stable or usable as 9.64 or 10.10. Thus I recommend not to overwrite the opera10 extension with it, if it gets packaged.
Title: Re: Opera
Post by: roberts on July 05, 2010, 12:45:48 PM
I was so hoping and looking forward to a fast stable Opera. Seems stability has given way to the race to be the fastest. But what good is being the fastest if not stable.
Title: Re: Opera
Post by: maro on July 05, 2010, 06:42:05 PM
Robert, I think you should just give it a try. I started using an early alpha release of 10.5x and that was pretty bad. After lodging a few bug reports I was pleasantly surprised that "my bugs" got resolved pretty quickly. I then used the various 10.5x and 10.60 beta releases as my default browser and things just got more and more stable. I would not state that it was the most stable browser ever, but I had way more crashes using a FF v3.5x than with these Opera beta releases. It was certainly quite usable.

Unfortunately my main laptop is currently undergoing a warranty repair so I'm on a "diet" using TC 2.x on a 10 year old Dell notebook (500MHz Pentium III, 256MB). This is very limiting compared to my default system. I therefore restrict myself to Opera 9.64, and have not yet used the final 10.60 version. But I'm rather confident that it would become my default browser. It only needs the 'fontconfig.tcz' extension, which is not too bad compared to Opera 10.10.

Whilst I'm typically strongly against having multiple versions of the same application in the repository I wonder whether we should (at least for a while) allow both the current Opera 10.10 and the new Opera 10.60. To be honest I'd say that the "heavy" dependencies of the old version alone would be a reason to remove it and replace it with the new one (as long as we keep the Opera 9.64 extension around).

So maybe if a few more Core members would give the latest one a trial we might be able to settle this question rather sooner than later.
Title: Re: Opera
Post by: roberts on July 06, 2010, 08:48:09 AM
Tried 10.60 and still experience not being able to enter text into some text input areas. This is same that I was experiencing with the beta. I am not able to use 10.60. 10.10 is way to bloated for my likes. 9.62 is way too old. So on to another browser for now.
Title: Re: Opera
Post by: Juanito on July 06, 2010, 08:59:13 AM
9.64 is way too old...

..but works fine for me  :)
Title: Re: Opera
Post by: roberts on July 06, 2010, 09:15:45 AM
I like to watch technical broadcasts from Google and others typically done in flash. 9.62 most often than not does not allow full screen. Pressing the full screen widget often is ignored. I am often asked about such my friends. If one does not use or need flash then basic browsing is OK.
Title: Re: Opera
Post by: curaga on July 06, 2010, 10:30:45 AM
9.64 is still my primary browser as well. I hope they can get a quality release out soon.
Title: Possible workaround for flash fullscreen
Post by: tinypoodle on September 05, 2010, 11:52:11 AM
Found following workaround for non working fullscreen feature on youtube:

1. On a youtube video click the "Pop out" button.
2. With the popout window being given focus, switch opera to fullscreen mode, e.g. with Alt+V->U.

This works for me with following setup:
TC 2.10, jwm-snapshot, opera-9.64.gcc4-static-qt3.i386, latest version 9 libflashplayer.so

With flashplayer 10 straight fullscreen per se works fine on some sites (incl. youtube), messes up with some others; trying flashplayer 7 patched to version 10 did not work for me at all.

Title: Re: Opera
Post by: curaga on December 16, 2010, 11:19:54 AM
So, Opera 11 is out. Based on my quick testing it's not as buggy as 10.x (x>=5), but it's still ugly as sin on the x11 backend, and the gtk backend handles a dark theme as gracefully as a pig in a porcelain shop.

No Opera 11 for me just yet...
Title: Re: Opera
Post by: SamK on December 16, 2010, 01:58:27 PM
So, Opera 11 is out. Based on my quick testing it's not as buggy as 10.x (x>=5), but it's still ugly as sin on the x11 backend, and the gtk backend handles a dark theme as gracefully as a pig in a porcelain shop.

No Opera 11 for me just yet...
I have two partitions, one is TC3.1, the other TC3.3.  They both run the same version of Opera (10.63) but both look totally different.  On the TC3.1 partition it is quite dark in presentation, fonts are very plain and relatively small, with menus that look very block like. 

On the 3.3 partition it is very different, looking much more modern and polished, almost like a different browser.

As the 3.1 browser is used infrequently, I have never got around to investigating what makes the contrast between them so marked.  Neither are running xorg.  Interestingly both seem quite stable.
   
Title: Re: Opera
Post by: curaga on December 16, 2010, 02:13:37 PM
If you haven't added/changed any themes yourself, the other install has gtk+ and the other doesn't; or one has gtk+, and the other has gtk+ and a theme (gtk-engines).
Title: Re: Opera
Post by: tinypoodle on December 16, 2010, 04:55:37 PM
or qt (appears to rely on a few kdelibs though)
Title: Re: Opera
Post by: curaga on December 17, 2010, 04:07:42 AM
The Qt backend is AFAIK disabled, and yes the KDE backend requires a lot of KDE.
Title: Re: Opera
Post by: tinypoodle on December 17, 2010, 06:04:00 AM
Code: [Select]
ldd liboperakde4.so |grep not
       
libkdecore.so.5 => not found
libkdeui.so.5 => not found
libkio.so.5 => not found
Title: Re: Opera
Post by: SamK on December 30, 2010, 02:36:13 AM
While doing something totally unrelated to this discussion, pure chance narrowed down the cause of the difference mentioned in reply#14.

Both partitions routinely load gtk2.tcz.  In the TC3.3 partition only, xfce4-notifyd.tcz is loaded, which includes includes gtk2.tcz as a dependency.  If xfce4-notifyd.tcz is not loaded, Opera is displayed in the less attractive mode described previously.   

It appears that the 'polished' look of Opera is caused by one or more of the dependencies of xfce4-notifyd.tcz minus gtk2.tcz.

Title: Re: Opera
Post by: curaga on December 30, 2010, 04:42:52 AM
Hm, gtk-engines is not in the dep tree. Perhaps one of the Xfce deps includes their own theme & engine.
Title: Re: Opera
Post by: tinypoodle on December 30, 2010, 11:08:27 AM
...or one of them might simply write to .gtkrc-2.0 or to an 'include' file of latter.

Comparing gtkrc-2.0 or resp. 'include' file before and after loading xfce4-notifyd.tcz as well as between the partitions would tell.
Title: Re: Opera
Post by: SamK on December 31, 2010, 05:37:39 AM
Not that I am going to pursue this with any degree of priority or urgency, however, as I had a fresh build to do of TC3.3 I was able to get a little more information.

Before any gtk2 elements had been added to the fresh build, the block like menus in Opera were present.  Adding xfce4-notifyd.tcz, and thereby gtk2 as a dependency, presented the more 'polished' appearance.  A copy of gtkrc-2.0 had not been generated at this point, or after a reboot.
   
Title: Re: Opera
Post by: Arslan S. on December 31, 2010, 06:14:32 AM
try loading only shared-mime-info and hicolor-icon-theme
then execute :
Code: [Select]
sudo gtk-update-icon-cache -q -f -t /usr/local/share/icons/hicolorthis is already done when you load xfce4-notifyd, see its tce.installed script

if still no result try loading libxcb, and libxcb-util too
Title: Re: Opera
Post by: tinypoodle on December 31, 2010, 10:57:13 PM
You could try to use opera:config#FileSelector|DialogToolkit and set value to 2 for gtk
Title: Re: Opera
Post by: tinypoodle on January 04, 2011, 06:38:18 PM
SamK, you could use

Code: [Select]
opera --full-version
at any given moment to see enabled capabilities.
Title: Re: Opera
Post by: SamK on January 07, 2011, 06:29:46 AM
try loading only shared-mime-info and hicolor-icon-theme
then execute :
Code: [Select]
sudo gtk-update-icon-cache -q -f -t /usr/local/share/icons/hicolorthis is already done when you load xfce4-notifyd, see its tce.installed script
Good call, this produces the more 'polished' look to the menu etc.
 
Title: Re: Opera
Post by: mpayne on June 30, 2011, 08:50:45 PM
I have been using Opera for quite a while now though recently, I have been experiencing problems with my browser. I have set the preferences to block all unwanted pop ups and for some reason, a web site I have been able to access before, I cant go to anymore.  When I click on the button, the page just refreshes and do not lead me to the main page. Any ideas on why this is happening?