[DebianGIS-dev] Bug#474626: #474626: still happens here

2008-08-04 Thread Bernd Zeimetz 
reopen 474626
found 474626 0.0.0.20080713-1
thanks

Hi,

 I guess it's your decision to make.  I can't say I'll hate you for it,
 since josm works fine for me with openjdk-6 :-)

unfotunately this is not the case for me, the window just stays white
here. Looking at the output of strace it seems to be stuck in a futex,
but I didn't see any useful informations on the first look. I've also
tried to run it in sun java 6, but still no output.
If there's anything I can help you with, please let me know.

Cheers,

Bernd

-- 
 Bernd Zeimetz   Debian GNU/Linux Developer
 GPG Fingerprint: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79



___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

[DebianGIS-dev] Processed: Re: Bug#474626: #474626: still happens here

2008-08-04 Thread Debian Bug Tracking System 
Processing commands for [EMAIL PROTECTED]:

 reopen 474626
Bug#474626: JOSM interface is empty
'reopen' may be inappropriate when a bug has been closed with a version;
you may need to use 'found' to remove fixed versions.
Bug reopened, originator not changed.

 found 474626 0.0.0.20080713-1
Bug#474626: JOSM interface is empty
Bug marked as found in version 0.0.0.20080713-1.

 thanks
Stopping processing here.

Please contact me if you need assistance.

Debian bug tracking system administrator
(administrator, Debian Bugs database)


___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

[DebianGIS-dev] Bug#474626: Bug#474626: #474626: still happens here

2008-08-04 Thread Andreas Putzo 
Hi,

On Aug 04  11:01, Bernd Zeimetz wrote:
  unfotunately this is not the case for me, the window just stays white
  here. Looking at the output of strace it seems to be stuck in a futex,
 
 the gps traces server is down today, could this be the reason?

No, josm should at least start. Downloading gps traces works anyway, only
uploading is currently disabled.

Maybe you can see something with jdb from the opendj-6-jdk package.

$ /usr/lib/jvm/java-6-openjdk/bin/jdb -classpath 
/usr/share/java/metadata-extractor.jar:/usr/share/java/gettext-commons.jar:/usr/share/josm/josm.jar
 org.openstreetmap.josm.gui.MainApplication
$  run 
$  suspend
$  where all

for a start..

Regards,
Andreas



___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel

[DebianGIS-dev] Bug#474626: Bug#474626: #474626: still happens here

2008-08-04 Thread Bernd Zeimetz 
Hi,

 Maybe you can see something with jdb from the opendj-6-jdk package.

Let's give it a try :)

 $ /usr/lib/jvm/java-6-openjdk/bin/jdb -classpath 
 /usr/share/java/metadata-extractor.jar:/usr/share/java/gettext-commons.jar:/usr/share/josm/josm.jar
  org.openstreetmap.josm.gui.MainApplication
 $  run 
 $  suspend
 $  where all

127 [EMAIL PROTECTED]:/tmp$ /usr/lib/jvm/java-6-openjdk/bin/jdb -classpath
/usr/share/java/metadata-extractor.jar:/usr/share/java/gettext-commons.jar:/usr/share/josm/josm.jar
org.openstreetmap.josm.gui.MainApplication
Initializing jdb ...
 run
run org.openstreetmap.josm.gui.MainApplication
Set uncaught java.lang.Throwable
Set deferred uncaught java.lang.Throwable

VM Started: mappaint: Using jar's elemstyles.xml:
jar:file:/usr/share/josm/josm-0.0.0.20080713.jar!/styles/standard/elemstyles.xml
Mappaint: Icon nautical/viaduct.png not found, using default icon

 suspend
All threads suspended.
 where all
Signal Dispatcher:
Finalizer:
  [1] java.lang.Object.wait (native method)
  [2] java.lang.ref.ReferenceQueue.remove (ReferenceQueue.java:133)
  [3] java.lang.ref.ReferenceQueue.remove (ReferenceQueue.java:149)
  [4] java.lang.ref.Finalizer$FinalizerThread.run (Finalizer.java:177)
