Opera 11.11 pet +portable +WebM +locales +flash-adblock

[Michalis]

Allô Eyes-Only et merci beaucoup

I also hope to see opera's code open someday. They were discussing it but haven't heard any news about. If we overlook this by my opinion is the fastest browser yet rich in features around.

About flash is my worst nightmare while browsing I can't stand at all this useless bloat all around the net this days. Flashblock is always the first I install after the browser. I just hope someday to have a good non bloat open source alternative, till now the alternative isn't so useful.

About the pets I make, are also the ones I like to use most and if by just giving them also to our community is a very nice side-effect.


Thank you again for your kind words

[sheldonisaac]

Opera updated to version 10.01

Michalis, thanks a lot.

Can you or someone help me to make this Opera usable from the Internet group of the main Puppy menu?

At present, I have to use the Rox filer to navigate to the opera script in the directory where I extracted the
Opera-10.01-portable-customized.tar.gz

Thank you again,


Sheldon Isaac

[Michalis]

Done Sheldon Isaac, check the first post.

The only thing you have to do before you install the pet is to symlink the opera executable to /usr/bin/ in every puppy, or other distro you are using it.

[Michalis]

Opera updated to version 10.10

[JMX]

The portable version is great, even when it is on a FAT32 partition.

I must click directly on the portable "opera" file to make it run, and I have to use the middle mouse button if Rox is set to a different function for the left-click button.

I cannot get symlinks to work as expected in Puppy 4.3.1, even when running from an ext2 partition, but ttuuxxx's updated 431 Puppies version handles absolute-path symlinks just fine. I must designate absolute paths to avoid conflicting with another Opera already installed.

It works without surprises in NOP and Boxpup.

Portable Opera1010 even works with the updated Puppy 214x when I add "/lib/firefox/plugins" to Opera's pluginpath.ini file for full flashplayer support.

Nice...

[aarf]

this portable opera is what is deinitely needed. thank you.
can confirm that "Opera version 10.10 portable and customized 33Mb extracted" will run from sdcard and externally as in "not in the pupsave", in multiple puppies but haven't succeeded in running it from a desktop link, or from the menu even after trying both relative and absolute symlnks to /usr/bin/ and installing Opera-portable-menu.pet, this testing is for upup425.
also can't configure it to open .mht files when clicked on, drag and drop into opera works for .mht files though.

[werwinn]

It works well on my 1000ha from Pupeee on a removable usb stick, however as with the two recent posts I must open ROX filer and click on the executable.

I wonder if the symlinks are sticking - Does anyone know how to troubleshoot.

To all thanks again, and a happy New Year!

werwinn

[Michalis]

First of all Happy New Year.

Thank you for the feedback. I'll check the problem with the symlinks later today and will report back. It's a bit strange though that doesn't work since Opera-portable-menu.pet has only a menu entry file pointing to /usr/bin/Opera and I'm wondering whether there is maybe a problem with refresh menus.

Anyway tonight I'll check it again on puppy 432. Werwinn unfortunately I don't have eeepc to check Pupeee except if it can also work in a normal pc, does it? Aarf can you also point me where can I download upup425 because I find many different upups in the forum (a bit confusing) yet not 425. You can both pm me for the answers.

I'll also fix the mht files problem. It's normal for the time not working with opera portable since I haven't configure it to change the default player handling them.

[aarf]

you may also be interested in opera portable in dpup484 problems with flashplayer at
http://www.murga-linux.com/puppy/viewto ... 656#377656

[aarf]

sorry it is upup452 not upup425

http://www.murga-linux.com/puppy/viewto ... 02&t=49665
http://www.diddywahdiddy.net/Puppy400/upup-452.iso

[aarf]

clicking the symlink in /usr/bin/opera doesnt open opera either.

just to be sure which opera must be symlinked

/mnt/home/opera10.10/Opera-10.10-portable-customized/opera

or

/mnt/home/opera10.10/Opera-10.10-portable-customized/usr/lib/opera/opera

i believe i have tried both.

[Michalis]

Ok back home time to start the job.

First of all the one that has to be symlinked is:
/.../Opera-10.10-portable-customized/opera

I'm using opera now (Opera-10.10-portable-customized) in dpup running live from the cd. Because on opera the default place to look for firefox plugins is: /usr/lib/mozilla/plugins, I had to add also the path used in dpup: /lib/firefox/plugins in order for the plugins to work. Afterwards I run omelette.swf (/usr/share/examples/vector-images/omelette.swf) and didn't had any crash, I also opened the default adobe flash page as also couple youtube videos and didn't had any problem. Add the /lib/firefox/plugins path and remove the other and check whether it's working ok. Next opera releases will have also /lib/firefox/plugins path (even that it would be better all the mozilla based browsers had a common plugin path in every puplet-woof version).

For the following console errors don't bother is normal:
ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored.

