[Bug 1140288] New: games:tools/discord: Bug
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288 Bug ID: 1140288 Summary: games:tools/discord: Bug Classification: openSUSE Product: openSUSE.org Version: unspecified Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: 3rd party software Assignee: matthias@mailaender.name Reporter: mestre.cavalheiro@gmail.com QA Contact: bnc-team-screening@forge.provo.novell.com CC: opensuse@dstoecker.de Found By: --- Blocker: --- Recently I've stumbled on a small but frustrating issue. Let me tell the issue and the fix I did. Scenario My computer runs openSUSE Tumbleweed, and there's in official repository a package with Discord client. Very well. My computer is used by my wife and me, each one with their own user account on OS, both of us Discord users, and both of us leave their users logged on OS. Problem When one of us open and log on Discord client and then start a parallel session on OS with other user (multiuser OS and me, this is love), the second user can't open Discord. App complains about that /tmp/discord.sock can't be deleted, so the second user can't start their Discord client. Troubleshooting I got a nice error message, telling me on which file was the error (app.asar). Very well, I opened it on vim and see at line 969 how that /tmp/discord.sock name is generated. I got shocked by seeing that name is hardcoded on that app.asar file! My fix Since I can read coding but can't code myself, I needed to devise a turnaround. I looked on /usr/share/applications/discord.desktop (official openSUSE Tumbleweed package put the file on this place) to see how I could solve my problem, which I did by changing the line Exec=/usr/bin/discord (openSUSE official package put binary on that place) to Exec=/bin/bash -c "mkdir -p /tmp/${USER} ; TMPDIR=/tmp/${USER} /usr/bin/discord" I know that the right stuff would be I have $TMPDIR set for each user instead of using default /tmp, but I think that a massive number of common users (myself included) never bothered with configuring that. And a fair amount of GNU/Linux users today wouldn't devise a fix for that alone and would ditch Discord client because that issue alone. I'm also sending this to Discord dev team, of course, but I think you would like knowing that. Best Regards Luís Cavalheiro -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288
Luís Cavalheiro
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288
Dirk Stoecker
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288#c1
Jimmy Berry
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288
http://bugzilla.opensuse.org/show_bug.cgi?id=1140288#c2
Jon Brightwell
participants (2)
-
bugzilla_noreply@novell.com
-
bugzilla_noreply@suse.com