Bug#852398: same here

2017-03-29 Thread my
Dear Devs, This is not really helpful at all, as whatever the intention was, the easy solution was to install google-chrome, which is hardly a solution at all. Whether we like it or not, many things we need are neither free nor open source, and this compilation means one must either use

Bug#852398: STILL PRESENT on Version 57.0.2987.98 built on Debian 9.0, running on Debian 9.0 (64-bit)

2017-03-29 Thread Michael Wilson
This is getting beyond an absolute joke. It has been over a month since the community has spoken of this issue and the maintainer has said almost nothing. This is clearly just a terrible decision made by the maintainer. It is a major usability issue. How are we to expect new users to join Debian

Bug#852398: Issue still present in 57.0.2987.98-1

2017-03-23 Thread Lev Livnev
Just upgraded to 57.0.2987.98-1 on stretch, the bug is still present. Can confirm that CHROMIUM_FLAGS='--enable-remote-extensions' workaround is effective.

Bug#852398: Updated 56.0.2924.76-5 still contains bug

2017-03-10 Thread Alexander Davis
I am using Debian Stretch. I had noticed this bug on Chromium for the past few weeks or so and had therefore been refusing to update it. Listbug did not show the bug for the past day or two so today I decided to update Chromium. When I updated and ran chromium, I was no longer able to install

Bug#852398: chromium: I updated to 56.0.2924.76-5 earlier today and after the update was thereafter unable to install either extensions or Chrome Apps.

2017-03-10 Thread alex
Package: chromium Version: 56.0.2924.76-5 Followup-For: Bug #852398 Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What

Bug#852398: chromium: Issue not resolved

2017-03-05 Thread Kyle Bentley
Package: chromium Version: 56.0.2924.76-4 Followup-For: Bug #852398 Dear Maintainer, Problem is still present in stretch; launching /usr/bin/chromium doesn't bring up previously installed or enabled extensions. -- System Information: Debian Release: 9.0 APT prefers testing APT policy

Bug#852398: Chromium might as well be broken

2017-03-03 Thread Kyle Bentley
I'll chime in and state that this was a terrible idea. I'm not sure what outcome was expected, but breaking normal behavior for no good reason is just insane. I'd go as far as suspecting sabotage! Why else would disabling extensions, without so much as a warning, have been done? Please revert

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-02-09 Thread Andrea
Package: chromium Version: 56.0.2924.76-3 Followup-For: Bug #852398 Like other users, I am also very disappointed by this change of behaviour. The user is not warned in any way that his extensions are not loaded by default anymore. I had to hack into /usr/bin/chromium script to re-enable them. I

Bug#852398:

2017-02-07 Thread Carter Kolwey
Disabling part of the functionality of a program for no apparent reason, while providing no information about why it was disabled or how to re-enable it ("Installation is not enabled" does not qualify) counts as breaking it, IMHO, especially since the internet is nearly unusable without extensions

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-02-07 Thread k_f
The current behavior is really, really bad since it exposes users, who thought a little of their privacy by installing privacy extensions like privacy badger (EFF privacy extension), no-script, ad-blocker or other extensions like that to the websites and ad networks. Next time you do something

Bug#852398: current behavior stops security extensions

2017-02-07 Thread k_f
The current behavior is really, really bad since it exposes users, who thought a little of their privacy by installing privacy extensions like privacy badger (EFF privacy extension), no-script, ad-blocker or other extensions like that to the websites and ad networks. Next time you do something

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-02-06 Thread Niels Elgaard Larsen
På Mon, 6 Feb 2017 21:09:16 +0100 Michael Franzl skrev: > On Mon, 6 Feb 2017 11:27:55 +0100 Simon Ruderich CHROMIUM_FLAGS='--enable-remote-extensions' chromium > > I put this into ~/.profile: > >

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-02-06 Thread Michael Franzl
On Mon, 6 Feb 2017 11:27:55 +0100 Simon Ruderich wrote: > Setting the option in a environment variables seems to work as > workaround for me: > > CHROMIUM_FLAGS='--enable-remote-extensions' chromium I put this into ~/.profile:

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-02-06 Thread Simon Ruderich
severity 852398 important thanks Package: chromium Version: 56.0.2924.76-3 Followup-For: Bug #852398 Hello, Setting the option in a environment variables seems to work as workaround for me: CHROMIUM_FLAGS='--enable-remote-extensions' chromium However I urge you to change the default back

Bug#852398: To load extensions

2017-02-03 Thread Édouard WILLISSECK
This workaround works great thanks ! I hope we'll get a proper fix soon though. On Wed, 01 Feb 2017 00:29:50 + Alok Singh wrote: > Copying this over from #851692. A method of enabling extensions without > re-compiling Chromium. Not saying it is ideal >  > 1. Find your

Bug#852398: To load extensions

2017-01-31 Thread Alok Singh
Copying this over from #851692. A method of enabling extensions without re-compiling Chromium. Not saying it is ideal 1. Find your extensions: They are in $XDG_CONFIG_DIR/chromium//Extensions// For example, uBlock is at

Bug#852398: Severity

2017-01-31 Thread Douglas Perkins
I agree with others: the severity is more than minor. I would say it's important, and at the least normal. With AdBlock unavailable, many websites that were fine before become borderline unusable. To me and many others, that's a major usability problem.

Bug#852398: Extensions broken

2017-01-30 Thread Tim
I too can confirm that extensions are broken in chromium. Many users rely on extensions to perform basic tasks on a day to day basis. For me, the lost of extensions is much more than a minor severity issue. Please remove the whacky extension-blocking patches until this policy can be

Bug#852398:

2017-01-25 Thread allan
Can duplicate on 32-bit Sid. Extensions are broken.

Bug#852398: chromium: option --enable-remote-extensions does work: extensions cannot be enabled nor be installed

2017-01-24 Thread Ara Keary
Package: chromium Version: 55.0.2883.75-6 Severity: normal Dear maintainers, remote extensions are disabled now by default I understand that official chrome extensions such as Adblock Plus (or similar ones) and non-official extensions can be enabled and can be installed only if the