Puppy Linux Discussion Forum

*** Browser Appimages ***

Update 2021-12-09:
Most of the Browser Appimages that I shared here are becoming outdated soon, to create a Browser Appimage from newest version, see: Create Browser Appimage
===============================================================================================================
Here are some browser appimages that I shared earlier in different threads, and more.
(thought it would be good to collect these here, in one place)

If anyone else has a browser appimage to share, please post here.
Or if anyone wants some other browser "appimaged", I may take requests

Firefox appimage: (see also viewtopic.php?p=29854#p29854)
32-bit: https://drive.google.com/uc?export=down ... yo7Pb0eWxV
64-bit: https://drive.google.com/uc?export=down ... _ldwxdeC2s
Firefox-ESR appimage: v78.12.0
32-bit: https://drive.google.com/uc?export=down ... 4h3EYCG4rB
64-bit: https://drive.google.com/uc?export=down ... dpWIuCJK9y

Google-chrome appimage: (see also viewtopic.php?p=29855#p29855)
64-bit: https://drive.google.com/uc?export=down ... VIw481EydI

Iron-browser appimage:(see also viewtopic.php?p=30621#p30621)
64-bit: https://drive.google.com/uc?export=down ... ZT5v9efOtG

Brave-browser appimage: (see also viewtopic.php?p=30738#p30738)
64-bit: https://drive.google.com/uc?export=down ... vxRcum1h4h

Seamonkey appimage (v2.53.8): (see also viewtopic.php?p=30648#p30648)
64-bit: https://drive.google.com/uc?export=down ... hrv2xhpCr_
32-bit: https://drive.google.com/uc?export=down ... iACZhRSSns

Opera-browser appimage: (see also viewtopic.php?p=29856#p29856)
64-bit: https://drive.google.com/uc?export=down ... Bcz63DYLS0

Vivaldi appimage: Made from Mike's portable Vivaldi, see: viewtopic.php?p=v32.0.4.0113#p113
64-bit: https://drive.google.com/uc?export=down ... ckParZKBu1
32-bit: https://drive.google.com/uc?export=down ... fqL2wDUDaa

EDIT:
Slimjet Browser (Flashpeak-Slimjet) appimages Stable Version (make executable before running):
32-bit: https://drive.google.com/uc?export=down ... n_mfE9XFjv EDIT 2021-11-30 Link replaced now version 32.0.4.0
64-bit: https://drive.google.com/uc?export=down ... kbS-yj3BeK EDIT 2021-11-30 Link replaced now version 32.0.4.0
Profile directory "slimjet-profile" will be at the same level as the appimage.

EDIT: Folder on Google-Drive containing the appimages: https://drive.google.com/drive/folders/ ... jdWLDvgLnL

Fred

Ferdinand - Ons moet 'n Hollandse/Afrikaanse forum-seksie begin.

I want to add a directory to firefox that stops the automatic update, is it possible to unpack an appimage and add a directory to it?

thanks
wizard

wizard wrote: ↑Mon Jul 12, 2021 4:26 pm

I want to add a directory to firefox that stops the automatic update, is it possible to unpack an appimage and add a directory to it?

thanks
wizard

Hi wizard, firefox cannot update itself, because the appimage is mounted read-only when you run it.
EDIT: To answer how to unpack, run it with --appimage-extract, e.g from terminal:
./Firefox-Portable64 --appimage-extract
A 'squashfs-root' directory will appear. To repack, run from inside squashfs-root :
./cr-appimage2

Thanks fred, just wasn't sure if ff would try to update into the save file which would be really messy. Do we have a how to and/or package for creating appimages?

wizard

wizard wrote: ↑Mon Jul 12, 2021 7:17 pm

.... Do we have a how to and/or package for creating appimages?

wizard

Officially, see: https://appimage.org/ but I have my own "unorthodox" method see: viewtopic.php?p=29851#p29851 and program: viewtopic.php?f=106&t=590

Added Vivaldi-Portable64 appimage, see post #1
Made from Mike's portable Vivaldi share, see: viewtopic.php?p=113#p113

Hi fred, the links were just what I needed. A couple of years ago I used a program: create-portable32. Did a search and can't find any info on it. Do you know are appimages a lot different than what that program produced?

thanks
wizard

wizard wrote: ↑Tue Jul 13, 2021 3:44 pm

Hi fred, the links were just what I needed. A couple of years ago I used a program: create-portable32. Did a search and can't find any info on it. Do you know are appimages a lot different than what that program produced?

thanks
wizard

I'm not sure what's your question exactly, more about create-portable in the old forum: https://oldforum.puppylinux.com/viewtop ... 6#p1011814 (download is old version, new version with bugfix in this forum, link at my post above).
There are several ways to create an appimage, but there's always "AppRun" inside.

Hi fred, I guess my question was, does the program create-portable32 (that i used before) create an appimage. Your links answered that question, it does.

thanks for your help.
wizard

wizard wrote: ↑Tue Jul 13, 2021 7:27 pm

Hi fred, I guess my question was, does the program create-portable32 (that i used before) create an appimage. Your links answered that question, it does.

thanks for your help.
wizard

Ah..., yes, it does after you setup the "appdir" manually first (as you probably know already), it can be e.g. an extracted .deb, .pet or .sfs.

@All : Added 32-bit Seamonkey (v2.53.8) appimage to post #1

Fred

Added Vivaldi 32-bit appimage and Firefox-ESR appimages (32 and 64 bit) to First post

I've added Slimjet appimages (32 and 64 bit) see near the bottom at: first post

what about the Min browser? is it possible to make an appimage of it?

fredx181 wrote: ↑Mon Aug 09, 2021 10:30 am

I've added Slimjet appimages (32 and 64 bit) see near the bottom at: first post

Hi fred, I am using slimjet 64 bit. So far, your appimage works well. Thanks for this.

Just sharing my thoughts after using these appimages...

I think the approach of using appimages or any portable apps fits into the Puppy Linux principle of being a small or portable OS. I think this is a good solution for unavoidable "big" applications like browsers and office suites (I use sfs for these).
Browsers for example, create huge profile folders over time and eats up the puppy save file. I also don't like creating huge save files because it tends to make copying and booting up longer.
Portable appimage is a really good solution here because I can save it elsewhere and fire it up from there so it won't affect puppy save space. Plus if you have multiple puppy installations or even other linux distro, they can all use the same appimage and you retain the same profile across your puppies/distro. How convenient is that?
I also appreciate the extra convenience of having a .desktop file automatically created by the appimage. Very good job here fred.

Based on my experience with these appimages, I think this is a good benchmark for creating puppy appimage.
1. creates profile/config/cache in the same directory as the appimage.
2. automatically creates .desktop file at .local/share/applications

That way, we will have the same expectation for most puppy appimage in terms of behavior.

regards,
ronriel

Preview, experimented with method to update existing appimage with newest version, this Slimjet-Portable64 appimage can be run with argument "-update" to be able to choose a directory with newest Slimjet version, download zip from here https://www.slimjet.com/en/postdl.php?v ... 4&type=zip" (and extract) to create new appimage.
Slimjet-Portable64 appimage: (EDIT: Download link replaced, fixed when running from path with spaces viewtopic.php?p=35541#p35541)
https://drive.google.com/uc?export=down ... 211H9rJzQJ
Run as ./Slimjet-Portable64 -update or /path/to/Slimjet-Portable64 -update and follow instructions:

Need to say that above appimage is latest Slimjet version (v31.0.2.0), so at this point of time updating doesn't make any difference, so for now just for testing the concept, feedback appreciated.
I plan to update all appimages at first post with this -update option included, this Slimjet appimage is just first start.

fredx181 wrote: ↑Sat Aug 28, 2021 8:35 pm

Need to say that above appimage is latest Slimjet version (v31.0.2.0), so at this point of time updating doesn't make any difference, so for now just for testing the concept, feedback appreciated.
I plan to update all appimages at first post with this -update option included, this Slimjet appimage is just first start.

I'll try this once a new slimjet version comes out. Thanks for doing slimjet first. It happens to be my main browser.

-ronriel

@fredx181 ,

I'd like to report a problem. When you save the directory with a space in the name (ex. "Portable Apps" - note the space between "Portable" and "Apps"), the profile will be saved in another directory, not in the same directory as the appimage. In my case, it's here:

/initrd/dev_saveApps/Slimjet/slimjet-profile

Apparently, "Portable " was not read. The solution is easy - don't use space in directory names, but you'll mess with your directory if you're not aware of this.
Tested in BionicPup and DupBuster, same issue encountered.

-ronriel

ronriel wrote: ↑Mon Aug 30, 2021 2:30 am

@fredx181 ,

I'd like to report a problem. When you save the directory with a space in the name (ex. "Portable Apps" - note the space between "Portable" and "Apps"), the profile will be saved in another directory, not in the same directory as the appimage. In my case, it's here:

Code: Select all

/initrd/dev_saveApps/Slimjet/slimjet-profile

Apparently, "Portable " was not read. The solution is easy - don't use space in directory names, but you'll mess with your directory if you're not aware of this.
Tested in BionicPup and DupBuster, same issue encountered.

-ronriel

Yes, thanks for reporting, here's new Slimjet-Portable64, should be OK now when running from path including spaces:
https://drive.google.com/uc?export=down ... 211H9rJzQJ
The cause was that I forgot to put double quotes around some variables here and there in the scripts.
Also improved the "-update" option a little.

EDIT: RE-UPLOADED again, download link replaced, one thing I had forgotten, that the path in the Exec=... line in the created .desktop launcher should be surrounded by quotes too, fixed.

Re-uploaded Slimjet-Portable64 again with small fix (hopefully last), see EDIT previous post.

fredx181 wrote: ↑Mon Jul 12, 2021 8:58 am

*** Browser Appimages ***

Here are some browser appimages that I shared earlier in different threads, and more.
(thought it would be good to collect these here, in one place)

Seamonkey appimage (v2.53.8): (see also viewtopic.php?p=30648#p30648)
64-bit: https://drive.google.com/uc?export=down ... hrv2xhpCr_
32-bit: https://drive.google.com/uc?export=down ... iACZhRSSns

Hi Fred,

I downloaded the 32bit seamonkey appimage and I am wondering if you could clarify where the cache is placed please? I thought the cache may be kept inside the appimage but when I rightclick the appimage I do not see a "Look inside" option so I can't get in there to check/delete the cache.

Any thoughts please?
Cheers!

@greengeek :-

Should be within the profile, Ian.....labelled "cache2", I believe. And if I understand the way Fred has buit these particular versions, the profile should be created alongside the AppImage, at the same level.

Hope that helps!

Mike.

mikewalsh wrote: ↑Tue Oct 05, 2021 12:18 am

Should be within the profile, Ian.....labelled "cache2", I believe. And if I understand the way Fred has buit these particular versions, the profile should be created alongside the AppImage, at the same level.

Thanks Mike - yes that's exactly where the profile is appearing. Not sure what I must have been doing before. I was testing a couple of versions of SeaMonkey and mustv confused myself because there was no profile in any of the usual places. Loose nut behind the wheel.

Do you have any idea why I can't "Look inside" the appimage? (Maybe it's a special variant of appimages??)

Cheers!

Do you have any idea why I can't "Look inside" the appimage? (Maybe it's a special variant of appimages??)

That "look inside" option goes for a "rox-app" (which is a directory containing "AppRun") not for an appimage.
But you can turn it into a rox-app by extracting the appimage:
./myappimage --appimage-extract
A folder squashfs-root will appear (rename as you wish) where you can "look inside" and you can run it as a rox-app as well.

Other way to look inside is: run the appimage, then go in /tmp and open folder ./mount_.... (e.g. /tmp/.mount_SeamonoQr9Vl/)

fredx181 wrote: ↑Tue Oct 05, 2021 8:59 am

That "look inside" option goes for a "rox-app" (which is a directory containing "AppRun") not for an appimage.
But you can turn it into a rox-app by extracting the appimage:...

Thanks Fred. I will try that and get a better understanding. Haven't had much to do with appimages before.
Cheers!

Hi Fred,
The slimjet 32 bits (your message of july the 12th) works fine with my two 64 bits computers running with a 32 bits puppy, but doesn't work with my 32 bits computer...
May be the next one, with the new slimjet 32.0.4.0 (november 14 2021) ...

gilles wrote: ↑Sun Nov 28, 2021 3:28 pm

Hi Fred,
The slimjet 32 bits (your message of july the 12th) works fine with my two 64 bits computers running with a 32 bits puppy, but doesn't work with my 32 bits computer...
May be the next one, with the new slimjet 32.0.4.0 (november 14 2021) ...

Hi gilles, I need to know some more details so I can possibly test (although I don't have 32-bit computer):
- From which Puppy you tried Slimjet-Portable32 on your 32 bits computer?
- Can you run Slimjet-Portable32 on your 32 bits computer from terminal, look for errors and post here ?

Hi Fred,

I tried your slimjet appimage with Xenial 32 bits and with Focal Fossa 32 bits (always frugal install) In both cases, it works fine with my two 64 bits computers but doesn't work with my 32 bits computer.

Terminal (32 bits computer) :
Focal Fossa :
# /opt/Slimjet-Portable32
mkdir: cannot create directory ‘/opt/slimjet-profile’: File exists
./runapp: line 4: 5287 Illegal instruction "$HERE/flashpeak-slimjet" --user-data-dir="$(dirname $APPIMAGE)/$PROFILE" --test-type --no-sandbox "$@"
#
Xenial : https://onedrive.live.com/?authkey=%21 ... t&o=OneUp
May be, it will work better with the next appimage, made with the new slimjet, released on november the 14th 2021...

If I uninstall slimjet, I still have it in the menu, but I cannot delete it in the menu...

You don't have a 32 bits computer. If you want, I can help you doing what you want with my 32 bits computer for this appimage, or any other. But you may need my e mail. I can give it to you if you want

@gilles
Here's newest 32-bit Slimjet-Portable32 (made from v32.0.4.0):
https://drive.google.com/uc?export=down ... n_mfE9XFjv
Maybe you can try first on your 32-bit computer, but to be honest, I'd be surprised if it works, worth testing though, I guess, but... perhaps your 32-bit computer is too old.

Btw, you can test also by download and extract the newest 32-bit slimjet and edit "flashpeak-slimjet" line 9-11 (as we discussed before) to:

#if [ "`whoami`" = "root" ]; then
#  echo "Don't run this as root."
#  exit;
#fi

and run from terminal inside the slimjet directory:
./flashpeak-slimjet --no-sandbox
If that doesn't work (giving the same "Illegal instruction" error) on your 32-bit computer then obviously the portable won't work too.

EDIT:

If I uninstall slimjet, I still have it in the menu, but I cannot delete it in the menu...

You can delete the .desktop file from /root/.local/share/applications, and run fixmenus (and probably also, not sure jwm -reload)

EDIT2:
Updated Slimjet-Portable64 for 64-bit too (v32.0.4.0):
https://drive.google.com/uc?export=down ... kbS-yj3BeK