I'm having a problem with the latest ABrowser on Belenos. It may just be a
problem with the particular site (http://thedailyblog.co.nz/), but I'm
reporting it here, as it may also be a Abrowser (or upstream) bug related to
the ones that were recently fixed.
When I visit the site, I usually
I just got back from a week AFK, and downloaded the latest ABrowser patch
(40.0.3) on both Trisquel 6 and 7. This seems to have fixed the segfault
crashes on 6 (writing this in 6), and improved the stability in 7. Thanks to
everyone who helped triage and fix the bugs involved. Great work!
The latest version should fix this for 32-bit toutatis.
Fixed in Abrowser 40
Upgrade to ABrowser 40 on Trisquel 7 seems to have fixed the crashing issues
for now. Thanks to everyone who worked on this. Will test on Trisquel 6 next.
There's an update in my ppa which should work.
Just tried ABrowser in Trisquel 6(.0.1). No joy, window doesn't even appear.
Running 'sudo apt-cache show abrowser' shows that the version is 40. Running
'abrowser' in a terminal returns the response 'segmentation fault'.
If I haven't mentioned before, my machine is 32bit.
Check here
u_u!
I tried an update from the repo, it didn't work, then build it myself hoping
it could be some random thing that building it myslef could fix it.
It didn't work either, after that, i read your response and well, yeah:
Dependency hell! :'(
It's a shame that this release is the one that
It's alive
Muahahahaha!
Thanks a bunch, i really hope this update will hit the main repo not so far
:)
Again, thanks! ^_^!
Really?, why?
Please tell me more :)
Newer versions of Firefox cannot be built with GCC 4.6, the version of GCC in
precise. So Ubuntu backported GCC 4.8 (the version in trusty) to precise as
the package gcc-mozilla. The bug in 32-bit builds of Firefox was caused by a
bug in GCC. The fix to GCC was made in trusty, so that was
I recently learned that I should regularly get-upgrade after get-update, and
it upgraded Abrowser.
No crash whatsoever, but I can't get true fullscreen.
In that screenshot, you can see that the bar is still in sight (it should be
hidden) and also, there are the minimize/fullscreen/close icons
It turns out that the issue is a bit complicated in 32-bit Toutatis. You will
have to wait a bit.
Would you build the 40 release for Toutatis?
I'm still getting the same behaviour on the trisquel 40 build, i purge and
delete the .mozilla file on home, but it still no luck on it, on my 64 bit
machine it works fine.
Thanks :)
Still crashes on my 32bits machines. Abrowser updated to 39.0.3+build2, same
for previous versions, except 33. The problem is, enabled javascript, when
disabled, I have no problems. Tryed with clean install of OS, no addons or
plugins, but same happens for Abrowser with addons or plugins.
@Magic Banana,
I agree with you.
Here's my thoughts on the topic:-
GNU IceCat is built keeping user freedom and privacy as the top-notch
priority; SPY Block, HTTPS Everywhere!, Tor Proxy and LibreJS are a few tools
to defend the user from known vulnerabilities. (And of course, they are
Most people download and install Trisquel GNU/Linux on weekends. (Saturday,
Sunday.)
The very first web browser they will be using on a fresh install is most
probably Abrowser. (I am not ignoring GNU IceCat; But most people will get it
as a single click download option from Abrowser.)
Try my PPA as a temporary solution;
$ sudo add-apt-repository ppa:legimet/abrowser-kde
$ sudo apt-get update
$ sudo apt-get install abrowser
You can use it as a temporary solution.
$ sudo add-apt-repository ppa:legimet/abrowser-kde
$ sudo apt-get update
$ sudo apt-get install abrowser
Back on IceCat as, like others, my Abrowser broke again with the recent
update. :( I noticed that IceCat hasn't been updated to match the most secure
Firefox version. Is that correct?
Also, what are the main differences between IceCat and Abrowser? Is it the
plugins installed by default
The primary difference between IceCat and Abrowser is essentially the range of
plugins installed- Abrowser is a more or less vanilla Firefox (except it does
not recommend non-free plugins) while IceCat has HTTPS Everywhere, LibreJS, and
HTML5 Video installed by default, as well as the IceCat
Now, Abrowser 39.0.3 on a 32-bit machine suffers the same issue. (At least
for me.)
Someone needs to test the latest Abrowser version(s) on different
architectures before pushing them for the routine updates.
Hope the issue get resolved the sooner possible.
I'm having the same issue with 39.03 on Trisquel 7. The last system update
seemed to fix the random crashing problem, this one has broken it again :(
Problems is ongoing on Trisquel 6. Using IceCat as my main browser now on
both installs (with LibreJS turned off, except for testing sites
Thank you, Legimet.
But wouldn’t it be nice if the developer(s) themselves release the fix as
an official update?
Its not that I don't trust you; But I am having practically no experience
dealing with PPAs.
There was a new update and it broke Abrowser again... Damn it
rrgmitchell, could you try the package from my PPA and tell me if it works?
Just run
sudo add-apt-repository ppa:legimet/abrowser-kde
sudo apt-get install abrowser
ignore this post, I didn't think it posted since the website went down on me
that day when i hit post. But when it came back up everything was working
and I couldn't crash abrwoser even if I tried
Thanks. I forgot to tell you to run apt-get update, which is why you didn't
get the PPA version at first. The PPA is actually for KDE integration, so if
you don't use KDE, I suggest removing the PPA as soon as the fix comes out in
the official repos.
On the other hand, KDE users will see
I'm afraid not: crashes in the same way as before. In terminal
user@user-ThinkPad-X60:~$ abrowser
1438456792906 addons.repository WARNSearch failed when repopulating
cache
console.error:
[CustomizableUI]
Custom widget with id loop-button does not return a valid node
I spoke too soon!
I did the two commands you suggested, but the apt-get must have installed the
standard v39 from the toutatis repository again. Which crashed. I should have
realised it was still the wrong version since there was hardly any download
time..
I then went into Synaptic and
The recent update has fixed the problem for me as well. Thank you to the
developers for working to get that fixed.
Again, I stress that these types of problems are a HUGE deal. I really would
have liked to see some better communication to the community as to how this
problem was going to
I'm back in Abrowser, so the update worked for me as well. I agree with
@alucardx about better communication and appreciate all of the feedback here
in the forum in the meantime. Thanks everyone!
A recent software update seems to have solved this issue.
Nice work, team!!
But there was a minor issue, at least for me; The proxy configuration changed
from system proxy settings to manual proxy settings. So I was presented with
French version of some websites.
No big deal, flipped
On my machine, the apt-get-upgrade I ran today has fixed ABrowser on Trisquel
7. Great stuff!
However, a previous automatic update (ABrowser 38 39) created the same
problems on Trisquel 6, and even though I ran apt-get-upgrade on that install
today as well, the problem persists. This is
Is there a version for those of us on Trisquel 6?
The problem was due to the gcc version used to build firefox.An updated
package is avaliable for testing here:
http://jenkins.trisquel.info/jenkins-repos/belenos/abrowser_39.0+build5-0ubuntu0.14.04.1+7.0trisquel39_i386.deb
You can download and install it with:
wget
I am myself not much experienced with apparmor profiles, but being Icecat (or
Icecactus as I recently started to call it, hmm..) based on FF (just like
Iceweasel and Abrowser) the profiles shouldn't differ much.
In Icecat your connection gets routed through Tor when you are in private
I tried this and it worked!
I'm typing this on the reinstalled Abrowser right now.
Everything works, until I try to sign into firefox sync. Then it seg
faults,and then i unable to run firefox without segfaulting, until I run
abrowser -P to delete teh profile.
there is no tor process running on my machine all the time. Unless its from
installing icecat which I don't use.
I believe it is real, just sharing my anecdote.
I see interesting. is there a button for tor in icecat? to toggle it on or
off? and also i'm curious is there an apparmor profile for it anywhere?
Yes. We are talking about Icecat and its tor implementation. Abrowser doesn't
have it. The tor package gets installed when you install Icecat. You can
remove it if you don't want it though, and keep Icecat. Tor browser bundle is
much better anyway.
jdenz - sudo netstat -tulpn will give you the info. If I recall correctly
the process tor on Trisquel *is* indeed running all the time but it only
listens to local host so, no biggy..
cheers!
Well, this is real. For what it's worth, I'm on 32 bit Trisquel 7, just
updated from Abrowser 38 to Abrowser 39 (waited for a resolution before
updating sooner, but didn't want to wait any longer ... typing this on
IceCat), NoScript, plus a bunch of other plugins ... didn't get Abrowser 39
FWIW I'm on 64 bit Trisquel 6. Abrowser 39 + NoScript - Gnash. Very solid
experience, as always.
I'm using IceCat on Trisquel 7 now. It mostly runs ok if I keep LibreJS
turned off, but it still crashes from time to time. If I actually want to get
some work done without periodic browser crashes, I have to go back to my
Trisquel 6 install.
Browser crashes in Trisquel 6
Come to think of
this looks promising, hopefully it will be fixed in a future update from
upstream. But personally, I didn't experience this problem on a machine
running Lubuntu with all the newest updates...
See https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1474003
Oh well..
Happened to me after I uploaded an update.
Not a fan of Abrowser anyway. Not a good web browser during its best time.
I had to upload an obsolete version of Dooble to come here and find this
out.
I don't have the 33 version of Abrowser on my system so I had downloaded
icecat
Just as an experiment I recompiled abrowser from source from the Trisquel
repositories. It took nine hours to complete but the end result was no
different. I know that if I download the official Firefox 32-bit binary
everything works just fine.
This means that it must either be a change
@alucardx Yeah, I think this is an important issue. I don't have the skills
to fix it myself though. :(
I solved the problem with Abrowser 39 on Trisquel 7
(http://trisquel.info/en/forum/abrowser-behaves-strangely-after-system-update#comment-73839)
by going back to Trisquel 6.
I'm now using ABrowser 38 on Trisquel 6 (same hardware). Most things work,
but I just tried to use Subrosa.io
Once you install abrowser 39 you can't downgrade back to 38. You can go to
33.
The problem I have with Icecat is that it is so privacy and security oriented
that it breaks sites. Normally that is not a major problem for me but there
are a few that won't work at all because of the tight
Exact same issue for me after v 39 upgrade, on my GlugGlug X60 laptop.
Immediate crash. I've had to install the only other version in the repo,
which was version 19!
You can't use abrowser 38 on trisquel 7? Or isn't it maybe safer to use
icecat on trisquel 7 until issue is fixed?
Abrowser 39 crashes on my 32-bit Trisquel 6 machine as well.
I second this.
You can temporally use abrowser 33:
1) Open Synaptic
2) Search for abrowser
3) Click the package named abrowser
4) Press Control + E
5) Select 33.0 for the version
6) Force the version
7) Click on Apply
8) Wait
9) Enjoy abrowser 33
It's and old one. But, what's the deal? I have been using
There have been bugs filed and many people are experiencing this problem. Due
to the fact that this is the default browser for the system and it is the
most friendly to most mainstream sites I don't know why this is taking so
long for there to be an official response.
Are any maintainers
I tried it on Lubuntu 14.04, 64-bit, Firefox 39 does not crash at all. On my
trisquel-mini 32-Bit setup the crash occures however... It seems like
something went wrong in the process of changing Firefox to Abrowser?
Did those of you with problems get Abrowser 39.0 working again? If so, how?
I had to install another browser (IceCat).
I realize your all talking about abrowser 39 but it may be related to this
known issue. Also it only effects 32 bit systems.
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1471949
It seems more like this past bug. In other words people segfaulting after
loading certain webpages.
https://bugzilla.mozilla.org/show_bug.cgi?id=1038860
A couople users up above say its happening to them on 64 bit machines.
pretty bizarre.
Maybe you can try the builds from my PPA:
https://launchpad.net/~legimet/+archive/ubuntu/abrowser-kde/. Don't worry
about the KDE support if you don't need it.
Am I the only person here not experiencing any strange issues with the latest
Abrowser? It works perfectly for me. Haven't changed any settings since before
the update. I don't even mind reader mode. I tried it out the first time,
didn't really see the point (though it is a nice gimmick) and it
I am experiencing the same behaivour, but setting the reader.parse.onload to
false didn't help. Icecat is unaffected.
I also get the same output as ssdclickofdeath.
I have 6GB of memory and 3,2GB swap, while running mini-trisquel.
One note: I am using Trisquel 7 32-bit. Can anyone confirm whether or not
this is happening on a 64-bit machine?
I'm not having this issue either, and I have addons and plugins installed...
I'm not experiencing issues either.
Are you guys all using 64-bit or 32-bit Trisquel?
What is the quickest way to get this problem fixed? It seems like a major
issue like this should be dealt with more quickly.
Also, why is it that as soon as a new package version is available the old
one is immediately removed from the repos? In a situation like this I'd like
to downgrade
It seems so, I have a 32bit computer and I'm having these issues
I have 64bit and I am getting the same crashes as others have reported.
Except I can't go to any websites thus far witout it crashing.
64-bit
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What am I doing wrong? Abrowser 39 doesn't crash here. I have Trisquel
7.0, 64-bit, running on a laptop with 3 GB ram and 6 GB swap. I'll
try 32-bit on my other machine.
On 07/19/2015 05:57 PM, dh...@openmailbox.org wrote:
I have 64bit and I am
so only people on 32bit are having the problem it seems?
64-bit.
I'm running a fairly fresh install (from a few days ago) of Trisquel 7
(32bit), on an Acer Aspire One. I have 1GB memory, which was always enough on
Trisquel 6, and I'm using a swap partition.
Just updated to ABrowser 39, which crashed repeatedly. I had this page open
in a tab:
I hear Icecat is better anyway.. ;)
64-bit.
I don't think the system is low on memory; This is the present state of my
memory.
That's your hard disk space. The fact you don't have swap means you're more
likely having to deal with the oom killer. This seems like a decent overview
of the beast
@Mzee,
I
am having HTML5 Video Everywhere!, Private Browsing Tor
Proxy 2.3 and AbrowserHome 1.0 as extensions and default
addons.
@lembas,
I don't think the system is low on memory; This is the present state of
my memory.
Total Used
/19.6 GB 006.9 GB (37%
A person in irc room said she deleted the profile folder removed abrowser and
reinstalled and has same issues even on safe mode.
Not sure why, only diff she was on KDE, i'm on the default gnome desktop
maybe? don't know why that would make a diff though.
I'm on Iceweasel and icecat and thankfully don't have this reader or
several other bloatware entries in my about:config :)
I am experiencing the same issue with abrowser 39. Thanks for reporting the
bug.
Abrowser 39.0 on Trisquel 7 doesn't work at all. I tried launching it three
times and every time it shows the window that checks for add-on compatibility
then it crashes.
~$ abrowser
(process:6389): GLib-CRITICAL **: g_slice_set_config: assertion
'sys_page_size == 0' failed
Could you be running out of (memory + swap)? In that case it could've been
the oom (out of memory) killer. You should find his calling card in the logs.
As lembas pointed out, it seems to me that you are running out of mem. Check
your mem and swap.
If you don't like it, you can disable the reader thingy by toggling this to
false in about:config- reader.parse-on-load.enabled
Both fsf.org and mozilla.org work for me without problems with Abrowser 39.0.
Are you using any add-ons that might cause problems?
It also works like shit in my system.
I think it is a general problem. It happens when the browser blocks specific
sites.
It is bug and an important one. I'm going to report it.
I like the Reader View. Just note that if you have NoScript, you will have to
allow scripts from about:reader.
abrowser is working fine for me. I did disable that readerview, not really
knowing what it is.
I use the settings and addons here
https://trisquel.info/en/wiki/tweak-your-browser-enhance-security-and-privacy
Same strange behaviour after update.
So I'm using IceCat as long as necessary.
96 matches
Mail list logo
