<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p>UPDATE: Chromium came back to life after upgrade to version
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<span style="color: rgb(48, 57, 66); font-family: "DejaVu
Sans", Arial, sans-serif; font-size: 12px; font-style:
normal; font-variant-ligatures: normal; font-variant-caps:
normal; font-weight: normal; letter-spacing: normal; orphans: 2;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: 2; word-spacing: 0px;
-webkit-text-stroke-width: 0px; display: inline !important;
float: none;">56.0.2924.76. Thank you!<br>
<br>
<br>
</span></p>
<br>
<div class="moz-cite-prefix">Em 17-02-2017 01:00, Debian Bug
Tracking System escreveu:<br>
</div>
<blockquote class=" cite"
id="mid_handler_854925_D854925_148730030725744_notifdone_bugs_debian_org"
cite="mid:handler.854925.D854925.148730030725744.notifdone@bugs.debian.org"
type="cite">
<pre wrap="">This is an automatic notification regarding your Bug report
which was filed against the chromium package:
#854925: chromium: Chromium does not start -- execv failed: No such file or directory
It has been closed by Michael Gilbert <a class="moz-txt-link-rfc2396E" href="mailto:mgilbert@debian.org"><mgilbert@debian.org></a>.
Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Michael Gilbert <a class="moz-txt-link-rfc2396E" href="mailto:mgilbert@debian.org"><mgilbert@debian.org></a> by
replying to this email.
</pre>
</blockquote>
<br>
<div class="moz-signature"><br>
</div>
</body>
</html>