Reference Handler:
  [1] java.lang.Object.wait (native method)
  [2] java.lang.Object.wait (Object.java:502)
  [3] java.lang.ref.Reference$ReferenceHandler.run (Reference.java:133)
Java2D Disposer:
  [1] java.lang.Object.wait (native method)
  [2] java.lang.ref.ReferenceQueue.remove (ReferenceQueue.java:133)
  [3] java.lang.ref.ReferenceQueue.remove (ReferenceQueue.java:149)
  [4] sun.java2d.Disposer.run (Disposer.java:143)
  [5] java.lang.Thread.run (Thread.java:636)
AWT-XAWT:
  [1] sun.awt.X11.XToolkit.waitForEvents (native method)
  [2] sun.awt.X11.XToolkit.run (XToolkit.java:543)
  [3] sun.awt.X11.XToolkit.run (XToolkit.java:518)
  [4] java.lang.Thread.run (Thread.java:636)
Keep-Alive-Timer:
  [1] java.lang.Thread.sleep (native method)
  [2] sun.net.www.http.KeepAliveCache.run (KeepAliveCache.java:168)
  [3] java.lang.Thread.run (Thread.java:636)
AWT-Shutdown:
  [1] java.lang.Object.wait (native method)
  [2] java.lang.Object.wait (Object.java:502)
  [3] sun.awt.AWTAutoShutdown.run (AWTAutoShutdown.java:281)
  [4] java.lang.Thread.run (Thread.java:636)
AWT-EventQueue-0:
  [1] java.lang.Object.wait (native method)
  [2] java.lang.Object.wait (Object.java:502)
  [3] java.awt.EventQueue.getNextEvent (EventQueue.java:484)
  [4] java.awt.EventDispatchThread.pumpOneEventForFilters
(EventDispatchThread.java:247)
  [5] java.awt.EventDispatchThread.pumpEventsForFilter
(EventDispatchThread.java:200)
  [6] java.awt.EventDispatchThread.pumpEventsForHierarchy
(EventDispatchThread.java:190)
  [7] java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:185)
  [8] java.awt.EventDispatchThread.pumpEvents (EventDispatchThread.java:177)
  [9] java.awt.EventDispatchThread.run (EventDispatchThread.java:138)
DestroyJavaVM:




stracing the running process shows a loop consisting of

[pid 19263] ... futex resumed )   = -1 ETIMEDOUT (Connection timed
out)
[pid 19263] futex(0x610dc8, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19263] futex(0x610df4, 0x80 /* FUTEX_??? */, 1 unfinished ...
[pid 19278] ... futex resumed )   = -1 ETIMEDOUT (Connection timed
out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278] futex(0x41a19d38, 0x81 /* FUTEX_??? */, 1) = 0
[pid 19278] futex(0x41a19d64, 0x80 /* FUTEX_??? */, 1) = -1 ETIMEDOUT
(Connection timed out)
[pid 19278]

[DebianGIS-dev] Bug#474626: Bug#474626: Bug#474626: #474626: still happens here

2008-08-04 Thread Andreas Putzo 
On Aug 04  20:38, Bernd Zeimetz wrote:
 
 Looking at this I started to wonder if the bug is really in josm, so
 I've tried it with a different window manager and I had to realize that
 it works well in Fluxbox. What I'm using at the moment is xmonad as
 window manager within KDE, so the problem seems to be somewhere within
 java, xmonad and KDE...

That's indeed interesting and i can reproduce it with xmonad (without
kde).
Funny thing is if you start josm with java -verbose -jar
/usr/share/josm/josm.jar and click with the mouse in the grey josm
window you trigger click events and i even managed to produce a correct
popup window with this.
I tried freemind, which also uses java swing, and this works fine in
xmonad, so it might well be something weird in josm, though i didn't
spot anything at a first glance.

Regards,
Andreas




___
Pkg-grass-devel mailing list
Pkg-grass-devel@lists.alioth.debian.org
http://lists.alioth.debian.org/mailman/listinfo/pkg-grass-devel