#7672 closed defect (othersoftware)
half screen artifacts on second link in bug report dialogue
Reported by: | skyper | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Core | Version: | latest |
Keywords: | bug report artifact link | Cc: |
Description
- get an exception
- (switch user with gdm3)
- (log out second user and switch back to previous virtual terminal)
- move mouse on second link in bug report dialogue
- wait 1-2 seconds
I get artifacts across the whole lower half of the screen instead of the link info.
Both other links work.
Do not know if this is caused by switching the virtual terminals or maybe gnome3.
Repository Root: http://josm.openstreetmap.de/svn Build-Date: 2012-05-05 01:31:01 Last Changed Author: simon04 Revision: 5211 Repository UUID: 0c6e7542-c601-0410-84e7-c038aed88b3b URL: http://josm.openstreetmap.de/svn/trunk Last Changed Date: 2012-05-04 19:15:59 +0200 (Fri, 04 May 2012) Last Changed Rev: 5211 Identification: JOSM/1.5 (5211 en) Memory Usage: 388 MB / 1820 MB (119 MB allocated, but free) Java version: 1.6.0_24, Sun Microsystems Inc., OpenJDK 64-Bit Server VM Operating system: Linux Dataset consistency test: No problems found Plugin: PicLayer (27883)
Debian wheezy (testing), gnome3, gdm3, gtk3
Attachments (1)
Change History (9)
by , 12 years ago
Attachment: | artifacts_on_link.png added |
---|
comment:2 by , 12 years ago
Replying to anonymous:
If you are on testing, have you tried openjdk-7?
I did test on a different machine using the test files from #7266:
- with openjdk-6 I got artifacts on all links
- with openjdk-7 no problem the link info is show.
java version "1.6.0_24" OpenJDK Runtime Environment (IcedTea6 1.11.1) (6b24-1.11.1-3) OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)
and
java version "1.7.0_03-icedtea" OpenJDK Runtime Environment (IcedTea7 2.1) (7~u3-2.1-3) OpenJDK 64-Bit Server VM (build 22.0-b10, mixed mode)
follow-up: 4 comment:3 by , 12 years ago
Resolution: | → othersoftware |
---|---|
Status: | new → closed |
comment:4 by , 12 years ago
follow-up: 6 comment:5 by , 12 years ago
I don't know it, sorry. But if it works with openjdk-7, it's not JOSM fault, hence the "othersoftware" resolution. Have you tried to contact openjdk-6 maintainers on Debian side ?
comment:6 by , 12 years ago
Replying to Don-vip:
I don't know it, sorry. But if it works with openjdk-7, it's not JOSM fault, hence the "othersoftware" resolution. Have you tried to contact openjdk-6 maintainers on Debian side ?
No, JOSM is written for java 1.6 not 1.7, or did I miss something.
Is it a debian bug or a java bug ?
I did not contact any maintainer as I did not know if JOSM source did change or if it was a bug introduced by a java update but if you can tell me that JOSM did not change or that it is working with other distributions I will definitly fill a bug report.
comment:7 by , 12 years ago
I have never seen such artefacts with openSUSE using Sun6 Java and openJDK6. Even if JOSM does something wrong (which I doubt) the result is in any case an issue with java or the windowing system, as a java application should not be allowed to produce such an error.
screenshot