-----BEGIN PGP SIGNED MESSAGE-----
On 14-09-15 00:23, Sebastiaan Couwenberg wrote:
> On 14-09-15 00:07, Jonas Smedegaard wrote:
>> Quoting Jonas Smedegaard (2015-09-14 00:00:23)
>>> Quoting Sebastiaan Couwenberg (2015-09-13 22:09:11)
>>>> 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.
>>> My machine is a Lenovo Edge 145 laptop with AMD Radeon HD 8240
>>> GPU using the free driver.
>>> A possible difference - if you tested with both those DEs
>>> installed - might be some package dependency missing from josm
>>> or a java library which gets pulled in by larger DEs and
>>> therefore often unnoticed. I use Awesome and mostly GTK-based
>>> applications, avoiding both KDE and GNOME as much as I can. I
>>> do generally respect recommends, however - attached is the list
>>> of unsatisfied reverse recommends (too long, as some are
>>> satisfied by alternative packages).
> Awesome doesn't appear to be a good choice of DE. I can reproduce
> the problem with josm under awesome. This issue should probably be
> reassigned to awesome, this isn't an issue with josm.
I've tested this issue with the new JOSM 8800 from experimental, which
still has this issue.
Interestingly the 'Download from OSM' window does work, new tiles get
downloaded when zooming with the scroll wheel and hitting enter
downloads the area in question, it just doesn't get rendered.
Jonas, do you think it's worthwhile to reassign this issue to awesome?
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