Closed StrikerMan780 closed 6 years ago
Hi StrikerMan. I am happy to take a look into this issue, perhaps a bug in our registration methods on Linux. Truthfully, Linux users comprise a small part of any gaming community, so sometimes these bugs come up later than those on other operating systems, like Windows, that simply have more users banging against the code.
On an unrelated note, "Getting sick of these kinds of issues" is a rather inappropriate way to ask for assistance. I can assure you that the people maintaining this repository—which, coincidentally, is mostly me—are always trying to incorporate feedback and fix bugs. As you can see from previous issues that were opened, like the Ask to Join bug, it's not always a simple task.
Anyway, I'll check this out. I know your game is not distributed via steam, so I'll check out our generic Linux registration protocols with a test app, and see what I can find.
I am unable to reproduce this issue. Here is the setup.
Inside a Fresh Ubuntu VM
On macOS
Back in VM
Expected result: game launches from a closed state Actual result: game launches from a closed state
If you could perhaps get one of your users to make a video of the game not launching, with Discord console logs, it would be helpful to have repro steps. Otherwise, this may be an issue with the way you're registering your game to the operating system.
Haven't heard an update from this. Please re-open this issue with reproducible steps if the problem persists.
I'm not the one with the problems, so it's up to them to report. But from what I've seen most of the issues are on Arch Linux, Xubuntu and similar distros. Never heard any reports from Ubuntu users.
Still happening. Played with a user on Ubuntu 14.04, 64-bit. Same issue as before, clicking "join" doesn't work. They have to manually launch the app after clicking "join".
The same person also sometimes sees open lobbies as "ended".
The same person also sometimes sees open lobbies as "ended".
That's an interesting piece of info. What I've seen in the past is that this issue stems from a system clock being off. I don't know how direct of contact you have with the user, but could you ask if their date/time settings on their machine are correct?
I had this happen to me on a test PC a while ago and went mad from trying to debug. If your system date/time is not set properly, Discord gets real confused with the timestamps sent in the UpdateActivity()
payload vs. what you've got locally.
Next time I talk to this person, and they get the issue, I'll ask.
For some reason some Linux users (So far, on Xubuntu and Arch Linux), Discord just outright does not launch my app when they join.
I'm constantly being told "when I click join nothing happens", from the linux playerbase.
Getting sick of these kinds of issues.