Bug#855324: pdfsam fails to start

[tony mancill]

On Sun, Feb 19, 2017 at 11:36:05PM +0100, gregor herrmann wrote:
> On Sun, 19 Feb 2017 18:09:22 +0100, Philip Rinn wrote:
> 
> > On 19.02.2017 at 04:56, gregor herrmann wrote:
> > > After this change, pdfsam starts for me and shows me an empty white
> > > window (or grey-ish) with nothing in it.
> > Uh, strange. So this seems not to be a general fix :(
> > Gregor, could you try '0'?
> 
> With "0" I still get an empty greyish window and nothing more.

Ugh!  I'm just guessing, but I suspect you are now seeing a *different*
issue related to one of the AWT race conditions we seem to encounter
from time to time.  If you're willing to try with another window
manager, that might tell us something.  You can also try exporting
"NOISY_AWT=true" and hitting CTRL-Shift-F1 to dump the AWT component
hierarchy [1] (and then sending that to me so I can compare it with the
hierarchy I see on my system).

But the larger question of whether pdfsam is fit for stretch is probably
the more pressing.  The Debian packaging is quite dated at this point
[2], and while looking into this issue, I noticed that the Debian
version phones home for an update check during its startup...  :(

Cheers,
tony

[1] http://www.oracle.com/technetwork/java/javase/awt-138016.html#gchlz
[2] https://github.com/torakiki/pdfsam/releases
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-java-maintainers/attachments/20170220/fed651e8/attachment-0001.sig>