- User Since
- Jun 11 2019, 3:25 AM (37 w, 1 d)
Dec 17 2019
For anyone coming here, a workaround is to close and relaunch the software center. Over and over if necessary. I just had do this 6 or 7 times I think. No reboot is necessary.
The issue isn't unstable connections because of the server, it's unstable because of the geographical location of the server hosting the packages compared to your location, and all the hops in between. The connection is much less likely to fail if there are fewer hops. This is the main reason that a CDN exists in the first place, getting the data closer to you for lower latency, higher bandwidth, and fewer hops.
Nov 18 2019
Here is the submitted patch: https://github.com/getsolus/os-installer/pull/2
We know. It's not getting fixed until Fastly is in place
Nov 12 2019
Hi, good to see that it's a known issue. It happened to me on my first install on June 11.
And now it happened on my second install on another computer on another network.
Oct 2 2019
Aug 12 2019
Aug 6 2019
Jul 22 2019
Jul 15 2019
Fixed confirmed, thanks :)
Jul 8 2019
I can reproduce on another machine
- OS: Antergos (Arch Linux)
- Java version: 12
This current issue isn't about «Error: Attribution is not loaded yet» => one just have to zoom in and out a bit and tiles load. So lets forget about the Bing issue.
Great that you can reproduce.
Try with another imagery than Bing to see if you get the same rendering issues. Because Bing take few tries to load due to the attribution needing to be loaded first.
can you try launching it with java -jar /usr/share/josm/josm.jar?
Just tested with version 15155 and the issue still percists.
What can I do to investigate?
Jun 29 2019
Jun 28 2019
Added in T5874
Jun 27 2019
Multiple version cohabitation: for a first step, is cohabitation needed from a user (non-dev) point of view?
For example I would like a JRE > 8 to make JOSM (or any app) faster and allow the devs to deprecate JRE 8 sooner and don't be stuck with only the Java features from 5 years ago.
Jun 19 2019
Hi @JoshStrobl , it doesn't seems to be a duplicate of T1216, because the issue is that I don't get to choose the layout so it's defaulted to qwerty. So it is normal that the initramfs gets a qwerty layout.
In the mentioned ticket, they can choose their layout in the installer. While in this case, I can't choose a layout in the installer, that's the issue.