Opera 32 bit
Opera 32 bit
The 32-bit version of Opera works on both LxPup and LxPupSc (the Slacko-6.3.0/Slackware 14.1 and Slackware Current flavours of LxPup). Opera-Beta was the version tested.
Direct download and install of the .deb via pkgs.org:
http://deb.opera.com/opera-beta/pool/no ... pera-beta/
Direct download and install of the .deb via pkgs.org:
http://deb.opera.com/opera-beta/pool/no ... pera-beta/
- Attachments
-
- Screenshot.png
- LxPup
- (172.88 KiB) Downloaded 4428 times
-
- Screenshot.png
- LxPupSc
- (170.57 KiB) Downloaded 4387 times
Last edited by peebee on Sat 20 Feb 2016, 19:58, edited 1 time in total.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
The opera.com website seems to suggest that this version is as up to date as any other (Windows, Android, Linux-64).....???slavvo67 wrote:The 32 Bit Opera has been unsupported for sometime, now. That could raise some security issues, no?
http://www.opera.com/blogs/desktop/2015 ... a-release/
Just offered a link for people's interest - no need to use it if you don't want to....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Thanks - there are 3 types - stable, beta and developer - depending how adventurous you are! The link about is to beta - your link is to developer.rokytnji wrote:Just info I use
http://murga-linux.com/puppy/viewtopic. ... 10990561cf
Just passing it on.
http://www.opera.com/blogs/desktop/
http://www.opera.com/blogs/desktop/streams/
I am not advocating Opera - just noting that the official downloads work OOTB on LxPup.
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Opera at version 36 - pet to create menu entry
Hi All,
As I explore many puppies, I prefer running browsers either as SFSes or from folders located on /mnt/home. As you may also know currently my default browser is slimjet. But slimjet presents a problem. Puppies may be built from Ubuntu, or Slackware or debian or, theoretically, any other distro's binaries. With slimjet, one size doesn't fit all.
Opera, on the other hand, appears to. I've used the same deployment from /mnt/home in MintPup, Tahrpup and am currently posting from pupjibaro -- built from debian jessie binaries. [Edit: Did not work under Slacko 5.7, perhaps as I started with the deb opera provides for Ubuntu/debian. Also did not work under Carolina Vanguard].
There are things I don't like about the "new" opera. The old --thru 12.16-- opera was self contained: its config and cache held within its folder, thus --when on /mnt/home-- outside one's SaveFile. New versions place those folders in /root. Consequently, like palemoon or firefox it is advisable to move them out of that location/the SaveFile and symlink them back.
And while opera uses the blink engine. opera's extensions aren't as extensive as Chromium or Slimjet. Still, it is fast and it's nice to have a browser you can use as soon as you establish an internet connection, without even having to install it so you can test and explore even before creating a SaveFile/folder.
The location of opera's executable has changed. Consequently, the pet I previously made to create a menu entry had to be modified. I've attached it for your convenience. To use it "as is" you'll only have to do the following:
(1) Download the compressed file from opera -- as I was running Tahrpup, it offered and I accepted the ".deb".
(2) Extract the file.
(3) Rename the folder created by extraction "opera32-36" -- without the quotes. [I have 64-bit Puppies, and also run 64-bit opera. And the download was of opera's version 36. Ergo, the specific name I used.]
(4) Install the pet.
Creating a menu entry makes it possible to specify opera in launchers.
mikesLr
As I explore many puppies, I prefer running browsers either as SFSes or from folders located on /mnt/home. As you may also know currently my default browser is slimjet. But slimjet presents a problem. Puppies may be built from Ubuntu, or Slackware or debian or, theoretically, any other distro's binaries. With slimjet, one size doesn't fit all.
Opera, on the other hand, appears to. I've used the same deployment from /mnt/home in MintPup, Tahrpup and am currently posting from pupjibaro -- built from debian jessie binaries. [Edit: Did not work under Slacko 5.7, perhaps as I started with the deb opera provides for Ubuntu/debian. Also did not work under Carolina Vanguard].
There are things I don't like about the "new" opera. The old --thru 12.16-- opera was self contained: its config and cache held within its folder, thus --when on /mnt/home-- outside one's SaveFile. New versions place those folders in /root. Consequently, like palemoon or firefox it is advisable to move them out of that location/the SaveFile and symlink them back.
And while opera uses the blink engine. opera's extensions aren't as extensive as Chromium or Slimjet. Still, it is fast and it's nice to have a browser you can use as soon as you establish an internet connection, without even having to install it so you can test and explore even before creating a SaveFile/folder.
The location of opera's executable has changed. Consequently, the pet I previously made to create a menu entry had to be modified. I've attached it for your convenience. To use it "as is" you'll only have to do the following:
(1) Download the compressed file from opera -- as I was running Tahrpup, it offered and I accepted the ".deb".
(2) Extract the file.
(3) Rename the folder created by extraction "opera32-36" -- without the quotes. [I have 64-bit Puppies, and also run 64-bit opera. And the download was of opera's version 36. Ergo, the specific name I used.]
(4) Install the pet.
Creating a menu entry makes it possible to specify opera in launchers.
mikesLr
- Attachments
-
- opera32_external-32.36.pet
- Pet to create menu entry for opera unpacked to /mnt/home.
- (3.03 KiB) Downloaded 699 times
Re: Opera at version 36 - pet to create menu entry
Don't know about Slimjet's extensions, but for Chromium compatibility go to the Opera Extensions download page and get "Download Chrome Extensions". After this step you'll be able to install extensions from Chrome Web Store. So far all the ones I installed have worked flawlessly.mikeslr wrote:...opera's extensions aren't as extensive as Chromium or Slimjet...
- Attachments
-
- xscreenshot00000.png
- in opera://extensions/
- (13.2 KiB) Downloaded 3859 times
[url=http://murga-linux.com/puppy/viewtopic.php?t=117546]Fatdog64-810[/url]|[url=http://goo.gl/hqZtiB]+Packages[/url]|[url=http://goo.gl/6dbEzT]Kodi[/url]|[url=http://goo.gl/JQC4Vz]gtkmenuplus[/url]
-
- Posts: 63
- Joined: Wed 14 May 2014, 20:19
opera 32 bit
got it, installed it, went to the Icon, click. Nothing.
LxPup 15.06
very sad, new Opera runs fast on my Winders machines
LxPup 15.06
very sad, new Opera runs fast on my Winders machines
Re: opera 32 bit
I haven't tested but I suspect LxPup-15.06 is too old to run the latest Opera which is based on Chromium-56.XP Refugee wrote:got it, installed it, went to the Icon, click. Nothing.
LxPup 15.06
very sad, new Opera runs fast on my Winders machines
I do know it works fine on LxPupSc-17.02.1.....but that is not an upgrade possibility from 15.06 I'm afraid.
There used to be a page on the Opera website with older versions but this seems to have disappeared....
LxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64
- OscarTalks
- Posts: 2196
- Joined: Mon 06 Feb 2012, 00:58
- Location: London, England
Forgive me, without looking it up I am not sure what LxPup 15.06 is based on, but I took a quick look at current stable Opera 43.0.2442.991 and it runs in Wheezy and Precise and Slacko 5.7 (with libgconf2 added of course) if you just do --user-data-dir=/$HOME/.config/opera --no-sandbox --disable-infobars
I also tried the bbe modification of the binary and that worked for enabling SUID sandbox although Slacko 5.7 still requires --disable-namespace-sandbox switch.
There are still the strange networking messages in terminal which look like they are failed updater connection attempts or something. This was the main reason I gave up experimenting with Opera a while ago (since other Chromium deivatives are available) but the on-board VPN does look like a nice touch I must say.
I also tried the bbe modification of the binary and that worked for enabling SUID sandbox although Slacko 5.7 still requires --disable-namespace-sandbox switch.
There are still the strange networking messages in terminal which look like they are failed updater connection attempts or something. This was the main reason I gave up experimenting with Opera a while ago (since other Chromium deivatives are available) but the on-board VPN does look like a nice touch I must say.
Oscar in England
Opera at version 36 - pet to create menu entry
Hi mikeslr,
Thanks for your post and pet.
I agree with OscarTalks. The free no registration vpn within Opera
is the simplest and best performing that I have ever seen.
It can of course only be used within Opera but gives access to anything
that would otherwise be geo-blocked.
An unlisted video of it in action (UK > Canada) follows:
https://youtu.be/b4YF8_FBx4o
.
Thanks for your post and pet.
I agree with OscarTalks. The free no registration vpn within Opera
is the simplest and best performing that I have ever seen.
It can of course only be used within Opera but gives access to anything
that would otherwise be geo-blocked.
An unlisted video of it in action (UK > Canada) follows:
https://youtu.be/b4YF8_FBx4o
.
Regards ETP
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
[url=http://tinyurl.com/pxzq8o9][img]https://s17.postimg.cc/tl19y14y7/You_Tube_signature80px.png[/img][/url]
[url=http://tinyurl.com/kennels2/]Kennels[/url]
-
- Posts: 63
- Joined: Wed 14 May 2014, 20:19
I got opera working ok in that new 17.4 sc? delta? i have NO IDEA why there are so many qualifiers needed for these things. BUT, this lxpup runs like a snail so far. Quite odd. And I can't find many of the files i got for 15.06? in the PPM. Such as mate-system monitor. I assume it comes with repositories that have stuff known to work with it
Re: Opera 46
Hi - which Tahrpup please? cheersdalderton wrote:Opera developer 46 works well on Tahrpup straight from the Opera website in deb form.I have been using Firefox but prefer this Opera version.
Regards Dennis.
FYI upupbb bionic delivered with opera 45.0 by csipesz.
FYI upupbb bionic delivered with opera 45.0 by csipesz.
Blue icon on LH : messenger
Blue icon on LH : messenger
- Attachments
-
- messenger.jpg
- messenger
- (55.29 KiB) Downloaded 422 times
Re: Opera at version 36 - pet to create menu entry
Do you have an sfs for slacko 6.3.2 ? Thanksmikeslr wrote:Hi All,
As I explore many puppies, I prefer running browsers either as SFSes or from folders located on /mnt/home. As you may also know currently my default browser is slimjet. But slimjet presents a problem. Puppies may be built from Ubuntu, or Slackware or debian or, theoretically, any other distro's binaries. With slimjet, one size doesn't fit all.
Opera, on the other hand, appears to. I've used the same deployment from /mnt/home in MintPup, Tahrpup and am currently posting from pupjibaro -- built from debian jessie binaries. [Edit: Did not work under Slacko 5.7, perhaps as I started with the deb opera provides for Ubuntu/debian. Also did not work under Carolina Vanguard].
There are things I don't like about the "new" opera. The old --thru 12.16-- opera was self contained: its config and cache held within its folder, thus --when on /mnt/home-- outside one's SaveFile. New versions place those folders in /root. Consequently, like palemoon or firefox it is advisable to move them out of that location/the SaveFile and symlink them back.
And while opera uses the blink engine. opera's extensions aren't as extensive as Chromium or Slimjet. Still, it is fast and it's nice to have a browser you can use as soon as you establish an internet connection, without even having to install it so you can test and explore even before creating a SaveFile/folder.
The location of opera's executable has changed. Consequently, the pet I previously made to create a menu entry had to be modified. I've attached it for your convenience. To use it "as is" you'll only have to do the following:
(1) Download the compressed file from opera -- as I was running Tahrpup, it offered and I accepted the ".deb".
(2) Extract the file.
(3) Rename the folder created by extraction "opera32-36" -- without the quotes. [I have 64-bit Puppies, and also run 64-bit opera. And the download was of opera's version 36. Ergo, the specific name I used.]
(4) Install the pet.
Creating a menu entry makes it possible to specify opera in launchers.
mikesLr