'Abrowser' behaves strangely after a system update.

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?

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

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.

Same strange behaviour after update.
So I'm using IceCat as long as necessary.

abrowser is working fine for me. I did disable that readerview, not really knowing what it is. I'm using the default gnome environment.

I use the settings and addons here https://trisquel.info/en/wiki/tweak-your-browser-enhance-security-and-privacy

@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% approx.)
/home 35.9 GB 097.9 MB (00% approx.)
RAM Memory 02.0 GB 568.7 MB (27% approx.)
Swap (Not available.) (0% used.)

CPU1 70% used.
CPU2 90% used.

[Source: GNOME System Monitor Program while loading Abrowser.]
By the way, where can I get the log report you mentioned?

@Legimet & SuperTramp83,
Can you share your settings in 'about:config' related to the 'Reader View'? May be I can get it to work by replicating your configurations.

Please note that I do not even have a NoScript addon on Abrowser.

@a_slacker_here,
Thank you for the Bug report.

@a_slacker_here and Bertel,
Thank you for the confirmation.

@cooloutac,
will try out them later. Thank you for showing up!

I'm on Iceweasel and icecat and thankfully don't have this "reader" or several other bloatware entries in my about:config :)

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 do have a swap setup also, but can't see this being the issue eiher.

I also have all the plugins set to never activate always, divx, itunes, quicktime, shockwave, vlc, wmp

there is a similar past bug report here with people segfaulting with libmozalloc.so and libxul.so and they narrowed it down to a flash plugin. https://bugzilla.mozilla.org/show_bug.cgi?id=1038860

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

(abrowser:6389): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised
1437273586327 addons.repository WARN Search failed when repopulating cache
Segmentation fault

A few more times of trying to launch it, then a window appears offering me the options of starting Abrowser in safe mode or "refreshing" the browser, which is really a complete reset of the browser. I started it in safe mode and the main window appeared for a few seconds, then it crashed. I think it exited with a segmentation fault.

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 has never
popped up again.

It's probably because I don't really use any of the addons- I kept my
browser as vanilla as possible.

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 trisquel-mini.

One note: I am using Trisquel 7 32-bit. Can anyone confirm whether or not this is happening on a 64-bit machine?

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 back to abrowser 38 but can't. I had to go back to 33.1 instead.

I experience the same issue. Never had any oom problems before. Disabled reader view but it still segfaults. No downgrade possible as mentioned by alucardx.

I am also on 32bit.

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:
https://trisquel.info/en/forum/radio-talk-show-covering-free-software-declare-your-independence-ernest-hancock

...and the podcast in that thread open in a second tab. I opened a third tab, and tried to search "!imdb the cartel" thrice. The first time I did it from the address bar, instant crash. The second time I tried it from the search box, instant crash. The third time, I closed the other two tabs and tried it, instant crash.

Then I open ABrowser, closed the session restore, and closed the browser. Then opened it again. Did the same search in the address bar, instant crash. Same again with the search bar. Tried again with the !imdb, same result from both address bar and search box.

Tried safe/ troubleshooting mode, seemed to make no difference. Then it offered me the choice to refresh ABrowser, which I did. Same search, still crashed. Same when I used the search bar in the start page. Entered 'duckduckgo.com' into the address bar and pressed enter, instant crash.

I'd also like the option to roll back to a previous version when this happens with application updates.

I hear Icecat is better anyway.. ;)

so only people on 32bit are having the problem it seems?

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.

Did those of you with problems get Abrowser 39.0 working again? If so, how?

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

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.

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?

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 actually looking into this problem right now?

Understand I'm not critisizing or trying to downplay the excellent job that the maintainers do. I'm just trying to bring attention to the fact that this is a big issue and it has gone on since the update was made available and it still isn't fixed.

If we ever want to attract new users, issues like this can't linger.

So, Abrowser inherited the bug from Ubuntu... Like always.

The browser is one of the most important components of an OS these days (if not the most important one). There are also no real Libre alternatives available for Trisquel. I am writing this from QupZilla right now but you can't compare it with a full IceCat/Abrowser.

So without a browser, a LibreOS is not much worth to me and I am thinking about switching to a more stable base like Debian GNU/Linux. With only the main repo active this should fulfill my needs for Libre Software as well and even if it's not officially listed on the Free Distributions list, RMS recently mentioned that it can be seen as Libre when only the main repo is used.

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 (GPLv3, encrypted-by-default, multi-user, video conferencing and text chat, using WebRTC protocol). It worked fine when I first tried it in May (same hardware, same OS, whichever version of ABrowser was current), but today it hit errors which made it impossible to add a new contact without it reloading. All of my few existing contacts appeared to be offline, so it's hard to know whether they actually were, or whether that was a bug as well.

I've tried on IceCat 31.8 (same OS, same hardware), with almost identical results. Then I got the same results again testing it on FireFox on my fiancee's MacBook (haven't convinced her to make the switch to freedom yet), so I thought it was a FireFox problem. But then I tested it on Safari, same problem, so I think Subrosa have some testing and patching to do at their end to get up-to-date with the recent changes across browsers.

BTW IceCat crashes so constantly in Trisquel 6 that it's really usable either.