From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Thomas Schmitt" <scdbackup@gmx.net>
Subject: bug#33639: ISO installer image is broken on i686
Date: Wed, 10 Apr 2019 13:17:14 +0200
Message-ID: <16217671677318139528@scdbackup.webframe.org>
References: <20190409221313.b3uzvcj5bluoygp5@pelzflorian.localdomain>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([209.51.188.92]:60168)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hEBD1-0004fg-Et
	for bug-guix@gnu.org; Wed, 10 Apr 2019 07:16:04 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Debian-debbugs@debbugs.gnu.org>) id 1hEBD0-00071r-AI
	for bug-guix@gnu.org; Wed, 10 Apr 2019 07:16:03 -0400
Received: from debbugs.gnu.org ([209.51.188.43]:38888)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <Debian-debbugs@debbugs.gnu.org>)
	id 1hEBD0-00071Z-3t
	for bug-guix@gnu.org; Wed, 10 Apr 2019 07:16:02 -0400
Sender: "Debbugs-submit" <debbugs-submit-bounces@debbugs.gnu.org>
Resent-Message-ID: <handler.33639.B33639.155489493627999@debbugs.gnu.org>
In-Reply-To: <20190409221313.b3uzvcj5bluoygp5@pelzflorian.localdomain>
List-Id: Bug reports for GNU Guix <bug-guix.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/bug-guix/>
List-Post: <mailto:bug-guix@gnu.org>
List-Help: <mailto:bug-guix-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-guix>,
	<mailto:bug-guix-request@gnu.org?subject=subscribe>
Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org
Sender: "bug-Guix" <bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org>
To: bug-xorriso@gnu.org
Cc: 33639@debbugs.gnu.org

Hi,

Ludovic Court=C3=A8s wrote:
> > Florian: could you check whether the patch below solves the problem fo=
r
> > you?

Florian Pelz wrote:
> No, sadly not.

Given the smell of a race condition, i would next try to let the VM
wait 10 or 15 seconds after xorriso is finished and before it shuts down.

Not as a final remedy but just as proof that the VM end is really the
culprit. (It could also be an i/o problem between VM and host which
is unrelated to the VM end.)


Have a nice day :)

Thomas