[SOLVED] Discord app not connecting after last mass rebuild
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Discord app not connecting after last mass rebuild
As the topic says. It had no problems connecting before the rebuild, but afterwards, all I can do is connect using a web browser. Functionally, it works, but I much prefer using the app.
The best I can come up with for this odd behavior is that there was something in the software rebuilds that is blocking the app's connecting to the Discord servers.
Any help would be greatly appreciated. Thanks!
Happy Slacking!
EDIT 1: I'm updating my system now, seeing if that helps...
EDIT 2: No joy. Still needing help! Thanks!
Last edited by 1337_powerslacker; 03-09-2021 at 10:28 AM.
Did you install via a slackbuild? If so, did you also install libc++ ? (If so, maybe recompile that.)
On Slackware 14.2, you need to install several other SBo packages as requirements, but current has all other requirements installed already.
On Slackware current however, I did have to "ln -s /usr/include/locale.h /usr/include/xlocale.h" to get libc++ to compile.
Interesting you should ask that question; that's probably what I should have done myself but didn't, for some unknown reason. There is a missing library, "libffmpeg.so". Even more interestingly, the ffmpeg package does not have a libffmpeg.so.
Which package did you grab? I just grabbed the tar.gz package, unzipped it into my home directory, and fired it up. I can stream to it, do voice chat, etc. No problems
Well, an encouraging update is in order. After updating to the latest version, Discord now connects, no problem. Have no idea what changed, but I certainly won't complain!
I started using Discord way back when the only way to run it on Linux was the Discord-Canary build which was soon abandoned. So I started using the webapp and that seemed wiser anyway in terms of data gathering even though since that time it seems Discord has been largely absolved of such practices. However it appears Microsoft has made an offer of something like 10 Billion dollars to buy out Discord. Whether or not this bid finalizes may be one important issue (consider the running of Skype off the rails for starters) but in any case it appears Discord is looking for a buyout and partly because their monetization has been weak.
Discord has been a remarkably good application and very impressive how something so simple could expand services so easily and solidly but the future may not be so bright. I think it behooves us to start looking around for a replacement this year just in case since it seems highly likely it will change rather drastically to make money and that most likely will be from data mining privacy invasion. Be aware and alert.
I started using Discord way back when the only way to run it on Linux was the Discord-Canary build which was soon abandoned. So I started using the webapp and that seemed wiser anyway in terms of data gathering even though since that time it seems Discord has been largely absolved of such practices. However it appears Microsoft has made an offer of something like 10 Billion dollars to buy out Discord. Whether or not this bid finalizes may be one important issue (consider the running of Skype off the rails for starters) but in any case it appears Discord is looking for a buyout and partly because their monetization has been weak.
Discord has been a remarkably good application and very impressive how something so simple could expand services so easily and solidly but the future may not be so bright. I think it behooves us to start looking around for a replacement this year just in case since it seems highly likely it will change rather drastically to make money and that most likely will be from data mining privacy invasion. Be aware and alert.
Thanks for your input, enorbet! I always appreciate what you have to say. I was made aware that Microsoft has made a bid to buy out Discord. I understand that there is a reason that the monetization scheme has not worked out as well as they had hoped. Technically, I don't think that Discord's functionality would be difficult to replicate, but Discord is what I would call a category killer. It does its job so well, and the name is a household one, that getting a similar app adopted would be a difficult journey, at best. But if it can be accomplished, count me among the first adopters. I have no issue with beta testing, if it gets that far.
Yes Discord does have difficulty monetizing but they apparently accidentally hit something of a gold mine because the number of global active users (not just lamer duck subscribers) has grown vastly beyond all expectations. If Facebook is good for nothing else it has demonstrated that vast wealth exists in data mining vast numbers of people. So who knows what MS will do but it's obvious they are drooling over such prospects.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.