Meltie

Welcome to the community!

This bug does not exist in M3 (Cataclysm). Appears to exist only in M0 (Vanilla).

Segmentation fault is more then likely coming from the OpenSSL library, cause I've seen this happen on my local machines with version 3.x. Ubuntu 22.04 ships with OpenSSL 3.x by default. More then likely have to reinstall OpenSSL library with version 1.1.x instead of 3.x. Still need to implement proper messages within CMake itself to warn users using OpenSSL 3.x. I would try Ubuntu 21.10 or 20.04 and see if this happens again.

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Normal Changed Sub-Category to Minor

I don't think the owner has had much time to work on this project lately. Might have to wait and see when they have the time to make some more progress on it. The user has been active recently. Just have to see what happens.

Changed Status to Completed Changed Implemented Version to 22.xx (Current Master Branch) Changed Milestone to Unset Changed Priority to New

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Urgent

Changed Status to Confirmed Changed Implemented Version to 22.xx (Current Master Branch) Changed Milestone to Unset Changed Priority to High

Changed Status to Completed Changed Implemented Version to Unset

Changed Status to Completed

Changed Status to Completed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to New Changed Sub-Category to Show Stopper

Changed Status to Completed

Awesome work! Did some research on the tracker and found similar issues with this. Hopefully this gets merged soon.

Changed Status to Duplicate

Welcome to the community Juggernaut! Contribution big or small is always welcomed. Hope to see some of your commits in the near futures.

Changed Status to Confirmed Changed Implemented Version to Unset Changed Milestone to Unset Changed Priority to Normal Changed Main Category to Realm Daemon

How to reproduce this issue as shown above on any client locale. Not restricted to French Locale. Set your RealmZone other then 0. Start your Realm Daemon. Login to any account and view the RealmList window. (If you only have one realm, nothing will appear)

@DaveJ61 A number of reason can cause this problem on Linux Systems. Here's a list that could be the cause but not limited too: Application doesn't have permission to run Application can't run properly do to missing libraries Mismatch between 32-bit and 64-bit libraries (should run, but could cause problems) Missing libraries after upgrading system image Can you look at your journal when trying to run the extractor tools and see what error are being throwing with better details on what is going on. Command to do that is journalctl -x. Linux dumps good logs if you know where to look. I hope this might help.

This looks like the issues I temp fixed some months ago, which wasn't fully fixed. The use of .server shutdown 0 or .server restart 0. This is from the server unable to use the call function from 0. As I recall, I believe this is on all cores. Tips: Try using a high number then 0

Arcemu has something like this already. I recommend you looking on Arcemu side for it.

[quote=Talendrys]Hi Titan, can you try this bug fix and provides feedback ? :-) [url]https://github.com/Warkdev/server/commit/69982e8767d9f65d60e0bc8a2b85cb48f21a8ae3[/url] Thanks.[/quote] Talendrys, this posted fix, is hacky.. Shouldn't call exposed data like that.. Plus is fix was taken from Silverpine Project, which no credits were given.

This is included by default. I can use SOAP in Zero just fine on Unix. Reason of the message, because it's most likely not turned on via config file.

Looks like a tags are changed around.

This is a minor issue.. I'll look into this when I get that chance.. From map updates before Rel19, could have broken the system for LoS and Movement. This is confirmed on both windows and unix systems, where the reading of the tiles are not fully loaded during start-up. As of right now, its [u]not a required function[/u].