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.

Sign up for GitHub

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

Jump to bottom

IPC Path Problem On Ubuntu 18.04 #36

Closed
PolyMeilex opened this issue Jun 18, 2018 · 1 comment
Closed

IPC Path Problem On Ubuntu 18.04 #36

PolyMeilex opened this issue Jun 18, 2018 · 1 comment

Comments

@PolyMeilex
Copy link

PolyMeilex commented Jun 18, 2018 •
edited
Loading

Problem

So... On Ubuntu 18.04 path to discord ipc is /run/user/1000/snap.discord/discord-ipc-{Id}
instead of /run/user/1000/discord-ipc-{Id} with cause Could not connect error

WorkAround For Ubuntu Users

Hard code new path to every discord-rpc/src/transports/IPC.js file on your computer.
Path is on line 128.

return `${prefix.replace(/\/$/, '')}/snap.discord/discord-ipc-${id}`;
@devsnek
Copy link
Member

devsnek commented Jun 18, 2018

my library matches with discord's reference implementation: https://github.com/discordapp/discord-rpc/blob/7c41a8ec1969b9b4b0c2360c6b632ebd16a92b69/src/connection_unix.cpp#L29

open an issue on that repo if you find the behaviour unsatisfactory.

@devsnek devsnek closed this as completed Jun 18, 2018
This was referenced Oct 22, 2018
Closed
Closed
@FichteFoll FichteFoll mentioned this issue Mar 29, 2019
Closed
FichteFoll added a commit to Snazzah/SublimeDiscordRP that referenced this issue Mar 29, 2019
@FichteFoll
Support Discord installed via snap
9415b09 
According to discordjs/RPC#36, Discord uses a
different path for its pipes when installed as a snap, so we just check
whether that sub-folder exists first.

Fixes #38 (hopefully).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@devsnek @PolyMeilex