The next line is also normal, is a small hack I put in, in order to work in the normal puppy:
ln: creating symbolic link `/usr/lib/libaudio.so.2': File exists


Ok I found where the problem with the menu is. The problem has nothing to do with the Opera-portable-menu.pet. Unfortunately the problem is with the symlinked wrapper and the libraries paths and is the same that affects every puplet-wooflet. For the time being I'm trying to hack the code but I'm not succeeding Anyhow it will take some time since I have to do some homework in bash programming and especially some functions. I don't guarantee that I'll manage to solve it

[abushcrafter]

For the following console errors don't bother is normal:
ERROR: ld.so: object 'libjvm.so' from LD_PRELOAD cannot be preloaded: ignored.
ERROR: ld.so: object 'libawt.so' from LD_PRELOAD cannot be preloaded: ignored.

In prefs set the path to java.

[aarf]

Ok now no crashing after adding new path, unticking the old path, then rescanning the plugins.
After the omelette test went back and reticked the mozilla path so i can use opera in other puppies. Did the omelette test again. Still no crash so opera looks fixed. The symlink issue may be something that needs looking into in dpup or in puppy itself.

[Dingo]

Opera 10.10 static packages mirrored on dokupuppy (no wait time for download) coming soon I'll add other mirrors

http://puppylover.netsons.org/dokupuppy ... ms:browser

[rokytnji]

Ok I found where the problem with the menu is. The problem has nothing to do with the Opera-portable-menu.pet.

I think you are right. Because I downloaded your tar.gz instead of the pet. I extracted it to /opt.

The opera shellscript in the file in /opt/Opera-10.10-portable-customized/opera opens Opera 10.1 just fine from rox. When I drag opera to desktop and set icon , it will fail to open.

Renamed it opera2 (because I have another opera in /usr/bin that works which is Opera 10) and tried making a launcher from there but no go either. Gonna rename opera2 back to opera in /opt. Deleted the experiment opera2 in /usr/bin since that didn't work.

Haven't messed with the adblock pet yet. Figured I would figure out how come it won't launch from /opt via Desktop Icon first. Like I said. Clicking on it in /opt launches just fine. Happy trails, Rok

Edit: just for info I clicked on my opera2 renamed file in /opt and opera opened up just fine. So renaming it opera2 didn't change anything as far as how it acts.

[aarf]

If you symlink opera to /opera and also symlink the other folders and then click the opera symlink it will start opera. But wont link on the desktop.
So i think if you make the extractable so that it is /usr/bin/opera and configure the paths accordingly it may then symlink to the desktop as did the previous portable opera that you helped me configure.

[ttuuxxx]

I tossed it in Fire Hydrant Retro Lite, First I changed the layout so it somewhat works like most browsers do, gui on top of the tabs
http://www.murga-linux.com/puppy/viewtopic.php?t=31049
ttuuxxx

[rokytnji]

Just some more feedback for you. Portable Opera 10 Customized tar.gz. /opt/Opera-10.10-portable-customized/opera. Puppy 4.31 full.

Flashblock works without any config from me.
Flash works fine with sound and everything.
Picked up my Java 6ui7 ok
Faster than Opera 10 Pet I have installed in /usr/bin

Still working on Launcher from Desktop Icon.

[Michalis]

Some info about the problem

The problem is in the wrapper which gives the position of the libraries and executables. The problem is that depending from where someone calls the wrapper gives different pathways. In most cases gives the relative path but not always also.

To make it more clear let's say that the portable package is extracted at /mnt/sad7/ then the wrapper will be:
/mnt/sda7/Opera-10.10-portable-customized/opera
If you click over the wrapper it works fine because gives the correct relative paths for everything in the opera. For example will tell that opera executable is located at:
Opera-10.10-portable-customized/opera/usr/lib/opera/opera
and so on with all the executables and libraries.

Now in case anybody will call the wrapper from any other position, like symlink it or from the terminal it fails to give the correct path. For example when symlinked to /usr/bin/ it believes that the opera executable is located at:
/usr/bin/usr/lib/opera/opera or /usr/lib/opera/opera
which of course doesn't exist and thous it fails. The same is happening for every library, exe.

I believe that the problem can be fixed by changing the wrapper and make it always to give the relative path according to the position where it's located. Actually I can't be 100% sure that is going to work since opera is closed search and because of that I can't know if there any other internal calls that are looking for some libraries in paths other than the wrapper has pointed to. Also my programming skills are very primitive and bash is a lot different from pascal and C++ that was using in the university, many times I don't understand it. Nevertheless is interesting trying to learn something new and look what it will come out.

If anyone has programming skills in bash is invited to try to solve the problem. A possible useful command is #realpath that gives back the real absolute path of the wrapper where over it must be placed the relative paths. Of course if there are any other suggestions on how to overcome it please post them.

@abushcrafter
I know it's about java but even with java installed and running I get those errors. So I don't search more, don't bother with them

@aarf
Good to see that the plugins problem is solved
About symlinking the folders that must work (haven't tried it) but that means that someone must do it manually for all the folders in every puppy. That's why I'm trying to do it through the wrapper

@rokytnji
About launching opera from the desktop I believe now you understand why can't work yet.
The customized opera has adblock and flashblock installed and configured, enjoy it

@ttuuxxx
Download and ready for inspection
I didn't understand what you changed in the layout but I'll find out.


One way to make a bit easier the launch of the opera in the portable form is to symlink the folder e.x:/mnt/sda7/Opera-10.10-portable-customized/ to the desktop. That way you open the folder and by clicking at opera it launch. Not perfect solution but a 2 click solution.