-----BEGIN PGP SIGNED MESSAGE-----
Thanks for the additional information.
On 13-09-15 20:06, Jonas Smedegaard wrote:
> Quoting Jonas Smedegaard (2015-09-13 18:47:18)
>> Quoting Sebastiaan Couwenberg (2015-09-13 17:57:34)
>>> On 13-09-15 17:18, Jonas Smedegaard wrote:
>>>> Choosing either Open or Open from OSM provides a blank
>>>> JOSM seems completely useless to me currently.
>>> I'm sorry to hear josm is not working for. Unfortunately I
>>> cannot reproduce the problem. It works as expected on my
>>> freshly upgrade unstable VM.
>>> A broken fileselector leads me to think GTK is not in order on
>>> your system.
>> Did you test also the Open from OSM?
I did, and that works as expected too. Opening local OSM files too.
>>> Can your start josm with --debug and provide this logging, it
>>> may help pinpoint the issue on your system.
> Attached are now debug output from these two commands:
> JAVACMD=/usr/lib/jvm/java-8-openjdk-amd64/jre/bin/java LANG=C josm
> --debug | tee josm-openjdk8 LANG=C josm --debug | tee
> The first command is because apparently the JOSM wrapper script
> fails to respect my "update-java-alternatives --set
josm like many other Java packages have a startup script that tests
JRE paths, that doesn't support openjdk-8 yet, nor does it use the
> In both cases, the output until and including "INFO: Enabled EDT
> checker..." was emitted _before_ final version info splash screen
> was rendered and I selected "Download from OSM..." - only the final
> "DEBUG: TMS - found in tile cache:..." lines was emitted when I was
> presented with a blank window that I could only continue from by
> hitting CTRL+c - and then I quit the program.
I've tested both Plasma/KDE and GNOME 3, under both josm works as
expected. So it's not a GNOME 3 specific issue at least. I've also
tested both openjdk-7 & 8, and josm also works as expected with both.
Your debug output doesn't show anything out of the ordinary. So I
still have no clue what's different on your system to break josm.
Maybe a GPU driver issue that fumbles drawing the new windows.
Please try the upstream JOSM releases, those are a better choice
anyway due to the inability of updating the Debian package.
If you don't trust the upstream builds or otherwise don't want to use
them, you can try moving your ~/.josm out of the way and having josm
create a new profile. There may be a broken plugin or configuration in
your JOSM profile.
GPG Key ID: 4096R/6750F10AE88D4AF1
Fingerprint: 8182 DE41 7056 408D 6146 50D1 6750 F10A E88D 4AF1
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2
-----END PGP SIGNATURE-----
Pkg-grass-devel mailing list