The point is this...natively this package(38.0.2125.101-2) is > broken...so this bug will not be fixed because there is a way of > forcing the API keys google???
> Can someone explain this new policy? I use debian testing and I expect > software fairly stable and functioning(I'm aware of some sporadic bug) > > I do not want to open controversy....only understand the situation...I > do NOT want to sound arrogant...I am aware that the work of the > maintener is the fruit of your free time...I respect that.... Have a nice day Marco
