How-to install abrowser on Devuan
- Inicie sesión ou rexístrese para enviar comentarios
QUICK AND DIRTY WAY (no auto updates): 1. Grab the latest abrowser .deb package for your hardware at https://archive.trisquel.info/trisquel/pool/main/f/firefox/?C=M;O=D
2. Install with "sudo apt install ./abrowser_90.0+build1-0ubuntu0.18.04.1+9.0trisquel80_amd64.deb" or whatever the name of your deb file is.
FULL REPO INSTALLATION METHOD (for receiving auto updates of abrowser):
# Install the trisquel-keyring package
# from https://archive.trisquel.info/trisquel/pool/main/t/trisquel-keyring/:
wget https://archive.trisquel.info/trisquel/pool/main/t/trisquel-keyring/trisquel-keyring_2018.02.19_all.deb
sudo apt install ./trisquel-keyring...deb
# Add the trisquel 'etiona-updates' repo to your apt sources list:
cd /etc/apt/sources.list.d/
sudo mousepad trisquel.list
#type in the repo line for adding the Trisquel repo for abrowser
deb http://archive.trisquel.info/trisquel/ etiona-updates main
# Apt pinning of the etiona-updates repo to NOT be updated from, but from the abrowser package TO be updated. Create a file with any name (called 'trisquel' here) and put the following apt pinning preferences in it
cd /etc/apt/preferences.d
sudo mousepad trisquel
#type in the apt pinning config into /etc/apt/preferences.d/trisquel:
Package: * #all packages from this repo
Pin: release a=etiona-updates #tells apt this apt that this pin is just for this repo
Pin-Priority: -1 #negative number pin tells apt to ignore these packages
Package: abrowser #only for the abrowser package
Pin: release a=etiona-updates #same repo
Pin-Priority: 700 #says that just for this one package, give it a high priority, so that it can be installed and updated normally
Package: trisquel-keyring #only update if there is a new trisquel-keyring
Pin: release a=etiona-updates #same repo
Pin-Priority: 700 #give this one package a high pin priority so that it will update normally
#update and install
sudo apt update
sudo apt install abrowser
#should work!
OK, that's super messy on the screen, let me know if you can't read it, I'll post it as a text file.
Here is an md text file in a compressed tar package.
| Anexo | Tamaño |
|---|---|
| abrowser_devuan.tar.xz | 1.01 KB |
As a pdf, if you prefer.
| Anexo | Tamaño |
|---|---|
| abrowser_devuan.pdf | 23.84 KB |
Yes, that pdf looks much better, thanks @loldier!
So I dusted that antique eeepc and...am still updating existing beowulf packages. It must have stayed on its shelf for months, winter and all.
Anyway, apt pinning the trisquel repo is done so next step is to try and install abrowser, and see what I did wrong.
By the way, is Devuan still supposed to be using slim? Slim seems to have been abandoned around 2014, which in computing time is eons ago. I might never have found out about this were it not for slim stubbornly starting xfce by default instead of MATE. I might simply uninstall xfce in order to solve the problem without having to reverse to manual login. Or do you know of any reliable alternative to slim? What about LightDM?
I dunno, but antiX and I think a bunch of other distros use slim. Not sure it's really needed any updates since 2014. It's a pretty simple login manager (thus the name).
That's what I was thinking, but I found contradictory instructions on how to configure it, so I guess it is working fine until you need to configure its default startup behavior. I always love to configure these little things on spare computers, so I might give it another try if I can find instructions that fit what slim config files came with beowulf.
LightDM for instance was totally straight to configure: add two short lines in the config file to tell it which user to login by default, and into which DE. To be fair, I had initially missed the small icon on the top right corner of the login screen where you can choose your session (repeatedly pressing F1, as with slim, only made the login fields bigger, which is cool but irrelevant).
I have a hunch it might have something to do with that "default Xsession" thing which appeared in the session list after I installed lightDM. Slim was logging me into the xfce session at startup, which comes by default in Devuan. I need to find where that "default Xsession" is defined. I could not find it, so I installed lightDM instead.
Update: now browsing with abrowser 90.0 on beowulf and its 4.19.0-9 kernel, with MATE 1.20.4.
Downdate: installing lightDM made things worse, I cannot even choose a MATE session at login any more. It appears slim might not be the culprit after all. I managed to configure lightDM so the MATE session is the default autologin session.
Woohoo!! Ride 'em cowboy!
- Inicie sesión ou rexístrese para enviar comentarios