to
clearly define expectations/guidelines on how the chromium package will interact
with Google. Right now, Debian's stance seems inconsistent at best, and that is
creating a confusing user experience.
Regards,
Eloston
omium-79.0.3945.79
$ dpkg-buildpackage -b -uc
After several hours, packages should appear in chromium-
c88b97a6dc183a6a7f8a05aee9e99957285a9371
Regards,
Eloston
commit 9a07b14585c4948d3baf2763d0f71ac5b3af758c
Author: Eloston
Date: Mon Dec 30 21:34:23 2019 +
Revert disabling tracing
d
. cd chromium-x.x.x.x && dpkg-buildpackage -b
-uc
NOTE: These changes will make the browser depend on minified javascript files
again, which was the original motivation for disabling tracing (as noted in the
header of disable/tracing.patch).
Hope that helps,
Eloston
at st-widget.c:603
> Control: forwarded -1 https://gitlab.gnome.org/GNOME/gnome-shell/issues/1018
>
> On Mon, 15 Apr 2019 at 12:12:36 -0700, Eloston wrote:
> > Just using GNOME normally causes the crash to happen.
>
> This is probably going to make it hard to fix the crash
Package: gnome-shell
Version: 3.30.2-3
Severity: critical
Justification: causes serious data loss
Dear Maintainer,
* What led up to the situation?
Just using GNOME normally causes the crash to happen.
* What exactly did you do (or not do) that was effective (or
ineffective)?
On Thu, 6 Sep 2018 19:50:24 -0700 Josh Triplett wrote:
>
> This is not in any way an explanation. "users have stated concern" -
> *what* concern?
>
> At the very least, this needs an explanation commensurate with "why is
> it important to break people's ability to do screen sharing by default
>
6 matches
Mail list logo
