[SOLVED] This computer will stop receiving Google Chrome updates because this Linux system will no longer be supported.
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Your explanation is appreciated but if it's also an excuse, then it doesn't fly with me. And just because Google can't be bothered to write one sentence what something is, doesn't mean you should do the same.
You provide download links on that page.
It's simply an unnecessary omission (and in my opinion rather unprofessional) to not have even just one sentence explaining what that site is all about.
The link from here took me to vivaldi.net not vivaldi.com and I find a site with download links, and lots of Vivaldi this and Vivaldi that, and yet don't have a freaking clue what it's all about.
I don't think you can build pepperflash. I'm pretty sure it is extracted from Chrome, and is not included in the Chromium source. This looks like the end of newer flash versions on 32bit Linux.
Only if you use chrome or browsers based on chromium. Firefox (and other browsers supporting NPAPI plugins) is still able to use pipelight, which provides an up-to-date flash plugin on 32 bit. Alien BOB provides packages, though they lag a little behind. It's easy to change the version and build an up-to-date package, though. Those interested may want to grab the SlackBuild and start building:
Your explanation is appreciated but if it's also an excuse, then it doesn't fly with me. And just because Google can't be bothered to write one sentence what something is, doesn't mean you should do the same.
You provide download links on that page.
It's simply an unnecessary omission (and in my opinion rather unprofessional) to not have even just one sentence explaining what that site is all about.
The link from here took me to vivaldi.net not vivaldi.com and I find a site with download links, and lots of Vivaldi this and Vivaldi that, and yet don't have a freaking clue what it's all about.
From vivaldi.net we have a blog (see the title at the top of the page) that we use to provide downloads for Vivaldi snapshot builds (these are like dev builds on Chrome). They are not generally recommended for most people. That blog is for our hardcore followers who want weekly builds with every single latest fix (those users already know what Vivaldi is). Our homepage is https://vivaldi.com which displays our most stable channel (currently in beta since we have yet to release a stable).
The link from here to vivaldi.nett is from another user. So he linked to the wrong site (the one he uses), never mind. It happens. The page you want and the one we expect most to visit is vivaldi.com. This is also the page that turns up if you search for "Vivaldi Browser" in search engine.
P.S. I'll take the feedback that we could add a more prominent link from vivaldi.net to vivaldi.com (perhaps an about us link or something like that) to help people who stumble across the "wrong" site.
From vivaldi.net we have a blog (see the title at the top of the page) that we use to provide downloads for Vivaldi snapshot builds (these are like dev builds on Chrome). They are not generally recommended for most people. That blog is for our hardcore followers who want weekly builds with every single latest fix (those users already know what Vivaldi is). Our homepage is https://vivaldi.com which displays our most stable channel (currently in beta since we have yet to release a stable).
The link from here to vivaldi.nett is from another user. So he linked to the wrong site (the one he uses), never mind. It happens. The page you want and the one we expect most to visit is vivaldi.com. This is also the page that turns up if you search for "Vivaldi Browser" in search engine.
P.S. I'll take the feedback that we could add a more prominent link from vivaldi.net to vivaldi.com (perhaps an about us link or something like that) to help people who stumble across the "wrong" site.
Yes, I got all that from your first response.
My point is that both domains are equivalent. There is no "wrong" site. All .com, .net, .org, etc will get indexed by search engines too and will be found by web surfers.
Once you have a site tied to a domain and hosted on the Internet, it's out there and open to everyone.
So yeah, having a top link to vivaldi.com via "About Vivaldi" which takes people to the .com site is all it would take to remove any confusion.
Only if you use chrome or browsers based on chromium. Firefox (and other browsers supporting NPAPI plugins) is still able to use pipelight, which provides an up-to-date flash plugin on 32 bit. Alien BOB provides packages, though they lag a little behind. It's easy to change the version and build an up-to-date package, though. Those interested may want to grab the SlackBuild and start building:
This only works for people who are willing to add a huge dependency of wine (and the additional dependencies associated with that) to their system just for flash playback. I guess for those who can't move to 64bit (or don't want to), this is a decent alternative, but this change from Google effectively ends distribution of an up-to-date native Linux flash plugin.
This only works for people who are willing to add a huge dependency of wine (and the additional dependencies associated with that) to their system just for flash playback. I guess for those who can't move to 64bit (or don't want to), this is a decent alternative, but this change from Google effectively ends distribution of an up-to-date native Linux flash plugin.
Well, if you call wine "huge" … Dependencies are just OpenAL and cabextract (on a full install; OpenAL and cabextract are available from Alien BOB as binary packages). Building wine on my Thinkpad T60 takes about 45-60 minutes. The PepperFlash plugin never worked on my T60 anyway, had choppy YouTube playback with it.
Can't get vivaldi to work on my 32 bit netbook. deb2tgz comes back with not a valid deb. rpm2tgz works and installpkg works well but then can't get vivaldi to load. I even went to the install folder and tried the executable but no dice.
Next I tried the slackbuild and got a 404 error when getting source.
Last edited by Gordie; 03-15-2016 at 03:07 PM.
Reason: slackbuild info
Well, if you call wine "huge" … Dependencies are just OpenAL and cabextract (on a full install; OpenAL and cabextract are available from Alien BOB as binary packages). Building wine on my Thinkpad T60 takes about 45-60 minutes. The PepperFlash plugin never worked on my T60 anyway, had choppy YouTube playback with it.
On a chromium based browser, pepperflash is around a ~5MB package, whereas wine-pipelight adds, by itself, 119MB just for the package (not sure how much once it's extracted) and not counting any additional dependencies. That would make it the largest program package on a stock install (the next closest is Calibre, which is somewhere in the 80MB range).
Last edited by bassmadrigal; 03-15-2016 at 04:07 PM.
The package for x86_64 is bigger than the one for x86 (~63 MB compressed)—on 64 bit, both 32 bit and 64 bit versions of wine are getting built as well—, but I get your point; additional dependencies are few and small, though, as said (OpenAL, webcore-fonts-installer, cabextract -- and fontforge if you want to build it; everything else is taken care of by a full install of Slackware).
ruario had this command in his blog post about a minimal Slackware install:
According to this, llvm is the biggest stock package I have installed (59 MB compressed, 290 MB uncompressed; mostly a full install, but with only little of xap/ and kde/ installed), the biggest foreign package is libreoffice (122 MB compressed, 571 MB uncompressed), followed by wine-pipelight (70 MB compressed, 222 MB uncompressed). However, I don't care that much about space, as even on my 80 GB HDD, I have plenty of space reserved for /, I mostly care about build time. webkitgtk is smaller than wine-pipelight, but can take more than 10 hours to build on older hardware, if not more. Building a generic kernel takes more than two hours as well on my thinkpad. As written above, I get your point, though.
The package for x86_64 is bigger than the one for x86 (~63 MB compressed)—on 64 bit, both 32 bit and 64 bit versions of wine are getting built as well—, but I get your point; additional dependencies are few and small, though, as said (OpenAL, webcore-fonts-installer, cabextract -- and fontforge if you want to build it; everything else is taken care of by a full install of Slackware).
Oops, I must've checked 64bit by accident. That's quite the big difference in size between the two.
Quote:
Originally Posted by lems
ruario had this command in his blog post about a minimal Slackware install:
According to this, llvm is the biggest stock package I have installed (59 MB compressed, 290 MB uncompressed; mostly a full install, but with only little of xap/ and kde/ installed), the biggest foreign package is libreoffice (122 MB compressed, 571 MB uncompressed), followed by wine-pipelight (70 MB compressed, 222 MB uncompressed). However, I don't care that much about space, as even on my 80 GB HDD, I have plenty of space reserved for /, I mostly care about build time. webkitgtk is smaller than wine-pipelight, but can take more than 10 hours to build on older hardware, if not more. Building a generic kernel takes more than two hours as well on my thinkpad. As written above, I get your point, though.
That shows my largest is calligra (not calibre, like I had listed in my previous post -- I got the two names mixed up), with the next largest being llvm.
But. as I said in my original post, I suppose for those users who need to stay on 32bit (whether due to hardware limitations, software requirements, or just a personal desire to do so), this is a good alternative for those who still require newer flash versions and don't mind the additional dependencies that pipelight requires. In the grand scheme of things, the space used is minimal and the resources used (CPU cycles and RAM) probably aren't noticed. But for me, it just seems a little crazy that for what should be a ~5MB plugin, you need to install more than 10x that in dependencies (no judgement for those who choose to do this, I've done similar things in the past when needed). But it is great that the users who need/want it have the ability to do it. Just another great thing about Linux
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.