Bug#798855: java.io.FileNotFoundException: /usr/share/josm/images/none

[Jonas Smedegaard]

retitle 798855 josm: Download from OSM... gives just a blank window
thanks

Quoting Sebastiaan Couwenberg (2015-09-13 17:57:34)
> On 13-09-15 17:18, Jonas Smedegaard wrote:
>> On a fresh install on an up-to-date Sid I get this warning while 
>> starting JOSM:
>> 
>> java.io.FileNotFoundException: /usr/share/josm/images/none
>> 
>> ...and then a long stacktrace.
>
> The missing images exceptions are nothing to worry about.
>
> openstreetmap-map-icons misses few images that are available in the 
> upstream josm build as jar resources.

Ok.  Then I'll ignore above problem, and we both please ignore it for 
this bugreport.


>> Choosing either Open or Open from OSM provides a blank window.
>>
>> 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.

Whoops - I thought it was both but in fact it was only the OSM one - 
specifically it is "Download from OSM...". standard GTK+ dialogue pops 
up fine.

Did you test also the Open from OSM?


> Can your start josm with --debug and provide this logging, it may help 
> pinpoint the issue on your system.

Using /usr/lib/jvm/java-7-openjdk-amd64/bin/java to execute josm.
INFO: Look and Feel not found: javax.swing.plaf.gtk.GTKLookAndFeel

Oh, indeed it spits above as very first line when starting.

With --debug enabled the startup spits a bunch of extra messages, but 
none when I select the "Download from OSM..." menu item.

You think that dump from startup is any relevant?



>> Splash screen claims the version is odd and there's a newer stable 
>> release - I have no idea if that's related...
>
> There have been several new JOSM releases, but they all require JCS 
> which I've not had much luck getting packaged for Debian (#783538). 
> The recent JMapViewer release now likewise require JCS and cannot be 
> updated in Debian until we get JCS packaged.
>
> Help is very much appreciated. If I cannot get JCS packaged before the 
> freeze, I'll have JOSM removed from the archive.

I have now read a few of the trail of bugreports.  I can see how it is 
frustrating :-(

I will have your plea for help in mind, but am cautious not to get too 
involved (already maintain 400+ packages and will likely add ~50 more 
for Beaker Notebook)...


> Several of the popular plugins now require newer JOSM versions than we 
> have available in Debian, so the josm package is becoming increasingly 
> irrelevant anyway.

Uhm, I don't follow your "ayway" above: Is the problem of plugins no 
longer compatible with Debian release of JOSM not solved together with 
the JOSM upgrade issues described above?


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-grass-devel/attachments/20150913/9b93689a/attachment.sig>