Welcome, Guest. Please login or register.
Did you miss your activation email?

Author Topic:  [Fixed] Don't upgrade to chromium 50 for now!  (Read 6629 times)

Offline gerd

  • User
  • Posts: 147
[Fixed] Don't upgrade to chromium 50 for now!
« on: 2016/04/16, 13:47:37 »
It crashes on every site with a video. There is already a bug report that i can confirm for my notebook
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154
« Last Edit: 2016/04/24, 17:10:26 by gerd »

Offline devil

  • Administrator
  • User
  • *****
  • Posts: 4.842
Re: Don't upgrade to chromium 50 for now!
« Reply #1 on: 2016/04/16, 19:07:22 »
Chrome 50 does not show this behaviour.


greetz
devil

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: Don't upgrade to chromium 50 for now!
« Reply #2 on: 2016/04/16, 20:08:00 »
Neither does SRWare Iron 48.   ;)
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline ghstryder

  • User
  • Posts: 95
Re: Don't upgrade to chromium 50 for now!
« Reply #3 on: 2016/04/16, 23:15:47 »
With 50.0.2661.75-1 I get an "aw snap" when I try to load a page - however, it doesn't matter if the page has video. This did not happen prior to the last update. To make that more clear, Chromium will open, and I open three tabs on start-up. If I try to click on one of the tabs I get the "aw snap" error.

Chrome (Version 50.0.2661.75) does not exhibit this behavior
SRWare Iron 48 does not exhibit this behavior (and I'd use it full time if I could get flash to work!)
« Last Edit: 2016/04/16, 23:21:29 by ghstryder »

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: Don't upgrade to chromium 50 for now!
« Reply #4 on: 2016/04/16, 23:31:04 »
flash is no longer a kubuki dance for SRWare Iron, since pepperflash came along.  I am leaving the house at this moment, but tomorrow I'll write the 3 ofr 4 steps to get it done.

System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline ghstryder

  • User
  • Posts: 95
Re: Don't upgrade to chromium 50 for now!
« Reply #5 on: 2016/04/17, 00:04:53 »
Thank you dibl, I look forward to seeing your explanation.

I was inspired to try it again - as usual, I was concentrating so hard I missed the fact that they had a folder in the text I copied that I do not have.

With that corrected, I was able to open it from the terminal, with a few errors, but flash worked.
One of the errors was a sandbox error, but it seems to have corrected itself. I added the entry to the menu and it works fine.

Now, I just see the following errors if I open it from the terminal. I would certainly welcome input. I'm guessing the tracker and registration errors may not be all bad.
Code: [Select]
[4875:4891:0416/175221:ERROR:connection_factory_impl.cc(368)] Failed to connect to MCS endpoint with error -105
[4875:4875:0416/175223:ERROR:account_tracker.cc(357)] OnGetTokenFailure: Invalid credentials.
[4875:4875:0416/175223:ERROR:account_tracker.cc(357)] OnGetTokenFailure: Invalid credentials.
[4875:4891:0416/175223:ERROR:registration_request.cc(184)] URL fetching failed.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: Don't upgrade to chromium 50 for now!
« Reply #6 on: 2016/04/17, 13:44:33 »
Here is the note I wrote for myself (note in the EXEC line I use a temporary cache in /run/user -- you don't have to do that):


For PLasma 5 workspace

1. Install SRWare Iron
2. Install pepperflashplugin-nonfree
3. Open the file /usr/lib/pepperflashplugin-nonfree/manifest.json and in the line that begins "version" note the version number between the quote marks, for example "18.0.0.194".
4. Copy the file /usr/lib/pepperflashplugin-nonfree/libpepflashplayer.so to /usr/share/iron.
5. Open a text editor in root mode, and open /usr/share/applications/iron.desktop.
6. Change the "Exec" line as follows:


FROM: Exec=/usr/share/iron/iron
TO:   Exec=/usr/share/iron/iron  --disk-cache-dir=/run/user/1000/chromium-cache  --ppapi-flash-path=/usr/share/iron/libpepflashplayer.so --ppapi-flash-version=18.0.0.194 %U


(using the currently installed version of pepperflashplugin, of course).
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline mrsarmitage

  • User
  • Posts: 32
Re: Don't upgrade to chromium 50 for now!
« Reply #7 on: 2016/04/17, 14:46:04 »
chromium  50.0.2661.75 crasht beim Aufruf vom Gmail, lesen von mails nicht möglich.
[/size][/color]

Offline paxmark2

  • User
  • Posts: 85
Re: Don't upgrade to chromium 50 for now!
« Reply #8 on: 2016/04/17, 15:15:49 »

0.0.2661.75-1 Chromium gives me a "Snap" page all too often.  Reload rarely works.  I had never seen the snap page prior.     Firefox for me at this time.  have not tried with gmail. 


Offline ghstryder

  • User
  • Posts: 95
Re: Don't upgrade to chromium 50 for now!
« Reply #9 on: 2016/04/17, 15:28:51 »
Thanks dibl!

That is pretty much what I had, once I realized that I can't read.

Offline titan

  • User
  • Posts: 312
Re: Don't upgrade to chromium 50 for now!
« Reply #10 on: 2016/04/17, 18:17:58 »
Neither does SRWare Iron 48.   ;)


The SRWare site only compares Iron with Chrome I can't find a comparison with Chromium which would be more relevant. Are there any advantages I can't see any.

Offline dibl

  • siduction community member
  • Global Moderator
  • User
  • *****
  • Posts: 2.358
    • Land of the Buckeye
Re: Don't upgrade to chromium 50 for now!
« Reply #11 on: 2016/04/17, 19:41:53 »
I can't find a comparison with Chromium which would be more relevant.


I can't either.  Per that indisputable expert, wikipedia:


Quote
While Iron does not provide extra privacy compared to Chromium after proper settings are altered in the latter, it does implement some additional features that distinguish it from Google Chrome, such as built-in ad blocking.


and, I might add, less "aw-snapping".  :)
System76 Oryx Pro, Intel Core i7-11800H, SSD 970 EVO Plus;  Asus ROG STRIX X299-E, Core i7-7740X, Nvidia GTX-1060, dual monitors, SSD 860 EVO

