'Abrowser' behaves strangely after a system update.
- Inicie sesión o regístrese para enviar comentarios
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 made upstream by Ubuntu or a change made for Trisquel.
Now again,I have to ask: Why hasn't anyone been trying to resolve this? Why aren't we even getting feedback on this? This is not a minor problem when your primary and most functional browser is broken. I am not trying to critisize, but understand.
Does anyone else feel like this should be getting more attention or is it just me?
@alucardx Yeah, I think this is an important issue. I don't have the skills to fix it myself though. :(
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 that someone else here recommended.
I think it's bad that whoever prepared the downloads did not realize or was not told not to update Abrowser/place it on mirrors so it could be downloaded since this problem supposedly happened elsewhere on other distributions.Or so it is said.
Don't know if I will go back to Abrowser if I have a choice once it is fixed.If it is fixed.
I am a translator!
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...
FWIW I'm on 64 bit Trisquel 6. Abrowser 39 + NoScript - Gnash. Very solid experience, as always.
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 to load once without immediately crashing since the update. :(
I've been using Abrowser for a long time now and never had a problem like this. I'm disappointed.
IceCat is similar though, so it'll all work out in the end. Some questions about IceCat and Tor though ... is Tor always running in the background now? How can I check this?
I understand that when I switch to private browsing, IceCat changes the proxy to the Tor proxy and when I switch back, it changes back to the normal system proxy. The change takes place so seamlessly that it appears as if Tor is always running. Is this true?
Is there a source I can go to in order to learn more?
I believe it is real, just sharing my anecdote.
I am a translator!
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!
there is no tor process running on my machine all the time. Unless its from installing icecat which I don't use.
I am a translator!
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.
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?
or so you think I should stick with tor-browser? I'm just having troupble getting an apparmor profile to work right with it, i'm too noob lol.
I am a translator!
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 browsing mode. If you are just viewing cats and dogs pictures it is perfectly fine to use it. But if you are doing anything important, compromising, vital etc.. use the Tor BB! You shouldn't mix your standard browser with tor. Fingerprinting techniques are much easier on Icecat because not many people use it. Another thing is, if you read the "how to stay anon" on the Tor website it will clearly explain you that installing addons on Tor can completely screw you anonymity. So if you have installed, say, jap dictionary plugin.. you may have problems.
Tor Browser Bundle is used by many people and basically all the TBBs are identical so no fingerprinting techniques can be used against you. Make sure you set Tor to the strictest setting in "privacy and sec" settings, that is to say, make sure you completely disable javashit.
The problem was due to the gcc version used to build firefox.An updated package is avaliable for testing here:
You can download and install it with:
wget http://jenkins.trisquel.info/jenkins-repos/belenos/abrowser_39.0+build5-0ubuntu0.14.04.1+7.0trisquel39_i386.deb sudo dpkg -i abrowser_39.0+build5-0ubuntu0.14.04.1+7.0trisquel39_i386.deb
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.
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....
Is there a version for those of us on Trisquel 6?
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
I'm afraid not: crashes in the same way as before. In terminal
user@user-ThinkPad-X60:~$ abrowser
1438456792906 addons.repository WARN Search failed when repopulating cache
console.error:
[CustomizableUI]
Custom widget with id loop-button does not return a valid node
console.error:
[CustomizableUI]
Custom widget with id loop-button does not return a valid node
Segmentation fault
user@user-ThinkPad-X60:~$
Thanks for trying.
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 carefully made sure to choose your version to install - which took a decent time to download. And it is working fine so far (up for about 10 min).
Many thanks!
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 improvements with filetype associations and other things when using the patched version from the PPA along with the abrowser-kde-support package. See https://trisquel.info/en/wiki/abrowser-kde-users.
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 back to system proxy settings.
Now I can access the Indian versions.
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 still my production system, so a fix would be much appreciated.
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 be handled. If nothing else, as was said by another member there should have been a downgrade to abrowser 38 as a temporary option. Is there a policy in place for dealing with this type of thing?
Anyway, thank you for fixing this!!!!
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!
There was a new update and it broke Abrowser again... Damn it
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.
Can you try the packages from my PPA?
https://launchpad.net/~legimet/+archive/ubuntu/abrowser-kde/
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.
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
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 :)
It turns out that the issue is a bit complicated in 32-bit Toutatis. You will have to wait a bit.
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 just a matter of using the latest version in the repos. However, in precise, the fixed gcc-mozilla package is not in the repos, as aklis found out yesterday. He later found that the updated gcc-mozilla was in a PPA, so this package has to be manually backported to Trisquel toutatis. Unfortunately, the gcc-mozilla package build-depends on a newer version of dpkg-dev than in the toutatis/precise repos. I don't know if aklis figured out how to build it yet.
Basically, dependency hell :(
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 has WebRTC support finally, i was eager to test meet.jit.si (on both 32 and 64 Toutatis versions)
I knew that someday i had to drop 32 bits, but i didn't see it coming so fast :P.
Thanks for your response.
There's an update in my ppa which should work.
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 before I contact them about freeing their scripts).
Try my PPA as a temporary solution;
$ sudo add-apt-repository ppa:legimet/abrowser-kde
$ sudo apt-get update
$ sudo apt-get install abrowser
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.)
Thus it would be wise to schedule sensitive updates (Other than essential security updates.) away from weekends. Otherwise, new users will get turned off and may never come back due to the bitter experience they had, at first hand.
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 and the use of Tor? Are the default settings different? Is there a wiki page (or something similar) about this?
EDIT: Grammar fix.
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 homepage thingy.
Neither Abrowser nor IceCat use Tor, however.
Tor is a dependency of Icecat. I believe Icecat's private mode uses Tor.
@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 free as in free speech....!!)
Abrowser too has HTML5 Video and its custom homepage add-on. Tor proxy is available to Abrowser too, provided you have installed GNU IceCat. (Tor proxy comes pre-installed with GNU IceCat.)
Abrowser tracks the most recent Firefox build, whereas IceCat tracks the ESR release; (Similar to Ubuntu's LTS edition, Trisquel GNU/Linux's upstream.)
As a result, GNU IceCat is generally more stable, while latest features from Firefox are available on Abrowser.
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.
UPDATE: after update v40, no problem with javascript.
Nevermind, I solved my issue right after posting...
Not related to the crash btw.
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.
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.
- Inicie sesión o regístrese para enviar comentarios