On Fri, Jan 11, 2019 at 1:03 PM Patrick Häcker wrote:
> I can confirm, that version 72.0.3626.7-6 is fixing the issue. Thanks a lot
> for
> pointing me to the unstable version.
>
> So as soon as this version enters testing, this bug report can be closed.
It can't be closed because the problem
Hi Tom,
> On 20 Dec 2018, at 17:10, Patrick Häcker wrote:
> > Maybe you can elaborate on your working setup.
>
> I've just run a dist-upgrade and 72.0.3626.7-6 installed and works.
I can confirm, that version 72.0.3626.7-6 is fixing the issue. Thanks a lot for
pointing me to the unstable
On 20 Dec 2018, at 17:10, Patrick Häcker wrote:
> you wrote on the upstream bug tracker that you have resolved the issue with
> an
> upgrade and version 70.0.3538.67-2. Did you upgrade to testing? Maybe you can
> elaborate on your working setup.
>
> I upgraded to testing, but to no avail. As
Hi Tom,
you wrote on the upstream bug tracker that you have resolved the issue with an
upgrade and version 70.0.3538.67-2. Did you upgrade to testing? Maybe you can
elaborate on your working setup.
I upgraded to testing, but to no avail. As there is no testing or unstable
armhf version of
Hi,
I have reported this upstream:
https://bugs.chromium.org/p/chromium/issues/detail?id=877480
Kind Regards
--
Tom
Hi,
I don't think it is related to a minor update, it seemed to break when
going from version 67 to 68.
I tried some packages from snapshot and it works with:
https://snapshot.debian.org/package/chromium-browser/67.0.3396.87-1/
and crashes with:
6 matches
Mail list logo
