Siduction Forum

Siduction Forum => Upgrade Warnings => Topic started by: horo on 2017/01/17, 22:23:00

Title: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: horo on 2017/01/17, 22:23:00

Solved by chromium 55.0.2883.75-5 today - to enable extensions call chromium as

Code: [Select]

chromium --enable-remote-extensions
Hi,
Today's DU breaks chromium / nach dem heutigen DU ist chromium unbrauchbar:
 

Code: [Select]

/usr/bin/chromium: 122: /usr/bin/chromium: Syntax error: "fi" unexpected (expecting "}")
It looks like it's related to a missing double-quote at the end of line 21 and it's fixed by the following patch:
Es scheinen die schließenden Anführungszeichen am Ende von Zeile 21 zu fehlen, Reparatur mit diesem Patch:

Code: [Select]

21c21
<   echo "        --enable-remote-extensions Allow extensions from remote sites
---
>   echo "        --enable-remote-extensions Allow extensions from remote sites"

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851634

Ciao, Martin

Title: Re: chromium 55.0.2883.75-4 unusable
Post by: finotti on 2017/01/18, 15:19:40

Confirmed here...  See the bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851634

Note that, for me at least. besides fixing the quote on line 21, I had to start chromium (as suggested in the bug report) with

Code: [Select]

chromium --enable-remote-extensions
or my extensions would not work.

Thanks for the heads up!

Title: Re: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: mithat on 2017/01/27, 01:13:21

I've documented a couple "set and forget" ways of applying the "--enable-remote-extensions" workaround here (https://lovingthepenguin.blogspot.com/2017/01/fixing-chromium-remote-extension_23.html). It works for me on Debian sid so I think it'll work on Siduction as well.

Title: Re: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: dibl on 2017/01/27, 17:47:25

Interesting that SRWare Iron ver. 55.0.2900.0 does not show the problem.

Title: Re: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: finotti on 2017/01/27, 19:30:05

Quote from: mithat on 2017/01/27, 01:13:21

I've documented a couple "set and forget" ways of applying the "--enable-remote-extensions" workaround here (https://lovingthepenguin.blogspot.com/2017/01/fixing-chromium-remote-extension_23.html). It works for me on Debian sid so I think it'll work on Siduction as well.

I'd never needed to add the "--enable-remote-extensions" until the  55.0.2883.75-4 version (with the fix), and I don't need it after that.  (Currently on version 55.0.2883.75-6.)

EDIT: I was wrong here.  My extensions were not present without the "--enable-remote-extensions" option.

Title: Re: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: mithat on 2017/01/27, 20:10:13

Quote from: finotti on 2017/01/27, 19:30:05

I'd never needed to add the "--enable-remote-extensions" until the  55.0.2883.75-4 version (with the fix), and I don't need it after that.  (Currently on version 55.0.2883.75-6.)

My reading of Debian bug report #851927 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851927) suggests that the new Debian policy is that remote extensions will now be disabled by default. Anyone have anything more concrete (or a different reading)?

Title: Re: [SOLVED] chromium 55.0.2883.75-4 unusable
Post by: finotti on 2017/01/31, 19:28:57

Quote from: mithat on 2017/01/27, 20:10:13

Quote from: finotti on 2017/01/27, 19:30:05

I'd never needed to add the "--enable-remote-extensions" until the  55.0.2883.75-4 version (with the fix), and I don't need it after that.  (Currently on version 55.0.2883.75-6.)

My reading of Debian bug report #851927 (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=851927) suggests that the new Debian policy is that remote extensions will now be disabled by default. Anyone have anything more concrete (or a different reading)?

It seems that I was wrong...  I indeed have no extensions if not using the "--enable-remote-extensions" option.  Sorry for the misinformation...