Closed graemeg closed 2 years ago
This is one of those bugs that exists just because we didn't test it on freebsd yet, ill see what I can to get it fixed. Alot of us run linux so I know how it feels to have just random shit not be supported for basically no reason.
Thank you very much. As I mentioned, if you need any assistance it testing, I'm more than happy to help where I can.
Just to add. Renaming the DiscordRPC.kt
(so it doesn't compile), commenting two lines in Capes.kt and removing the jarLibs Discord line in build.gradle
(just for good measure)... When I then build the Lambda client, it runs just fine under FreeBSD.
Sadly, discord rpc library is currently not supported for freebsd. Maybe this issue will be solved in future.
I honestly don't care about the DiscordRPC module (I don't need it), but if Lambda could be modified so it doesn't try and load anything Discord related, when the module is disabled, that should fix the issue. At the moment it tries to initialize the discord library, even though the DiscordRPC module is disabled - which doesn't seem right.
Sure, here is the link: https://paste.ee/p/mycnW Log has been attached too.
I build and ran the latest master
and plugins
branches (I did the latter because I saw it had more recent commits). In both cases Lambda fails to start up under FreeBSD. I think lazy loading would be the best way to go.
bump, @graemeg can you please test changes
Apologies for the delay, I've been away on work for a while. I've just tested the lazy-rpc
branch and it seems to work well. :partying_face: As expected (based on what was changed in the branch) the modules still show in the menus (as it should), and now gracefully show a error without crashing the client, when I try and manually enable the Discord module.
Screenshot of the "graceful showing an error":
So yeah, this seems to work perfectly under FreeBSD now. Thank you.
Describe the bug I was trying to use the latest official Lambda release v2.07.01 on my FreeBSD system but it simply crashes MC. As Minecraft with Forge runs fine on my system. I tried Impact, ForgeHax and the Seppuku mods and they work just fine. Seems Lambda is trying to load a native library for Discord integration, even though I have the module disabled. This doesn't seem right.
To Reproduce
Expected behaviour I double checked in the
default.json
file, and I have the DiscordRPC disabled, but it seems Lambda is still trying to load some or other discord library regardless ofenabled: false
setting.Debug info
Additional context / media Let me know if there is anything else you need or debug builds I can test. I don't mind.