Page 1 of 2

Strange Chromium browser behaviour

Posted: 13 Mar 2013, 11:09
by viking60
I made this link:
http://bit.ly/16reGvb
on lmgtfy.com today, and it runs nicely in Firefox but not in Chromium!
It takes forever to run or not at all...
Since Chromium is a Google browser that is odd.
I use Version 25.0.1364.172 (187217) and it does not matter if I deactivate adblock. :confused
Does anyone else have this behaviour in Chromium? I suspect it must be a Javascript setting thing....
Edit;
And while you are testing let's have some fun:
http://bit.ly/sYS0Jx
(Tell me what happened :-D )
http://bit.ly/teVeFN
I love to do this one on the computers of others when I pass because it is so fast - and then I watch the frentic virus search and calling.... :-D
It works in any Google search field or in the integrated search field of your browser if you have Google as your search engine. Except in Chromium... (Yes IE too - those are the ones calling MS support when you do this :lol: )

Re: Strange Chromium browser behaviour

Posted: 13 Mar 2013, 14:39
by rolf
The first one, http://bit.ly/16reGvb works in my latest 64-bit Seamonkey, which has Ghostery and is my main browser.
It also works in my Chromium, which I only use for google talk and is pretty vanilla, nothing to block the "Sexy Lingerie" ad at google,
Version 21.0.1180.81 Mandriva 2011.0 (151980) :confused
Next! :berserkf

http://bit.ly/sYS0Jx works on both, pretty cool. :s
Next! :berserkf

http://bit.ly/teVeFN works on both. :B

Re: Strange Chromium browser behaviour

Posted: 13 Mar 2013, 15:19
by viking60
Hm Must be either the version or some of my paranoid settings in Arch.
It works in Iron on my Mandiva too :think:

Re: Strange Chromium browser behaviour

Posted: 13 Mar 2013, 15:58
by dedanna1029
Yeah, I was going to say, for someone so privacy-minded, you sure use a browser that's not privacy-minded (Chrome). Glad to see you do use Iron.

Works for me. FF, Chrome. I'm having a bit of an issue getting Iron installed these days, so no results for it.
Where are you getting the google-chrome install file from? Have you installed the google repo in Mandriva, or do they have it in their repo?

Re: Strange Chromium browser behaviour

Posted: 13 Mar 2013, 19:35
by viking60
I have Iron in Mandriva thanks to our MiB friends no chrome. So it would be the MiB 64 bit repo.

Re: Strange Chromium browser behaviour

Posted: 14 Mar 2013, 00:23
by dedanna1029
I go get it from the site. They do .rpm and .deb now; noarch.

The problem is, the last three releases have depended on something not in any repos. I'll explain that further in another thread sometime.

Re: Strange Chromium browser behaviour

Posted: 14 Mar 2013, 01:13
by viking60
Looks like Chromium just decided to be moody after a logout it all works again :confused

Re: Strange Chromium browser behaviour

Posted: 15 Mar 2013, 01:08
by dedanna1029
Kewl.

Re: Strange Chromium browser behaviour

Posted: 15 Mar 2013, 18:17
by viking60
..And now it hangs or freezes again. This Chromium version is not very stable.

Re: Strange Chromium browser behaviour

Posted: 19 Mar 2013, 12:05
by viking60
Grr that's it I will not use chromium on this box anymore it has frozen several times in the middle of posting. :f This is written from a fully functioning Opera....

Re: Strange Chromium browser behaviour

Posted: 19 Mar 2013, 12:07
by dedanna1029
I've also been prone to not using it lately, and with Iron's code being based on it... also asks for a dependency that's ludicrous these days, and not in any repos I've found.

Yeah, Chrome/Chromium both crash a lot here.

Re: Strange Chromium browser behaviour

Posted: 15 Apr 2013, 11:17
by dedanna1029
The crashing issue seems to have been fixed in the latest Chrome/Chromium (google repos, v. google-chrome-stable-26.0.1410.63-192696). I also now have Iron working so highly recommend it, the latest 25.0.1400.0 Stable for Linux tar.gz download here.

Try the tar.gz, extracted to /home and /usr/local both, if it works both ways, get the .rpm or .deb download from the same link, and install with one of them. Use the tar.gz to test first.