Offline der_bud

  • User
  • Posts: 1.072
  • member
Re: Don't upgrade to chromium 50 for now!
« Reply #12 on: 2016/04/17, 21:12:47 »
Not a comparison, but a hint from their FAQ:
Quote
Can't i just use an precompiled unchanged Chromium-Build from the  Google Server?

This is not useful because the original Chromium-Builds have nearly the same functions inside than the original Chrome. We can only provide Iron because we massively modified the source.
Whatever that means... ;)
Du lachst? Wieso lachst du? Das ist doch oft so, Leute lachen erst und dann sind sie tot.

Offline titan

  • User
  • Posts: 312
Re: Don't upgrade to chromium 50 for now!
« Reply #13 on: 2016/04/18, 23:23:54 »
Looks like it is closed source and gives no advantage over Chromium or even Chrome https://en.wikipedia.org/wiki/SRWare_Iron

jdhedden

  • Guest
Re: Don't upgrade to chromium 50 for now!
« Reply #14 on: 2016/04/19, 05:15:38 »

According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=821154#34
Quote
I can confirm this problem for the sid package 50.0.2661.75-1 when
installed on testing.
However, the problem does not occur with the package
50.0.2661.75-1~deb8u1 from stable-security on testing, although it's
basically the same version of chrome.
I was able to obtain chromium-50.0.2661.75-1~deb8u1 here:  https://packages.debian.org/jessie/chromium
I can confirm that it does not have the 'snap' problem.  Installed it using 'sudo dpkg -i chromium_50.0.2661.75-1-deb8u1_amd64.deb', and then held it using 'sudo apt-mark hold chromium'.