Does anyone have access to a Debian testing/unstable system? Could you
check if Etoys really gets stuck, and maybe figure out why?

I suspect it might be because they're running on x86_64. The VM is
4.10.2-2614.

- Bert -

---------- Forwarded message ----------
From: Víctor Bettachini <victorb at gmx.net>
Date: Sun, May 14, 2017 at 9:50 PM
Subject: Bug#862576: etoys: Doesn't get beyond Squeak security key
generation
To: Debian Bug Tracking System <submit at bugs.debian.org>


Package: etoys
Version: 5.0.2408-1
Severity: grave
Justification: renders package unusable

Dear Maintainer,

*** Reporter, please consider answering these questions, where appropriate
***

   * What led up to the situation?
        Just running etoys&.
   * What exactly did you do (or not do) that was effective (or
     ineffective)?
        Run etoys&
   * What was the outcome of this action?
        It gets stuck at 99% of the Squeak security key generation
procedure.
   * What outcome did you expect instead?
        The same procedure in a Jessie installation in the same system just
took a few seconds and led to eToys main screen.

*** End of the template - remove these template lines ***


-- System Information:
Debian Release: 9.0
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: amd64
 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.9.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=es_AR.utf8, LC_CTYPE=es_AR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages etoys depends on:
ii  squeak-vm  1:4.10.2.2614-4+b1

Versions of packages etoys recommends:
ii  etoys-doc  5.0.2408-1

etoys suggests no packages.

-- no debconf information
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20170523/38396084/attachment.html>