Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maptiler Key does not work in Ubuntu but works in Windows 11 #253

Open
STfanboy1981 opened this issue Jul 27, 2024 · 8 comments
Open

Maptiler Key does not work in Ubuntu but works in Windows 11 #253

STfanboy1981 opened this issue Jul 27, 2024 · 8 comments
Labels
bug Something isn't working

Comments

@STfanboy1981
Copy link

STfanboy1981 commented Jul 27, 2024

Hello,

I have Ubuntu 24.04 with version 0.4.5 in xorg and when I try to put the API key in from Maptiler I still get a black screen. I thought I needed to close and reopen the program but it's still doing the same thing. I even restarted and again a black screen. So I booted on the windows side of my PC and used the same key and set the same settings. The Windows 11 version works just fine. I even tried on my Windows 11 gaming laptop. Works there too. Do you know what would be the cause of this?

Also, Both the Ubuntu and Windows versions will not switch to fusion modes.

Thank you

@STfanboy1981 STfanboy1981 added the bug Something isn't working label Jul 27, 2024
@dpaulat
Copy link
Owner

dpaulat commented Jul 27, 2024

Selecting a theme requires restarting the application. On Linux, Fusion is many times already the default. Fusion may or may not currently present a dark mode based on Window manager settings.

Ubuntu should work the same as you're experiencing in Windows. You can find configuration and logs located in ~/.local/share/Supercell Wx on Linux. If the API key in settings.json looks correct, can you provide me with a log file from that directory?

@STfanboy1981
Copy link
Author

Thank you for responding. Yeah, that's what I was looking for is a dark mode. I'm a noob at Linux so where would I find the window manager? I've attached the log file.
supercell-wx.57092.log

@STfanboy1981
Copy link
Author

I also looked in the settings file and the Key is correct but it did have a question mark in front of it. I deleted it and saved and relaunched the program. I got the same thing with the black screen.

@dpaulat
Copy link
Owner

dpaulat commented Jul 28, 2024

I see the following in the log:
[2024-07-27 14:04:10.414] [57121] [warning] [scwx::qt::manager::update_manager] Invalid API response: [0] SSL: couldn't create a context: error:0A080024:SSL routines::reason(36)

Are you by chance running with a Ryzen 3000 series CPU? You may need to apply a BIOS update.

Another user found this a couple weeks ago. The 3000 series has a bug with its random number generator that the OpenSSL dependency does not like. Supercell Wx is unable to establish any HTTPS/TLS connections (GitHub update check, warnings, map and radar data).

@STfanboy1981
Copy link
Author

Yes! I am running a Ryzen 9 3900x. That's unfortunate. I guess I can wait till I get a new machined built. It will be with a 12900K. I've had no luck upgrading a BIOS on previous machines. I've bricked a couple in the process just to get things running before. I have a lot of projects I work on the windows side that I do not want to lose. I don't want to lose them just because one program doesn't like the way a CPU does things. I have Radarscope running on the other OS and my Laptop. I use it a lot because I live in the Midwest US. So once I get the new machine built I'll go ahead and get SupercellWX running. Thanks for the help and hopefully when I get the new machine built, we won't have this issue.

@dpaulat
Copy link
Owner

dpaulat commented Jul 28, 2024

Sorry to hear about your bad luck updating the BIOS! From what I've been able to gather, I believe this issue is limited to the Linux kernel disabling erroneous functionality (or maybe not exactly...) on the Ryzen 3000 series without the requisite microcode update. I have no reason to believe CPUs outside of the Ryzen 3000 series present an issue. As far as I know your 12900K should work just fine.

@dpaulat
Copy link
Owner

dpaulat commented Jul 28, 2024

You may be able to disable the offending RDRAND functionality by adding nordrand to the Linux boot line according to the following Ars Technica article:
https://arstechnica.com/gadgets/2019/10/how-a-months-old-amd-microcode-bug-destroyed-my-weekend/

image

You may also be able to edit the Linux boot line on the fly from GRUB before applying changes to your default configuration.

The author reports this disables RDRAND, which hopefully will workaround the issue in the OpenSSL library.

@AdenKoperczak
Copy link
Contributor

I would also recommend making sure that the amd64-microcode package is installed and up to date. It should include the same fixes as a BIOS update would, but only for Ubuntu, and without the risk of breaking the board. From my memory, it is usually installed automatically on Ubuntu, but maybe it is outdated or is not installed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants